sixarm_css_holy_grail_layout_with_flexbox
SixArm.com » CSS » Holy Grail layout with flexbox
https://github.com/sixarm/sixarm_css_holy_grail_layout_with_flexbox
Science Score: 44.0%
This score indicates how likely this project is to be science-related based on various indicators:
-
✓CITATION.cff file
Found CITATION.cff file -
✓codemeta.json file
Found codemeta.json file -
✓.zenodo.json file
Found .zenodo.json file -
○DOI references
-
○Academic publication links
-
○Committers with academic emails
-
○Institutional organization owner
-
○JOSS paper metadata
-
○Scientific vocabulary similarity
Low similarity (9.0%) to scientific vocabulary
Keywords
Repository
SixArm.com » CSS » Holy Grail layout with flexbox
Basic Info
- Host: GitHub
- Owner: SixArm
- Language: CSS
- Default Branch: main
- Size: 9.77 KB
Statistics
- Stars: 10
- Watchers: 2
- Forks: 2
- Open Issues: 0
- Releases: 0
Topics
Metadata Files
README.md
SixArm.com » CSS »
Holy Grail layout with flexbox
To accomplish a CSS "Holy Grail" layout with flexbox, we use the excellent work published by Philip Walton, in the open source "Solved By Flexbox" repository: https://github.com/philipwalton/solved-by-flexbox/blob/master/demos/holy-grail.md
Files:
Changes
We have edited the CSS code with the goal of making it easier for beginners:
- Added comments and examples
- Added blank classes to make it easier to see how to customize this.
- Omitted inessential items, such as margin, padding, color, border, etc.
- Renamed classes to make them more generic and also more semantic.
Naming Conventions
The CSS code uses the naming conventions of SuitCSS:
- .ComponentName
- .ComponentName-partName
- .ComponentName--modifierName
- .ComponentName.is-stateOfComponent
If you know CSS well, and you want to optimize this file for speed, then you may want to elide the blank classes, combine equal classes, delete these comments, and ideally also use a CSS preprocessor.
Header, Leader, Footer
Our layout has these sections:
- header
- leader, which has first area, main area, last area
- footer
The "header" and "footer" are the typical HTML5 tags.
The "leader" is our naming convention for the middle area that goes between the header tag and the footer tag. We hope the HTML standard will add a tag for this area. Some coders call it "master container", or "body content", or similar names. You can rename "leader" if you prefer.
The leader has these areas:
- first area. This is the left column on a big screen, or the top row on a small screen.
- The main area. This is the middle center area on any size scren, and it grows to fit.
- The last area. This is the right column on a big screen, or the bottom row on a small screen.
HTML example:
<body class="HolyGrail">
<div class="HolyGrail-header">
<header>...</header>
</div>
<div class="HolyGrail-leader">
<div class="HolyGrail-leader-first"><aside>Show first, at top or left</aside></div>
<div class="HolyGrail-leader-main"><main>Show in main area, in the middle</main></div>
<div class="HolyGrail-leader-last"><aside>Show last, at bottom or right</aside></div>
</div>
<div class="HolyGrail-footer">
<footer>...</footer>
</div>
</body>
We recommend using the HTML tag main for the main area.
We suggest using the HTML tag aside for the first area and laster area,
unless you feel there is a better tag, such as nav for a navigation area.
Pro Tip for SEO
If you're building a page that you want to be indexed by search engines,
then we suggest you rearrange the leader areas to make the main area
comes before the first area and the last area.
Example:
<div class="HolyGrail-leader-main"><main>Show in main area, in the middle</main></div>
<div class="HolyGrail-leader-first"><aside>Show first, at top or left</aside></div>
<div class="HolyGrail-leader-last"><aside>Show last, at bottom or right</aside></div>
Pro Tip for optimization
Do you have goals like these?
- Use a typical "nav" section at the top or left side.
- Use a typical "main" section, and load it high on the page because of SEO.
- Use a typical "aside" tag at the bottom or right side.
- Use each specific HTML tag when possible, rather than using unnessary div tags.
Example:
<body class="HolyGrail">
<header class="HolyGrail-header">...</header>
<div class="HolyGrail-leader">
<main class="HolyGrail-leader-main">Show in main area, in the middle</main>
<nav class="HolyGrail-leader-first">Show first, at top or left</nav>
<aside class="HolyGrail-leader-last">Show last, at bottom or right</aside>
</div>
<footer class="HolyGrail-footer">...</footer>
</body>
Media queries
The layout uses media queries to enable responsive pages:
- A small screen shows the three areas as rows.
- A large screen shows the three areas as columns.
We choose 768 pixels as the start of a large screen size.
If you prefer different settings, or prefer more than two screen sizes, then you'll want to edit these media queries.
Owner
- Name: SixArm
- Login: SixArm
- Kind: organization
- Email: sixarm@sixarm.com
- Location: San Francisco
- Website: http://sixarm.com
- Twitter: sixarm
- Repositories: 580
- Profile: https://github.com/SixArm
SixArm Software
Citation (CITATION.cff)
cff-version: 1.2.0
title: SixArm.com » CSS » <br> Holy Grail layout with flexbox
message: >-
If you use this work and you want to cite it,
then you can use the metadata from this file.
type: software
authors:
- given-names: Joel Parker
family-names: Henderson
email: joel@joelparkerhenderson.com
affiliation: joelparkerhenderson.com
orcid: 'https://orcid.org/0009-0000-4681-282X'
identifiers:
- type: url
value: 'https://github.com/SixArm/sixarm_css_holy_grail_layout_with_flexbox/'
description: SixArm.com » CSS » <br> Holy Grail layout with flexbox
repository-code: 'https://github.com/SixArm/sixarm_css_holy_grail_layout_with_flexbox/'
abstract: >-
SixArm.com » CSS » <br> Holy Grail layout with flexbox
license: See license file
GitHub Events
Total
- Push event: 1
Last Year
- Push event: 1
Committers
Last synced: 9 months ago
Top Committers
| Name | Commits | |
|---|---|---|
| Joel Parker Henderson | j****l@j****m | 13 |
Committer Domains (Top 20 + Academic)
Issues and Pull Requests
Last synced: 9 months ago
All Time
- Total issues: 0
- Total pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Total issue authors: 0
- Total pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0
Past Year
- Issues: 0
- Pull requests: 0
- Average time to close issues: N/A
- Average time to close pull requests: N/A
- Issue authors: 0
- Pull request authors: 0
- Average comments per issue: 0
- Average comments per pull request: 0
- Merged pull requests: 0
- Bot issues: 0
- Bot pull requests: 0