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

Main Catalog Page (Frontend) and Integrate w/ Backend #9

Closed
ThatMegamind opened this issue Jan 3, 2024 · 0 comments · Fixed by #20
Closed

Main Catalog Page (Frontend) and Integrate w/ Backend #9

ThatMegamind opened this issue Jan 3, 2024 · 0 comments · Fixed by #20
Assignees
Labels

Comments

@ThatMegamind
Copy link
Collaborator

ThatMegamind commented Jan 3, 2024

Instructions

  • We don’t have the lo-fi design for this page yet, but for now we’ll just create a placeholder page to allow us to implement some key functionality and remove potential bottlenecks
  • This will serve as the primary page for users accessing the Catalog, which will (eventually) allow users to view catalog events, add new events, sort/query events, and add an event from the Catalog to the Published Schedule
  • For now though, this page will be comprised of a simple table with the following headers: Title, Host, Cohort Type, Event Type, Subject, and Description
  • The page should utilize the backend routes created in previous tasks to populate the table with the data currently in the Catalog table in the database

Notes

  • You can verify the page is correctly populating by checking the database as well
  • Make sure to use ChakraUI components and styling over standard HTML/CSS whenever possible
  • Add your new page in a new subfolder called pages (i.e. the route should be /src/pages/YourFolder/YourFiles)

Acceptance Criteria

  • All the data from the catalog table is visible in the frontend

Resources

As always, feel free to message Michael and Michelle if you have any questions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants