-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve Information Architecture #111
Comments
Hi @dselman I can do this ;) |
There have been good improvements already. We will discuss and review at the next Tech WG call, Wed 4pm EST. You are welcome to join! |
I really like some of the suggested reorganisations. I have a couple of suggestions though with the following goals:
I've put those ideas into a similarly-shaped spreadsheet here: Differences with the previous spreadsheet:
|
…ject#111 Signed-off-by: Jerome Simeon <[email protected]>
Signed-off-by: Jerome Simeon <[email protected]>
@dselman @4katie @peterhunn @irmerk Has this been addressed by the latest reorganisation of the documentation, or should we leave this open and do another round? |
@jeromesimeon I think it looks pretty good for now, maybe if more feedback comes along we can make more amendments then? |
Happy to close. You win this round! |
I'd like to see this as a happy compromise between best and good! Closing this issue. |
A top-down review of how we organise the information in the documentation and who it is for.
This is becoming more pressing as we work on the documentation for Cicero v0.20 with the new CiceroMark markup, as well as folding in the documentation for Concerto.
Related issues:
#108
#96
#91
Straw man proposal:
https://docs.google.com/spreadsheets/d/1YaGFm6t0Y__tzdG_N6fUCG5EvjdeiffpB3JMdKR-zA0/edit#gid=0
The text was updated successfully, but these errors were encountered: