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>
103 lines
2.6 KiB
Markdown
103 lines
2.6 KiB
Markdown
---
|
|
id: 614385513d91ae5c251c2052
|
|
title: Step 2
|
|
challengeType: 0
|
|
dashedName: step-2
|
|
---
|
|
|
|
# --description--
|
|
|
|
Add a `title` element with the text `CSS Grid Magazine`, a `link` element for the `https://fonts.googleapis.com/css?family=Anton|Baskervville|Raleway&display=swap` font stylesheet, a `link` for the `https://use.fontawesome.com/releases/v5.8.2/css/all.css` FontAwesome stylesheet, and a `link` for your `./styles.css` stylesheet.
|
|
|
|
Your font stylesheet will load three separate fonts: `Anton`, `Baskervville`, and `Raleway`.
|
|
|
|
# --hints--
|
|
|
|
Your code should have three `link` elements.
|
|
|
|
```js
|
|
assert(code.match(/<link/g)?.length === 3);
|
|
```
|
|
|
|
Your `link` elements should be self-closing elements.
|
|
|
|
```js
|
|
assert(code.match(/<\/link>/i) === null);
|
|
```
|
|
|
|
Your `link` elements should be within your `head` element.
|
|
|
|
```js
|
|
const head = code.match(/<head>(.|\r|\n)*<\/head>/i)?.[0];
|
|
assert(head.match(/<link/g)?.length === 3)
|
|
```
|
|
|
|
Your three `link` elements should have a `rel` attribute with the value `stylesheet`.
|
|
|
|
```js
|
|
assert(code.match(/<link[\s\S]*?rel=('|"|`)stylesheet\1/gi)?.length === 3);
|
|
```
|
|
|
|
One of your link elements should have the `href` set to `https://fonts.googleapis.com/css?family=Anton|Baskervville|Raleway&display=swap`.
|
|
|
|
```js
|
|
const links = [...document.querySelectorAll('link')];
|
|
assert(links.find(link => link.getAttribute('href') === 'https://fonts.googleapis.com/css?family=Anton|Baskervville|Raleway&display=swap'));
|
|
```
|
|
|
|
One of your link elements should have the `href` set to `https://use.fontawesome.com/releases/v5.8.2/css/all.css`.
|
|
|
|
```js
|
|
const links = [...document.querySelectorAll('link')];
|
|
assert(links.find(link => link.getAttribute('href') === 'https://use.fontawesome.com/releases/v5.8.2/css/all.css'));
|
|
```
|
|
|
|
One of your `link` elements should have an `href` attribute with the value `styles.css`.
|
|
|
|
```js
|
|
assert.match(code, /<link[\s\S]*?href=('|"|`)(\.\/)?styles\.css\1/)
|
|
```
|
|
|
|
Your code should have a `title` element.
|
|
|
|
```js
|
|
const title = document.querySelector('title');
|
|
assert.exists(title);
|
|
```
|
|
|
|
Your project should have a title of `CSS Grid Magazine`.
|
|
|
|
```js
|
|
const title = document.querySelector('title');
|
|
assert.equal(title?.text?.trim()?.toLowerCase(), 'css grid magazine')
|
|
```
|
|
|
|
Remember, the casing and spelling matter for the title.
|
|
|
|
```js
|
|
const title = document.querySelector('title');
|
|
assert.equal(title?.text?.trim(), 'CSS Grid Magazine');
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
<html>
|
|
--fcc-editable-region--
|
|
<head>
|
|
<meta charset="UTF-8" />
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
|
</head>
|
|
--fcc-editable-region--
|
|
<body>
|
|
</body>
|
|
</html>
|
|
```
|
|
|
|
```css
|
|
|
|
```
|