make communit-at presentable

Author: essential-randomness

astro.config.mjs

@@ -2,6 +2,7 @@
 import { defineConfig } from "astro/config";
 import starlight from "@astrojs/starlight";
 import starlightSidebarTopics from "starlight-sidebar-topics";
+import starlightLinksValidator from "starlight-links-validator";
 
 // https://astro.build/config
 export default defineConfig({
@@ -24,7 +25,7 @@ export default defineConfig({
             link: "/sociocracy",
             items: [
               {
-                label: "Example Guide",
+                label: "About Sociocracy",
                 autogenerate: { directory: "sociocracy" },
               },
             ],
@@ -43,11 +44,15 @@ export default defineConfig({
           {
             label: "FujoCoded Resources",
             icon: "seti:db",
-            link: "/fujowebdev",
+            link: "/fujowebdev/style-guide",
             items: [
               {
-                label: "Writing for FujoGuide",
-                autogenerate: { directory: "fujowebdev" },
+                label: "FujoGuide Style Guide",
+                autogenerate: { directory: "fujowebdev/style-guide" },
+              },
+              {
+                label: "Extra Bits",
+                autogenerate: { directory: "fujowebdev/extras" },
               },
               {
                 label: "GitHub Resources",
@@ -56,6 +61,7 @@ export default defineConfig({
             ],
           },
         ]),
+        starlightLinksValidator(),
       ],
     }),
   ],

package-lock.json

@@ -13,6 +13,7 @@
     "@astrojs/starlight": "^0.36.1",
     "astro": "^5.14.5",
     "sharp": "^0.32.5",
+    "starlight-links-validator": "^0.19.2",
     "starlight-sidebar-topics": "^0.6.2"
   },
   "repository": {

package.json

@@ -1,17 +1,25 @@
 ---
-title: Notes from Writing the Learn-Along
+title: Ms Boba's Extra Notes from Writing the Learn-Along
 sidebar:
   order: 6
 ---
 
-Notes from my review of our learn-along, that show changes I made and how I
+Notes from my [Ms Boba's] review of our learn-along, that show changes I made and how I
 came to them. I had to formulate principles post-facto, as I never really
 spelled them out before.
 
 I had already seen (and written part of) the writing beforehand. Hopefully
 this will help me get it right quicker myself next time—I keep forgetting
 this is how we write.
 
+:::caution[Classic Ms Boba]
+
+I changed a lot of this again before shipping the learn along, so some of this may be
+inaccurate/different in the final version. I think the general principles hold, but
+take all this with a big asterisk.
+
+:::
+
 ## Fortune Generator — Before You Start
 
 I'll go through each change by bit, but if you want to read the before/after in full,
@@ -177,7 +185,7 @@ you can find it here.
 
 ### The Preamble
 
-Principles extracted:
+Principles I extracted:
 
 - **Active, narrative voice:** Don't describe what the code is, actively (and
   cheerfully) explain what it does.
@@ -224,13 +232,15 @@ Extra things I considered changing:
 
 ### Prerequisites #1
 
-Principles extracted:
+Principles I extracted:
 
 - **Write _to_ the audience:** Address the reader directly, set clear
   expectations, and anticipate questions they may have. Talk about different
   ways they might approach the material.
 - **Call to adventure:** You're telling the tale of a valiant hero that is about
-  to go fight a trecherous enemy (JavaScript). Your language should reflect that.
+  to go embark on a trecherous journey, and your language should reflect that.
+  Note that this doesn't mean that itself JavaScript is treacherous: it's just what
+  Boba-tan tells herself to psych herself up.
 - **Group related content, don't change "subject":** Paragraphs and sections
   often serve specific purposes. Don't let unrelated notes slip in: move them
   around, or reframe them so they match their surroundings.
@@ -347,7 +357,7 @@ What I notice:
 
 - **Frame challenges as fun, approachable, and within the person's reach:** When
   a task feels overwhelming, try thinking about what could make it easier for
-  them and where they're likely to get stuck. Try getting them "out of their
+  them and where they're likely to get stuck. Try getting them "out of their own
   heads".
 - **Normalize struggling with code, and encourage a growth mindset:** Where you can,
   offer suggestions on how to tackle a task, and remind people it's ok to struggle

src/assets/bobawip-color.png

@@ -4,6 +4,13 @@ sidebar:
   order: 1
 ---
 
+:::caution
+
+This style guide is an older version we've been reworking. New one will be
+published soon.
+
+:::
+
 Clear and approachable learning content for beginner-to-intermediate hobbyist
 web developers that is:
 
@@ -43,7 +50,7 @@ We assume they:
 As we write, we primarily imagine an audience that is:
 
 - **Very online**, aware of online memes and parlance
-- **Millennial**, coming online around the 00s-10s period (or wishing they had)
+- **Wistfully Millennial**, coming online around the 00s-10s period (or wishing they had)
 - **Nostalgic**, of a time when the internet didn’t take itself so seriously and
   possibilities felt endless
 - **Unapologetically passionate**, not afraid of being seen as “cringe” as they