Le 4 août 07 à 04:22, Jesse Ross a écrit : > With 0.2 out the door and work starting on 0.3, I think it's time > to put a fresh face on the website.
Good idea :-) > Some site-related issues I've noticed: > > > Technical > ------------------------------ > - Our Mediawiki installation is in desperate need of an upgrade > (we're using 1.4beta4, the current version is 1.10.1) > - The blog is using a different content management system > (Blogger) than the rest of the site (Mediawiki), thus we're all > maintaining two separate accounts to get content onto the site. > > > Content/Navigation > ------------------------------ > - Our blog is not functionally integrated into the overall site > (URL or navigation-wise) > - Content management/navigation of Mediawiki is problematic (pages > are not in well-defined parent categories, end-users have > difficulty accessing relevant content) In June, I overhauled the navigation on several important pages like Applications, Frameworks, Developer Documentation etc. but I have never found enough time to finish the reorganization right in time for 0.2 release. I would say many sections are now rather well organized, but a lot of cruft remains and various aspects of the navigation need to be rethought. > - Recent code progress is still not in a prominent location > (making it hard for users to know that we're still alive) > - We need good, recent documentation in an easily searchable/ > browsable format > - URLs have a lot of cruft (ie: the About page is at http:// > www.etoile-project.org/etoile/mediawiki/index.php? > title=EtoileWiki:About , which would be much better as just http:// > etoile-project.org/about ) I initially planned to add rewrite rules but because I don't know Apache very well, I gave up on this one :-) > Visual > ------------------------------ > - Our identity is using violet, white, gray and black now -- the > blue, green and patterned background are not a major part of our > current identity as of 0.2, and will not be used at all for 0.3 Here is a gratuitous comment: patterned background is nice, may be we could reuse it future versions of Nesedah ;-) > - Large images (such as screenshots) overflow the page's edges > - The large central flower image, while attractive, provides no > functional information and becomes quickly redundant on subpages I agree, but I would very much appreciate to keep the image on the home page. > - The blog should be using a similar theme as the rest of the site > > > > I know most people are comfortable with Mediawiki based on > conversations we've had before, but I'm wondering if using > something else wouldn't be better. In the past I've proposed > WordPress, but Drupal looks like it might be a good long-term > solution also/instead. I'm wondering if anyone has any other > suggestions about what to do with the site, or if there are any > major objections to moving to something drastically different in > the process of building 0.3. I'm very open to any solutions similar to Mediawiki, but I don't know a lot about CMS and wikis. I initially picked Mediawiki because it had many features, was well supported and documented. It was also widely used and easier to set up than many other wikis. > I have some proposals for a new site hierarchy, which I've outlined > below -- if no one has any objections to it, I'd like us to move to > something that is more closely in line with this structure, > regardless of what underlying technical solution we use. A clean > URL hierarchy will help us keep new content focused and near other > relevant content. It will be important to add redirects > into .htaccess so that old links are redirected to the proper > location. This won't be easy as it'll have to all be done by hand, > but it needs to happen to make sure people are ending up in > (approximately) the right location. > > Home etoile-project.org > - News /news (blogs, press, feeds) ok, but I think important News must be replicated on the home page itself. > - Etoile /etoile -> /etoile/$version (overview) Not really clear… I suppose this replaces About. > - Download /download -> /etoile/$version/download > (should also provide a link to /more) > - Features /features -> /etoile/$version/features Here we surely need a Documentation section in addition to Features. I suppose Features would be a quick overview of Étoilé as whole and also of each key component. Documentation would be an area dedicated to User Guides and Manuals. It should also encompass Install Guide. > - Support /support (contact, bug submission, etc) > - Get More /more (apps, add-ons, etc) > - For Developers /dev -> dev.etoile-project.org > - Getting Started dev.etoile-project.org/start > - Installation dev.etoile-project.org/install > - Documentation dev.etoile-project.org/docs (needs to allow for > > user comments) Here is a wish… I would like to have Frameworks documentation reachable in no more than 2 or 3 clicks. For examples, on gnustep.org or apple.com, frameworks documentation takes too much time to find in my personal taste. > - Status dev.etoile-project.org/status (CIA feed) What about Development Status: roadmap, release strategy and progress/ status of stable and trunk. You forget the Team section ;-) In conclusion, I'm mostly ok with this proposal. Cheers, Quentin. _______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
