「利用者:Sam256/blender-org redesign」の版間の差分

提供: wiki
移動先: 案内検索
(Team Members)
(相違点なし)

2011年10月28日 (金) 20:58時点における版

Blender.org redesign

This page will try to collect ideas for the upcoming blender.org redesign. This page is subject to change.

However it's first purpose for now is to gather a small team of 3-4 people who want to participate in this project and nail down a basic development plan.

Team Members

  • Ondrej Brinkel (der_On @ IRC | info[at]anzui.de) - Please contact if interested in participating
  • M.G.Kishalmi (lmg @ IRC)

Roadmap

  1. Collect a small team of 3-4 people for the project.
  2. Discuss funding
  3. Analyze current information architecture and create a mindmap illustrating the structure.
  4. Collect ideas for new website features and contents.
  5. Reorganize/restructure/optimize the information and include optional new features/contents.
  6. Create wireframe layouts and interaction-flow charts that illustrate basic placement and functionality of elements on the website.
  7. Decide upon a Content Management System to use and how to integrate third party systems/data sources into it.
  8. Create up to 3 different designs of the frontpage, and a regular content page.
  9. Decide upon one of those designs and finish it in an iterative process including users that are not in the team.
  10. Create a styleguide (definition of placement, sizes, fonts, colors etc.) based on the finished design.
  11. Based on the CMS choosen in 6, create charts/mindmaps containing all content types/plugins/extensions and features to be used/coded.
  12. Outsource what kind of features of the website can be realized using existing OpenSource solutions (extensions, modules, plugins) and which have to be custom coded.
  13. Get a server and setup the development environment for the prototype of the website.
  14. Get coding! Use a bugtracker to assign issues/tasks to team members and make it possible to involve coders outside of the team.
  15. Iteratively make test-runs each time a feature has been finished. Gather testers from the community.
  16. Make a final test run and afterwards last minute changes.
  17. Move the website to a live server, keeping the development environment for further development. Setup a sync from live to dev.