Files

99 lines
1.6 KiB
JSON
Raw Permalink Normal View History

{
"name": "Learn CSS Flexbox by Building a Photo Gallery",
feat: enable new curriculum (#44183) * 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>
2021-12-20 10:36:31 -08:00
"isUpcomingChange": false,
"usesMultifileEditor": true,
"hasEditableBoundaries": true,
"dashedName": "learn-css-flexbox-by-building-a-photo-gallery",
feat: enable new curriculum (#44183) * 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>
2021-12-20 10:36:31 -08:00
"order": 6,
"time": "5 hours",
"template": "",
"required": [],
"superBlock": "2022/responsive-web-design",
"challengeOrder": [
[
"61537485c4f2a624f18d7794",
"Step 1"
],
[
"61537a8054753e2f1f2a1574",
"Step 2"
],
[
"61537bb9b1a29430ac15ad38",
"Step 3"
],
[
"61537c5f81f0cf325b4a854c",
"Step 4"
],
[
"61537c9eecea6a335db6da79",
"Step 5"
],
[
"61537d86bdc3dd343688fceb",
"Step 6"
],
[
"615380dff67172357fcf0425",
"Step 7"
],
[
"615f171d05def3218035dc85",
"Step 8"
],
[
"6153893900438b4643590367",
"Step 9"
],
[
"6153897c27f6334716ee5abe",
"Step 10"
],
[
"615389bd81347947ea7ba896",
"Step 11"
],
[
"6153908a366afb4d57185c8d",
"Step 12"
],
[
"615392916d83fa4f02f7e2cf",
"Step 13"
],
[
"6153938dce8b294ff8f5a4e9",
"Step 14"
],
[
"6153947986535e5117e60615",
"Step 15"
],
[
"61539e07e7430b528fbffe21",
"Step 16"
],
[
"61539f32a206bd53ec116465",
"Step 17"
],
[
"6153a04847abee57a3a406ac",
"Step 18"
],
[
"6153a3485f0b20591d26d2a1",
"Step 19"
],
[
"6153a3952facd25a83fe8083",
"Step 20"
],
[
"6153a3ebb4f7f05b8401b716",
"Step 21"
]
]
}