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>
75 lines
1.6 KiB
Markdown
75 lines
1.6 KiB
Markdown
---
|
|
id: 5f3477aefa51bfc29327200b
|
|
title: Step 15
|
|
challengeType: 0
|
|
dashedName: step-15
|
|
---
|
|
|
|
# --description--
|
|
|
|
You have styled three elements by writing CSS inside the `style` tags. This works, but since there will many more styles, it's best to put all the styles in a separate file and link to it.
|
|
|
|
We have created a separate `styles.css` file for you and switched the editor view to that file. You can change between files with the tabs at the top of the editor.
|
|
|
|
Start by rewriting the styles you have created into the `styles.css` file. Make sure to exclude the opening and closing `style` tags.
|
|
|
|
# --hints--
|
|
|
|
Your `styles.css` file should have the `h1, h2, p` type selector.
|
|
|
|
```js
|
|
const css = code.split('<!DOCTYPE html>')[0];
|
|
assert(__helpers.removeWhiteSpace(css).match(/(h1|h2|p),(h1|h2|p),(h1|h2|p){/))
|
|
```
|
|
|
|
Your selector should set the `text-align` property to `center`.
|
|
|
|
```js
|
|
const css = code.split('<!DOCTYPE html>')[0];
|
|
assert(css.match(/text-align:\s*center;?/));
|
|
```
|
|
|
|
You should only have one selector.
|
|
|
|
```js
|
|
const css = code.split('<!DOCTYPE html>')[0];
|
|
assert(css.match(/text-align:\s*center;?/).length === 1);
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta charset="utf-8" />
|
|
<title>Camper Cafe Menu</title>
|
|
<style>
|
|
h1, h2, p {
|
|
text-align: center;
|
|
}
|
|
</style>
|
|
</head>
|
|
<body>
|
|
<header>
|
|
<h1>CAMPER CAFE</h1>
|
|
<p>Est. 2020</p>
|
|
</header>
|
|
<main>
|
|
<section>
|
|
<h2>Coffee</h2>
|
|
</section>
|
|
</main>
|
|
</body>
|
|
<html>
|
|
```
|
|
|
|
```css
|
|
--fcc-editable-region--
|
|
|
|
--fcc-editable-region--
|
|
|
|
```
|