Skip to content
This repository has been archived by the owner on May 20, 2023. It is now read-only.

docs/UserGuide: improve structure of the user guide #111

Closed
wants to merge 6 commits into from

Conversation

lycjackie
Copy link

The feature list has a whole chunk of feature and command,
this will be quite hard for the user to identify and search for
what they need.

We should organize our feature properly for our users to be
able to use our user guide efficiently.

Let's rearrange our features and categories them according
to its purpose and:

  • summaries each category parameter in table form
  • add a badge for each command

The feature list have a whole chunk of feature and command,
this will be quite hard for the user to identify and search for
what they need.

Let's re-organize the flow of the feature and give them a
category for it.
There is not much description for the `clear` command.

Let's add a visual representation of what the user should expect
after entering the command
The explanation was in a point form, this may not be easy to read for
the users.

Let's update the explanation and put into a table form and:
- update the content to make it more relatable
The explanation was in a point form, this may not be easy to read for
the users.

Let's update the explanation and put into a table form
The explanation was in a point form, this may not be easy to read for
the users.

Let's update the explanation and put into a table form
There is no distinct different between a module command
and a requirement command

Let's give them some colors to differentiate between each
other

Note: The color will only be displayed in the `html` version
@lycjackie lycjackie added status.Ongoing The issue/PR is currently being worked on. note: remove this label before closing an issue/PR aspect.Docs User/developer docs, product website labels Mar 21, 2019
@coveralls
Copy link

Coverage Status

Coverage remained the same at 81.213% when pulling 03019b6 on lycjackie:ug-docs-qol into a74ccfc on CS2113-AY1819S2-T09-1:master.

@lycjackie lycjackie added this to the v1.4 milestone Apr 1, 2019
@lycjackie
Copy link
Author

Closing this in view of #207

@lycjackie lycjackie added status.Rejected Issues/PRs that are rejected and closed indefinitely and removed status.Ongoing The issue/PR is currently being worked on. note: remove this label before closing an issue/PR labels Apr 11, 2019
@lycjackie lycjackie closed this Apr 11, 2019
@lycjackie lycjackie deleted the ug-docs-qol branch April 14, 2019 09:30
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
aspect.Docs User/developer docs, product website status.Rejected Issues/PRs that are rejected and closed indefinitely
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants