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>
60 lines
1.1 KiB
Markdown
60 lines
1.1 KiB
Markdown
---
|
|
id: 5f33310c1851c6c4da013250
|
|
title: Step 8
|
|
challengeType: 0
|
|
dashedName: step-8
|
|
---
|
|
|
|
# --description--
|
|
|
|
It's time to add some menu content. Add a `main` element below the existing `header` element. It will eventually contain pricing information about coffee and desserts offered by the cafe.
|
|
|
|
# --hints--
|
|
|
|
Your code should have an opening `<main>` tag.
|
|
|
|
```js
|
|
assert(code.match(/<main>/i));
|
|
```
|
|
|
|
Your code should have a closing `</main>` tag.
|
|
|
|
```js
|
|
assert(code.match(/<\/main>/i));
|
|
```
|
|
|
|
You should not change your `header` element. Make sure you don't accidentally delete your closing tag.
|
|
|
|
```js
|
|
assert($('header').length === 1);
|
|
```
|
|
|
|
Your `main` tag should come after your `header` tag.
|
|
|
|
```js
|
|
const main = document.querySelectorAll('main')[0];
|
|
assert(main.previousElementSibling.tagName === 'HEADER');
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta charset="utf-8" />
|
|
<title>Camper Cafe Menu</title>
|
|
</head>
|
|
<body>
|
|
--fcc-editable-region--
|
|
<header>
|
|
<h1>CAMPER CAFE</h1>
|
|
<p>Est. 2020</p>
|
|
</header>
|
|
--fcc-editable-region--
|
|
</body>
|
|
<html>
|
|
```
|