User:Kerz/Todo list for kerz: Difference between revisions
Adam Conover (talk | contribs) (Added comments about URLs.) |
(the donate link has invalid code) |
||
| Line 1: | Line 1: | ||
== Not Resolved == | == Not Resolved == | ||
You're missing an equal sign between border and 0 in the Donate code snippet. - Waldo | |||
Add support for displaying images in topics (even if you're not letting files be uploaded, which is sort of an issue here). Being able to show off the looks of Firefox/Thunderbird/etc. in screenshots would be worth more to most prospective users than a page of hardcopy. How does one accurately explain an interface without a picture of it? The picture will complement the article and make it more useful. After all, we say Firefox has a clean interface, but how can one prove it without pictures? | Add support for displaying images in topics (even if you're not letting files be uploaded, which is sort of an issue here). Being able to show off the looks of Firefox/Thunderbird/etc. in screenshots would be worth more to most prospective users than a page of hardcopy. How does one accurately explain an interface without a picture of it? The picture will complement the article and make it more useful. After all, we say Firefox has a clean interface, but how can one prove it without pictures? | ||
Revision as of 22:24, 20 February 2004
Not Resolved
You're missing an equal sign between border and 0 in the Donate code snippet. - Waldo
Add support for displaying images in topics (even if you're not letting files be uploaded, which is sort of an issue here). Being able to show off the looks of Firefox/Thunderbird/etc. in screenshots would be worth more to most prospective users than a page of hardcopy. How does one accurately explain an interface without a picture of it? The picture will complement the article and make it more useful. After all, we say Firefox has a clean interface, but how can one prove it without pictures?
Figure out what to do about overly long titles, whether it's renaming them or changing the back-end coding. Firefox_:_Tips_:_Sorting_Bookmarks_Alphabetically and MozillaZine Knowledge Base:How does one edit a page both overlap the textbox slightly for searching on my 1024x768 screen, and that's a step above the current 800x600 minimum standards. (Note that this appears only on standards-based browsers, I think - IE6 just shifts the textbox&friends down.)
Creating a new page links to MozillaZine Knowledge Base:Help. Editing an existing page links to MozillaZine Knowledge Base:How does one edit a page. Neither of these pages exist. I think they're supposed to describe wiki syntax. -- Anyone can feel free to do this, as I don't think that I know enough about it to actually document it...
This page needs to be deleted: Sunbird_:_FAQs_:_Where
All the Firebird redirect pages to Firefox should be deleted. Afterwards, we can look on the list of orphans and sort things out. Special:Lonelypages
Firebird:issues needs to be deleted. So does Sunbird : FAQs Where can I get Sunbird?
Anchor tags need to be converted to wiki markup or HTML needs to be enabled for these articles (protected):
- MozillaZine Knowledge Base:Dead-end pages
- MozillaZine Knowledge Base:All pages by title
- MozillaZine Knowledge Base:Popular articles
Page titles collide with certain other content, such as top links on page history pages and the search box for pages with long titles. Click the page history of this page for an example of the former, and Ff : Issues : Installing ... Extension for an example of the latter.
URLs are long. (hao2lian: techniques could be stolen from how MovableType does article links).
- http://kb.mozillazine.org/index.phtml?title=Misc:_Get_Involved is what most links use.
- http://kb.mozillazine.org/?title=Misc:_Get_Involved works too, and it would be nice if it was the "default".
- http://kb.mozillazine.org/Misc/Get_Involved would be really nice.
- kerz -- look at the way MediaWiki does it. I think the easiest solution would be to make each category a mini-namespace of sorts. We could, by the way, just use forward slashes in links -- linking to Firefox/Issues/Blahblah instead of Firefox : Issues : Blah blah. (I brought this issue up in Talk:Rules, I believe). Using this method of naming pages would get us much closer to the third (ideal) example you've posted, and if we figure out MediaWiki's technique as well we'll have it. (Hope you don't mind me commenting directly on your todo list.) Adam Conover 11:30, 19 Feb 2004 (PST)
Can we have a new class for table cells to indicate "neutral"? The Comparison table looks half finished with lots of cells having a white background and a few having red / green backgrounds. Jgraham
Resolved
Would is be possible to move the left sidebar with the MediaWiki links over to the right side to join (above) the standard MozillaZine sidebars, in order to save space? - Done, I also moved the title up above the HR.
Misc: Get Involved still has the left sidebar, and it overlaps content. It can also be moved to Misc : Get Involved (correct spacing format). --Sidebar mysteriously fixed overnight.
I need someone to format the rules nicely, and add anything they think is missing. If you can do this, it would be great! Done! Thanks guys.
The editing-page page still sucks at 800x600, because the textarea goes behind the right sidebar. ---hao2lian: fixed, although you probably already know
Be nice to Google: support.mozillazine.org should redirect to kb.mozillazine.org instead of being an alias. -- Done.
Hmm, maybe this list should be in MozillaZine Knowledge Base:Bug reports, which the "Bug reports" link in the left sidebar links to. -- Nah, it's fine here.
The "gnu free documentation license" link at the bottom of most pages is broken. -- Fixed, :).
If you're not logged in and click a link to a page that doesn't exist, it says "Login required to edit" in a huge font. it should say "This page hasn't been created yet", like it does if you're logged in, and *below that* say "Want to create this page? Log in first." -- I've changed the wording slightly. There's no way for it to know if the page doesn't exist or not once it is generating, so I've made the message more generic.
Make it work in 800x600. Support Home doesn't work because of the PREs, and editing-page pages don't work because of the textareas. - No more PREs afaik.
Edit page disclaimer has a rogue "<": -- Taken care of.
