docs/wiki-page-map.md holds the draft structure and validation checklist for your 10-note personal wiki static site project. You’re building this project as a low-stakes way to practice static site generator (SSG) fundamentals, with no complex backend or database required, all content stored as plain markdown files you can port to any hosting platform or editing tool in the future. The 10 notes cover low-waste living topics you’ve researched over the past 6 months, so you don’t have to write new content from scratch, just organize existing snippets and connect them logically to create a usable, interconnected resource for yourself and any other readers who stumble on it.
File contents baseline
This is the unedited state of the file as you open it today, with no changes made yet. The core of the file is a pre-populated table that lists all 10 core wiki notes, their assigned URL slugs, topic focus, and minimum required inbound links to ensure the wiki works as an interconnected resource instead of a set of isolated, unconnected pages. You set the minimum inbound link counts based on how many other topics naturally reference each note, so higher-volume reference lists like the reusable kitchen swap guide have higher requirements than narrower, more specific guides like the small-space composting tutorial.
| Note ID | Slug | Topic | Minimum required inbound links |
|---|---|---|---|
| 1 | /notes/zero-waste-grocery-tips | Zero-waste grocery shopping hacks for people on tight budgets | 3 |
| 2 | /notes/compost-apartment-setup | Small-space apartment composting guide for renters with no outdoor access | 2 |
| 3 | /notes/reusable-kitchen-swap-list | Durable reusable kitchen swaps for beginners who hate single-use plastic | 4 |
| 4 | /notes/sustainable-laundry-routine | Low-waste laundry routine for renters who can’t install permanent appliances | 2 |
| 5 | /notes/upcycled-furniture-basics | Beginner upcycled furniture projects under $50 for small apartments | 3 |
| 6 | /notes/thrift-store-shopping-strategies | Thrift store shopping strategies for high-quality home goods that last 10+ years | 2 |
| 7 | /notes/zero-waste-bathroom-swaps | Zero-waste bathroom swaps for people with sensitive skin and product allergies | 3 |
| 8 | /notes/sustainable-pet-care-tips | Low-waste pet care for indoor cat owners who want to cut down on plastic waste | 2 |
| 9 | /notes/community-food-share-basics | How to join or start a local community food share to cut down on household food waste | 3 |
| 10 | /notes/circular-living-myth-busting | Common circular living myth busting for people new to low-waste lifestyle changes | 4 |
Illustrative example: If you only added 7 total inbound links across all notes instead of the 28 total required here, 75% of your internal link opportunities would be unused, making the wiki far less useful for readers who want to explore related topics without navigating back to a central home page every time. The baseline file also has a blank placeholder section for the internal link validation checklist, which is the only section you edit in this session. Build Next Stack’s static site project guide recommended mapping internal links before writing any deployment code to avoid broken link errors that delay launch, so you’re following that framework to keep the project on track.
One edit to add internal link validation checklist
This is the only edit you make to the file today, no changes to the core map table or any other existing content. You fill the blank placeholder section with a clear, pass/fail numbered checklist that you’ll use to validate all internal links once you finish drafting the individual markdown notes for each entry in the map. You write each step to be as specific as possible, so you don’t have to guess if a link is valid when you run through the checklist later:
- For every note, confirm all outbound links point to a valid slug listed in the map above, with no typos in file paths, missing leading slashes, or extra trailing slashes that would cause 404 errors in the deployed static site.
- Count inbound links for each note to meet or exceed the minimum listed in the map, prioritizing contextual links that fit naturally in the content instead of forced links added only to hit the quota.
- Add a “Related notes” section at the bottom of every individual markdown note that lists 2-3 linked notes relevant to the current topic, even if those links are already included in the main body text, to give readers clear next steps for exploration.
- Test every internal link locally using your SSG’s built-in development server before pushing any changes to your repository, to catch broken links that don’t appear when editing raw markdown files in your text editor.
- Flag any notes that have more than 8 outbound internal links for revision, to avoid overwhelming readers with too many off-topic navigation options mid-content that pull them away from the core topic they came to read.
You add a short line below the checklist that any new notes added to the wiki after the initial launch first get added to this map before you write any content for them, to keep the structure consistent as the project scales. You don’t add any deployment or hosting steps to this file, since those live in your repository’s root README, and you want this map to only cover content structure, not dev ops tasks. You save the edit and close the editing pane, no other changes made to the file in this session.
Next open state for this map file
The next time you open docs/wiki-page-map.md, you have already finished drafting all 10 individual markdown notes and you’re ready to run through the validation checklist end to end. You don’t make any changes to the core map table in that next session unless you find a clear logical gap in the internal link structure that requires adjusting the minimum inbound link counts for a small number of notes, like if you realize the composting guide is referenced far more often than you initially expected when you set the 2-link minimum.
When you open the file, you have your SSG dev server running in a split terminal pane, so you can click through each link as you check it off the list to confirm it loads the correct page without errors. You bring a short list of notes you flagged as having too many outbound links while drafting, and you cross-reference them with the map to decide which links to move to the related notes section instead of cutting them entirely, so you keep all relevant connections without cluttering the main body text. You also bring a handful of new topic ideas you came up with while drafting the 10 core notes, like a guide to low-waste office supplies for remote workers, and you add those to a new “Future note ideas” section at the bottom of the map that you’ll prioritize once you deploy the first version of the wiki. You don’t add any of those future notes to the core map table yet, since they’re not part of the initial 10-note launch scope.
The next time you close this file, every item on the checklist is marked as complete, all internal links are tested and working, and you’re ready to run your SSG build command and deploy the first version of the wiki to your chosen static hosting platform. You’ll use this same map file as the single source of truth for all content structure changes as the wiki grows, so you never end up with orphaned pages or broken links as you add more topics down the line. (Word count: 1382)