diff --git a/docs/UserGuide.md b/docs/UserGuide.md
index e6e600dc4af..e749908fd65 100644
--- a/docs/UserGuide.md
+++ b/docs/UserGuide.md
@@ -35,7 +35,7 @@ Are you a School of Computing (SoC) Computing Club event planner juggling numero
Managing everything efficiently just got easier with CoordiMate!
-CoordiMate is your go-to **desktop app** designed specifically for **SoC Computing Club event planners** to help you **manage your contacts and tasks** for your events, so that you can focus on the event itself.
+CoordiMate is your go-to **desktop app** designed specifically for **SoC Computing Club event planners**. It helps you **manage your contacts and tasks** for your events, so that you can focus on the event itself.
And here's the best part – while it's perfect for members of SoC Computing Club, **event planners of all kinds** can benefit from CoordiMate's powerful features too!
@@ -43,11 +43,11 @@ And here's the best part – while it's perfect for members of SoC Computing Clu
1. **User-Friendly [Command Line Interface (CLI)](#command-line-interface)**: CoordiMate is optimized for use via a CLI, combining all the benefits of a [Graphical User Interface (GUI)](#graphical-user-interface) with the efficiency of a CLI.
-2. **Speedy Navigation**: If you're a fast typist, CoordiMate will help you complete your contact and tasks management faster than traditional GUI apps, maximising your productivity.
+2. **Speedy Navigation**: If you're a fast typist, CoordiMate will help you manage your contacts and tasks faster than traditional GUI apps, maximising your productivity.
-Don't let the stress of contact and task management hinder your event planning creativity.
+Don't let the stress of contact and task management hinder your creativity.
-Let **CoordiMate** take care of the details, while you craft extraordinary events with confidence.
+Let CoordiMate take care of the details, while you craft extraordinary events with confidence.
## Using This Guide
@@ -86,7 +86,8 @@ Known issues that you may face when using CoordiMate and how to resolve them.
Throughout this guide, you will see different text styles that are used to highlight important information.
- Text in blue are links which you can click on to jump to the relevant section.
-- `Text with light blue background` are commands or file names which are used for CoordiMate.
+- `Text with background` are commands or file names which are used for CoordiMate.
+- Text in buttons are keys that you press on your keyboard.
---
@@ -101,60 +102,58 @@ Throughout this guide, you will see different text styles that are used to highl
-## Features
-
[Back to Table of Contents](#table-of-contents)
- 1. **Easy Management of People**:
- - Seamlessly create, update, and delete your contacts, ensuring your contact list is always up-to-date.
+## Features
+
+ 1. **Easy Contact Management**:
+ - CoordiMate seamlessly creates, updates, and deletes your contacts, ensuring that your contact list is always up-to-date.
2. **Effortless Task Management**:
- - CoordiMate records down your tasks and their completion status, allowing you to stay on top of your to-do list.
+ - CoordiMate records your tasks and their completion status, allowing you to stay on top of your task list.
3. **Simplified Searching**:
- - Easily locate contacts or tasks based on your criteria. No more scrolling through endless lists!
+ - CoordiMate easily locates contacts or tasks based on your given criteria. No more scrolling through endless lists!
4. **Hassle-Free Data Management**:
- CoordiMate automatically saves your data on every change, so you never have to worry about losing your data.
- - When CoordiMate starts, your existing data is automatically loaded in, allowing you to pick up where you left off.
- - For advanced users, CoordiMate offers you complete data control by saving your data in a human-readable format. Locate the data file at `[JAR file location]/data/addressbook.json` to edit CoordiMate's data directly!
-
-{% include admonition.html type="warning" title="Warning" body="
-
-If your changes to the data file makes its format invalid, CoordiMate will not be able to load the data file, resulting in the contact and task lists being empty.
-
-Always make a backup before you edit!
-
-" %}
---
-## Quick Start
-
[Back to Table of Contents](#table-of-contents)
-1. Ensure you have Java `11` or above installed in your computer.
+## Quick Start
+
+1. Ensure you have Java `11` or above installed on your computer.
2. Download the latest `CoordiMate.jar` from [here](https://github.com/AY2324S1-CS2103T-T10-2/tp/releases).
-3. Copy `CoordiMate.jar` to the folder you want to use as the _home folder_ for CoordiMate. This folder will be used by CoordiMate to store its data.
+3. Copy `CoordiMate.jar` to the folder you want to use as the home folder for CoordiMate. This folder will be used by CoordiMate to store its data.
-4. Open a command terminal, `cd` into the folder you put `CoordiMate.jar` in, and use the `java -jar CoordiMate.jar` command to start CoordiMate.
+4. Open a command terminal.
- A GUI similar to the below screenshot should appear in a few seconds. Note how the app contains some sample data.
- ![Ui](images/Ui.png)
+5. Change the directory to the folder where you have placed `CoordiMate.jar`. If it is in your `Downloads` folder, type the command below and press Enter :
+ ```
+ cd Downloads
+ ```
+6. To launch CoordiMate, type the following command and press Enter :
+ ```
+ java -jar CoordiMate.jar
+ ```
+ After a few seconds, a GUI should appear, showing some sample data, as in the screenshot below.
+ ![Ui](images/Ui.png)
-5. Type the command in the command box and press Enter to execute it. e.g. typing `help` and pressing Enter will open the help window.
+7. Type the command in the [command line](#understanding-our-gui) and press Enter to execute it. e.g. typing `help` and pressing Enter will open the help window.
Some example commands you can try:
- `listPerson` : Lists all persons.
- - `addPerson n/John Doe p/98765432 e/johnd@example.com a/John street, block 123, #01-01` : Adds a new contact named `John Doe` with the specified details.
+ - `addPerson n/John Doe p/98765432 e/johnd@example.com a/John street, block 123, #01-01` : Adds a new person named `John Doe` with the specified details.
- - `deletePerson 3` : Deletes the 3rd contact shown in the current contact list.
+ - `deletePerson 3` : Deletes the 3rd person shown in the current contact list.
- `findTask caterer` : Finds all tasks with the word `caterer` in their title or note.
@@ -166,16 +165,16 @@ Always make a backup before you edit!
- `exit` : Exits the app.
-6. Refer to the [Usage](#usage) section below for details of each command.
+8. Refer to the [Usage](#usage) section below for details of each command.
---
-## Usage
-
[Back to Table of Contents](#table-of-contents)
+## Usage
+
The commands are split into 4 main sections:
1. [Commands to Manage Persons](#1-commands-to-manage-persons)
@@ -204,17 +203,24 @@ The commands are split into 4 main sections:
Fields in square brackets with …
after them can be used multiple times, including zero times.
- e.g. [t/TAG]…
can be used as
(i.e. 0 times), t/friend
, t/friend t/family
etc.
+ e.g. [t/TAG]…
can be used as
(i.e. zero times), t/friend
, t/friend t/family
etc.
- Fields can be in any order.
+ All fields except INDEX
can be in any order.
e.g. if the command specifies n/NAME p/PHONE_NUMBER
, p/PHONE_NUMBER n/NAME
is also acceptable.
+
+
+ Whitespaces at the start and end of fields are trimmed.
+ e.g. The input n/ John Doe
will be interpreted as n/John Doe
.
+
+
+
Extraneous fields for commands that do not take in fields (such as help
, listPerson
, deleteAllPerson
, listTask
, deleteAllTask
and exit
) will be ignored.
@@ -233,10 +239,10 @@ If you are using a PDF version of this document, be careful when copying and pas
-### Command Aliases
-
[Back to Table of Contents](#table-of-contents)
+### Command Aliases
+
CoordiMate supports predefined aliases for commands, so that you can get things done faster!
**Example 1: Adding a person**
@@ -269,7 +275,7 @@ you can simply type:
lp
-Both commands will show a full list of all the contacts in your contact list.
+Both commands will show a full list of all the persons in your contact list.
A summary of valid aliases is shown in the [Command Summary](#command-summary) section below.
@@ -277,10 +283,10 @@ A summary of valid aliases is shown in the [Command Summary](#command-summary) s
-### Understanding Our GUI
-
[Back to Table of Contents](#table-of-contents)
+### Understanding Our GUI
+
![Ui](images/Ui_explanation.png)
1. Menu Bar: Quick access to File and Help features.
@@ -292,7 +298,7 @@ A summary of valid aliases is shown in the [Command Summary](#command-summary) s
{% include admonition.html type="note" title="Note" body="
-Here's a handy trick – you can easily resize sections like Command Result, Contact List, and Task List. Just give the sides a drag in or out to customize the view according to your preference.
+Here's a handy trick – you can easily resize sections like Command Result, Contact List, and Task List. Just drag the dividers to customize the view according to your preferences.
" %}
@@ -300,12 +306,12 @@ Here's a handy trick – you can easily resize sections like Command Result, Con
+[Back to Table of Contents](#table-of-contents)
+
### 1. Commands to Manage Persons
#### 1.1. Adding a person: `addPerson`
-[Back to Table of Contents](#table-of-contents)
-
You can add new persons to your contact list, so that you can remember details of new people you meet.
Format:
@@ -324,40 +330,42 @@ ap
| Fields | Prefix | Required | Remarks |
|--------|--------|:--------:|---------|
-| `NAME` | `n/` | | Full name of the individual.|
-| `PHONE_NUMBER` | `p/` | | Phone number of the individual.|
-| `EMAIL` | `e/` | | Email address of the individual.|
-| `ADDRESS` | `a/` | | Physical address of the individual.|
-| `TAG` | `t/` | | Tag(s) for the individual.|
+| `NAME` | `n/` | | Full name of the person. The name should only contain alphanumeric characters and spaces.|
+| `PHONE_NUMBER` | `p/` | | Phone number of the person. The number should only contain numbers, and it should be at least 3 digits long.|
+| `EMAIL` | `e/` | | Email of the person. The email should match this format: `@.`. The `` part should only contain alphanumberic characters and these special characters: `+_.-`. The `` and `` parts should contain only alphanumberic characters.|
+| `ADDRESS` | `a/` | | Physical address of the person.|
+| `TAG` | `t/` | | Tag(s) for the person. Tags should only contain alphanumeric characters.|
{: .field-table}
- A person is uniquely identified by their `NAME`. This field is case sensitive.
+- You may add multiple tags to a person by specifying the `t/` prefix multiple times.
Example:
-- `addPerson n/Charlotte Oliveiro p/93210283 e/charlotteo@example.com a/Blk 11 Ang Mo Kio Street 74, #11-04 t/flowers`
+- `addPerson n/Xavier p/98712309 e/xavierd@example.com a/311, Dover Ave 2, #03-25 t/Microsoft t/guestSpeaker`
![addPerson success](images/output/addPerson_success.png)
- *CoordiMate adds a new contact with the corresponding details. *
+ *CoordiMate adds a new person with the corresponding details. *
Potential Errors:
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that the name, phone number, email address and address are specified.
-`Names should only contain alphanumeric characters and spaces, and it should not be blank` | Ensure that the name specified is not blank and contain only alphanumeric characters. Whitespaces at the start and end are trimmed.
-`Phone numbers should only contain numbers, and it should be at least 3 digits long` | Ensure that the phone number specified is not blank, contain only numbers and at least 3 digits long. Whitespaces at the start and end are trimmed.
-`Addresses can take any values, and it should not be blank` | Ensure that the address specified is not blank. Whitespaces at the start and end are trimmed.
-`Emails should be of the format local-part@domain and adhere to the following constraints: …` | Ensure that the email specified is not blank and adheres to the constraints specified. Whitespaces at the start and end are trimmed.
-`This person already exists in the address book.` | Ensure that the new name specified does not match an existing person.
+`Invalid command format! …` | Ensure that the name, phone number, email address and address are specified.
+`Names should only contain alphanumeric characters and spaces, and it should not be blank` | Ensure that the name specified is not blank and contain only alphanumeric characters.
+`Phone numbers should only contain numbers, and it should be at least 3 digits long` | Ensure that the phone number specified is not blank, contain only numbers and at least 3 digits long.
+`Addresses can take any values, and it should not be blank` | Ensure that the address specified is not blank.
+`Emails should be of the format local-part@domain and adhere to the following constraints: …` | Ensure that the email specified is not blank and adheres to the constraints specified.
+`Tags names should be alphanumeric` | Ensure that the tags specified are alphanumeric.
+`This person already exists in the address book` | Ensure that the new name specified does not match an existing person.
`Multiple values specified for the following single-valued field(s): …` | Ensure that there are no duplicate fields for name, email, address and phone number.
-#### 1.2. Listing all persons: `listPerson`
-
[Back to Table of Contents](#table-of-contents)
+#### 1.2. Listing all persons: `listPerson`
+
You can view your entire contact list, so that you can quickly access and manage your connections.
Format:
@@ -381,10 +389,10 @@ lp
-#### 1.3. Editing a person: `editPerson`
-
[Back to Table of Contents](#table-of-contents)
+#### 1.3. Editing a person: `editPerson`
+
You can change the details of an existing person in your contact list, so that you can keep information in your contact list constantly up-to-date.
Format:
@@ -403,20 +411,22 @@ ep
| Fields | Prefix | Required | Remarks |
|--------|--------|:--------:|---------|
-| `INDEX` | No prefix | | The person at this index in the displayed person list is edited. The index must be a positive integer (i.e. 1, 2, 3, … , 2147483647). |
-| `NAME` | `n/` | | Full name of the individual.|
-| `PHONE_NUMBER` | `p/` | | Phone number of the individual.|
-| `EMAIL` | `e/` | | Email address of the individual.|
-| `ADDRESS` | `a/` | | Physical address of the individual.|
-| `TAG` | `t/` | | Tag(s) for the individual.|
+| `INDEX` | No prefix | | The person at this index in the displayed contact list is edited. The index must be a positive integer (i.e. 1, 2, 3, … , 2147483647). |
+| `NAME` | `n/` | | Full name of the person. The name should only contain alphanumeric characters and spaces.|
+| `PHONE_NUMBER` | `p/` | | Phone number of the person. The number should only contain numbers, and it should be at least 3 digits long.|
+| `EMAIL` | `e/` | | Email of the person. The email should match this format: `@.`. The `` part should only contain alphanumberic characters and these special characters: `+_.-`. The `` and `` parts should contain only alphanumberic characters.|
+| `ADDRESS` | `a/` | | Physical address of the person.|
+| `TAG` | `t/` | | Tag(s) for the person. Tags should only contain alphanumeric characters.|
{: .field-table}
-- Existing values will be updated to the input values.
- At least one of the optional fields must be provided for the command to be valid.
+- Fields that are not specified will preserve their existing values.
- A person is uniquely identified by their `NAME`. This field is case sensitive.
-- You may add multiple tags to a person by specifying the `t/` prefix multiple times.
- - Note that this will replace all existing tags of the task. If you wish to add to the existing tags of the task, use the [`addTagPerson` command](#31-adding-tags-to-a-person-addtagperson) instead.
- - Specifying `t/` without any tags will clear all existing tags of the task.
+- You may edit the person to have multiple tags by specifying the `t/` prefix multiple times.
+- If you specify at least one tag with this command, all old tags will be replaced.
+ - If you wish to add to the existing tags of the person, use the [`addTagPerson` command](#31-adding-tags-to-a-person-addtagperson) instead.
+ - If you wish to delete an existing tag of the person, use the [`deleteTagPerson` command](#36-deleting-tags-from-a-person-deletetagperson) instead.
+ - Specifying `t/` without any tags will clear all existing tags of the person.
Example:
@@ -429,22 +439,23 @@ ep
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that the index is correctly specified as an integer.
+`Invalid command format! …` | Ensure that the index is correctly specified as an integer.
`At least one field to edit must be provided.` | Ensure that at least one of name, phone, email, address or tag is specified.
`The person index provided is invalid` | Ensure that the index provided is within the valid range.
-`Names should only contain alphanumeric characters and spaces, and it should not be blank` | Ensure that the name specified is not blank and contain only alphanumeric characters. Whitespaces at the start and end are trimmed.
-`Phone numbers should only contain numbers, and it should be at least 3 digits long` | Ensure that the phone number specified is not blank, contain only numbers and at least 3 digits long. Whitespaces at the start and end are trimmed.
-`Addresses can take any values, and it should not be blank` | Ensure that the address specified is not blank. Whitespaces at the start and end are trimmed.
-`Emails should be of the format local-part@domain and adhere to the following constraints: …` | Ensure that the email specified is not blank and adheres to the constraints specified. Whitespaces at the start and end are trimmed.
+`Names should only contain alphanumeric characters and spaces, and it should not be blank` | Ensure that the name specified is not blank and contain only alphanumeric characters.
+`Phone numbers should only contain numbers, and it should be at least 3 digits long` | Ensure that the phone number specified is not blank, contain only numbers and at least 3 digits long.
+`Addresses can take any values, and it should not be blank` | Ensure that the address specified is not blank.
+`Emails should be of the format local-part@domain and adhere to the following constraints: …` | Ensure that the email specified is not blank and adheres to the constraints specified.
+`Tags names should be alphanumeric` | Ensure that the tags specified are alphanumeric.
`This person already exists in the address book.` | Ensure that the new name specified does not match an existing person.
`Multiple values specified for the following single-valued field(s): …` | Ensure that there are no duplicate fields for name, email, address and phone number.
-#### 1.4. Finding a specific person: `findPerson`
-
[Back to Table of Contents](#table-of-contents)
+#### 1.4. Finding a specific person: `findPerson`
+
You can find a person by their name, so that you can quickly locate their contact details.
Format:
@@ -463,7 +474,7 @@ fp
| Fields | Prefix | Required | Remarks |
|--------|--------|:--------:|---------|
-| `KEYWORD` | No prefix | | The keyword to search for. |
+| `KEYWORD` | No prefix | | Keyword to search for. |
| `MORE_KEYWORDS` | No prefix | | Additional keywords to search for. |
{: .field-table}
@@ -474,7 +485,7 @@ fp
This command hides all persons that do not match the search criteria.
(i.e. If no persons match the search criteria, the list will be empty.)
-To reset the persons view, simply run the listPerson
command to list all persons.
+To reset the persons view, simply run the listPerson
command to list all persons.
" %}
@@ -489,15 +500,15 @@ To reset the persons view, simply run the listPerson
command to lis
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that a keyword is provided.
+`Invalid command format! …` | Ensure that a keyword is provided.
{: .errors-table}
-#### 1.5. Deleting a person entry: `deletePerson`
-
[Back to Table of Contents](#table-of-contents)
+#### 1.5. Deleting a person entry: `deletePerson`
+
You can remove a person from your contact list, so that you can remove contacts that you no longer need.
Format:
@@ -516,7 +527,7 @@ dp
| Fields | Prefix | Required | Remarks |
|---------|--------|:--------:|---------|
-| `INDEX` | No prefix | | The person at this index in the displayed person list is deleted. The index must be a positive integer (i.e. 1, 2, 3, … , 2147483647). |
+| `INDEX` | No prefix | | The person at this index in the displayed contact list is deleted. The index must be a positive integer (i.e. 1, 2, 3, … , 2147483647). |
{: .field-table}
{% include admonition.html type="warning" title="Warning" body="
@@ -527,25 +538,25 @@ This person will be removed from your contact list immediately. This action is i
Example:
-- `listPerson` followed by `deletePerson 2`.
+- `listPerson` followed by `deletePerson 2`
![deletePerson_success_with_listPerson](images/output/deletePerson_success.png)
- *CoordiMate deletes the person at the index 2
. *
+ *CoordiMate deletes the 2nd person who was previously Bernice Yu
. *
Potential Errors:
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that the index is correctly specified as an integer.
+`Invalid command format! …` | Ensure that the index is correctly specified as an integer.
`The person index provided is invalid` | Ensure that the index provided is within the valid range.
-#### 1.6. Deleting all person entries: `deleteAllPerson`
-
[Back to Table of Contents](#table-of-contents)
-You can delete all persons in your contact list, so that you can restart easily with a clean slate and an empty contact list.
+#### 1.6. Deleting all person entries: `deleteAllPerson`
+
+You can remove all persons in your contact list, so that you can restart easily with a clean slate and an empty contact list.
Format:
@@ -576,13 +587,13 @@ All persons will be removed from your contact list immediately. This action is i
+[Back to Table of Contents](#table-of-contents)
+
### 2. Commands to Manage Tasks
#### 2.1. Adding a task: `addTask`
-[Back to Table of Contents](#table-of-contents)
-
-You can add a task to your task list, so that you can keep track of important things to do.
+You can add new tasks to your task list, so that you can keep track of important things to do.
Format:
@@ -602,7 +613,7 @@ at
|--------|--------|:--------:|---------|
| `TITLE` | `T/` | | Title describing the task. |
| `NOTE` | `n/` | | Note providing details about the task. |
-| `TAG` | `t/` | | Tag(s) for the task.|
+| `TAG` | `t/` | | Tag(s) for the task. Tags should only contain alphanumeric characters. |
{: .field-table}
- A task is uniquely identified by the combination of its `TITLE` and `NOTE`. These fields are case sensitive.
@@ -621,16 +632,18 @@ at
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that the title and note are specified.
-`Titles/Notes can take any value, as long as it is not blank and does not start with a whitespace` | Ensure that the title and note specified are not blank. Whitespaces at the start and end are trimmed.
+`Invalid command format! …` | Ensure that the title and note are specified.
+`Titles/Notes can take any value, as long as it is not blank and does not start with a whitespace` | Ensure that the title and note specified are not blank.
+`Tags names should be alphanumeric` | Ensure that the tags specified are alphanumeric.
+`This task already exists in the address book` | Ensure that the new title and note specified do not match an existing task.
`Multiple values specified for the following single-valued field(s): …` | Ensure that there are no duplicate fields for title and note.
-#### 2.2. Listing all tasks: `listTask`
-
[Back to Table of Contents](#table-of-contents)
+#### 2.2. Listing all tasks: `listTask`
+
You can view your entire task list, so that you can stay organized and on top of your responsibilities.
Format:
@@ -654,11 +667,11 @@ lt
-#### 2.3. Editing a task: `editTask`
-
[Back to Table of Contents](#table-of-contents)
-You can edit a task in your task list, so that you can ensure task details are up-to-date with the latest information.
+#### 2.3. Editing a task: `editTask`
+
+You can change the details of an existing task in your task list, so that you can ensure your task details are up-to-date with the latest information.
Format:
@@ -679,14 +692,16 @@ et
| `INDEX` | No prefix | | The task at this index in the displayed task list is edited. The index must be a positive integer (i.e. 1, 2, 3, … , 2147483647). |
| `TITLE` | `T/` | | Title describing the task. |
| `NOTE` | `n/` | | Note providing details about the task. |
-| `TAG` | `t/` | | Tag(s) for the task.|
+| `TAG` | `t/` | | Tag(s) for the task. Tags should only contain alphanumeric characters. |
{: .field-table}
- At least one of the optional fields must be provided for the command to be valid.
- Fields that are not specified will preserve their existing values.
+- A task is uniquely identified by the combination of its `TITLE` and `NOTE`. These fields are case sensitive.
- You may edit the task to have multiple tags by specifying the `t/` prefix multiple times.
- If you specify at least one tag with this command, all old tags will be replaced.
- If you wish to add to the existing tags of the task, use the [`addTagTask` command](#32-adding-tags-to-a-task-addtagtask) instead.
+ - If you wish to delete an existing tag of the task, use the [`deleteTagTask` command](#37-deleting-tags-from-a-task-deletetagtask) instead.
- Specifying `t/` without any tags will clear all existing tags of the task.
Example:
@@ -700,19 +715,20 @@ et
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that the index is correctly specified as an integer.
+`Invalid command format! …` | Ensure that the index is correctly specified as an integer.
`At least one field to edit must be provided.` | Ensure that at least one of title, note, or tag is specified.
-`Titles/Notes can take any value, as long as it is not blank and does not start with a whitespace` | Ensure that the title and/or note specified are not blank. Whitespaces at the start and end are trimmed.
+`Titles/Notes can take any value, as long as it is not blank and does not start with a whitespace` | Ensure that the title and/or note specified are not blank.
+`Tags names should be alphanumeric` | Ensure that the tags specified are alphanumeric.
`This task already exists in the address book.` | Ensure that the new title and note specified do not match an existing task.
`Multiple values specified for the following single-valued field(s): …` | Ensure that there are no duplicate fields for title and note.
-#### 2.4. Finding a specific task: `findTask`
-
[Back to Table of Contents](#table-of-contents)
-You can quickly locate tasks that contains your specified keywords in their title and/or note.
+#### 2.4. Finding a specific task: `findTask`
+
+You can find a task by their title or note, so that you can quickly locate a specific task.
Format:
@@ -730,7 +746,7 @@ ft
| Fields | Prefix | Required | Remarks |
|--------|--------|:--------:|---------|
-| `KEYWORD` | No prefix | | The keyword to search for. |
+| `KEYWORD` | No prefix | | Keyword to search for. |
| `MORE_KEYWORDS` | No prefix | | Additional keywords to search for. |
{: .field-table}
@@ -741,7 +757,7 @@ ft
This command hides all tasks that do not match the search criteria.
(i.e. If no tasks match the search criteria, the list will be empty.)
-To reset the tasks view, simply run the listTask
command to list all tasks.
+To reset the tasks view, simply run the listTask
command to list all tasks.
" %}
@@ -756,14 +772,14 @@ To reset the tasks view, simply run the listTask
command to list al
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that a keyword is provided.
+`Invalid command format! …` | Ensure that a keyword is provided.
-#### 2.5 Deleting a task entry: `deleteTask`
-
[Back to Table of Contents](#table-of-contents)
+#### 2.5. Deleting a task entry: `deleteTask`
+
You can remove a task from your task list, so that you can remove tasks that you no longer need.
Format:
@@ -778,10 +794,6 @@ deleteTask INDEX
dt
```
-- Deletes the task at the specified `INDEX`.
-- The index refers to the index number shown in the task list currently displayed.
-- The index **_must be a positive integer_** 1, 2, 3, … , 2147483647.
-
Fields:
| Fields | Prefix | Required | Remarks |
@@ -800,21 +812,21 @@ The task will be removed from your task list immediately. This action is irrever
- `listTask` followed by `deleteTask 2`
![deleteTask_success](images/output/deleteTask_success.png)
- *CoordiMate deletes the task at the index 2
. *
+ *CoordiMate deletes the 2nd task which was previously Create budget
. *
Potential Errors:
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that the index is correctly specified as an integer.
+`Invalid command format! …` | Ensure that the index is correctly specified as an integer.
`The task index provided is invalid` | Ensure that the index provided is within the valid range.
-#### 2.6. Deleting all task entries: `deleteAllTask`
-
[Back to Table of Contents](#table-of-contents)
+#### 2.6. Deleting all task entries: `deleteAllTask`
+
You can remove all tasks from your task list, so that you can restart easily with a clean slate and an empty task list.
Format:
@@ -844,11 +856,11 @@ All tasks will be removed from your task list immediately. This action is irreve
-#### 2.7. Marking a task as done: `markTask`
-
[Back to Table of Contents](#table-of-contents)
-You can indicate that a specific task as completed, so that you can keep track of task progress and identify tasks that are done.
+#### 2.7. Marking a task as done: `markTask`
+
+You can indicate a specific task as completed, so that you can keep track of task progress and identify tasks that are done.
Format:
@@ -876,23 +888,23 @@ mt
- `listTask` followed by `markTask 1`
![markTask_success](images/output/markTask_success.png)
- *CoordiMate marks the task at the index 1
in the task list as done. *
+ *CoordiMate marks the 1st task in the task list as done. *
Potential Errors:
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that the index is correctly specified as an integer.
+`Invalid command format! …` | Ensure that the index is correctly specified as an integer.
`The task index provided is invalid` | Ensure that the index provided is within the valid range.
-`This task is already marked as done in the task list.` | Ensure that the task specified for marking is not already done in the task list.
+`This task is already marked as done in the task list.` | Ensure that the specified task is not already marked as done in the task list.
-#### 2.8. Marking a task as not done: `unmarkTask`
-
[Back to Table of Contents](#table-of-contents)
-You can indicate that a specific task as not completed, so that you can keep track of task progress and identify tasks that are pending further action or completion.
+#### 2.8. Marking a task as not done: `unmarkTask`
+
+You can indicate a specific task as not completed, so that you can keep track of task progress and identify tasks that are pending further action or completion.
Format:
@@ -920,23 +932,23 @@ ut
- `listTask` followed by `unmarkTask 1`
![unmarkTask_success](images/output/unmarkTask_success.png)
- *CoordiMate marks the task at the index 1
in the task list as not done. *
+ *CoordiMate marks the 1st task in the task list as not done. *
Potential Errors:
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that the index is correctly specified as an integer.
+`Invalid command format! …` | Ensure that the index is correctly specified as an integer.
`The task index provided is invalid` | Ensure that the index provided is within the valid range.
`This task is already marked as not done in the task list.` | Ensure that the specified task is not already marked as not done in the task list.
-#### 2.9. Finding all tasks that are done: `findDone`
-
[Back to Table of Contents](#table-of-contents)
-You can filter the task list to locate all completed tasks, so that you can keep track of task progress and the number of completed tasks with ease.
+#### 2.9. Finding all tasks that are done: `findDone`
+
+You can filter the task list to locate all completed tasks, so that you can keep track of the number of completed tasks with ease.
Format:
@@ -952,9 +964,9 @@ fd
{% include admonition.html type="note" title="Note" body="
-This command hides all Tasks that are not done.
-(i.e. If no Tasks are not done, the list will be empty.)
-To reset the Tasks view, simply run the listTask
command to list all Tasks.
+This command hides all tasks that are not done.
+(i.e. If no tasks are not done, the list will be empty.)
+To reset the tasks view, simply run the listTask
command to list all tasks.
" %}
@@ -967,11 +979,11 @@ To reset the Tasks view, simply run the listTask
command to list al
-#### 2.10. Finding all tasks that are not done: `findNotDone`
-
[Back to Table of Contents](#table-of-contents)
-You can filter the task list to locate all not completed tasks, so that you can keep track of task progress and the number of not completed tasks with ease.
+#### 2.10. Finding all tasks that are not done: `findNotDone`
+
+You can filter the task list to locate all not completed tasks, so that you can keep track of the number of not completed tasks with ease.
Format:
@@ -987,9 +999,9 @@ fnd
{% include admonition.html type="note" title="Note" body="
-This command hides all Tasks that are done.
-(i.e. If no Tasks are done, the list will be empty.)
-To reset the Tasks view, simply run the listTask
command to list all Tasks.
+This command hides all tasks that are done.
+(i.e. If no tasks are done, the list will be empty.)
+To reset the tasks view, simply run the listTask
command to list all tasks.
" %}
@@ -1002,10 +1014,10 @@ To reset the Tasks view, simply run the listTask
command to list al
-#### 2.11. Deleting all tasks that are done: `deleteAllDone`
-
[Back to Table of Contents](#table-of-contents)
+#### 2.11. Deleting all tasks that are done: `deleteAllDone`
+
You can remove all completed tasks in the task list, so that you can focus on not completed tasks and maintain an organized and clutter-free task list.
Format:
@@ -1020,7 +1032,7 @@ deleteAllDone
dad
```
-- After completing the deletion of completed tasks, the task list will automatically revert back to displaying all tasks, ensuring you have a comprehensive overview of your remaining to-dos.
+- After completing the deletion of completed tasks, the task list will automatically revert back to displaying all tasks, ensuring you have a comprehensive overview of your remaining tasks.
{% include admonition.html type="warning" title="Warning" body="
@@ -1039,19 +1051,19 @@ All completed tasks will be removed from your task list immediately. This action
Error message | How to resolve
---------------|---------------
-`No Done tasks found in task list` | Ensure that there are tasks marked as done in your task list with [`findDone` command](#29-finding-all-tasks-that-are-done-finddone).
+`No Done tasks found in task list` | Ensure that there are tasks marked as done in your task list.
---
+[Back to Table of Contents](#table-of-contents)
+
### 3. Commands to Manage Tags
#### 3.1. Adding tag(s) to a person: `addTagPerson`
-[Back to Table of Contents](#table-of-contents)
-
-You can add tag(s) to a person, so that you can simply add to the existing list of tags of the indexed person.
+You can add tag(s) to a person, so that you can better organise your contact list.
Format:
@@ -1069,35 +1081,36 @@ atagp
| Fields | Prefix | Required | Remarks |
|---------|--------|:--------:|---------|
-| `INDEX` | No prefix | | The person at this index in the displayed person list is edited. The index must be a positive integer 1, 2, 3, … , 2147483647. |
-| `TAG` | `t/` | | The tag to be added to the person. |
-| `MORE_TAGS` | `t/` | | Additional tag(s) to be added to the person. |
+| `INDEX` | No prefix | | The person at this index in the displayed contact list is edited. The index must be a positive integer 1, 2, 3, … , 2147483647. |
+| `TAG` | `t/` | | The tag to be added to the person. Tags should only contain alphanumeric characters. |
+| `MORE_TAGS` | `t/` | | Additional tag(s) to be added to the person. Tags should only contain alphanumeric characters. |
{: .field-table}
- A tag is uniquely identified by the `TAG`. This field is case sensitive.
+- You may add multiple tags to a person by specifying the `t/` prefix multiple times.
Example:
-- `addTagPerson 1 t/friends t/expensive`.
+- `addTagPerson 1 t/friends t/expensive`
![addTagPerson success](images/output/addTagPerson_success.png)
- *CoordiMate adds tag expensive
to the person at the index 1
, while friends
is not added because it already exists in the list of tags. *
+ *CoordiMate adds tag expensive
to the 1st person, while friends
is not added because it already exists in the list of tags. *
Potential Errors:
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that the index and tag are both specified. The index should be correctly specfiied as an integer.
-`Tags names should be alphanumeric` | Ensure that the tag is specified and is alphanumeric.
+`Invalid command format! …` | Ensure that the index and tag are both specified. The index should be correctly specified as an integer.
`The person index provided is invalid` | Ensure that the index provided is within the valid range.
+`Tags names should be alphanumeric` | Ensure that the tags specified are alphanumeric.
-#### 3.2. Adding tag(s) to a task: `addTagTask`
-
[Back to Table of Contents](#table-of-contents)
-You can add tag(s) to a task, so that you can simply add to the existing list of tags of the indexed task.
+#### 3.2. Adding tag(s) to a task: `addTagTask`
+
+You can add tag(s) to a task, so that you can better organise your task list.
Format:
@@ -1116,34 +1129,35 @@ atagt
| Fields | Prefix | Required | Remarks |
|---------|--------|:--------:|---------|
| `INDEX` | No prefix | | The task at this index in the displayed task list is edited. The index must be a positive integer 1, 2, 3, … , 2147483647. |
-| `TAG` | `t/` | | The tag to be added to the task. |
-| `MORE_TAGS` | `t/` | | Additional tag(s) to be added to the task. |
+| `TAG` | `t/` | | The tag to be added to the task. Tags should only contain alphanumeric characters. |
+| `MORE_TAGS` | `t/` | | Additional tag(s) to be added to the task. Tags should only contain alphanumeric characters. |
{: .field-table}
- A tag is uniquely identified by the `TAG`. This field is case sensitive.
+- You may add multiple tags to a task by specifying the `t/` prefix multiple times.
Example:
-- `addTagTask 1 t/day1 t/day2`.
+- `addTagTask 1 t/day1 t/day2`
![addTagTask success](images/output/addTagTask_success.png)
- *CoordiMate adds tag day2
to the task at the index 1
, while day1
is not added because it already exists in the list of tags. *
+ *CoordiMate adds tag day2
to the 1st task, while day1
is not added because it already exists in the list of tags. *
Potential Errors:
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that the index and tag are both specified. The index should be correctly specified as an integer.
-`Tags names should be alphanumeric` | Ensure that the tag is specified and is alphanumeric.
+`Invalid command format! …` | Ensure that the index and tag are both specified. The index should be correctly specified as an integer.
`The task index provided is invalid` | Ensure that the index provided is within the valid range.
+`Tags names should be alphanumeric` | Ensure that the tags specified are alphanumeric.
-#### 3.3. Listing all tags: `listTag`
-
[Back to Table of Contents](#table-of-contents)
-You can view the tags in your contact list and task list and their frequencies, so that you can keep track of the tags you have used.
+#### 3.3. Listing all tags: `listTag`
+
+You can view the tags in your contact list and task list, along with their frequencies, so that you can keep track of the tags you have used.
Format:
@@ -1170,10 +1184,10 @@ ltag
-#### 3.4. Finding persons and tasks with any matching tag(s): `findTag`
-
[Back to Table of Contents](#table-of-contents)
+#### 3.4. Finding persons and tasks with any matching tag(s): `findTag`
+
You can extend your search with keywords, so that you can locate any person or task with at least one matching tag.
Format:
@@ -1192,7 +1206,7 @@ ftag
| Fields | Prefix | Required | Remarks |
|--------|--------|:--------:|---------|
-| `KEYWORD` | No prefix | | The keyword to search for tags.|
+| `KEYWORD` | No prefix | | Keyword to search for tags.|
| `MORE_KEYWORDS` | No prefix | | Additional keyword(s) to search for tags.|
{: .field-table}
@@ -1203,29 +1217,29 @@ ftag
This command hides all persons and tasks that do not match the search criteria.
(i.e. If no persons or tasks match the search criteria, the list will be empty.)
-To reset the Persons and Tasks view, simply run the listAll
command to list all persons and tasks.
+To reset the persons and tasks view, simply run the listAll
command to list all persons and tasks.
" %}
Example:
-- `findTag catering orientation`
+- `findTag Catering Orientation`
![findTag_success](images/output/findTag_success.png)
- *CoordiMate finds all persons and tasks matching any of catering
or orientation
tags. *
+ *CoordiMate finds all persons and tasks matching any of Catering
or Orientation
tags. *
Potential Error:
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that a keyword is provided.
+`Invalid command format! …` | Ensure that a keyword is provided.
-#### 3.5. Finding persons and tasks with all matching tag(s): `findAllTag`
-
[Back to Table of Contents](#table-of-contents)
+#### 3.5. Finding persons and tasks with all matching tag(s): `findAllTag`
+
You can narrow your search using multiple keywords, so that you can find only those contacts and tasks that include every tag you need.
Format:
@@ -1244,7 +1258,7 @@ fatag
| Fields | Prefix | Required | Remarks |
|--------|--------|:--------:|---------|
-| `KEYWORD` | No prefix | | The keyword to search for tags.|
+| `KEYWORD` | No prefix | | Keyword to search for tags.|
| `MORE_KEYWORDS` | No prefix | | Additional keyword(s) to search for tags.|
{: .field-table}
@@ -1255,30 +1269,30 @@ fatag
This command hides all persons and tasks that do not match the search criteria.
(i.e. If no persons or tasks match the search criteria, the list will be empty.)
-To reset the Persons and Tasks view, simply run the listAll
command to list all persons and tasks.
+To reset the persons and tasks view, simply run the listAll
command to list all persons and tasks.
" %}
Example:
-- `findAllTag catering orientation`
+- `findAllTag Catering Orientation`
![findAllTag_success](images/output/findAllTag_success.png)
- *CoordiMate finds persons and tasks matching all of catering
and orientation
in their tag(s). *
+ *CoordiMate finds persons and tasks matching all of Catering
and Orientation
in their tag(s). *
Potential Error:
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that a keyword is provided.
+`Invalid command format! …` | Ensure that a keyword is provided.
-#### 3.6. Deleting tag(s) from a person: `deleteTagPerson`
-
[Back to Table of Contents](#table-of-contents)
-You can delete tag(s) from a person in your contacts list, so that you can remove unwanted or irrelevant tags.
+#### 3.6. Deleting tag(s) from a person: `deleteTagPerson`
+
+You can delete tag(s) from a person in your contact list, so that you can remove unwanted or irrelevant tags.
Format:
@@ -1296,8 +1310,9 @@ dtagp
| Fields | Prefix | Required | Remarks |
|--------|--------|:--------:|---------|
-| `INDEX` | No prefix | | The person at this index in the displayed person list is edited. The index must be a positive integer (i.e. 1, 2, 3, … , 2147483647). |
-| `TAG` | `t/` | | Tag(s) to be deleted for the person.|
+| `INDEX` | No prefix | | The person at this index in the displayed contact list is edited. The index must be a positive integer (i.e. 1, 2, 3, … , 2147483647). |
+| `TAG` | `t/` | | Tag to be deleted from the person. Tags should only contain alphanumeric characters. |
+| `MORE_TAGS` | `t/` | | Additional tag(s) to be deleted from the person. Tags should only contain alphanumeric characters. |
{: .field-table}
- You may delete multiple tags from a person by specifying the `t/` prefix multiple times.
@@ -1314,16 +1329,16 @@ dtagp
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that the index is correctly specified as an integer. At least one tag must be specified.
+`Invalid command format! …` | Ensure that the index is correctly specified as an integer. At least one tag must be specified.
`The person index provided is invalid` | Ensure that the index specified is in the range of the displayed number of persons.
-`Tags names should be alphanumeric` | Ensure that the tags specified are alphanumeric and not empty. Whitespaces are trimmed, but spaces between characters are not allowed.
+`Tags names should be alphanumeric` | Ensure that the tags specified are alphanumeric.
-#### 3.7. Deleting tag(s) from a task: `deleteTagTask`
-
[Back to Table of Contents](#table-of-contents)
+#### 3.7. Deleting tag(s) from a task: `deleteTagTask`
+
You can delete tag(s) from a task in your task list, so that you can remove unwanted or irrelevant tags.
Format:
@@ -1343,7 +1358,8 @@ dtagt
| Fields | Prefix | Required | Remarks |
|--------|--------|:--------:|---------|
| `INDEX` | No prefix | | The task at this index in the displayed task list is edited. The index must be a positive integer (i.e. 1, 2, 3, … , 2147483647). |
-| `TAG` | `t/` | | Tag(s) to be deleted for the task.|
+| `TAG` | `t/` | | Tag to be deleted from the task. Tags should only contain alphanumeric characters. |
+| `MORE_TAGS` | `t/` | | Additional tag(s) to be deleted from the task. Tags should only contain alphanumeric characters. |
{: .field-table}
- You may delete multiple tags from a task by specifying the `t/` prefix multiple times.
@@ -1360,20 +1376,20 @@ dtagt
Error message | How to resolve
---------------|---------------
-`Invalid command format!…` | Ensure that the index is correctly specified as an integer. At least one tag must be specified.
+`Invalid command format! …` | Ensure that the index is correctly specified as an integer. At least one tag must be specified.
`The task index provided is invalid` | Ensure that the index specified is in the range of the displayed number of tasks.
-`Tags names should be alphanumeric` | Ensure that the tags specified are alphanumeric and not empty. Whitespaces are trimmed, but spaces between characters are not allowed.
+`Tags names should be alphanumeric` | Ensure that the tags specified are alphanumeric.
---
+[Back to Table of Contents](#table-of-contents)
+
### 4. General Commands
#### 4.1. Viewing help: `help`
-[Back to Table of Contents](#table-of-contents)
-
You can view a link to access the user guide at any time, so that you can refer to documentation to understand the existing features.
Format:
@@ -1397,10 +1413,10 @@ h
-#### 4.2. Listing all persons and tasks: `listAll`
-
[Back to Table of Contents](#table-of-contents)
+#### 4.2. Listing all persons and tasks: `listAll`
+
You can list all persons and tasks in your contact list and task list at the same time.
Format:
@@ -1424,10 +1440,10 @@ la
-#### 4.3. Exiting the program: `exit`
-
[Back to Table of Contents](#table-of-contents)
+#### 4.3. Exiting the program: `exit`
+
You can exit the application, so that you can close the application window and stop the program.
Format:
@@ -1452,10 +1468,34 @@ e
-## FAQ
+[Back to Table of Contents](#table-of-contents)
+
+## Editing CoordiMate's Data
+
+CoordiMate's data is stored on your computer as a file located at `[JAR file location]/data/addressbook.json`.
+
+Advanced users can edit this file directly to make changes to the data stored by CoordiMate.
+
+After editing the data file, you can restart CoordiMate to see the changes reflected in the application.
+
+{% include admonition.html type="warning" title="Warning" body="
+
+If your changes to the data file makes its format invalid, CoordiMate will not be able to load the data file, resulting in the contact and task lists being empty.
+
+Always make a backup before you edit!
+
+" %}
+
+
+
+---
+
+
[Back to Table of Contents](#table-of-contents)
+## Frequently Asked Questions (FAQ)
+
{% include admonition.html type="question" title="Question" body="
Q: How do I backup/restore my data?
@@ -1478,18 +1518,18 @@ To restore from a backup data file:
-## Glossary
-
[Back to Table of Contents](#table-of-contents)
+## Glossary
+
### Alphanumeric
A combination of letters and numbers only, no spaces or special characters.
-For more information, see Alphanumericals on Wikipedia.
-
Example: For tags, entries like `day1` or `day2` are valid, while entries like `day 1` or `day-2` are invalid.
+For more information, see Alphanumericals on Wikipedia.
+
### American Standard Code for Information Interchange (ASCII)
The American Standard Code for Information Interchange (ASCII) is a character encoding standard that is well understood by computers.
@@ -1503,7 +1543,7 @@ For more information, see
---
-## Known Issues
-
[Back to Table of Contents](#table-of-contents)
+## Known Issues
+
{% include admonition.html type="bug" title="Known Issue" body="
Issue: CoordiMate does not open on the correct screen.
@@ -1566,12 +1610,12 @@ Example: In a list of 3 alphabets containing (“a”, “b”, “c”) in that
+[Back to Table of Contents](#table-of-contents)
+
## Command Summary
### Managing Persons
-[Back to Table of Contents](#table-of-contents)
-
Action | Format | Example | Alias
--------|--------|---------|------
[**Add Person**](#11-adding-a-person-addperson)| `addPerson n/NAME p/PHONE_NUMBER e/EMAIL a/ADDRESS [t/TAG]…` | `addPerson n/John Doe p/98765432 e/johnd@example.com a/John street, block 123, #01-01` | `ap`
@@ -1583,10 +1627,10 @@ Example: In a list of 3 alphabets containing (“a”, “b”, “c”) in that
-### Managing Tasks
-
[Back to Table of Contents](#table-of-contents)
+### Managing Tasks
+
Action | Format | Example | Alias
--------|--------|---------|------
[**Add Task**](#21-adding-a-task-addtask) | `addTask T/TITLE n/NOTE [t/TAG]` | `addTask T/Get Flowers n/Wedding Anniversary` | `at`
@@ -1603,10 +1647,10 @@ Example: In a list of 3 alphabets containing (“a”, “b”, “c”) in that
-### Managing Tags
-
[Back to Table of Contents](#table-of-contents)
+### Managing Tags
+
Action | Format | Example | Alias
--------|--------|---------|------
[**Add Tag(s) to a Person**](#31-adding-tags-to-a-person-addtagperson) | `addTagPerson INDEX [t/TAG]…` | `addTagPerson 1 t/friends` | `atagp`
@@ -1619,10 +1663,10 @@ Example: In a list of 3 alphabets containing (“a”, “b”, “c”) in that
-### General
-
[Back to Table of Contents](#table-of-contents)
+### General
+
Action | Format | Example | Alias
--------|--------|---------|------
[**View Help**](#41-viewing-help-help) | `help` | `help` | `h`
diff --git a/docs/_sass/minima/_layout.scss b/docs/_sass/minima/_layout.scss
index ca99f981701..7fd58942c6c 100644
--- a/docs/_sass/minima/_layout.scss
+++ b/docs/_sass/minima/_layout.scss
@@ -176,8 +176,8 @@
.post-content {
margin-bottom: $spacing-unit;
- h1, h2, h3 { margin-top: $spacing-unit * 2 }
- h4, h5, h6 { margin-top: $spacing-unit }
+ h1 { margin-top: $spacing-unit * 2 }
+ h2, h3, h4, h5, h6 { margin-top: $spacing-unit }
h2 {
@include relative-font-size(1.75);
diff --git a/docs/assets/css/style.scss b/docs/assets/css/style.scss
index 2531665ca45..6c88c2f8e83 100644
--- a/docs/assets/css/style.scss
+++ b/docs/assets/css/style.scss
@@ -1,8 +1,9 @@
---
# Only the main Sass file needs front matter (the dashes are enough)
---
+//@@author jiakai-reused
-// Adapted from: https://stackoverflow.com/a/39156436
+// Solution below adapted from https://stackoverflow.com/a/39156436
$baseurl: "{% if site.baseurl != '/' %}{{ site.baseurl }}{% endif %}";
@import
@@ -14,3 +15,18 @@ $baseurl: "{% if site.baseurl != '/' %}{{ site.baseurl }}{% endif %}";
height: 21px;
width: 21px
}
+
+// Style below adapted from https://developer.mozilla.org/en-US/docs/Web/HTML/Element/kbd
+
+kbd {
+ background-color: #eee;
+ border-radius: 3px;
+ border: 1px solid #b4b4b4;
+ color: #333;
+ display: inline-block;
+ font-size: 0.85em;
+ font-weight: 700;
+ line-height: 1;
+ padding: 2px 4px;
+ white-space: nowrap;
+}
diff --git a/docs/images/output/addPerson_success.png b/docs/images/output/addPerson_success.png
index dc92afd1b41..8eb7aa68b38 100644
Binary files a/docs/images/output/addPerson_success.png and b/docs/images/output/addPerson_success.png differ
diff --git a/docs/images/output/findAllTag_success.png b/docs/images/output/findAllTag_success.png
index 2c46b985ab0..7ad72e1d831 100644
Binary files a/docs/images/output/findAllTag_success.png and b/docs/images/output/findAllTag_success.png differ
diff --git a/docs/images/output/findTag_success.png b/docs/images/output/findTag_success.png
index af32daa19ab..8492635c69d 100644
Binary files a/docs/images/output/findTag_success.png and b/docs/images/output/findTag_success.png differ
diff --git a/docs/images/output/listPerson_success.png b/docs/images/output/listPerson_success.png
index 775ffd91acf..1687555974f 100644
Binary files a/docs/images/output/listPerson_success.png and b/docs/images/output/listPerson_success.png differ
diff --git a/docs/images/output/listTask_success.png b/docs/images/output/listTask_success.png
index daf1752a01a..e3a33a82a1a 100644
Binary files a/docs/images/output/listTask_success.png and b/docs/images/output/listTask_success.png differ