If the user creates account, redirect to /setup, if the user logs in, this means considering he hasn't been redirected to /setup, that he has role USER. However, this is contingent on this fact that NEWBIES cannot even reach login endpoint, which is not elegant. Consider other ways to solve this

Since using a traditional backend, using the MVC pattern would be a good idea.

Read more on this here: https://medium.com/@thejasonfile/dumb-components-and-smart-components-e7b33a698d43

Store objects such as icons, user inputted images, as well as possibly the downloadable (HTML, CSS, JS) files linked to a users account.

Use imports like

import { Loader } from “components/loader”

instead of

import { Loader } from “../components/loader”

When a user is in NEWBIE phase (role), he should always be redirected to /setup. Solving this with localStorage is possible, but not elegant.

Grant users permission to bypass waitlist through email

everything in the backend in the production/aws-ec2 branch works just perfectly except settings cookies and maybe also retrieving them but I think only setting them is the problem. The cookies are set in CustomAuthenticationSuccessHander.java where the problem lies. Everything except setting cookie works

By removing image I mean removing that image location, but still allowing the user to hover over that area to re add a new image

Bare bones, low css. Some people like this.

All items must be editable, next, u need to allow things to be removed or added in a section, then u need to allow entire sections to be added and removed

Make a simple email template, for verification emails and unsubscribe emails.

1.)When the user logs in w/ oauth, his session id is deleted, and then redirects him to login, when he reauth's with oauth, it sends him to a localhost:8080 error endpoint. This is a new error.
2.)Some other form related auth issues

Create a modal when the user clicks remove page, which asks them to confirm they want to remove it. When they click confirm, the page card is replaced with a loader equivalent in size it takes, it fires based on the theme to a certain function which deletes all the rows from the theme tables for that user, as well as if there are any deployments.

pre requisites: allow deletion of custom domain websites because if this is not a function, when they delete their web builder from codefoli, their website will still be deployed on a custom domain which we are paying for the infrastructure not being used.

move away from this type of type model. The methods should be returning a single type of JSON format. Each method can have its own type of JSON format, but for any return case, it should adhere to this. And this means we should be saying if the return.status === 'OK' or something. Not checking solely if response.ok is true in frontend. This is a more mundane task, so do this when ur just bored or something.

We will have all pages done and dynamic once this is complete, and from here, will need to enable editing vs preview mode, which will allow each component to be edited

All logic will be on frontend, we will simply emulate what the users page will look like. And as far as the editing goes, since we're not storing any files in a bucket storage, this means we will need a user column for every editable thing on the users page. For downloading, the build process will take place on the backend, and the build logic will be comparable to the preview frontend logic.

Later, we will allow them to put their name servers in so the link can be custom

#8 the tailwind migration pull request moves all css to tailwind, and it is all fine, however, the header and home components styling for smaller screens is not proper and must be fixed.

Make each section a component, and dashboard (home) and about can have any section (FAQ, core values, skills and services, story, resume, and more sections to be made). Contact and projects will be more locked down 👌

Some components such as Setup.tsx are as large as 1,000+ lines of code. This is not maintainable for big changes, and is bad practice. Additionally, we should centralize some redundant functions, such as possibly update text handlers, this could likely be a single function with different parameter options as the parameter type.

Finished the bulk of the sectionifying the home page, next, I put the + button above each sections loop and below the loop itself. Also, need to add the - for each section

The cards need to work properly on md and large screens too. The files that will need to be changed to fix this will be SkillServiceCards.tsx and Card.tsx.

and probably remove the add section component in about altogether

https://github.com/noahgsolomon/Codefolio-frontend/blob/e01cfbd8327c813b299a52f5405540c59560bf79/src/auth/isAuthenticated.tsx#L1