-
-
Notifications
You must be signed in to change notification settings - Fork 6
Headers and footers
Greg Bowler edited this page Sep 7, 2018
·
5 revisions
// TODO: Useful to have site-wide headers and footers.
It is possible to override the header and/or footer for nested directories by placing another header/footer file in a lower directory, such as page/admin/_header.html. In this example, all page requests to /admin and deeper (such as /admin/settings, /admin/users) will have the new header applied.
It is beneficial to have the same consistent header and footer throughout your application wherever possible, but certain pages may need the header/footer removing, so that they can specify their own.
This is done on a per-file basis by inserting an HTML comment as the first line of the file. There are three comments to use:
-
<!--no-header-->- Disable loading the_header.htmlfile. -
<!--no-header-footer-->- Disable loading both the_header.htmland_footer.htmlfiles. -
<!--no-footer-->- Disable loading the_footer.htmlfile.
- Request-response lifecycle
- Running your application
- Project layout
- Application architecture
- Web servers
- URIs
- Page view
- Dynamic URIs and pages
- Headers and footers
- Page logic
- Protected globals
- User input
- Cookies
- Sessions
- DOM manipulation
- Custom HTML components
- DOM templates
- Binding data to the DOM
- Database
- Client side assets
- API Webservices
- Security
- Configuration
- Build system
- Coding styleguide