Skip to content
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

Update ug format #181

Merged
merged 9 commits into from
Oct 26, 2020

Conversation

m0nggh
Copy link

@m0nggh m0nggh commented Oct 24, 2020

Made some readjustments to the UGs as much as possible according to the review comments.

  • Update numbering format and standardise spacings
  • Made it more user-centric
  • Include a simple legend (can update more if necessary)
  • Rearranged the features in alphabetical order (please say if another format is preferred)
  • Sort's parameter is capitalised to suit the command format

Resolves #158
Resolves #159
Resolves #161
Resolves #163
Resolves #165
Resolves #166

@m0nggh m0nggh changed the title Branch update ug format Update ug format Oct 24, 2020
@m0nggh m0nggh added this to the v1.3 milestone Oct 24, 2020
@codecov
Copy link

codecov bot commented Oct 24, 2020

Codecov Report

Merging #181 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #181   +/-   ##
=========================================
  Coverage     73.18%   73.18%           
  Complexity      476      476           
=========================================
  Files            80       80           
  Lines          1473     1473           
  Branches        150      150           
=========================================
  Hits           1078     1078           
  Misses          342      342           
  Partials         53       53           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 13be7de...b4099a7. Read the comment docs.


<div markdown="block" class="alert alert-info">

**:information_source: Provides additional notes and constraints for certain information.**<br>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think you can delete the <br> at the end of this line cos it makes the spacing off


## FAQ

**Q**: How do I transfer my data to another Computer?<br>
**A**: Install the app in the other computer and overwrite the empty data file it creates with the file that contains the data of your previous ZooKeep home folder.

**Q**: Can I record the feeding times of a specific animal in any order I prefer?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add <br> to the end of this line

**Q**: Can I record the feeding times of a specific animal in any order I prefer?
**A**: The feeding time will be arranged in chronological order regardless of the order entered for easier reference.

**Q**: Can I search for animals based on a certain alphabet or half specified keywords?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add <br> to the end of this line

**A**: The feeding time will be arranged in chronological order regardless of the order entered for easier reference.

**Q**: Can I search for animals based on a certain alphabet or half specified keywords?
**A**: The find feature will only list animals with the exact specified keyword provided.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe can include that it is case insensitive?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think i placed it as a tip under the find feature, thanks anyways!

<br> Here are some example commands you can try:

* **`list`** : Lists all animals.
* **`exit`** : Exits the app.

1. Refer to the [Features](#features) below for details of each command.
1. You can refer to the [Features](#features) below for the details of each command. The features are categorised in alphabetical order for easier reference.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor nitpick in language. "listed" instead of "categorised".

@lamlaaaam
Copy link

Just a thought, is listing the features alphabetically the best bet? Currently it references the less "basic" features first like "append". Furthermore these features reference features that are later down the list, meaning the user would not have read them yet. Shall we consider listing from basic to advanced?


## Legend

<div markdown="block" class="alert alert-info">

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry i think the reason why the spacing is weird is bc it is a block. could you change it to try changing it to markdown="span"?

@lamlaaaam lamlaaaam merged commit 1b23f2d into AY2021S1-CS2103T-W15-4:master Oct 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants