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

Notion - Content Management System #190

Closed
8 of 12 tasks
DBprassan12 opened this issue Jul 18, 2021 · 0 comments
Closed
8 of 12 tasks

Notion - Content Management System #190

DBprassan12 opened this issue Jul 18, 2021 · 0 comments
Assignees
Labels
backend Task must have a back end issue documentation Improvements or additions to documentation epic This issue is a large body of work that is broken down into a number of smaller tasks

Comments

@DBprassan12
Copy link

DBprassan12 commented Jul 18, 2021

Notion will be used as a Content Management System.

We will store images and associated information of everyday food characters, superhero food characters and recipes in a Notion workspace, from which the client will be able to add, edit or delete food characters or recipes.

Notion workspace requirements:

  • There should be a table for managing the everyday food characters. The following data should be stored with every everyday food character record:
    • What location in Tucker Island the character is associated with
    • The "About", "Likes..." and "Recipe" information
    • The associated superhero food character with its image
      • The "Superpowers", "Use" and "Likes..." information of that superhero food character
  • There should be a table for managing recipes. The following data should be associated with every recipe:
    • Ingredients
    • Equipment
    • The recipe steps with associated images.

Note: Please refer to the Superhero Foods Handbook and Let's Cook handbook respectively for best understanding these requirements as the information on certain pages of this book reflect the information that needs to be shown to the user in the app.

Part 1

  • Setup notion workspace for Foodbank
  • Setup notion API (Create an integration - Use internal integration for now)
  • Share a database with your integration

Part 2

  • Create two tables - one for food characters and one for recipes
  • Populate the Notion tables with some characters and recipes respectively (Add some item to the database) (We still need to confirm if all assets are up to date with their current branding.)
    • You could just do either one for now - characters or recipes, to start off with and and continue with the rest of the steps to see that the integration stuff works or not.
  • Add the required fields for every record in each of the tables.

Part 3 (Integration)

  • Integrate the characters table with the characters page of the locations in the tucker island (homepage) (Depending on issue Create Characters page #26. Will be integrated once it's done)
  • Integrate the recipes table with the recipes page.
  • Integrate the recipe page
  • Integrate the View All steps page
  • Integrate the Let's Cook page
  • Test if all assets are being scaled and pulled accordingly

For more information, please reference https://developers.notion.com/docs
This video has a very helpful demonstration on how to fetch data from a notion database using NextJS:
https://www.youtube.com/watch?v=YMbQxavquKc

The following video may be useful for setting up notion API: https://www.youtube.com/watch?v=zVfVLBjQuSA

@DBprassan12 DBprassan12 added backend Task must have a back end issue documentation Improvements or additions to documentation labels Jul 18, 2021
@HereItGoes HereItGoes self-assigned this Jul 18, 2021
@HereItGoes HereItGoes removed their assignment Nov 13, 2021
@CodeWithTheDoctor CodeWithTheDoctor changed the title Notion - Client Management Interface Notion - Content Management System Nov 26, 2021
@innoc3ntt innoc3ntt self-assigned this Nov 27, 2021
@innoc3ntt innoc3ntt removed their assignment Nov 27, 2021
@CodeWithTheDoctor CodeWithTheDoctor added the epic This issue is a large body of work that is broken down into a number of smaller tasks label Dec 3, 2021
@CodeWithTheDoctor CodeWithTheDoctor assigned x4wiz and unassigned j-vanrav and bryce-oc Dec 4, 2021
@innoc3ntt innoc3ntt self-assigned this Dec 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Task must have a back end issue documentation Improvements or additions to documentation epic This issue is a large body of work that is broken down into a number of smaller tasks
Projects
None yet
Development

No branches or pull requests

7 participants