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.0 KiB
Markdown
62 lines
1.0 KiB
Markdown
---
|
|
id: 5f3313e74582ad9d063e3a38
|
|
title: Step 2
|
|
challengeType: 0
|
|
dashedName: step-2
|
|
---
|
|
|
|
# --description--
|
|
|
|
Add a `head` element within the `html` element, so you can add a `title` element. The title element's text should be `Camper Cafe Menu`.
|
|
|
|
# --hints--
|
|
|
|
You should have an opening `<head>` tag.
|
|
|
|
```js
|
|
assert(code.match(/<head>/i));
|
|
```
|
|
|
|
You should have a closing `</head>` tag.
|
|
|
|
```js
|
|
assert(code.match(/<head>/i));
|
|
```
|
|
|
|
You should have an opening `<title>` tag.
|
|
|
|
```js
|
|
assert(code.match(/<title>/i));
|
|
```
|
|
|
|
You should have a closing `</title>` tag.
|
|
|
|
```js
|
|
assert(code.match(/<\/title>/i));
|
|
```
|
|
|
|
Your `<title>` element should be nested in your `<head>` element.
|
|
|
|
```js
|
|
assert(code.match(/<head>\s*<title>.*<\/title>\s*<\/head>/i));
|
|
```
|
|
|
|
Your `<title>` element should have the text `Camper Cafe Menu`. You may need to check your spelling.
|
|
|
|
```js
|
|
assert(code.match(/<title>camper\scafe\smenu<\/title>/i));
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
<html>
|
|
--fcc-editable-region--
|
|
|
|
--fcc-editable-region--
|
|
</html>
|
|
```
|