A simple rack web layer for delivering rendered static files.
$ gem install flatrack
$ flatrack new my-website
You should have 4 directories:
- assets
- layouts
- pages
- partials
Location of sprockets assets, flatrack comes with Sass and Coffeescript out of the box.
- images
- javascripts
- stylesheets
Pages are the guts of your site, this is what your users will ultimately see. Basically put your content here.
Layouts are the skin of your site, it's what takes all those guts that your users need and crave and puts them in a nice pretty layout for them to enjoy.
You can also define a custom layout using the following syntax:
<!-- /pages/my-view.html.erb -->
<%- use_layout :custom_layout %>
<p>Hello World</p>
$ flatrack start
Anything in /pages maps to a URL at /, root of a directory will always map to the index.html.* file in it.
for example
GET /foo.html would map to /pages/foo.html.erb, the erb (or any other format) is optional if you wish to render your pages dynamically.
Pull Request to add yours!
git checkout -b my-new-feature)git commit -am 'Add some feature')git push origin my-new-feature)FAQs
Unknown package
We found that flatrack demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
OpenSSF has published OSPS Baseline, an initiative designed to establish a minimum set of security-related best practices for open source software projects.
Security News
Michigan TypeScript founder Dimitri Mitropoulos implements WebAssembly runtime in TypeScript types, enabling Doom to run after processing 177 terabytes of type definitions.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.