+
+### Our new Discourse Server
+
+We have mentioned in multiple previous blog posts how we would like to reduce our reliance on GitHub. Whilst our assessment of Codeberg will run in the background via our website development work stream, Codeberg does not have a comparable feature to GitHub Discussions. As such, we looked at our wider options and found Discourse to be a good option for our needs and a forum platform that is fairly widely used within the wider open source community.
+
+The Discourse team were kind enough to sponsor the project with a free hosted instance, which we have gladly accepted.
+
+Over the course of the last month, we have worked with a number of our Trusted Contributors to start using the forum and to provide feedback. We believe the forum is now ready for wider public use and can continue to iterate on the design as we get more familiar with it.
+
+One area of feedback has been a concern that having a more traditional forum on top of our Zulip server may end up splitting the community between two platforms and/or give users two places to "keep up" with aerynOS. We hear the feedback but are also conscious that different users will have different preferences on how they wish to interact with the project. If in the medium to long term, we feel that maintaining two community locations isn't beneficial, we can always adapt our approach again.
+
+You can find the Discourse server [here](https://aerynos.discourse.group/). Sign up, look around and get involved!
+
+
+
+### Branding and visual identity
+
+
+
+During our [April blog post](https://aerynos.com/blog/2026/04/30/rebranding-upgrading-and-wallpapering-aerynos-april-glow-up/) we launched our new logomark, moving away from our older LLM-created A symbol. As the project continues to evolve, and as new members with design expertise join our community, we are continuing to refine our branding.
+
+One of the more visible changes is a transition from `AerynOS` to `aerynOS`. We are working through our various repositories to ensure consistency with the new spelling but this will take some time. Most of the high-visibility areas, such as our website, have already been transitioned.
+
+Concurrently, relatively new contributor [Nona](https://codeberg.org/nona) has been working with us on refining the project's visual identity. The existing triquetra logo is **not** being replaced. Instead, we are refining the shades of orange and green used by the project and working through the choice of font and kerning to bring the various elements of our branding together more consistently. It's important to note part of this fine-tuning is also to consider various accessibility needs such as different forms of colour blindness. We take accessibility considerations fairly seriously within this project.
+
+This is a relatively small piece of work compared with the engineering happening elsewhere in the project, but completing these details will allow us to finally bring the visual side of the aerynOS rebrand to a more finished state.
+
+### Website development and code licensing
+
+We have ramped up progress on our website redesign over on [Codeberg](https://codeberg.org/aerynOS/dotcom) in the last month. Whilst not yet ready to launch, it is nearing "completion", although we may end up launching the site in stages.
+
+The goal is to eventually deliver a single site that covers what both our [dotcom](aerynos.com) and [dotdev](aerynos.dev) currently cover. However, we may split this into two transitions, with the main site transitioning first and our dotdev documentation site moving over at a later stage once we have done a full review of the documentation and brought it in line with the current state of the project.
+
+One important point to note is that we have created a new repository for this work. We had originally created a brand new repository for the Hugo/Hextra redesign but that meant that we had not copied over authorship history from the existing website. We have now forked our existing website and subsequently overlaid our new Hugo/Hextra work on top to maintain as much of the git history as we can.
+
+As part of our website work, we noted that there wasn't any licence attributed to the code. We had a look at what is considered standard practice in this area for other Linux distributions, as well as the licences used by Astro, Hugo and Hextra, and have decided on licensing our website code as MIT, our blog posts as CC BY-ND 4.0 and our documentation as CC BY-SA 4.0. This has already been applied to our current websites and will carry over to our new site once it is launched.
+
+
+
+
+
+## Next Steps
+
+There are several major pieces of work already in progress which will continue into the next month.
+
+The EROFS metadata-image work will continue towards a production-ready implementation, with the `fstree` abstraction and overlay-image driver providing the foundation for this work.
+
+The moss CLI refactor will continue through [PR #687](https://github.com/aerynOS/os-tools/pull/687), while [PR #788](https://github.com/aerynOS/os-tools/pull/788) will continue to develop the new search experience.
+
+We're also expecting the new TUI version of lichen to go through additional rounds of development based on the feedback from community testing. Once the outstanding issues have been addressed and the installer has received sufficient testing, we can begin looking towards including it in a future ISO.
+
+There is still plenty to do, but the work across `moss`, `boulder`, `lichen` and the recipes infrastructure is increasingly building on the foundations we have established within the project to date.
+
+## Supporting the project
+
+If you would like to support the project, you can do this in multiple ways. You can help with documentation, supporting our website redesign in Hugo/Hextra, get involved with deeper code development or join us in our [Zulip server](https://aerynos.zulipchat.com/)r and help us grow our community!
+
+Outside of this, you can also help support the project financially through one of our supported sponsorship platforms.
+
+
+
+We are always open to engagement with hardware vendors and infrastructure partners around the open source community. We have been lucky enough to engage with some very cool businesses to provide hardware or service solutions sponsorship. If you would like to get in touch to discuss any sponsorship opportunities, please reach out to us at [contact@aerynos.com](mailto:contact@aerynos.com).
+
+## Thank You!
+
+We are very grateful for your support, be it financial or via project contributions in the form of carefully written bug reports, code contributions, design contributions, documentation updates, general feedback, package updates and overall enthusiasm around the project.
+
+We hope that you will continue showing enthusiasm for our project, and that you will want to get involved in whichever way, shape, or form works for you!
diff --git a/src/content/docs/blog/2026/08/31/A community that works together, builds together/rebrand.webp b/src/content/docs/blog/2026/08/31/A community that works together, builds together/rebrand.webp
new file mode 100644
index 00000000..76148c4b
Binary files /dev/null and b/src/content/docs/blog/2026/08/31/A community that works together, builds together/rebrand.webp differ
diff --git a/src/content/docs/blog/2026/08/31/A community that works together, builds together/unsplash-welding.webp b/src/content/docs/blog/2026/08/31/A community that works together, builds together/unsplash-welding.webp
new file mode 100644
index 00000000..715123e2
Binary files /dev/null and b/src/content/docs/blog/2026/08/31/A community that works together, builds together/unsplash-welding.webp differ