On Jun 7, 2011, at 8:20 AM, Igor Galić wrote: > You *could* use the web interface: > > https://cms.apache.org/ -- but right now, that has the old HTML site in there. > We should probably change that. > > I pre-build the changes on my local box. > To do this I check out the cms: > > svn co https://svn.apache.org/repos/infra/websites/cms/build cms > > You'll need the python-markdown version of markdown installed. > Given that in Ubuntu it's called /usr/bin/markdown_py - I *symlink* it to > /usr/local/bin > Where, by default, it's expected to be anyway. > > There are a number of CPAN modules that you'll need: > SVN::Client, SVN::Wc > LWP::Simple > XML::Atom > XML::RSS::Parser::Lite > > Then, to build: > > i.galic@panic ~/Projects/asf/cms (svn)-[build:787652] % export > MARKDOWN_SOCKET=$PWD/logs/mardownd.pipe > i.galic@panic ~/Projects/asf/cms (svn)-[build:787652] % python markdownd.py > i.galic@panic ~/Projects/asf/cms (svn)-[build:787652] % .. > i.galic@panic ~/Projects/asf % $PWD/cms/build_site.pl --source-base ats-cms > --target-base ats-cms-docroot > > Can't open cgi-bin [skipping]: No such file or directory at > /home/i.galic/Projects/asf/cms/build_site.pl line 57. > i.galic@panic ~/Projects/asf
Wow. Sounds like a project to tackle when I get a lot smarter. I hope this both sounds a lot less daunting for others, and something like this is rarely needed. I'll download the html and make some modifications to the pages. >> Do the site pages (home and download) have to have the same CSS as >> the documentation? > > Probably not - I'm pretty sure there's a simple and sane way to give > them a different CSS. But I would suggest to really stick to one > design.. It's kinda confusing - or irritating when it switches. > > Witness: http://httpd.apache.org/ vs > http://httpd.apache.org/docs/trunk/mod/core.html#adddefaultcharset The general look and feed doesn't have to change. IMO, the current staged front page does not look good. The projects that have front pages that I think look decent (Cassandra (http://cassandra.apache.org/), Memcached (http://memcached.org/), Wordpress (http://wordpress.org/), Redhat (http://www.redhat.com/), Miro (http://www.getmiro.com/), Pidgim (http://www.pidgin.im/), etc) have mixed grids, with 1-3 columns per 'row.' I'm ok with not using the current live front page design -- but, it really should be somewhat purposely designed -- the current staged front page gives me a feeling it got the default documentation treatment, and suffers as a result. A bit of css isn't really going to help that -- there isn't enough document structure to change much. >>> Fonts >>> ===== >>> > > Again, I'm suggesting to stick to one font(style). I don't know > if my choice was any good. Actually, you've done the opposite. You are letting each browser/OS choose for you instead of sticking to one. To get something more consistent, you should borrow from the css resets -- like font:13px/1.231 arial,helvetica,clean,sans-serif; *font-size:small; *font:x-small; > >>> >>> Search (HTML/JavaScript) >>> ======================== >>> >>> Our old documentation has a Google search - our new documentation >>> should have that too! (Or, if you're bored and want to do >>> solr/lucene...) Our >> >> What is the primary issue -- ie, is there a reason we can't just copy >> over the form and search page? > > There probably isn't. The reason why I didn't include it was because it > contained icky stuff I don't know how to handle (JavaScript and Google) Ah. I used Google because it was 16 lines of cut and paste html/javascript and configuring it to search confluence, the mail-archives and the site took typing in 3 addresses. I don't think we should go live with the new stuff until we have search -- it looks to be our 5th most popular page. miles
