User:SOTO/Forum Archive/The Panopticon/@comment-24894325-20161219001033/@comment-1432718-20161219012946: Difference between revisions
(Bot: Automated import of articles) |
m (Bot: Automated text replacement (-'''User:(SOTO/Forum Archive)/(.*?)/\@comment-([\d\.]+)-(\d+)/\@comment-([\d\.]+)-(\d+)'''\n([\s\S]*)\[\[Category:SOTO archive posts\]\] +\7\2/\4-\3/\6-\5)) |
||
| Line 1: | Line 1: | ||
<div class="quote"> | <div class="quote"> | ||
SOTO wrote: | SOTO wrote: | ||
| Line 9: | Line 8: | ||
</div> | </div> | ||
What we '''always''' have to keep in mind is that we wiki editors are probably more familiar with the DWU and its publications than the average wiki reader, and I think separating all the ranges into their own navboxes would leave unfamiliar users unable to find what they want. So I'd prefer a different solution than complete separation, though I don't (yet?) have anything to suggest. | What we '''always''' have to keep in mind is that we wiki editors are probably more familiar with the DWU and its publications than the average wiki reader, and I think separating all the ranges into their own navboxes would leave unfamiliar users unable to find what they want. So I'd prefer a different solution than complete separation, though I don't (yet?) have anything to suggest. | ||
<noinclude>[[Category:SOTO archive posts]]</noinclude> | <noinclude>[[Category:SOTO archive posts|The Panopticon/20161219001033-24894325/20161219012946-1432718]]</noinclude> | ||
Latest revision as of 22:31, 27 April 2023
SOTO wrote: BF is always really unclear about ranges, and changes categorisations all the time. It's all very confusing.
That is certainly true, as I've discovered when working with the BF credits project.
We really need to pick something that's consistent and that will work for us in the years to come. Would it make sense to make a template for every new series Doctor featured?
What we always have to keep in mind is that we wiki editors are probably more familiar with the DWU and its publications than the average wiki reader, and I think separating all the ranges into their own navboxes would leave unfamiliar users unable to find what they want. So I'd prefer a different solution than complete separation, though I don't (yet?) have anything to suggest.
