Community Wishlist Survey 2015/Templates

Inserting templates in PDF and Books

Since... well, don't know since when, books and PDFs are not rendering information inside templates. As lots of information is inside templates (also happens with tables) all of this is not rendered when you download the file in PDF. -Theklan (talk) 22:18, 9 November 2015 (UTC)[reply]

I think that it comes from the templates, some of them contain the "class=noprint" because the local community decided it.

But if you want to generate some books with their recurrent templates (eg: disclaimer), dynamically from its table of content, I recommend you to export my Lua module. JackPotte (talk) 23:11, 9 November 2015 (UTC)[reply]

Endorsed Taha (talk) 00:18, 10 November 2015 (UTC)[reply]

Endorsed @JackPotte, the problem it's not the "class=noprint", the current pdf engine is especially buggy in rendering table and dont show template containing table (like infobox). On november 2014 a message from Erik Moeller on wikitech ambassors mailing list describe the current status and said that is not a high priority project to fix them.--Moroboshi (talk) 07:30, 10 November 2015 (UTC)[reply]

Endorsed--Bramfab (talk) 18:05, 11 November 2015 (UTC)[reply]

As the author of the PDF backend, I can confirm that the issue is not with templates, it is with tables. We have a large number of very complicated tables in our projects, and it is a non-trivial task to figure out how to lay them out in LaTeX. Basic patch here: https://gerrit.wikimedia.org/r/107587 -- but it would break more pages than it would help at this point. Help wanted, of course! But it would be even better to write an HTML-based PDF backend for mw:OCG and bypass LaTeX altogether. Hopefully we could use phantomjs 2.0 and not lose the nice support for Indic languages that we currently have. Cscott (talk) 18:39, 11 November 2015 (UTC)[reply]

A powerful, handy TemplateTiger

Currently, TemplateTiger feeds on dumps and is very unhandy, if you are dealing with high-use templates. Therefore please, oh WMF, please provide a tiger which prowls through templates live and which can be piloted as easy as catscan (when it's available). → «« Man77 »» ^[de] 18:40, 10 November 2015 (UTC)[reply]

Endorsed Having a live version would definitely be useful. Other things that would be useful for maintenance are detection of invalid parameters (I maintain a similar tool that provides this for frwiki, but unfortunately, I don't have resources and time to run it for any other wiki). Orlodrim (talk) 19:04, 10 November 2015 (UTC)[reply]

Endorsed —MisterSynergy (talk) 21:07, 10 November 2015 (UTC)[reply]

Central Global Repository for Templates, Lua modules, and Gadgets

Tracked in Phabricator:
Task T41610

Tracked in Phabricator:
Task T1238

Tracked in Phabricator:
Task T91162

We could use a single location where to keep templates, Lua modules, and Gadgets that are used on all the wikipedia projects. Just like images from commons can be used on other projects, code from such site would be visible to all the projects. The current system of 100's of out of sync copies of the same templates or Lua modules occasionally synchronized with the original is very hard to maintain. --Jarekt (talk) 20:06, 10 November 2015 (UTC)[reply]

Endorsed --Jarekt (talk) 20:06, 10 November 2015 (UTC)[reply]
Endorsed. See also mw:Extension:Gadgets/Roadmap. Helder 20:53, 10 November 2015 (UTC)[reply]
Endorsed —MisterSynergy (talk) 21:10, 10 November 2015 (UTC)[reply]
Endorsed Danmichaelo (talk) 21:25, 10 November 2015 (UTC)[reply]
Endorsed A best-of-breed centralised Lua toolkit for Wikidata is particularly needed. Jheald (talk) 22:53, 10 November 2015 (UTC)[reply]
Endorsed--Shizhao (talk) 02:32, 11 November 2015 (UTC)[reply]
Endorsed Amir (talk) 10:13, 11 November 2015 (UTC)[reply]
Endorsed Having spent entirely too much time lately shuffling templates, template docs, and modules from one project to another as I tried to use them and discovered they didn't exist locally, I say an emphatic "yes" to this! Fluffernutter (talk) 17:30, 11 November 2015 (UTC)[reply]
I think that phab:T91162 ("Shadow namespaces") is also related, since it proposes a concrete mechanism for implementing a global repository. Cscott (talk) 19:31, 11 November 2015 (UTC)[reply]
Endorsed It would redeem smaller wiki-projects --Usien6 (talk) 19:47, 13 November 2015 (UTC)[reply]
Endorsed. --Stegop (talk) 19:58, 13 November 2015 (UTC)[reply]
Endorsed Very nice idea! --Sampayu (talk) 20:18, 14 November 2015 (UTC)[reply]
Endorsed While one central "Global Repository" would be valuable, even better is if we can transclude a generic page from any sister-wiki. With the recent development of SUL, the recent development of special translation support, and the current work on cross-wiki notifications, the ability to "locally-write" information for cross-wiki work and have it "locally displayed" on another wiki opens revolutionary opportunities. One of the most immediate Use Cases would be for the WMF to simply post Project announcements (and this Wishlist survey!) on a WMF-local announcement page. The page(s) would be displayed in sections at EnWiki Village Pump elsewhere. Local wikis could then apply the new translation features. This functionality is very valuable to the Community, and it's a huge boon for the plans at WMF_product_development_process. Alsee (talk) 12:13, 15 November 2015 (UTC)[reply]
Endorsed Some valuable templates are only available in few projects. Having a central repo for templates would make all the projects benefit of all templates. Moreover, this would remove all potential duplicates of code. That said, the migration to a central repo should be done with care (converging similar templates to a unique one, removing all unneeded templates, ...). Bibi6 (talk) 15:53, 15 November 2015 (UTC)[reply]
Endorsed Please, please, please. With proper code review (ideally, a git bridge with gerrit code-review on top of it and a way to test candidate changesets directly on-wiki) — Arkanosis ^✉ 16:30, 18 November 2015 (UTC)[reply]
Endorsed 4nn1l2 (talk) 00:09, 19 November 2015 (UTC)[reply]
Endorsed --Jane023 (talk) 12:55, 19 November 2015 (UTC)[reply]
Endorsed --Susannaanas (talk) 16:26, 20 November 2015 (UTC)[reply]
Endorsed This would be really useful! Thanks. Mike Peel (talk) 18:50, 20 November 2015 (UTC)[reply]
Endorsed YuviPanda (talk) 09:53, 22 November 2015 (UTC)[reply]
Endorsed -- Stephan Kulla (talk) 14:40, 22 November 2015 (UTC)[reply]
Endorsed --Voll (talk) 15:52, 27 November 2015 (UTC)[reply]
Endorsed as per my proposal. This would eliminate duplication of work and will allow multilingual support. A great opportunity to bring together the relatively much smaller community of people who understand the templates, people who will direct their energy in creating new, easier better templates, rather than duplicating / updating templates from other wikipedias. --FocalPoint (talk) 21:15, 28 November 2015 (UTC)[reply]