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>
64 lines
1.7 KiB
Markdown
64 lines
1.7 KiB
Markdown
---
|
|
id: 5f07be6ef7412fbad0c5626b
|
|
title: Step 15
|
|
challengeType: 0
|
|
dashedName: step-15
|
|
---
|
|
|
|
# --description--
|
|
|
|
Before adding any new content, you should make use of a `section` element to separate the cat photos content from the future content.
|
|
|
|
Take all the elements currently located within the `main` element and nest them in a `section` element.
|
|
|
|
# --hints--
|
|
|
|
Your `section` element should have an opening tag. Opening tags have the following syntax: `<elementName>`.
|
|
|
|
```js
|
|
assert(document.querySelector('section'));
|
|
```
|
|
|
|
Your `section` element should have a closing tag. Closing tags have a `/` just after the `<` character.
|
|
|
|
```js
|
|
assert(code.match(/<\/section\>/));
|
|
```
|
|
|
|
The entire `section` element should be between the opening and closing tags of the `main` element.
|
|
|
|
```js
|
|
assert(document.querySelector('section').parentNode.nodeName === 'MAIN');
|
|
```
|
|
|
|
The existing `h2`, comment, `p` element, and anchor (`a`) element should be between the opening and closing tags of the `section` element.
|
|
|
|
```js
|
|
const childrenOfSection = [...document.querySelector('section').childNodes];
|
|
const foundElems = childrenOfSection.filter((child) => {
|
|
return ['H2', 'A', 'P'].includes(child.nodeName);
|
|
});
|
|
assert(foundElems.length === 3);
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<html>
|
|
<body>
|
|
<h1>CatPhotoApp</h1>
|
|
--fcc-editable-region--
|
|
<main>
|
|
<h2>Cat Photos</h2>
|
|
<!-- TODO: Add link to cat photos -->
|
|
<p>Click here to view more <a target="_blank" href="https://freecatphotoapp.com">cat photos</a>.</p>
|
|
<a href="https://freecatphotoapp.com"><img src="https://cdn.freecodecamp.org/curriculum/cat-photo-app/relaxing-cat.jpg" alt="A cute orange cat lying on its back."></a>
|
|
</main>
|
|
--fcc-editable-region--
|
|
</body>
|
|
</html>
|
|
```
|
|
|