![]() If someone has to do adjustments to the chat-window, what is more clear than having a chat-window folder? The following examples are for an Angular project, but your base structure should be framework agnostic. Any developer starting to work in your code base should find their way easily. It will have messages, a chat window and maybe a settings panel. Let’s say it is a chat application we are building. You will benefit from a flat, feature based folder structure. Now you really have to think about how you can divide your application into features. Now we would have something like this: /app index.html main.js Most files that will go in the root of your webserver could go here (like the favicon and stuff like that). ![]() A javascript web app will probably have something like a main.js, from where all modules are loaded, or the initial page load is handled. A lot of project will have an index.html, put it in the root. So we could now have: /app /node_modules gulpfile.js package.json. I think this is a good practice, because the non-application files can become quite a lot. This is to seperate the app folder from the development tooling (gulp, npm etc.). ![]() How do we go about this in a front-end application? Base structureĪ lot of project scaffolds put the application code itself into a sub folder, mostly called ‘app’. I enjoy working in a neatly structured project. I have always been very picky about a good folder structure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |