Gentoo Wiki talk:Article blueprints

From Gentoo Wiki
Jump to:navigation Jump to:search
Note
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using ~~~~:
A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC)
: A reply [[User:Sally|Sally]] 05:37, 15 July 2024 (UTC)
:: Your reply ~~~~

"Variables" section

Talk status
This discussion is done as of 2024-03-31.

I'm tempted to remove the "Variables" section, as Gentoo_Wiki:Article_Blueprints/Variables and Template:Gentoo_variable seem empty. Is there any more information on this ? I can't see where it is used... Ris (talk) 19:19, 16 October 2021 (UTC)

I have removed the reference to Gentoo_Wiki:Article_Blueprints/Variables. I have also requested to have that page deleted and I have opened a new discussion on its talk page. Waldo Lemmer (talk) 13:13, 31 March 2024 (UTC)

Deprecated calls

Talk status
This discussion is done as of 2024-05-01.

I can't find an alternative to the deprecated source tag. The combination of nowiki and pre does not work with nested pre. Nested pre is required by Template:RootCmd. --Lars Hint (talk) 14:02, 22 April 2024 (UTC)

Found it, syntaxhighlight works perfectly. --Lars Hint (talk)
You beat me to it. I found it by starting at the implementation of {{CodeBox}} and going deeper and deeper. — Waldo Lemmer 14:23, 22 April 2024 (UTC)
Thanks for trying to help. :) --Lars Hint (talk) 14:38, 22 April 2024 (UTC)
Maybe we should use {{CodeBox}} with <nowiki> instead:
CODE
{{ProductPage|Brand (e.g. ASRock)|motherboards|Computer architecture (e.g. AMD64)}}
{{InfoBox stack
|{{InfoBox homepage|https://url/to/hardware/manufacturer's/product/homepage|header=true}}
|{{InfoBox wikipedia|HardwareArticleOnWikipedia}}
}}
[[Category:AMD64]]
Nevermind. {{CodeBox}} doesn't parse angled brackets correctly because it uses {{#tag}}. See Template:PreBox/sandbox.
Waldo Lemmer 05:18, 1 May 2024 (UTC)

Row ID

Talk status
This discussion is still ongoing.

Is there a specific reason why row identifiers (e.g. id="cpu") are present in the table? Most contributors don't like it, so they don't use it. --Lars Hint (talk) 14:43, 22 April 2024 (UTC)

Optional sections

Talk status
This discussion is still ongoing.

Some blueprints use the following format:

(optional section blah blah)

And some use another one:

<!-- optional section blah blah -->

Which one should be preferred? --Lars Hint (talk) 15:30, 22 April 2024 (UTC)

I'd say the former, so it's easier for contributors to notice that they forgot to populate (or remove) a section. It acts as a kind of to-do list where items can't be ignored like they can with comments.
By the way, I think blueprints should be implemented using Handbook-like variables, parts and blocks. Seeing the same format duplicated across eight pages hurts the deepest parts of my soul. I can't do it in the near future since I already have a bunch of other stuff to do, but it might be a fun learning experience for someone else to try.
Waldo Lemmer 18:45, 28 April 2024 (UTC)
I don't know much about the templates, but wouldn't the Handbook-like variables make it impossible to implement the code rendering?
FILE Template:LaptopBlueprint (pseudocode)
if (code is true) {
 <syntax>
}

raw template data

if (code is true) {
 </syntax>
}
If "raw template data" is a call to another template, then syntax will render the call, but not the result. --Lars Hint (talk) 20:14, 1 May 2024 (UTC)
I don't know how everything is executed, syntax probably takes effect after the "raw template data" is executed, in which case everything should work. However, what about the blueprint examples? What will they render in "Edit"? --Lars Hint (talk) 20:27, 1 May 2024 (UTC)
Okay, maybe that's not a good idea. An alternative could be a massive template that takes all information as arguments and has the placeholder text as default arguments. The examples would then transclude this template and pass the example information as arguments. Editors would then use subst: with only one argument (the name of the blueprint) to paste the skeleton, and then they would replace the placeholder text (which were the default arguments) by hand. More experienced editors could pass the arguments from the get go.
Waldo Lemmer 04:19, 2 May 2024 (UTC)