wanted A bit of help for custom template

[Kesta]

Hello !

 

I'm trying to put together a template for my user-made guide for FO4. The objective is essentially to make it easy to maintain for me, and ensure visual-consistency between every listed mod.

 

Basically, I need a header for the mod (its name with a link to download it), its version and author, and the list of files to download on the mod page.

 

That part was easy. However, I'd like to split the list between the 5 different sections you can find on nexus mods (fyi : main, update, optional, miscellaneous, older). To get one sorted properly, it's okay. However, if there is files to download in two different sections, things get tricky to put in a template, and I'd like a bit of help with that.

 

 

Here is what I've done so far : https://wiki.step-project.com/index.php?title=User:Kesta/CustomFO4Mod

 

Now, since the number of potential categories is predefined, I'm pretty sure I could do a big ugly thing like this :

[spoiler=includeonly code]

<div><span>[{{{2}}} {{{1}}}] - {{{3}}} - by {{{4}}}</span><br>
<span>'''Files''' : 
{{#switch: {{{5}}}
| MAIN = MAIN - {{#arraymap:{{{6|}}}|;|%|''%''}}
| UPDT = UPDATE - {{#arraymap:{{{6|}}}|;|%|''%''|}}
| OPT = OPTIONAL - {{#arraymap:{{{6|}}}|;|%|''%''|}}
| MISC = MISCELLANEOUS - {{#arraymap:{{{6|}}}|;|%|''%''|}}
| OLD = OLD VERSIONS - {{#arraymap:{{{6|}}}|;|%|''%''|}}
| #default = ''{{{6}}}''
}}
{{#switch: {{{7}}}
| MAIN = MAIN - {{#arraymap:{{{8|}}}|;|%|''%''}}
| UPDT = UPDATE - {{#arraymap:{{{8|}}}|;|%|''%''|}}
| OPT = OPTIONAL - {{#arraymap:{{{8|}}}|;|%|''%''|}}
| MISC = MISCELLANEOUS - {{#arraymap:{{{8|}}}|;|%|''%''|}}
| OLD = OLD VERSIONS - {{#arraymap:{{{8|}}}|;|%|''%''|}}
| #default = ''{{{8}}}''
}}
{{#switch: {{{9}}}
| MAIN = MAIN - {{#arraymap:{{{10|}}}|;|%|''%''}}
| UPDT = UPDATE - {{#arraymap:{{{10|}}}|;|%|''%''|}}
| OPT = OPTIONAL - {{#arraymap:{{{10|}}}|;|%|''%''|}}
| MISC = MISCELLANEOUS - {{#arraymap:{{{10|}}}|;|%|''%''|}}
| OLD = OLD VERSIONS - {{#arraymap:{{{10|}}}|;|%|''%''|}}
| #default = ''{{{10}}}''
}}
{{#switch: {{{11}}}
| MAIN = MAIN - {{#arraymap:{{{12|}}}|;|%|''%''}}
| UPDT = UPDATE - {{#arraymap:{{{12|}}}|;|%|''%''|}}
| OPT = OPTIONAL - {{#arraymap:{{{12|}}}|;|%|''%''|}}
| MISC = MISCELLANEOUS - {{#arraymap:{{{12|}}}|;|%|''%''|}}
| OLD = OLD VERSIONS - {{#arraymap:{{{12|}}}|;|%|''%''|}}
| #default = ''{{{12}}}''
}}
{{#switch: {{{13}}}
| MAIN = MAIN - {{#arraymap:{{{14|}}}|;|%|''%''}}
| UPDT = UPDATE - {{#arraymap:{{{14|}}}|;|%|''%''|}}
| OPT = OPTIONAL - {{#arraymap:{{{14|}}}|;|%|''%''|}}
| MISC = MISCELLANEOUS - {{#arraymap:{{{14|}}}|;|%|''%''|}}
| OLD = OLD VERSIONS - {{#arraymap:{{{14|}}}|;|%|''%''|}}
| #default = ''{{{14}}}''
}}</span></div>
 

 

I don't know for wiki content editor, but as a programmer, this really hurt my eyes. Since I know there is some pretty skilled wiki editor arround, I figured I could just ask for advices :)

 

 

The final objective is to be able to write something like this ;

[spoiler=Wiki content]

{{User:Kesta/CustomFO4Mod
|A mod name|A mod URL|VersionNumber|Author name(s)
|MAIN|File 1; File 1 bis
|MISC|File 18; File abcd}}
 

{{User:Kesta/CustomFO4Mod
|Another mod|its URL|OtherVersionNumber|The other author
|OPT|Patch for XYZ}}

And have everything layed out nicely.

[DoubleYou]

It will be easier if you label each parameter. What you want is rather simple. You will need to use an array for the filenames.

[Kesta]

Excellent, nor sure why I didn't think of that. Array are completely new to me, maybe I was a bit shy with it. Working like a charm.

[darkside]

Can you steal template from Neo? I actually like SRLE template. Plan to setup follow your guide soon.

[Kesta]

Neo isn't using a template, he's writing everything down. But I could somehow manage to have a similar look now that the template itself is set. (That's the purpose of a template, being able to alter the look of the whole guide just by editing a few lines).

 

But I don't think it'll end-up looking like SR:LE. Available tools and global modding capabilities are expanding, and I expect some part of mod management to be far more complex with FO4 than it used to be with Skyrim (1st reason being MO2 not managing .BA2 as MO1 did with .bsa, and the new ;ba2 caching), so using "old" layout might present some clarity issues at one point.

Edited December 4, 2015 by Kesta

[TechAngel85]

  On 12/4/2015 at 11:02 PM, Kesta said:

Neo isn't using a template, he's writing everything down. But I could somehow manage to have a similar look now that the template itself is set. (That's the purpose of a template, being able to alter the look of the whole guide just by editing a few lines).

I akin the wiki templates to the old HTML includes with SSI. Edit one file (aka page), and it changes it throughout the entire site. Of course if anyone wasn't designing web sites back in the days when SSI was very popular (think pre-WordPress), this would be just as foreign as the wiki templates.

[z929669]

It is very simple to create/use various look/feel templates, but it is almost just as simple to use standard look/feel if it works (as neo does). Templates are useful for article elements that use a specific format that employs wiki code reuse. Normal text and wiki code lists and such are not good candidates for handling via template. Repetitive custom layout and/or look/feel deviations are.

 

For example, it is not necessary to convert the followign to template:

some information:
* bulleted list

However, it may be convenient to use a template for the following:

some information:
: {{Fs|0.9em|{{Fc|white|'''Exceptions to said info'''}}}} 
*bulleted list