Per Einar Ellefsen wrote:
Since it seems like the place I'm most likely to be able to help, I'll try looking at the content.
So, what I need to do is:
- add descriptions all over
- check it all for HTML/CSS compliancy
- maybe work on some extra content for the front page (the introduction allan mentioned)
Ok, I'll try to get it at as soon as possible.. (not before wednesday)
Fantastic! If you need any help just shout my way :)
Couple of questions: - HTML and CSS validity tools (that work with Windows / Cygwin) ?
Not being an active HTML coder I hardly know of any for linux :) I think if you head to w3c.org you will find the right pointers. Otherwise google.com should be of a great help. On linux I use sgmlcheck.
Do let us know if you find some good tools and we document this for the future use.
- which sections should I look most carefully at? (for the doc that is)
OK, it goes like this:
1. All documents be they .html or .pod need to have description. for .pod files this is =head1 Description, where the first paragraph is being used as an abstract on the index.html pages. And for .html files this is a <meta name="Description" ...> see the existing examples.
2. need to check HTML/CSS validity.
- since most of the HTML is autogenerated if the templates and the pod2html converter are clean then the HTML will be created prop. One exception is unescaped unsafe HTML chars in POD (like & and <, >). I think I've shoot off most of these, but it's possible that some have stayed.
- there are a few HTML source docs and these should be checked one by one
- the output of search needs to be checked too and if something is wrong the search/search.tt is to be fixed.
Ideally if you find a tool that can work recursively through the whole tree, this will be the perfect thing.
3. Content:
/docs/1.0 - has been reviewed a lot so I'd look here at the very end
/docs/2.0 - is very new and probably very broken, but it doesn't matter, it's in very early alpha
but do go through the rest of the content which is just a few pages
notice that .pods under /maillist and /stories are autogenerated from the template.
I think that covers it all.
Thanks!
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
