-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restructure front end #1
Comments
Todo: build.sh
|
Todo: Client Views
|
Todo: Scripts and Styles
|
Todo: Third Party Dependencies
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We had a brief conversation on Facebook this morning about restructuring the front end. Then @mmitton and I discussed it a little in a PM.
The current goal is to make the front end a little more developer friendly. And the end user code bandwidth friendly.
What we are leaning towards is creating a client directory. Our code for the front end will rest in there. In it will be a package.json. This will have all our third party front end dependencies listed, our dev dependencies, etc. Devs who wish to maintain the client will need to install Node.js and run
npm install
. Running saynpm run build
or something like it could build the source and put a distribution version in the root of the client. Doing this we can minify the source, make tests, lint, etc. And the source will be restructured to be easier to maintain in an editor and we can have some automated quality control of the client.Both the source and distribution will be provided on the repo. Minus the node_modules directory which contain the unbuilt dependencies.
The html directory is being untouched for the current time. Until we make this transition completely. Afterwords it will be removed and you would develop out of client/src and your source will build to client directory.
The only changes on the server side would be path changes. And the end users would only notice path/file changes and nothing would be different for them.
If anyone has any objections, suggestions, changes, etc to this plan please feel free to comment.
The text was updated successfully, but these errors were encountered: