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>
83 lines
1.5 KiB
Markdown
83 lines
1.5 KiB
Markdown
---
|
|
id: 5d822fd413a79914d39e98d2
|
|
title: Step 10
|
|
challengeType: 0
|
|
dashedName: step-10
|
|
---
|
|
|
|
# --description--
|
|
|
|
Nest a `div` with a class of `bb1` in the background buildings container. Give it a `width` of `10%` and `height` of `70%`. "bb" stands for "background building", this will be your first building.
|
|
|
|
# --hints--
|
|
|
|
You should create a new `div` element.
|
|
|
|
```js
|
|
assert.equal(document.querySelectorAll('div').length, 2);
|
|
```
|
|
|
|
You should give the new `div` a class of `bb1`.
|
|
|
|
```js
|
|
assert.exists(document.querySelector('div.bb1'));
|
|
```
|
|
|
|
You should use a `.bb1` class selector to style the element.
|
|
|
|
```js
|
|
assert.exists(new __helpers.CSSHelp(document).getStyle('.bb1'));
|
|
```
|
|
|
|
You should give the `.bb1` element a `width` of `10%`.
|
|
|
|
```js
|
|
assert.equal(new __helpers.CSSHelp(document).getStyle('.bb1')?.width, '10%');
|
|
```
|
|
|
|
You should give the `.bb1` element a `height` of `70%`.
|
|
|
|
```js
|
|
assert.equal(new __helpers.CSSHelp(document).getStyle('.bb1')?.height, '70%');
|
|
```
|
|
|
|
# --seed--
|
|
|
|
## --seed-contents--
|
|
|
|
```html
|
|
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<title>freeCodeCamp Skyline Project</title>
|
|
<link href="styles.css" rel="stylesheet" type="text/css" />
|
|
</head>
|
|
|
|
<body>
|
|
--fcc-editable-region--
|
|
<div class="background-buildings"></div>
|
|
--fcc-editable-region--
|
|
</body>
|
|
</html>
|
|
```
|
|
|
|
```css
|
|
* {
|
|
border: 1px solid black;
|
|
box-sizing: border-box;
|
|
}
|
|
|
|
body {
|
|
height: 100vh;
|
|
margin: 0;
|
|
overflow: hidden;
|
|
}
|
|
|
|
.background-buildings {
|
|
width: 100%;
|
|
height: 100%;
|
|
}
|
|
|
|
```
|
|
|