* 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>
102 lines
2.2 KiB
Markdown
102 lines
2.2 KiB
Markdown
---
|
|
id: 5d822fd413a79914d39e98cc
|
|
title: Step 4
|
|
challengeType: 0
|
|
dashedName: step-4
|
|
---
|
|
|
|
# --description--
|
|
|
|
Add a `title` element to the `head`, and give your project a title of `freeCodeCamp Skyline Project`. Also, nest a self-closing `link` element in the `head` element. Give it a `rel` attribute value of `stylesheet`, a `type` attribute value of `text/css`, and an `href` attribute value of `styles.css`.
|
|
|
|
# --hints--
|
|
|
|
Your code should have a `title` element.
|
|
|
|
```js
|
|
const title = document.querySelector('title');
|
|
assert.exists(title);
|
|
```
|
|
|
|
The `title` element should be within the `head` element.
|
|
|
|
```js
|
|
const head = document.querySelector('head');
|
|
// TODO: head does not contain title...body contains title
|
|
```
|
|
|
|
Your project should have a title of `freeCodeCamp Skyline Project`.
|
|
|
|
```js
|
|
const title = document.querySelector('title');
|
|
assert.equal(title.text.toLowerCase(), 'freecodecamp skyline project')
|
|
```
|
|
|
|
Remember, the casing and spelling matters for the title.
|
|
|
|
```js
|
|
const title = document.querySelector('title');
|
|
assert.equal(title.text, 'freeCodeCamp Skyline Project');
|
|
```
|
|
|
|
Your code should have a `link` element.
|
|
|
|
```js
|
|
assert.match(code, /<link/)
|
|
```
|
|
|
|
You should not change your existing `head` tags. Make sure you did not delete the closing tag.
|
|
|
|
```js
|
|
const heads = document.querySelectorAll('head');
|
|
assert.equal(heads?.length, 1);
|
|
```
|
|
|
|
Your `link` element should be a self-closing element.
|
|
|
|
```js
|
|
assert(code.match(/<link[\w\W\s]+\/>/i));
|
|
```
|
|
|
|
Your `link` element should be within your `head` element.
|
|
|
|
```js
|
|
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`.
|
|
|
|
```js
|
|
assert.match(code, /<link[\s\S]*?rel=('|"|`)stylesheet\1/)
|
|
```
|
|
|
|
Your `link` element should have a `type` attribute with the value `text/css`.
|
|
|
|
```js
|
|
assert.match(code, /<link[\s\S]*?type=('|"|`)text\/css\1/)
|
|
|
|
```
|
|
|
|
Your `link` element should have an `href` attribute with the value `styles.css`.
|
|
|
|
```js
|
|
assert.match(code, /<link[\s\S]*?href=('|"|`)(\.\/)?styles\.css\1/)
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
<html>
|
|
--fcc-editable-region--
|
|
<head>
|
|
|
|
</head>
|
|
--fcc-editable-region--
|
|
<body>
|
|
</body>
|
|
</html>
|
|
```
|