Editing RimWorld Wiki:Admin noticeboard
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 25: | Line 25: | ||
=== Templates === | === Templates === | ||
| − | The idea, especially if we in the long-term move over to the [https://www.mediawiki.org/wiki/Extension:Cargo Cargo database system], is that each ''thing'' or ''category'' has its own template, and of course its each page. That is partly why I am opposed to super-templates that try to deal with everything. Another reason is that it makes it difficult for regular users to fix and update data in the pages. Even worse if they try to fix a template. Therefore, I have now created the first draft of such a template, namely the [[:Template:Infobox | + | The idea, especially if we in the long-term move over to the [https://www.mediawiki.org/wiki/Extension:Cargo Cargo database system], is that each ''thing'' or ''category'' has its own template, and of course its each page. That is partly why I am opposed to super-templates that try to deal with everything. Another reason is that it makes it difficult for regular users to fix and update data in the pages. Even worse if they try to fix a template. Therefore, I have now created the first draft of such a template, namely the [[:Template:Infobox animal]] template. |
The main difficulty is likely going to be to make sure we have all the variables we need, and that they are sensibly defined. Unlike in SWM, where each such definition needs its own property page, this is done in the template in Cargo. If you hit Edit on that page, you see how it works in roughly the top half of the template. First the database table is defined. Then the storage of data (from pages using the template) is defined. Currently the latter half is a mess and needs a near-total rewrite, because I used a template I wrote on Pillars of Eternity. We have no CSS for the infoboxes or classes used yet, and ought to first come up with a design choice for what the infoboxes should look like. [https://pillarsofeternity.gamepedia.com/Template:Infobox_bestiary This is] how this one happens to look on the Pillars of Eternity wiki, but we can of course change things a lot here, and not just in terms of colours. | The main difficulty is likely going to be to make sure we have all the variables we need, and that they are sensibly defined. Unlike in SWM, where each such definition needs its own property page, this is done in the template in Cargo. If you hit Edit on that page, you see how it works in roughly the top half of the template. First the database table is defined. Then the storage of data (from pages using the template) is defined. Currently the latter half is a mess and needs a near-total rewrite, because I used a template I wrote on Pillars of Eternity. We have no CSS for the infoboxes or classes used yet, and ought to first come up with a design choice for what the infoboxes should look like. [https://pillarsofeternity.gamepedia.com/Template:Infobox_bestiary This is] how this one happens to look on the Pillars of Eternity wiki, but we can of course change things a lot here, and not just in terms of colours. | ||