What's the process to upload the docs? Those files should be generated or copied into place by Sphinx.
There is a cron job that runs every 5 minutes or so...
hg pull && hg update
rsync -va --delete docs/ ~pygame/www/docstest/
There was an issue with 'make docs' in that it thought everything was already built. 'make docs' is still broken, but I made the script call 'python makeref.py' instead, and the http://pygame.org/docstest/ url has the css etc now :)
Ah, maybe a Makefile task with a dependency on a whole folder doesn't check the contents of the folder? Anyway, glad to see that's resolved.
I don't think there's a pressing need to distribute either comments or the wiki content - I suggest we keep it simple and just distribute static docs, while the comments and the wiki live on the website. I don't have any strong feelings about how the comments are handled online.
How are the docs looking now? Any remaining issues before we replace the existing ones?
Only thing left to do is the comments I think. We either replace the comments we have with disqus based commenting, or use the existing add comment functionality (with all the spam problems it has).
If we use the existing php commenting system, we need to copy the various .php files in when we rebuild the pages and publish. Not too hard.
The easiest way is for now to just use existing php commenting, and fix the publish step. Then we can deal with a new or improved commenting system as a separate task.
I agree distributing the comments or wiki content is not a big need at the moment.
I took a more detailed look at the new page, comparing the old ones side by side, so far camera --> image
Nothing major found, but a few things:
typo on the Event page which is also on the old site: "Pygame handles all it's event messaging through an event queue" ... should be "its" no apostrophe. Although in the spirit of maintaining the feel of the old site ... maybe it's a feature not a bug? haha.
the new yellow box for example code needs to truncate at the termination of the code. Right now it stretches across the page and that looks klunky imo. I'm using OSX Lion / Chrome .
instead of the 'method -> returnvalue' syntax, can we go back to 'method : returns returnvalue' ? I think that's clearer and more pythonic.
on the new site, many method calls use the standard font whereas on the old they're monospaced. I think the old site is more readable in this way. Lots on the event page here. I could compile a comprehensive list if that's helpful?
can we go back to a serif font for description? I think it has more personality than the non-serif we're using for most of the new pages, and pygame.org is definitely a personality site haha.
Thanks for your feedback :)
I fixed a couple of the "it's" usages.
I made the pre code blocks inline-block, to only take up width of the code, not 100% width.
hrmmm... not sure about this. It's a fair bit of work. I'm not sure what is better.
The fonts for method calls all seem monospaced to me... can you point out a specific one? Maybe I'm looking at something else.
The current website uses sans-serif... so using that for the moment.