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>
129 lines
3.0 KiB
Markdown
129 lines
3.0 KiB
Markdown
---
|
|
id: 5f3c866d5414453fc2d7b480
|
|
title: Step 32
|
|
challengeType: 0
|
|
dashedName: step-32
|
|
---
|
|
|
|
# --description--
|
|
|
|
Starting below the existing coffee/price pair, add the following coffee and prices using `article` elements with two nested `p` elements inside each. As before, the first `p` element's text should contain the coffee flavor and the second `p` element's text should contain the price.
|
|
|
|
```bash
|
|
Caramel Macchiato 3.75
|
|
Pumpkin Spice 3.50
|
|
Hazelnut 4.00
|
|
Mocha 4.50
|
|
```
|
|
|
|
# --hints--
|
|
|
|
You should have five `article` elements.
|
|
|
|
```js
|
|
assert($('article').length === 5);
|
|
```
|
|
|
|
Each `article` element should have two `p` elements.
|
|
|
|
```js
|
|
const articles = $('article');
|
|
assert(articles[0].children.length === 2);
|
|
assert(articles[1].children.length === 2);
|
|
assert(articles[2].children.length === 2);
|
|
assert(articles[3].children.length === 2);
|
|
assert(articles[4].children.length === 2);
|
|
```
|
|
|
|
Your first `article` element should have `p` elements with the text `French Vanilla` and `3.00`.
|
|
|
|
```js
|
|
const children = $('article')[0].children;
|
|
assert(children[0].innerText.match(/French Vanilla/i));
|
|
assert(children[1].innerText.match(/3\.00/i));
|
|
```
|
|
|
|
Your second `article` element should have `p` elements with the text `Caramel Macchiato` and `3.75`.
|
|
|
|
```js
|
|
const children = $('article')[1].children;
|
|
assert(children[0].innerText.match(/Caramel Macchiato/i));
|
|
assert(children[1].innerText.match(/3\.75/i));
|
|
```
|
|
|
|
Your third `article` element should have `p` elements with the text `Pumpkin Spice` and `3.50`.
|
|
|
|
```js
|
|
const children = $('article')[2].children;
|
|
assert(children[0].innerText.match(/Pumpkin Spice/i));
|
|
assert(children[1].innerText.match(/3\.50/i));
|
|
```
|
|
|
|
Your fourth `article` element should have `p` elements with the text `Hazelnut` and `4.00`.
|
|
|
|
```js
|
|
const children = $('article')[3].children;
|
|
assert(children[0].innerText.match(/Hazelnut/i));
|
|
assert(children[1].innerText.match(/4\.00/i));
|
|
```
|
|
|
|
Your fifth `article` element should have `p` elements with the text `Mocha` and `4.50`.
|
|
|
|
```js
|
|
const children = $('article')[4].children;
|
|
assert(children[0].innerText.match(/Mocha/i));
|
|
assert(children[1].innerText.match(/4\.50/i));
|
|
```
|
|
|
|
# --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>
|
|
<h2>Coffee</h2>
|
|
--fcc-editable-region--
|
|
<article>
|
|
<p>French Vanilla</p>
|
|
<p>3.00</p>
|
|
</article>
|
|
--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;
|
|
}
|
|
```
|