90
edits
Changes
Jump to navigation
Jump to search
Line 25:
Line 25: − + − + + Line 38:
Line 39: + + + + + + + + +
Summer of Code/2016/Redesign and recreate Sugar Labs webappearance (view source)
Revision as of 06:54, 25 March 2016
, 06:54, 25 March 2016→Overview
===Overview===
===Overview===
The existing sites are very diversified in nature. The goal is to make a unified theme and apply it across all the sites (main page, planet, wiki etc.). This would ensure consistency and ease of use across all Sugar Labs sites. The obsolete pages would be dropped/re-designed according to the needs and minimal design would be applied.<br>
Sugar Labs aims at creating tools that learners use to explore, discover, create, and reflect with the mission to support the Sugar community of users and developers and establish regional, autonomous "Sugar Labs" around the world to help learners "learn how to learn" by tailoring Sugar to local languages and curricula.
Using less no. of technologies would make code maintenance easier and would also facilitate in dropping off unnecessary tools. This would mean unification in technology across all sites.
The existing sites are very diversified in nature. The goal is to make a unified theme and apply it across all the sites (main page, planet, wiki etc.). This would ensure consistency and ease of use across all Sugar Labs sites. The obsolete pages would be dropped/re-designed according to the needs and minimal design would be applied.<br>Using less no. of technologies would make code maintenance easier and would also facilitate in dropping off unnecessary tools. This would mean unification in technology across all sites.
===Goals===
===Goals===
# Getting feedback and re-iterating<br>
# Getting feedback and re-iterating<br>
This would help in revealing any bugs/mis-conception early in development phase itself and also give more time on enhancing the application as desired.
This would help in revealing any bugs/mis-conception early in development phase itself and also give more time on enhancing the application as desired.
==== Development Approach ====
The approach of Evolutionary Prototyping would be followed which will involve following phases:
* '''Phase 1''': Gathering of requirements
** Collecting all resources
* '''Phase 2''': Prototype development based on requirements
* '''Phase 3''': Feedback from the mentor for the developed prototype
* '''Phase 4''': Refinements based on the gathered feedback
This approach will help in making the development easily adaptable to changes in the requirements as well as help in identifying and rectifying bugs in the early development phase hence resulting in a better software at the end of the development cycle.
===Specifications===
===Specifications===