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>
2.4 KiB
id, title, challengeType, dashedName
| id | title | challengeType | dashedName |
|---|---|---|---|
| 5dc23991f86c76b9248c6eb8 | Step 6 | 0 | step-6 |
--description--
HTML elements are often nested within other HTML elements. In the previous step you nested the h2 element, comment and p element within the main element. A nested element is a child of its parent element.
To make HTML easier to read, indent the h2 element, the comment, and p element exactly two spaces to indicate they are children of the main element.
--hints--
Your should have an h2 element with text Cat Photos. You may have accidentally deleted it, it is missing both opening and closing tags, or the text has changed.
assert(
document.querySelector('h2') &&
code.match(/<\/h2\>/) &&
document.querySelector('h2').innerText.toLowerCase() === 'cat photos'
);
Your h2 element should below the main element's opening tag and its opening tag should start 6 spaces over from the start of the line.
assert(code.toLowerCase().match(/<main\>\n\s{6}<h2>/));
Your code should have a comment. You removed the comment from an earlier step.
assert(code.match(/<!--.*-->/));
The comment's text should be TODO: Add link to cat photos. Do not change the text or spacing of the comment.
assert(code.match(/<!--\s*todo:\s+add\s+link\s+to\s+cat\s+photos\.?\s*-->/i));
Your comment should be below the h2 element and start 6 spaces over from the start of the line.
assert(
code
.toLowerCase()
.match(/<\/h2>\n\s{6}<!--\s*todo:\s+add\s+link\s+to\s+cat\s+photos\s*-->/)
);
Your code should have a p element. You have removed the p element from an earlier step.
assert(document.querySelector('p'));
The text of the p element should be Click here to view more cat photos. Do not change the text, spacing, or punctuation of the p element.
assert(
document
.querySelector('p')
.innerText.toLowerCase()
.match(/click\s+here\s+to\s+view\s+more\s+cat\s+photos\.?$/)
);
Your p element should be below the comment and its opening tag should start 6 spaces over from the start of the line.
assert(code.toLowerCase().match(/-->\n\s{6}<p>/));
--seed--
--seed-contents--
<html>
<body>
<h1>CatPhotoApp</h1>
<main>
--fcc-editable-region--
<h2>Cat Photos</h2>
<!-- TODO: Add link to cat photos -->
<p>Click here to view more cat photos.</p>
--fcc-editable-region--
</main>
</body>
</html>