8614db7a32
* feat: use legacy flag chore: reorder challenges fix: linter revert: server change feat: unblock new editor fix: proper order fix: 0-based order fix: broke the order feat: move tribute certification to its own block feat: split the old projects block into 4 fix: put all blocks in order chore: add intro text refactor: use block, not blockName in query fix: project progress indicator * fix: reorder new challenges/certs * fix: reorder legacy challenges * fix: reintroduce legacy certs * feat: add showNewCurriculum flag to env * chore: forgot sample.env * feat: use feature flag for display * fix: rename meta + dirs to match new blocks * fix: add new blocks to help-category-map * fix: update completion-modal for new GQL schema * test: duplicate title/id errors -> warnings * fix: update completion-modal to new GQL schema Mk2 * chore: re-order metas (again) * fix: revert super-block-intro changes The intro needs to show both legacy and new content. We need to decide which pages are created, rather than than what a page shows when rendered. * feat: move upcoming curriculum into own superblock * fix: handle one certification with two superBlocks * fix: remove duplicated intros * fix: remove duplicate projects from /settings * fix: drop 'two' from Responsive Web Design Two * chore: rename slug suffix from two to v2 * feat: control display of new curriculum * feat: control project paths shown on /settings * fix: use new project order for /settings This does mean that /settings will change before the release, but I don't think it's serious. All the projects are there, just not in the legacy order. * fix: claim/show cert button * chore: remove isLegacy Since we have legacy superblocks, we don't currently need individual blocks to be legacy * test: fix utils.test * fix: verifyCanClaim needs certification If Shaun removes the cert claim cards, maybe we can remove this entirely * fix: add hasEditableBoundaries flags where needed * chore: remove isUpcomingChange * chore: v2 -> 22 Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
168 lines
3.7 KiB
Markdown
168 lines
3.7 KiB
Markdown
---
|
|
id: 5f46fc57528aa1c4b5ea7c2e
|
|
title: Step 76
|
|
challengeType: 0
|
|
dashedName: step-76
|
|
---
|
|
|
|
# --description--
|
|
|
|
Changing the `bottom-margin` to `5px` looks great. However, now the space between the `Cinnamon Roll` menu item and the second `hr` element does not match the space between the top `hr` element and the `Coffee` heading.
|
|
|
|
Add some more space by creating a class named `bottom-line` using `25px` for the `margin-top` property.
|
|
|
|
# --hints--
|
|
|
|
You should add a `.bottom-line` selector.
|
|
|
|
```js
|
|
const hasBottomLine = new __helpers.CSSHelp(document).getStyle('.bottom-line');
|
|
assert(hasBottomLine);
|
|
```
|
|
|
|
You should set the `margin-top` property to `25px`.
|
|
|
|
```js
|
|
const hasMarginTop = new __helpers.CSSHelp(document).getCSSRules().some(x => x.style['margin-top'] === '25px');
|
|
assert(hasMarginTop);
|
|
```
|
|
|
|
Your `.bottom-line` selector should have a `margin-top` of `25px`.
|
|
|
|
```js
|
|
const bottomLineMargin = new __helpers.CSSHelp(document).getStyle('.bottom-line')?.getPropertyValue('margin-top');
|
|
assert(bottomLineMargin === '25px');
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta charset="utf-8" />
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
|
<title>Camper Cafe Menu</title>
|
|
<link href="styles.css" rel="stylesheet" type="text/css" />
|
|
</head>
|
|
<body>
|
|
<div class="menu">
|
|
<header>
|
|
<h1>CAMPER CAFE</h1>
|
|
<p class="established">Est. 2020</p>
|
|
</header>
|
|
<hr>
|
|
<main>
|
|
<section>
|
|
<h2>Coffee</h2>
|
|
<article class="item">
|
|
<p class="flavor">French Vanilla</p><p class="price">3.00</p>
|
|
</article>
|
|
<article class="item">
|
|
<p class="flavor">Caramel Macchiato</p><p class="price">3.75</p>
|
|
</article>
|
|
<article class="item">
|
|
<p class="flavor">Pumpkin Spice</p><p class="price">3.50</p>
|
|
</article>
|
|
<article class="item">
|
|
<p class="flavor">Hazelnut</p><p class="price">4.00</p>
|
|
</article>
|
|
<article class="item">
|
|
<p class="flavor">Mocha</p><p class="price">4.50</p>
|
|
</article>
|
|
</section>
|
|
<section>
|
|
<h2>Desserts</h2>
|
|
<article class="item">
|
|
<p class="dessert">Donut</p><p class="price">1.50</p>
|
|
</article>
|
|
<article class="item">
|
|
<p class="dessert">Cherry Pie</p><p class="price">2.75</p>
|
|
</article>
|
|
<article class="item">
|
|
<p class="dessert">Cheesecake</p><p class="price">3.00</p>
|
|
</article>
|
|
<article class="item">
|
|
<p class="dessert">Cinammon Roll</p><p class="price">2.50</p>
|
|
</article>
|
|
</section>
|
|
</main>
|
|
<hr>
|
|
<footer>
|
|
<p>
|
|
<a href="https://www.freecodecamp.org" target="_blank">Visit our website</a>
|
|
</p>
|
|
<p>123 Free Code Camp Drive</p>
|
|
</footer>
|
|
</div>
|
|
</body>
|
|
<html>
|
|
```
|
|
|
|
```css
|
|
body {
|
|
background-image: url(https://cdn.freecodecamp.org/curriculum/css-cafe/beans.jpg);
|
|
font-family: sans-serif;
|
|
padding: 20px;
|
|
}
|
|
|
|
h1 {
|
|
font-size: 40px;
|
|
}
|
|
|
|
h2 {
|
|
font-size: 30px;
|
|
}
|
|
|
|
.established {
|
|
font-style: italic;
|
|
}
|
|
|
|
h1, h2, p {
|
|
text-align: center;
|
|
}
|
|
|
|
.menu {
|
|
width: 80%;
|
|
background-color: burlywood;
|
|
margin-left: auto;
|
|
margin-right: auto;
|
|
padding: 20px;
|
|
max-width: 500px;
|
|
}
|
|
|
|
hr {
|
|
height: 2px;
|
|
background-color: brown;
|
|
border-color: brown;
|
|
}
|
|
|
|
--fcc-editable-region--
|
|
|
|
--fcc-editable-region--
|
|
|
|
h1, h2 {
|
|
font-family: Impact, serif;
|
|
}
|
|
|
|
.item p {
|
|
display: inline-block;
|
|
margin-top: 5px;
|
|
margin-bottom: 5px;
|
|
font-size: 18px;
|
|
}
|
|
|
|
.flavor, .dessert {
|
|
text-align: left;
|
|
width: 75%;
|
|
}
|
|
|
|
.price {
|
|
text-align: right;
|
|
width: 25%
|
|
}
|
|
```
|
|
|