... | ... | @@ -35,12 +35,15 @@ Please take a look at the section below for your WG and update it as follows: |
|
|
* Chronologue
|
|
|
|
|
|
| Goal | Description | Priority | Status |
|
|
|
| Create MVP version of API | Ian did most of the work for this task. We have an API that works, but we still need to figure out where to host it, so it's accessible on the web. | High | Finished |
|
|
|
| Design high-fidelity prototype | UX Team tests and iterates constantly. Prototype should be finished before Portland| High | In progress |
|
|
|
| Build mock chronologue tool | We'll build the mock tool once we have the high-fidelity prototype. Probably after the Portland conference. | | |
|
|
|
| Create MVP version of API | Ian wrote an MVP of the Chronologue API using JSON. Ian, Felicity, and I gathered some historic and future events that the mock tool will display. | 1 | Finished |
|
|
|
| Design high-fidelity prototype | UX Team tests and iterates constantly. The prototype should be finished before Portland| 2 | In progress |
|
|
|
| Identify documentation needs and define information architecture| [Preliminary documentation plan](https://github.com/thegooddocsproject/chronologue/blob/main/documentation_plan.md) | 3| Done |
|
|
|
| Research doc tools setup | The documentation for Chronologue will live in the webite_hugo repository and use the Docsy theme. | 4 | Done |
|
|
|
| *Stretch Goals* | | | |
|
|
|
| Identify documentation needs and IA | Including whether templates exist for them | | |
|
|
|
| Research potential doc tools setup | We will probably use a Hugo & Docsy setup to test drive the doctools' group material. In the meantime, we will start drafting documentation using Markdown based on the templates that are ready for QA. | | |
|
|
|
| Build mock Chronologue tool | We'll build the mock tool once we have the high-fidelity prototype. Work will start probably after the Portland conference. |1 |Pending |
|
|
|
| Research how to host the mock tool and serve data from API | We need to look into how we build the mock tool and host it so it is agnostic of Github. A potential setup could be next.js together with Netlify and Netlify functions for the API. |2 |Pending |
|
|
|
|Create v1 of Chronologue documentation| PR: https://github.com/thegooddocsproject/website-hugo/pull/149 | 3| Pending|
|
|
|
|
|
|
|
|
|
* Community Docs
|
|
|
|
... | ... | |