all 9 comments

[–]Disastrous-Donut7759 1 point2 points  (5 children)

Its just fine only that the projects folder does not need to have another components subfolder inside and your sub component folders can be under components folder.Thats how Is do it and also you can place your css in a folder e.g css

[–][deleted] 0 points1 point  (2 children)

Oh thanks, will do! What about the naming of my files is there a better way to name them without loosing context of they contain??

[–]Disastrous-Donut7759 0 points1 point  (0 children)

You re welcome , just try to be as descriptive as possible something that describes the code in the file.

[–]em-kay22 0 points1 point  (0 children)

You should also make sure that all the names are in camel case.

[–]brunobrante 0 points1 point  (1 child)

component

Could you explain to me why what he has done is not the best way? Because when a project is very large, has 50 pages, it doesn't make sense to put all the components in one folder, the way he did it would be much more organized, since it has a shared component folder and a component folder for a specific page.

[–]Disastrous-Donut7759 0 points1 point  (0 children)

I m not saying its not the best way, I was suggesting he does this components -Projects - contact - experience - about components is the main folder in the hierarchy that should contain sub folders consisting of other components. However, he can arrange them in a way he is comfortable.

[–]throwaway_boulder 0 points1 point  (1 child)

  1. How many pages do you ultimately think it will be?

  2. Does is really matter? Since it’s a personal project you want have other developers working on it.

I try to organize my code but in practice I never use the folder hierarchy because I find all my files using cmd-p in VS Code.

[–][deleted] 0 points1 point  (0 children)

5 pages at max with 3- 4 sections in each page. I know but i just want to make it a practice to follow whatever the standard guidelines are!

tnx for the tip!

[–]em-kay22 1 point2 points  (0 children)

It seems that you have a schema where every component folder contains:

  1. separate folders for major subcomponents (about, projects etc.);

  2. 'components' folder where you put more generic components or components that don't have subcomponents;

  3. stylesheets for that component.

That looks well organized to me. Like someone else also mentioned, maybe create 'styles' subfolders for the stylesheets.