markdown formatting
This commit is contained in:
parent
95330d2c8b
commit
f37dc07b69
@ -18,8 +18,8 @@ Because choices are good
|
|||||||
#### What do we want it to do?
|
#### What do we want it to do?
|
||||||
|
|
||||||
1. Ask the user to select the Area and Category.
|
1. Ask the user to select the Area and Category.
|
||||||
1.1 Offer the user a list of current Areas/Categories to select by number
|
1.1 Offer the user a list of current Areas/Categories to select by number
|
||||||
1.2. If a selected slot is labeled `[unused]`, ask the user to supply a name and update the Index
|
1.2. If a selected slot is labeled `[unused]`, ask the user to supply a name and update the Index
|
||||||
2. Ask the user to name the new ID
|
2. Ask the user to name the new ID
|
||||||
3. Give the user their new ID complete with name for easy copy/paste
|
3. Give the user their new ID complete with name for easy copy/paste
|
||||||
4. Update the relevant files
|
4. Update the relevant files
|
||||||
@ -29,7 +29,7 @@ Because choices are good
|
|||||||
#### How do we want to store the data?
|
#### How do we want to store the data?
|
||||||
|
|
||||||
* Store the data in JSON; Generate a new Index each time, or don't, and let the user manually update the Index; offer the option
|
* Store the data in JSON; Generate a new Index each time, or don't, and let the user manually update the Index; offer the option
|
||||||
* This option would allow a local JS-flavored web view of the Index
|
* This option would allow a local JS-flavored web view of the Index
|
||||||
* Store the data in the text Index; update the Index whenever a new ID is generated; can break the script if the Index format gets screwed up
|
* Store the data in the text Index; update the Index whenever a new ID is generated; can break the script if the Index format gets screwed up
|
||||||
* Store the data in a database; this is most likely overkill
|
* Store the data in a database; this is most likely overkill
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user