|Biggest problems on the web site [message #561793]
||Fri, 29 April 2005 12:01
| Ed Burnette
Registered: July 2009
1. Users don't know where to go for help. Some find the newsgroups, some |
find the developer mailing lists. Some people don't like newsgroups and
post on the developer mailing lists even if they know it's the wrong
place. Adding to the confusion, a few mailing lists *are* for user
2. There are no screenshots.
3. Different projects have greatly different styles of doing things.
Compare these home pages:
and compare these download pages(all linked from the main download page):
4. There are no rollup packages, that combine, say, java programming,
web programming, modeling, and visual editing.
5. There is no site-wide update site story.
6. There is no syndication (RSS/Atom) of site contents, for example news
on particular projects.
7. There is no newsletter or announcements list that's actually used.
8. The web site is not data driven. For example to add a news item or
technical article involves cutting and pasting into an HTML unordered
list with special table formatting and whatnot. Yuck.
9. The web site should consistently use style sheets and not FONT tags
and TABLE. The webmaster should be able to change one css file and have
the whole site change.
If you can fix these very basic things then we can while away our time
arguing about numbers of columns and background colors and whatnot.
|Re: Biggest problems on the web site [message #673913 is a reply to message #561793]
||Wed, 25 May 2011 03:14
| Jeremie Bresson
Registered: November 2010
I totally agree with these different points. Even 6 years later. I wanted to update a project website, and I just do not get how to do it correctly. I found some guidelines (in the wiki) and some example (template.php in the default project), but I have the feeling that this is not enough. Maybe there is documentation I did not find.|
I found your post because I was looking how to integrate a new feed from a Blog into a Project Homepage. (Your point 6). From what I saw everybody is using its own script / library.
To my mind the problem is that nobody wants to invest enough time in the website. There is also no back-office tool like other open source forge can propose (Google Code, Apache, GitHub... they have different approach, but the different projects site looks similar. It is also a fact that Eclipse.org doesn't host as many projects.)
Powered by FUDForum
. Page generated in 0.01792 seconds