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>
62 lines
1.4 KiB
Markdown
62 lines
1.4 KiB
Markdown
---
|
|
id: 5dc23f9bf86c76b9248c6eba
|
|
title: Step 7
|
|
challengeType: 0
|
|
dashedName: step-7
|
|
---
|
|
|
|
# --description--
|
|
|
|
You can add images to your website by using the `img` element. `img` elements have an opening tag without a closing tag. A tag for an element without a closing tag is known as a <dfn>self-closing tag</dfn>.
|
|
|
|
Add an `img` element below the `p` element. At this point, no image will show up in the browser.
|
|
|
|
# --hints--
|
|
|
|
Your `img` element should have an opening tag. Opening tags have this syntax: `<elementName>`.
|
|
|
|
```js
|
|
assert(document.querySelector('img'));
|
|
```
|
|
|
|
Your `img` element should not have a closing tag. Closing tags have a `/` just after the `<` character.
|
|
|
|
```js
|
|
assert(!code.match(/<\/img\>/));
|
|
```
|
|
|
|
You should only have one `img` element. Remove any extras.
|
|
|
|
```js
|
|
assert(document.querySelectorAll('img').length === 1);
|
|
```
|
|
|
|
Your `img` element should be below the `p` element. You have them in the wrong order.
|
|
|
|
```js
|
|
const collection = [...document.querySelectorAll('p,img')].map(
|
|
(node) => node.nodeName
|
|
);
|
|
assert(collection.indexOf('P') < collection.indexOf('IMG'));
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<html>
|
|
<body>
|
|
<h1>CatPhotoApp</h1>
|
|
<main>
|
|
<h2>Cat Photos</h2>
|
|
<!-- TODO: Add link to cat photos -->
|
|
--fcc-editable-region--
|
|
<p>Click here to view more cat photos.</p>
|
|
--fcc-editable-region--
|
|
</main>
|
|
</body>
|
|
</html>
|
|
```
|
|
|