-
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
Static file default paths #35
Comments
The
It's just a matter of taste isn't it? E.g. semantic-ui uses
In my opinion it would be not consistent to use full names for |
I agree with the naming. I just thought it will be easier for new developers to be able to just copy and paste the files from bootstrap and html5 boilerplate. With rails they have a folder called public where they put their static files and the route is at root which will work the correct way with a robots.txt file They use dedicated folders for stylesheets, javascript, and images. Rails automatically creates the links to files in stylesheets and javascript folder. They also have a feature called asset pipeline which merges the stylesheets and javascript files into one file. The route for javascript, stylesheets, and images are at example.com/assets A feature like Asset Pipeline would be nice for Goal |
Maybe we can have the static path route to root and add a folder called assets to the static folder and have paths like |
@Davidhunter Support of a tool for merging static assets is not the highest priority right now (third party ones from JS or Ruby world still can be used). |
@Davidhunter Thanks, done. |
The default path for static files are at example.com/static/styles/app.css. Maybe it should be at root directory example.com/styles/app.css.
If someone adds a robots.txt file in the static folder it would be at example.com/static/robots.txt. I read that the robots.txt file should be at root example.com/robots.txt
I also think it would be nice to follow twitter bootstrap and html5 boilerplate naming of javascript and css folders. They use /css/main.css and /js/main.js
The text was updated successfully, but these errors were encountered: