Since most users of Open Competencies come from a non-technical background, the user interface needs to be as simple and clean as possible, as early as possible. Having a clear ui outlined will also guide development in this milestone.
Let's first think about what users will need to do, in order to build a set of standards on Open Competencies:
Create a user account.
For now, this will be a simple username/ password. Full implementation will require an email confirmation, which enables password reset. This is important, because people being locked out of their accounts would lose a lot of work.
Create or join a school.
Creating a school is straightforward, because the user will then take ownership of the school they create.
Joining a school involves sending a message to the school's owner, who will then have to approve the request. This will be in a separate milestone.
Create content:
Create a subject area, such as Science or Cross-Curricular Standards.
Create Graduation Standards.
Create Performance Indicators.
Create Learning Objectives.
View content:
In a simple hierarchical view (ie, view the entire system dumped into a single page).
In a single-page summary of a subject area.
One goal of the GSP model is to constrain a set of standards to a manageable size. The system should help enforce this constraint.
Since most users of Open Competencies come from a non-technical background, the user interface needs to be as simple and clean as possible, as early as possible. Having a clear ui outlined will also guide development in this milestone.