On Domingo 14 Noviembre 2010 04:24:21 Jesse Charbneau escribió: > Hello, > I have modified the contribute and support pages. Please review and let > me know if I’m heading in the right direction or not. Basically shifted > things to a single frame layout, removed some items others had proposed as > wiki bound and reworded some text here and there. Also let me know if the > knife went too deep and I can add items/sections back in as > needed/directed. I could use some direction on if I should also work some > of the items in the wiki and migrate the content there, etc. If I should > do that, please direct me on how to create a wiki account (sorry, I’ve > looked but haven’t found a “user registration” page - could be I’m blind > so please confirm if true :-) ). > The registration link is http://trac.enlightenment.org/e/register it was well camouflaged on track's footer :-P
I think someone has to give you admin rights to create new pages. Placing a recaptcha in the registration form and disabling this limitation would be a better idea IMO but I don't know who can make that happen. > Thanks, > Jess > > Contribute page: http://e-www.thecharbneaus.com/p.php?p=contribute&l=en > Support page: http://e-www.thecharbneaus.com/p.php?p=support&l=en > I like them, they are not intimidating anymore. A complete stranger can see what applies to him at a glance and get to the instructions if interested. There is a bit of redundant text and perhaps the sections could be a little different. Personally, this are the things I would do to the contribute page: * Remove "We can always use help with development, packaging, bug reports, tutorials or monetary donations". It's repeated later and implied by the section titles. * Remove the title "Development" and move those paragraphs at the top making them the new "We can always use..." neutral introduction. * From those three paragraphs move the first and the last one into different "Developers" and "Users" sections/sub-sections respectively. * Perhaps expand a little those sections/subsections and sprinkle some wiki links when applicable, like ECoding[1] and Guidelines[2] pages for example. So the developer with anonymous svn access know how to contribute until he gets commit rights. * Make the svn access instructions neutral? since both developers and packagers will use them. Perhaps add a packager section alongside "Users" and "Developers" mentioning they should use tarballs for releases and linking to both the download and the download.e.org/releases pages. But those are paper-cut level suggestion. If I can stress one it would be taking a look at the wiki index[3] and sprinkling links to those pages more often. Thanks for your work and good luck. [1] http://trac.enlightenment.org/e/wiki/ECoding [2] http://trac.enlightenment.org/e/wiki/Guidelines [3] http://trac.enlightenment.org/e/wiki/TitleIndex ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
