View source for User:DoggoBit/Sandbox/Infobox board

<includeonly>{{User:DoggoBit/Sandbox/Infobox
  |clip={{{clip|}}}
  |title={{{title|}}}
  |image={{{image|}}}
  |content={{User:DoggoBit/Sandbox/Infobox board/Content
    |manufacturer={{{manufacturer|}}}
    |architecture={{{architecture|}}}
    |support-status={{{support-status|}}}
    |soc={{{soc|}}}
  }}
  |footer={{{footer|}}}
}}</includeonly><noinclude>
{{User:DoggoBit/Sandbox/Infobox board
  |title=Raspberry Pi 5
  |image=Raspberry_Pi_5,_8_GB_RAM.jpg
  |manufacturer=Raspberry Pi Foundation
  |architecture=AArch64
  |support-status=Limited community efforts
  |soc=BCM2712
  |footer=[[NixOS on ARM|<span style="color: white;">Development Board</span>]]
}}
An infobox to be used on board-specific pages, e.g. [[NixOS_on_ARM/Raspberry_Pi_5]].
==Usage==
<pre>
{{Infobox board
  |title=Raspberry Pi 5
  |image=Raspberry_Pi_5,_8_GB_RAM.jpg
  |manufacturer=Raspberry Pi Foundation
  |architecture=AArch64
  |support-status=Limited community efforts
  |soc=BCM2712
  |footer=[[NixOS on ARM|Development Board]]
}}
</pre>

==Implementation details==

The ''"logical"'' elements of the box are also captured via CSS classes, so any styles could be incorporated into the website's [[MediaWiki:common.css]]. Each element has two classes: <code>nix-wiki</code> and <code>infobox-something</code>.

All CSS properties are implemented via variables, so style inheritance would apply if the styles would be moved into the global CSS. I.e. surrounding the template in a div that overrides any one of the values will propagate the changes. For example:

<pre>
<div style="--infobox-color: green;">
  {{Infobox board
    ...
  }}
</div>
</pre>

In the meantime, the CSS variables can also be set via MediaWiki variables, so we could easily implement something like:

<pre>
{{Infobox board
  |color=green
  ...
}}
</pre>

I would ''personally'' love to top-align the content cells, so that we don't get the staggered lines on multi-line cells, but that would be a lot of manual work now, and would result in an overly complicated template. However, it should be a common.css one-liner.