Pages built without UX thinking or a plan for maintenance go generic, stale or unused. So the goal was never more pages; it was a system: sites that drive adoption, need little upkeep, and serve both end users and contributors.

20 weeks, 350 hours, one site every two to three weeks. Each site ran the same three-step cycle, and the community bonding period went to the brand, the design system and a component blueprint, so the cycle could start fast.

The site list changed with my mentors during the summer: the AOSSIE website, MoveYourBody and Support Us Button came in, and a DebateAI gateway design took Djed Alliance's slot. Every commitment still landed, and so did work the proposal never asked for.

The brand lives in Figma; the design system lives in code. Components name what a colour is for, never which colour it is, so both themes come from one set of components and a palette change is one edit in one file.

Mobile runs on simulated slow 4G: every site scores 100 on Best Practices and SEO, and 96 to 100 on Performance.

The palette is built around Golden Wallet #FFCD00 and Baggy Green #00843D, Australia's national colours, with neutrals for both themes. Inter carries everything, from a 72px display size down to 14px captions, so any project can fall back to it.

More than ten logos were redrawn as clean SVGs, including Fate, CarbonTracker, Chainvoice, OrgExplorer, Zplit, Djed and Djed Alliance, plus a new logo for the Skills Ecosystem. They replaced the PNGs across AOSSIE, Stability Nexus and Djed Alliance sites.

An animated intro built from the brand colours and the logo, for videos, events and social media.

Zplit's first commit was a "website kickstart based on Template-Repo-NextJS", and Resonate and PictoPy were moved onto the same structure. Fixes found on one site, like the root route that keeps link previews on a static export, went to all of them.

Every navbar item, section and element mapped to where it takes the visitor: down the page, into the QR code modal (with a device switcher and store links), or off the site. Coral pills are redirections.

The flow's Download Now path, in code: Android goes straight to the Play Store, while iOS and desktop get the QR code. It finished the summer with 275 tests covering 99.6% of the code base.

Release 2.3.0 scopes all of its CSS to the component, so importing it never restyles the host page. That change is what let every AOSSIE site adopt it, and it ships with 148 tests at 100% statement coverage, published to npm as @aossie-org/support-us-button.

Content tests fail the build on any missing key or placeholder, and an agent skill keeps project translations in sync, so adding a project can't silently break the other 12 languages.

An indexing bug had given every sub-page the home page's canonical URL, telling search engines to ignore them. Each page now has its own canonical, matching the sitemap.

The device-based download button sits in the navbar and comes back in the hero and at the end of the page as a download reminder, so the visitor is never more than a glance from it.

Download buttons detect the platform and resolve the latest GitHub release, so the link never goes stale. The logic is a pure function, covered by unit and property tests.

GitHub's configure-pages action was silently rewriting `next.config.ts` and breaking the i18n setup in production. My first fix treated the symptom; the second found the cause. Since then I read the build logs before patching.

Unlike the other sites, Perspective is a web app, so its navbar is the product: Home, Impact, Contribute, About and Contact, with the Get Perspective button looping back to the input on the interactive globe.

The backend fetches any article URL it's given, so the security review's server-side request forgery finding mattered most. A new backend suite of 229 tests (99.7%) runs in its own CI.

Besides llms.txt, the site publishes openapi.json and /api/info, kept in sync with the page by a test, and its robots.txt welcomes AI crawlers. It ships with 260 tests at 99.7%.

Most visitors are copying code, and many are new to it. So the framework picker reveals only the steps for that framework, every block gets copy to clipboard, tooltips explain the technical terms, and the navbar's Share uses the library itself.

The library had no tests before the summer; it now has a suite with property-based tests that gates every npm release. Release 1.1.0 closed an XSS path and added a labels option, which is how the Hindi pages of every AOSSIE site translate it.

GitHub Pages can't run a server, but i18n routing assumes one, so bare domains exported as empty pages with no link preview. A small root route now ships the default locale's full metadata and redirects instantly.

A Pages action silently rewrote the Next.js config on one site; a stale config file overrode the real one on another. The fix was the same: read the build logs and config precedence instead of patching symptoms.

Re-solving i18n, themes, SEO and CI for every site wasn't sustainable. The template and design tokens made each site faster than the last, and two-week blocks with weekly public updates kept all eight on schedule.

• Designing a brand system that scales across products, with implementation in mind.
• Next.js static export with i18n, RTL locales and SEO that crawlers actually read.
• Test suites that cover a whole code base, CI/CD, and building and publishing npm packages.
• Writing PRs that are easy to review, and documenting for the next contributor.

To my mentors Bruno and Madhav for their reviews and trust, and to the AOSSIE community. Every design is public in Figma, and the full report, with every pull request, is on GitHub.