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>
85 lines
1.9 KiB
Markdown
85 lines
1.9 KiB
Markdown
---
|
|
id: 60b69a66b6ddb80858c51583
|
|
title: Step 13
|
|
challengeType: 0
|
|
dashedName: step-13
|
|
---
|
|
|
|
# --description--
|
|
|
|
Create four `div` elements inside your `offwhite-character` element. Give those `div` elements the following `id` values, in order: `white-hat`, `black-mask`, `gray-instrument`, `tan-table`.
|
|
|
|
# --hints--
|
|
|
|
You should add four `div` elements within your `.offwhite-character` element.
|
|
|
|
```js
|
|
assert(document.querySelectorAll('#offwhite-character div').length === 4);
|
|
```
|
|
|
|
Your first new `div` element should have the `id` of `white-hat`.
|
|
|
|
```js
|
|
assert(document.querySelectorAll('#offwhite-character div')[0]?.getAttribute('id') === 'white-hat');
|
|
```
|
|
|
|
Your second new `div` element should have the `id` of `black-mask`.
|
|
|
|
```js
|
|
assert(document.querySelectorAll('#offwhite-character div')[1]?.getAttribute('id') === 'black-mask');
|
|
```
|
|
|
|
Your third new `div` element should have the `id` of `gray-instrument`.
|
|
|
|
```js
|
|
assert(document.querySelectorAll('#offwhite-character div')[2]?.getAttribute('id') === 'gray-instrument');
|
|
```
|
|
|
|
Your fourth new `div` element should have the `id` of `tan-table`.
|
|
|
|
```js
|
|
assert(document.querySelectorAll('#offwhite-character div')[3]?.getAttribute('id') === 'tan-table');
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta charset="utf-8">
|
|
<title>freeCodeCamp Picasso Painting</title>
|
|
<link rel="stylesheet" type="text/css" href="./styles.css" />
|
|
<link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.8.2/css/all.css">
|
|
</head>
|
|
<body>
|
|
<div id="back-wall"></div>
|
|
<div class="characters">
|
|
<div id="offwhite-character">
|
|
--fcc-editable-region--
|
|
|
|
--fcc-editable-region--
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html>
|
|
```
|
|
|
|
```css
|
|
body {
|
|
background-color: rgb(184, 132, 46);
|
|
}
|
|
|
|
#back-wall {
|
|
background-color: #8B4513;
|
|
width: 100%;
|
|
height: 60%;
|
|
position: absolute;
|
|
top: 0;
|
|
left: 0;
|
|
z-index: -1;
|
|
}
|
|
```
|