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>
83 lines
2.0 KiB
Markdown
83 lines
2.0 KiB
Markdown
---
|
|
id: 5dc1798ff86c76b9248c6eb3
|
|
title: Step 2
|
|
challengeType: 0
|
|
dashedName: step-2
|
|
---
|
|
|
|
# --description--
|
|
|
|
The `h1` to `h6` heading elements are used to signify the importance of content below them. The lower the number, the higher the importance, so `h2` elements have less importance than `h1` elements. Only use one `h1` element per page and place lower importance headings below higher importance headings.
|
|
|
|
Add an `h2` element below the `h1` element that says `Cat Photos`.
|
|
|
|
# --hints--
|
|
|
|
Your `h1` element should have an opening tag. Opening tags have this syntax: `<elementName>`.
|
|
|
|
```js
|
|
assert(document.querySelector('h1'));
|
|
```
|
|
|
|
Your `h1` element should have a closing tag. Closing tags have a `/` just after the `<` character.
|
|
|
|
```js
|
|
assert(code.match(/<\/h1\>/));
|
|
```
|
|
|
|
You should only have one `h1` element. Remove the extra.
|
|
|
|
```js
|
|
assert(
|
|
document.querySelector('h1') && document.querySelectorAll('h1').length === 1
|
|
);
|
|
```
|
|
|
|
Your `h1` element's text should be 'CatPhotoApp'. You have either omitted the text or have a typo.
|
|
|
|
```js
|
|
assert(document.querySelector('h1').innerText.toLowerCase() === 'catphotoapp');
|
|
```
|
|
|
|
Your `h2` element should have an opening tag. Opening tags have this syntax: `<elementName>`.
|
|
|
|
```js
|
|
assert(document.querySelector('h2'));
|
|
```
|
|
|
|
Your `h2` element should have a closing tag. Closing tags have a `/` just after the `<` character.
|
|
|
|
```js
|
|
assert(code.match(/<\/h2\>/));
|
|
```
|
|
|
|
Your `h2` element's text should be 'Cat Photos'. Only place the text `Cat Photos` between the opening and closing `h2` tags.
|
|
|
|
```js
|
|
assert(document.querySelector('h2').innerText.toLowerCase() === 'cat photos');
|
|
```
|
|
|
|
Your `h2` element should be below the `h1` element. The `h1` element has greater importance and must be above the `h2` element.
|
|
|
|
```js
|
|
const collection = [...document.querySelectorAll('h1,h2')].map(
|
|
(node) => node.nodeName
|
|
);
|
|
assert(collection.indexOf('H1') < collection.indexOf('H2'));
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<html>
|
|
<body>
|
|
--fcc-editable-region--
|
|
<h1>CatPhotoApp</h1>
|
|
--fcc-editable-region--
|
|
</body>
|
|
</html>
|
|
```
|
|
|