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.9 KiB
id, title, challengeType, dashedName
| id | title | challengeType | dashedName |
|---|---|---|---|
| 61537485c4f2a624f18d7794 | Step 1 | 0 | step-1 |
--description--
Begin with your standard HTML boilerplate. Add a DOCTYPE declaration, an html element, a head element, and a body element.
--hints--
Your code should contain the DOCTYPE reference.
assert(code.match(/<!DOCTYPE/gi));
You should include a space after the DOCTYPE reference.
assert(code.match(/<!DOCTYPE\s+/gi));
You should define the document type to be html.
assert(code.match(/<!DOCTYPE\s+html/gi));
You should close the DOCTYPE declaration with a > after the type.
assert(code.match(/<!DOCTYPE\s+html\s*>/gi));
Your html element should have an opening tag.
assert(code.match(/<html\s*>/gi));
Your html element should have a closing tag.
assert(code.match(/<\/html\s*>/));
Your html element should be below the DOCTYPE declaration.
assert(code.match(/(?<!<html\s*>)<!DOCTYPE\s+html\s*>/gi));
You should have an opening head tag.
assert(code.match(/<head\s*>/i));
You should have a closing head tag.
assert(code.match(/<\/head\s*>/i));
You should have an opening body tag.
assert(code.match(/<body\s*>/i));
You should have a closing body tag.
assert(code.match(/<\/body\s*>/i));
The head and body elements should be siblings.
assert(document.querySelector('head')?.nextElementSibling?.localName === 'body');
The head element should be within the html element.
assert([...document.querySelector('html')?.children].some(x => x?.localName === 'head'));
The body element should be within the html element.
assert([...document.querySelector('html')?.children].some(x => x?.localName === 'body'));
--seed--
--seed-contents--
--fcc-editable-region--
--fcc-editable-region--