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>
80 lines
1.8 KiB
Markdown
80 lines
1.8 KiB
Markdown
---
|
|
id: 6140c9d35015ae0ba0c250e8
|
|
title: Step 2
|
|
challengeType: 0
|
|
dashedName: step-2
|
|
---
|
|
|
|
# --description--
|
|
|
|
Add a `div` within your `body` element and give it a `class` of `wheel`.
|
|
|
|
Inside your new `div`, add six `span` elements with a `class` set to `line`, and six `div` elements with a `class` set to `cabin`.
|
|
|
|
# --hints--
|
|
|
|
You should create a new `div` within your `body` element.
|
|
|
|
```js
|
|
const divs = [...document.querySelector('body')?.children].filter(child => child?.localName === 'div');
|
|
assert(divs?.length === 1);
|
|
```
|
|
|
|
Your `div` within your `body` element should have a `class` of `wheel`.
|
|
|
|
```js
|
|
assert(document.querySelector('body div')?.classList?.contains('wheel'));
|
|
```
|
|
|
|
Your `.wheel` element should have six `span` elements within.
|
|
|
|
```js
|
|
assert(document.querySelectorAll('.wheel span')?.length === 6);
|
|
```
|
|
|
|
Your six `span` elements within the `.wheel` element should have a `class` of `line`.
|
|
|
|
```js
|
|
const spans = [...document.querySelectorAll('.wheel span')];
|
|
assert(spans?.every(span => span?.classList?.contains('line')));
|
|
assert(document.querySelectorAll('.line')?.length === 6);
|
|
```
|
|
|
|
Your `.wheel` element should have six `div` elements within.
|
|
|
|
```js
|
|
assert(document.querySelectorAll('.wheel div')?.length === 6);
|
|
```
|
|
|
|
Your six `div` elements within the `.wheel` element should have a `class` of `cabin`.
|
|
|
|
```js
|
|
const divs = [...document.querySelectorAll('.wheel div')];
|
|
assert(divs?.every(div => div?.classList?.contains('cabin')));
|
|
assert(document.querySelectorAll('.cabin')?.length === 6);
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta charset="UTF-8">
|
|
<title>CSS Ferris Wheel</title>
|
|
<link rel="stylesheet" href="./styles.css" />
|
|
</head>
|
|
--fcc-editable-region--
|
|
<body>
|
|
|
|
</body>
|
|
--fcc-editable-region--
|
|
</html>
|
|
```
|
|
|
|
```css
|
|
|
|
```
|