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>
87 lines
1.5 KiB
Markdown
87 lines
1.5 KiB
Markdown
---
|
||
id: 5f35e5c4321f818cdc4bed30
|
||
title: Step 30
|
||
challengeType: 0
|
||
dashedName: step-30
|
||
---
|
||
|
||
# --description--
|
||
|
||
It’s looking good. Time to start adding some menu items. Add an empty `article` element under the `Coffee` heading. It will contain a flavor and price of each coffee you currently offer.
|
||
|
||
# --hints--
|
||
|
||
You should have an opening `<article>` tag.
|
||
|
||
```js
|
||
assert(code.match(/<article>/i));
|
||
```
|
||
|
||
You should have a closing `</article>` tag.
|
||
|
||
```js
|
||
assert(code.match(/<\/article>/i));
|
||
```
|
||
|
||
You should not change the existing `h2` element.
|
||
|
||
```js
|
||
assert($('h2').length === 1);
|
||
```
|
||
|
||
Your `article` element should come after your `h2` element.
|
||
|
||
```js
|
||
const article = $('article')[0];
|
||
assert(article.previousElementSibling.tagName === 'H2');
|
||
```
|
||
|
||
# --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>Est. 2020</p>
|
||
</header>
|
||
<main>
|
||
<section>
|
||
--fcc-editable-region--
|
||
<h2>Coffee</h2>
|
||
--fcc-editable-region--
|
||
</section>
|
||
</main>
|
||
</div>
|
||
</body>
|
||
<html>
|
||
```
|
||
|
||
```css
|
||
body {
|
||
background-image: url(https://cdn.freecodecamp.org/curriculum/css-cafe/beans.jpg);
|
||
}
|
||
|
||
h1, h2, p {
|
||
text-align: center;
|
||
}
|
||
|
||
.menu {
|
||
width: 80%;
|
||
background-color: burlywood;
|
||
margin-left: auto;
|
||
margin-right: auto;
|
||
}
|
||
```
|
||
|