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>
1.8 KiB
1.8 KiB
id, title, challengeType, dashedName
| id | title | challengeType | dashedName |
|---|---|---|---|
| 5f3477cb2e27333b1ab2b955 | Step 17 | 0 | step-17 |
--description--
Now you need to link the styles.css file so the styles will be applied again. Nest a self-closing link element in the head element. Give it a rel attribute value stylesheet, a type attribute value of text/css, and an href attribute value of styles.css.
--hints--
Your code should have a link element.
// link is removed -> if exists, replaced with style
const link = document.querySelector('body > style');
assert(link);
You should not change your existing head element. Make sure you did not delete the closing tag.
assert($('head').length === 1);
Your link element should be a self-closing element.
assert(code.match(/<link[\w\W\s]+\/>/i));
Your link element should be within your head element.
assert(code.match(/<head>[\w\W\s]*<link[\w\W\s]*\/>[\w\W\s]*<\/head>/i))
Your link element should have a rel attribute with the value stylesheet.
assert(code.match(/rel=('|")stylesheet\1/i));
Your link element should have a type attribute with the value text/css.
assert(code.match(/type=('|")text\/css\1/i));
Your link element should have an href attribute with the value styles.css.
assert(code.match(/href=('|")styles.css\1/i));
--seed--
--seed-contents--
<!DOCTYPE html>
<html>
--fcc-editable-region--
<head>
<meta charset="utf-8" />
<title>Camper Cafe Menu</title>
</head>
--fcc-editable-region--
<body>
<header>
<h1>CAMPER CAFE</h1>
<p>Est. 2020</p>
</header>
<main>
<section>
<h2>Coffee</h2>
</section>
</main>
</body>
<html>
h1, h2, p {
text-align: center;
}