merge

README.md

@@ -2,6 +2,8 @@
 
 [![pyco:bytes – exploring the magic of Python, week by week](assets/pycobytes-title-full-new.png)](https://sup2point0.github.io/pycobytes)
 
+[Site](https://sup2point0.github.io/pycobytes) · [Issues](issues/) · [FAQ](faq.md) · [About](synopsis.md)
+
 </div>
 
 ---
@@ -30,6 +32,7 @@ If you’ve got questons, check the [FAQ](faq.md). You can learn about how pycob
 
 | issue | date | title |
 | :---- | :--- | :---- |
+| [12](issues/12.md) | 06/12/24 | *import math* |
 | [11](issues/11.md) | 03/12/24 | *Short Circuits* |
 | [10](issues/10.md) | 26/11/24 | *For Any, For All* |
 | [9](issues/09.md) | 19/11/24 | *OR and AND do WHAT now?* |

edu.md

@@ -1,8 +1,14 @@
 # *decoded* – pycobytes
 
-> [!NOTE]
+> [!Note]
 > This is part of my [*decoded*](https://github.com/Sup2point0/Assort/blob/origin/~dev/decoded.md) series, a collection of lessons learnt from each major project I’ve undertaken.
 
+
+<br>
+
+
+## Learnings
+
 - Front-end development is a little too fun.
 - Svelte is awesome.
   - What’s the difference between Svelte and SvelteKit?
@@ -11,3 +17,12 @@
   - So plan *pragmatically* rather than programmatically.
 - Sometimes, it pays to have a little faith.
   - That said, leaving stuff until the last minute really isn’t fun.
+
+
+<br>
+
+
+## Challenges
+
+- Statically rendering dynamic `/[slug]/` routes was painfully nontrivial.
+  - In the end, statically generating every page turned out to be more convenient. And hey, we made a [framework](https://github.com/Sup2point0/stranger-quarkdown) out of it!

faq.md

@@ -1,7 +1,7 @@
 # Fervently Anticipated Questions
 
 ### What’s this for?
-I originally came up with pyco:bytes as a supplement to the other programming competitions going on at my school – I thought, given the ubiquity of Python as an introductory programming language, it’d be awesome (and hopefully somewhat helpful) to show everyone all the cool stuff you can do in the language.
+I originally came up with *pyco:bytes* as a supplement to the other programming competitions going on at my school – I thought, given the ubiquity of Python as an introductory programming language, it’d be awesome (and hopefully helpful) to show everyone all the cool stuff you can do in the language.
 
 ### What level do I need to be at?
 Yeah, that’s a difficult one. Pycobytes was primarily conceived with intermediates in mind – that is, programmers who’ve grasped the basics of coding, but now want to expand their knowledge to a much wider world of programming. So, it does assume some familiarity with the basics of Python.
@@ -14,27 +14,29 @@ I mean, we’re absolutely learning *more* about Python here, but if you’re as
 I’d say think of pycobytes as *enrichment* to deepen your understanding of Python and programming in general =)
 
 ### What even is there to learn in Python?
-Well, well, well, I’m glad you asked. There is *so* much incredible stuff to learn in Python, so so much. If you’re curious, stick around ;)
-<!-- If you’re in doubt, just take a look at the [index](https://sup2point0.github.io/pycobytes/issues) ;) -->
+Well, well, well, I’m glad you asked. There is *so* much incredible stuff to learn in Python, so so much. If you’re in doubt, just take a look at the [index](https://sup2point0.github.io/pycobytes/issues) ;)
 
 ### How did you create all this?
 See [Hacking the Mainframe](https://sup2point0.github.io/pycobytes/dev)!
 
+### Is it just you?
+Yeup, just me running this for now!
+
 ### Where did the name come from?
 BLOOD AND DEATH
 
-\*cough\* In all seriousness, *many* alternatives were considered. As we know, there are only 2 hard problems in computer science: cache invalidation, naming things, and off-by-one errors.
+\*cough\* In all seriousness, *many* alternatives were considered, and it took a lot of internal conflict. As we know, there are only 2 hard problems in computer science: cache invalidation, naming things, and off-by-one errors.
 
-Anyway, a picobyte doesn’t actually exist, but I think it conveys the intent here pretty well =)
+Anyway, it’s a parody of *picobyte* with *py*, like most Python-related IPs. Ofc a picobyte doesn’t actually exist, but I think it conveys the intent here pretty well =)
 
-### How do you pronounce pyco:bytes?
+### How do you pronounce *pycobytes*?
 Hmm, ain’t that a question?
 
 ### Why the colon in pyco:bytes?
 Idek, I just thought it’d be perfect when designing the logo.
 
-### What does ‘pips’ mean?
+### What does ‘pips’ even mean?
 Hey Vsauce, Michael here!
 
 ### What are these colours?
-[supcode Nova](https://github.com/Sup2point0/supcode/tree/sup/resources/Nova)! Like ’em?
+[supcode Nova](https://github.com/Sup2point0/supcode/tree/sup/resources/Nova)!

issues/08.md

@@ -128,7 +128,7 @@ Enjoy the efficiency, but use judiciously!
 
 ## Further Reading
 
-- Woah, it’s actually called the *ternary conditional operator*! – [Wikipedia<sup>↗</sup>](https://wikipedia.org/wiki/Ternary_conditional_operator)
+- Woah, it *is* actually called the ternary conditional operator! – [Wikipedia<sup>↗</sup>](https://wikipedia.org/wiki/Ternary_conditional_operator)
 
 
 <br>

synopsis.md

@@ -1,16 +1,16 @@
 # Synopsis
 
-pyco:bytes was a pretty involved project, and tons of fun to work on!
+*pyco:bytes* is a pretty involved project, and tons of fun to work on!
 
 
 <br>
 
 
 ## Site
 
-The site is made using [Svelte](https://svelte.dev) and [SvelteKit](https://kit.svelte.dev). Code is mostly in JavaScript with a few standalone modules in [TypeScript](https://www.typescriptlang.ory) (I love type hinting, tho not static typing). We’re using [SCSS](https://sass-lang.com) for stylesheets, which is an incredible upgrade over plain CSS.
+The site is built using [Svelte](https://svelte.dev) and [SvelteKit](https://kit.svelte.dev). Code is mostly in JavaScript with a few standalone modules in [TypeScript](https://www.typescriptlang.org). We’re using [SCSS](https://sass-lang.com) for stylesheets, which is an incredible upgrade over plain CSS.
 
-It’s built with Svelte’s SSG prerendering, and then deployed to [GitHub Pages](https://pages.github.com), all automated through [GitHub Actions](https://github.com/features/actions). We’ve also got a couple of Python helper scripts automating some tasks during the build process, which has proven to be indispensably convenient.
+It’s built with Svelte’s [SSG](https://svelte.dev/docs/kit/adapter-static) prerendering, and then deployed to [GitHub Pages](https://pages.github.com), all automated through [GitHub Actions](https://github.com/features/actions).
 
 
 <br>
@@ -20,7 +20,7 @@ It’s built with Svelte’s SSG prerendering, and then deployed to [GitHub Page
 
 Issues are written in Markdown, before being injected into Svelte using the [MDSveX](https://github.com/features/actions) plugin. [PrismJS](https://prismjs.com) is used for syntax highlighting code blocks.
 
-Emails in the email newsletter are created using the [Ecosend](https://ecosend.io) email builder, which provides rich formatting capabilities. This then exports to raw HTML (with embedded CSS) which can be sent as a deliciously styled email!
+Emails in the email newsletter are created using the [Ecosend](https://ecosend.io) free [email builder](https://ecosend.io/free-email-builder/), which provides rich formatting capabilities. This then exports to raw HTML (with embedded CSS) which can be sent as a deliciously styled email!
 
 
 <br>
@@ -36,4 +36,4 @@ Oh, you found the clicky, did you? That’s connected to a [Napkin](https://napk
 
 ## Assets
 
-All assets were lovingly crafted in PowerPoint 2016 offline~
+All assets were lovingly crafted in PowerPoint 2016 offline =)