v50 Steam/Premium information for editors
- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.
Editing Dwarf Fortress Wiki talk:Article Consolidation
Jump to navigation
Jump to search
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
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 42: | Line 42: | ||
::Details details ;). Yes, it should. Let's wait for some more comments on this. [[User:Mason11987|Mason]] <sup>([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]])</sup> 01:15, 27 April 2010 (UTC) | ::Details details ;). Yes, it should. Let's wait for some more comments on this. [[User:Mason11987|Mason]] <sup>([[User talk:Mason11987|T]]-[[Special:Contributions/Mason11987|C]])</sup> 01:15, 27 April 2010 (UTC) | ||
:I'm not sold on the value of individual pages. Particularly when most of them aren't and won't ever be filled with anything but raws info, except the ones people have helpfully added spiffy pictures to. Most of the arguments '''against''' tables here are arguments against ugly table arrangements, not tables in general. If we put them in a table -- a '''good table''' with relevant information as one mineral per row, properly fast-forwarded to by the search -- it will be every bit as relevant and informative as the individual article without the search spam. Having both essentially doubles the work and threatens to make the articles go out of sync with each other. --[[User:Corona688|Corona688]] 06:43, 27 April 2010 (UTC) | :I'm not sold on the value of individual pages. Particularly when most of them aren't and won't ever be filled with anything but raws info, except the ones people have helpfully added spiffy pictures to. Most of the arguments '''against''' tables here are arguments against ugly table arrangements, not tables in general. If we put them in a table -- a '''good table''' with relevant information as one mineral per row, properly fast-forwarded to by the search -- it will be every bit as relevant and informative as the individual article without the search spam. Having both essentially doubles the work and threatens to make the articles go out of sync with each other. --[[User:Corona688|Corona688]] 06:43, 27 April 2010 (UTC) | ||
− | |||
::Hard to get them out of sync if the data's pulled from the raws, I'd say. As far as I can see from the stone lookup template the raws in question are being stored somewhere centrally anyhow, so they should always be equal. -- [[User:Oddtwang of Dork|Oddtwang of Dork]] 09:35, 27 April 2010 (UTC) | ::Hard to get them out of sync if the data's pulled from the raws, I'd say. As far as I can see from the stone lookup template the raws in question are being stored somewhere centrally anyhow, so they should always be equal. -- [[User:Oddtwang of Dork|Oddtwang of Dork]] 09:35, 27 April 2010 (UTC) | ||
:::If the raws are being stored centrally, there's even less reason to have the separate pages -- they perform no function but repeating data stored elsewhere. --[[User:Corona688|Corona688]] 14:01, 27 April 2010 (UTC) | :::If the raws are being stored centrally, there's even less reason to have the separate pages -- they perform no function but repeating data stored elsewhere. --[[User:Corona688|Corona688]] 14:01, 27 April 2010 (UTC) |