(→How to get content on to developer.meego.com?) |
|||
| Line 25: | Line 25: | ||
For content on the actual site: | For content on the actual site: | ||
| - | + | # Create the content on wiki.meego.com | |
| - | + | # Create a "Content" bug with the suggested location of the content, and some description text. | |
(Be prepared to handle feedback related to the content). | (Be prepared to handle feedback related to the content). | ||
For content linked from developer.meego.com: | For content linked from developer.meego.com: | ||
| - | + | # Create a "Content" bug with a reason for linking the content, the suggested location of the content, and some description text | |
Contents |
developer.meego.com will be released first as a beta site before public release. The goal of this beta is to get feedback about the usability and design of the site. A secondary goal is to create content, and content ideas for the site.
Of particular importance is the ease of use for the guides and references, and general navigation throughout the site.
The best way to give feedback about developer.meego.com is through bugzilla.
A blank bug is here:
We are adding a "Content" component for bugs related to missing, wrong, or dead content.
The feedback gets reviewed and we will try to improve the site accordingly. Some items will obviously be easier to implement than others (for example, API searching was quite complex because we had to import the API reference as Drupal nodes, something that took time).
In the short-term for the content ramp-up we will use a very lightweight process.
For content on the actual site:
(Be prepared to handle feedback related to the content).
For content linked from developer.meego.com: