FlightGear wiki:Village pump
Welcome to the Village Pump. This page is used to discuss the technical issues, operations and guidelines of the FlightGear wiki.
Please add new topics to the bottom of this page.
Old discussions should be moved to a FlightGear wiki:Village pump/Archive YEAR. These discussions can then be moved to a relevant talk page if appropriate.
New Portal: Embedded or Hardware (02/2020)
Suggestion: Dedicated portal for articles relating to embedded/hardware topics (which would be in line with numerous threads on the forum, as well as existing articles on the wiki). - Hooray (talk) 11:59, 17 February 2020 (EST)
- That is slightly less complicated than you might think. What you would do is to create a new page with the prefix
Portal:and a suitable name, say for example Portal:Hardware development, Portal:Cockpit hardware or Portal:DIY cockpit hardware, or maybe Portal:Hardware if you would also like to see commercial hardware there, and then copy and modify the content from a similar portal.
- Hint: There is actually not a portal namespace, it is just a prefix. The portal pages are actually in the main namespaces, and thus function just like any other article page on the wiki.
- Though I think your Portal:Embedded might be more diffuse than Portal:Hardware for people that do not know what embedded software
is, I have still added it to the main page and added Category:Portals to it. It will get more use if people can find it. :-P
Use as few categories as possible
Always use as few categories as possible. Categories are a place in a structure rather than tags. Putting each page in a lot of categories will put a lot of of pages in each category. There is in particular no need to put a page in both a category and then in each category above that category.
Please see advice in Help:Your first article#Categories and maybe also Help:categories.
—Johan G (Talk | contribs) 13:04, 15 March 2020 (EDT)
Meta template and templates for commonly used logotypes and icons
Through a placeholder page (ugh!) and a edit summary Hooray suggested making a template for commonly used logotypes.
|
placeholder/stub for all sorts of wiki related logos that may need to be updated over time, but that are referenced on multiple pages - so that we don't need to edit each and every page here. |
|
|
|
@Johan: could use your help with this, unless I can write the heuristics in Php or JavaScript ;-) — Hooray, 11 April 2020, 08:04
|
|
I would guess you also intend it to be used for icons as well, for example the ready icons? Logotype/icon templates might not be a bad idea. Less typing is almost always good.
{{logo}} should probably be a meta template, a template used by other templates in this case by logotype templates. Meta templates are pretty common on MediaWiki wikis.
Essentially, there could be a set of logotype and icon templates, for example {{Compositor logo}}, {{FGInterface logo}}, {{Air refueling ready icon}} etc, that pass the image for the logotype, an alt text (for accessibility and when the image is not shown, for example due to browser settings) and a link to a relevant wiki page to {{logo}}. Possibly also optional parameters like other sizes etc. The meta template would then add the boilerplate stuff around that and set the size.
I would advise that having a suffix indicating the type of template, for example logo, icon like mentioned above or navigation (for navigation boxes), in essence having less ambiguous names, is generally a good idea.
I should mention that I am generally against placeholder pages.