@daowolf/system-design-quest 0.0.0-stage → 1.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +21 -0
- package/README.md +64 -2
- package/content/LICENSE.md +8 -0
- package/dist/chapters.json +4154 -0
- package/dist/element.js +4 -0
- package/dist/element.js.map +7 -0
- package/dist/style.css +792 -0
- package/package.json +62 -3
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 Oleg Desantis
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
package/README.md
CHANGED
|
@@ -1,3 +1,65 @@
|
|
|
1
|
-
#
|
|
1
|
+
# System Design Quest
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
Practise system design interviews as a game. Training chapters build the
|
|
4
|
+
knowledge; quests are katas where you design one product end to end.
|
|
5
|
+
|
|
6
|
+
**Try it:** [daowolf.com/system-design-quest](https://daowolf.com/system-design-quest)
|
|
7
|
+
|
|
8
|
+
## What you get
|
|
9
|
+
|
|
10
|
+
- **Training:** eight chapters, from the interview method to core concepts,
|
|
11
|
+
key technologies and patterns. They open in order, or jump into any of them.
|
|
12
|
+
- **Quests:** design a URL shortener, a rate limiter, file storage and sync,
|
|
13
|
+
nearby places and ride booking. Every quest is open from the start.
|
|
14
|
+
- **Eleven kinds of challenge:** trade-off duels, filling and labelling
|
|
15
|
+
diagrams, spotting the flaw, estimates, written answers, lightning rounds,
|
|
16
|
+
timed sprints and more.
|
|
17
|
+
- **Points for right answers only.** A miss costs nothing and comes back later.
|
|
18
|
+
- **An optional profile:** add who you're interviewing with and when, for a
|
|
19
|
+
countdown. Leave it empty and the game works the same.
|
|
20
|
+
- No account, no adverts, and nothing you type leaves your browser.
|
|
21
|
+
|
|
22
|
+
## Use it on your own page
|
|
23
|
+
|
|
24
|
+
```html
|
|
25
|
+
<script type="module" src="element.js"></script>
|
|
26
|
+
<system-design-quest static></system-design-quest>
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
Keep `style.css` and `chapters.json` next to the script (and
|
|
30
|
+
`element.js.map`, if you want source maps). Add `theme="dark"` or
|
|
31
|
+
`theme="light"` to override the visitor's setting.
|
|
32
|
+
|
|
33
|
+
Get the files one of two ways:
|
|
34
|
+
|
|
35
|
+
- **npm:** `npm install @daowolf/system-design-quest`, then copy
|
|
36
|
+
`node_modules/@daowolf/system-design-quest/dist/` into your site at build
|
|
37
|
+
time. npm shows which commit and workflow built each version (provenance).
|
|
38
|
+
- **A [release](https://github.com/dao-wolf/system-design-quest/releases):**
|
|
39
|
+
GitHub signs each one, so you can check where it came from.
|
|
40
|
+
|
|
41
|
+
## Develop
|
|
42
|
+
|
|
43
|
+
You need Node 22 or later, pnpm 10 and Python 3.10 or later.
|
|
44
|
+
|
|
45
|
+
```sh
|
|
46
|
+
pnpm install
|
|
47
|
+
python3 -m pip install -r requirements.txt
|
|
48
|
+
pnpm dev # local page on port 4181
|
|
49
|
+
pnpm check # everything CI runs
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
## How it's tested
|
|
53
|
+
|
|
54
|
+
- **Journeys:** Playwright plays the built game on a host page, under a strict
|
|
55
|
+
security policy, with axe checking accessibility.
|
|
56
|
+
- **Logic:** unit tests on the scoring engine and the content gate.
|
|
57
|
+
- **Content gate:** a script checks every challenge against its schema, length
|
|
58
|
+
limits and an allowlist of sources before it can ship.
|
|
59
|
+
- **Mutation testing:** Stryker changes the scoring engine on purpose; the
|
|
60
|
+
tests must notice.
|
|
61
|
+
- **Security:** lint rules, dependency checks and code scanning.
|
|
62
|
+
|
|
63
|
+
## Licence
|
|
64
|
+
|
|
65
|
+
Code: [MIT](LICENSE). Challenges: [CC BY 4.0](content/LICENSE.md).
|
|
@@ -0,0 +1,8 @@
|
|
|
1
|
+
# Licence for the challenges
|
|
2
|
+
|
|
3
|
+
The challenges in this folder are licensed under the
|
|
4
|
+
[Creative Commons Attribution 4.0 International licence (CC BY 4.0)](https://creativecommons.org/licenses/by/4.0/).
|
|
5
|
+
|
|
6
|
+
You may share and adapt them for any purpose, if you credit
|
|
7
|
+
"System Design Quest by Oleg Desantis" and link to
|
|
8
|
+
https://github.com/dao-wolf/system-design-quest.
|