-
Notifications
You must be signed in to change notification settings - Fork 3
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
Design changes #60
Comments
One important goal is to separate the audience:
|
This issue is a note to self about specific changes I’m making.
I believe currently documentation is clear on the first two points (if there’re concerns, I’m looking forward to issues filed separately!), as to the third perhaps you could write up a brief blog post about the issue from practical standpoint? (I do not have that information, I would either need to talk to you or read a blog post.)
… On Feb 23, 2019, at 5:23 PM, Ronald Tse ***@***.***> wrote:
One important goal is to separate the audience:
standard authors that are looking for documentation for their flavor
people who don’t know what metanorma is and want to learn about it
standards bodies that want to know how metanorma can help them
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <#60 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAR4X1eJ3rCxop4DHp-Y7UsoHQxVVsaAks5vQPp-gaJpZM4bNzbi>.
|
All these three types of people should be able to find what they want with one click. |
To be clear I’m not to claim my noted design changes are more important than the issues you raised, rather the opposite, just don’t want to mix the two. |
Yup, no problem here. I'll move my statement to a new issue. |
Taking notes of what has been on my mind for own reference:
The text was updated successfully, but these errors were encountered: