Cross-posted from the Yocto Blog, www.yoctoproject.org. Would love to get your feedback here.
We're currently looking over this website (www.yoctoproject.org) and discussing what we could improve. If you have any ideas, we would love to hear them - just pop a mail over to yocto@yoctoproject.org and send us your thoughts.
We continue to add important new pieces of documentation incrementally and to improve what is there, like the new kernel documentation, the demo video for our Eclipse plug-in, improving information about how to contribute, and upcoming new documentation for the application development tools. But are there things which could be done better structurally?
We're really not confused here about the purpose of the website: We're not selling online ads, and we're not trying to build a web-based app. The site is to inform people about the project who may be new to it to and accelerate them into being community participants and contributors. This means getting them into the mailing lists, the Bugzilla defect tracking system, the GIT source code repository, the Wiki knowledge system and the documentation and download mirrors.
But then, are there ways we could structure it better? Add information or tools which are not there now? Could it be a wee bit more attractive?
I make no secret of the fact that I am not an artist. It's like that old saying, "I don't know anything about art, but I know what I like." What I have learned about art is to evaluate a piece by how it makes me feel rather than anything else. So I can't tell whether a piece is good or bad, but I know which ones make me feel strongly.
I suppose that probably applies for me and web sites as well. I know the sites which are the easiest for me to use. And I certainly can tell you which ones I can't stand. But when it comes to creating one that is both beautiful and useful, I need a lot of help from people who know this stuff.
So, please help us out if you can by sending us an email rant or rave or filing a bug. Thanks.
We're currently looking over this website (www.yoctoproject.org) and discussing what we could improve. If you have any ideas, we would love to hear them - just pop a mail over to yocto@yoctoproject.org and send us your thoughts.
We continue to add important new pieces of documentation incrementally and to improve what is there, like the new kernel documentation, the demo video for our Eclipse plug-in, improving information about how to contribute, and upcoming new documentation for the application development tools. But are there things which could be done better structurally?
We're really not confused here about the purpose of the website: We're not selling online ads, and we're not trying to build a web-based app. The site is to inform people about the project who may be new to it to and accelerate them into being community participants and contributors. This means getting them into the mailing lists, the Bugzilla defect tracking system, the GIT source code repository, the Wiki knowledge system and the documentation and download mirrors.
But then, are there ways we could structure it better? Add information or tools which are not there now? Could it be a wee bit more attractive?
I make no secret of the fact that I am not an artist. It's like that old saying, "I don't know anything about art, but I know what I like." What I have learned about art is to evaluate a piece by how it makes me feel rather than anything else. So I can't tell whether a piece is good or bad, but I know which ones make me feel strongly.
I suppose that probably applies for me and web sites as well. I know the sites which are the easiest for me to use. And I certainly can tell you which ones I can't stand. But when it comes to creating one that is both beautiful and useful, I need a lot of help from people who know this stuff.
So, please help us out if you can by sending us an email rant or rave or filing a bug. Thanks.