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>
60 lines
1.2 KiB
Markdown
60 lines
1.2 KiB
Markdown
---
|
|
id: 60a3e3396c7b40068ad69970
|
|
title: Step 7
|
|
challengeType: 0
|
|
dashedName: step-7
|
|
---
|
|
|
|
# --description--
|
|
|
|
Before you can start styling the `div` you added, you need to link your CSS to your HTML.
|
|
|
|
Add a `link` element to link your `styles.css` file. Set the `href` to `./styles.css`, and remember to set the `rel` attribute to `stylesheet`.
|
|
|
|
# --hints--
|
|
|
|
Your code should have a `link` element.
|
|
|
|
```js
|
|
assert(/<link/.test(code))
|
|
```
|
|
|
|
Your `href` attribute should have the value `./styles.css`.
|
|
|
|
```js
|
|
assert(/href\s*=\s*('|")(\.\/)?styles\.css\1/.test(code));
|
|
```
|
|
|
|
Your `rel` attribute should have the value `stylesheet`.
|
|
|
|
```js
|
|
assert(/rel\s*=\s*('|")\s*stylesheet\s*\1/.test(code));
|
|
```
|
|
|
|
Your `link` element should have `href="./styles.css"` and `rel="stylesheet"` attributes
|
|
|
|
```js
|
|
assert(/<\s*link(\s+href\s*=\s*("|')(\.\/)?styles\.css\2\s*rel=('|")\s*stylesheet\s*\4|\s+rel\s*=\s*('|")\s*stylesheet\s*\5\s*href\s*=\s*("|')(\.\/)?styles\.css\6)\s*\/?>/.test(code));
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
<html lang="en">
|
|
<head>
|
|
<meta charset="UTF-8">
|
|
<title>Rothko</title>
|
|
--fcc-editable-region--
|
|
|
|
--fcc-editable-region--
|
|
</head>
|
|
<body>
|
|
<div class="canvas">
|
|
</div>
|
|
</body>
|
|
</html>
|
|
```
|