sonnyding1 / cs35l-egg Goto Github PK

Optionally, we can have a landing page for all logged out users to see. The landing page should contain a hero section, some sections that display our features, and a call to action section that redirects users to visit the community page, and also prompt them to sign up or log in.

When the backend file API endpoints are finished, remap the edit page "save" shortcut key to save the file to backend. Also add "download", which actually downloads files to local.

Implement undo/redo shortcut keys in edit page. This might be more complicated than it seems, we might have to implement a "kill ring" of some sort along with the shortcut keys. Also, when a user deletes 3 words by pressing and releasing delete key 2 times, does that count as 1 operation that can be undone? We might need to look into how to determine what exactly is 1 operation.

We may have a better 404 page.

The table component will be used in home page, community page, like page. Look into Tanstack table.

A user profile page should be a form that allows users to edit their profile pictures and names for now.

we might not do it due to time or money constraints though

Make a file name in edit page, and make that file name editable. For now, save the file name in a useState, and on save to a local file, save the file using that file name.

To ensure we have enough space for all the features for editing a document, consider adding a menu bar on edit page. Consider using this component from ShadCN.

CRUD operations for the comment model, including:

• create a new comment
• get all comments of a file
• update a comment
• delete a comment

this one is purely for fun lol

Refer to the user model, and write logic inside google endpoints to create new users or get user info. Also make sure to add usernames into session.

We can make the nav bar buttons uniform, move "Egg" to the left to make space for the user profile on the right.

Have a circular user profile if the user is logged in. On clicking the profile, it opens a dropdown that shows options for "profile" which links to a profile page, and "logout" which calls the logout function from the backend. If the user is not logged in, display 2 buttons, log in and sign up, respectively.

The file model should have: file name, content, username (the name of the owner of the file)