High-level description of the app's main features, serving as a reference for where we'd eventually like it to be rather than as an outline of requirements for MVP.

1. Main pages
   1. Feed
      1. User (home) feed
      2. Tag feed
   2. Search Results
   3. Onboarding/generic front page
   4. create/edit recipe
   5. create/edit menu
   6. menu page
      1. in-page
      2. archive?
   7. Viewing recipe page
   8. recipe archive page
   9. profile page
2. Recipe Text editor
   1. Autocomplete
      1. "#*" Recipe tagging command. typing ["#" + userString] will trigger req. for tag suggestions across 5 categories
         1. Func. Details:
            1. Matching recipe tag/title from user-owned recipes [fuzzy search ⇒ edit distance of 1.]
            2. Matching popular recipe tags (linked to a feed of recipes with matching tag)
               1. First result always is an exact match of the query string, for example typing "#hollan" may return something like:
                  1. hollan
                  2. hollandaise
                  3. hollandaise sauce
            3. Matching recipe tag/title from user's menus
            4. Matching recipe tag/title across recipes from user's network
            5. Matching recipe tag/title from public domain
         2. Challenges —
            1. this is a lot of different searches triggered by every change in user input after a hashbang.
               1. Slow response times
               2. High server load
               3. Res. data is outdated
            2. How to organize this cleanly from a UX perspective
      2. "+*" ingredient tagging command. Typing ["+" + userString] will trigger req for ingredient suggestions
         1. Func. Details:
            1. Will include a matched list of possible ingredients
               1. Rules for refining the list size (max. 8-10 results) are not yet defined.. Possibilities:
                  1. Matches refined to list of 8-10 results based on ingredient frequency
                  2. Res. refined through Bayesian inference
               2. Create a new ingredient option
            2. (after ingredient is selected), record measurement
               1. Field contains number/text input + measurement-type. Values are ideally prepopulated:
                  1. using Naive NLP
                  2. Or uses predefined parsing rules on client side, attempting to match words in the step against a hash table of common measurements.
               2. Option to skip recording
            3. Ingredient is subsequently recorded in the ingredients list with associated measurements, if applicable.
               1. If measurement is explicitly stated within the steps, ideally the listing in the ingredients section and in the steps are "symlinked", such that changes in one section will prompt/suggest the user to make a similar change in the "linked" section.
                  1. Eg. Step 1 calls for "add 500g of sugar"; the ingredients list includes 500g of sugar; Updating to 700g of sugar in the ingredient list will suggest a similar change to the writing in step 1. UX might be a highlight of the measures of sugar contained in the steps.
         2. Challenges:
            1. Convoluted UX
            2. Bad data, highly unstructured; unable to link string in steps to ingredients with high enough accuracy. Will need to be linked with special character within strings rather than separated as an object property within WYSIWYG object??
            3. A lot of different situations to account for
               1. Handling common ingredient in multiple steps
            4. Could be lots of work for minimal benefit — testing required
   2. Text-types include:
      1. bold
      2. underline
      3. italic
      4. links?
      5. Lists
3. Search
   1. Reusing some of the autocomplete functionality listed in [2.a]
   2. Filtering
      1. Query for matching recipe title and/or tag
      2. contains/excludes ingredient(s)
      3. By special recipe tags (?) - Vegetarian, vegan, nut free, gluten-free, on a budget (?)
      4. By menu ?
      5. Search for user?
   3. Sorting options ?
4. Identity management
   1. Can create user account
      1. Traditional way:
         1. Create unique used_id + password +email.
         2. Receive account confirmation email
      2. Through third-party —
         1. Google
         2. Pintrest
         3. Facebook
   2. Sign into user-account
      1. Traditional sign-in
      2. Third party sign-in
      3. Magic link
   3. Delete user account
   4. Admin features
5. Member features
6. Feed
7. Recipe/menu page
8. ML problems