I'm trying to come up with a file structure that is simple and future proof:
scaffolding-front-end
├ client
│ ├ scripts
│ ├ styles
│ └ templates
├ private
├ public
├ server
├ test
│ ├ functional
│ └ unit
└ vendor
right now the project would have only these basic folders: client, public and test.
the private and server ones would be created only if the project ended up being converted to a dynamic one, thus with back end stuff.
the public folder is the one every generated asset would go, just like a build or dist folder. I called it public because it's already the name chosen by other projects.
this whole structure was inspired by Meteor projects, which seems to be really clean and tidy!
I'm trying to come up with a file structure that is simple and future proof:
right now the project would have only these basic folders:
client
,public
andtest
.the
private
andserver
ones would be created only if the project ended up being converted to a dynamic one, thus with back end stuff.the
public
folder is the one every generated asset would go, just like abuild
ordist
folder. I called itpublic
because it's already the name chosen by other projects.this whole structure was inspired by Meteor projects, which seems to be really clean and tidy!