A template to get started with __frgmnt
Find a file
2025-11-26 23:02:59 +01:00
database [style] improved appearence around the edges of the screen 2025-11-25 20:27:29 +01:00
extensions [style] improved appearence around the edges of the screen 2025-11-25 20:27:29 +01:00
frgmnt-core@41807e091c [style] improved appearence around the edges of the screen 2025-11-25 20:27:29 +01:00
public [license] updated license 2025-11-26 23:02:59 +01:00
.gitignore big restructure to better organize later additions v2 2025-11-01 02:56:59 +01:00
.gitmodules moved 2025-11-15 12:40:22 +01:00
composer.json frontend has been decoupled from the core. example extension now renders the frontend 2025-11-07 23:22:00 +01:00
LICENSE big restructure to better organize later additions v2 2025-11-01 02:56:59 +01:00
readme.md Update template repo name 2025-11-15 13:03:07 +01:00

__frgmnt

This is the Content Management System for the dstwre.sh website.

Right now, it's basically finished, at least in the sense that it's functional and in active use. Of course, it'll never be truly done. I'll keep improving it over time.

This repo is not just the bare CMS: it's more of a template project. Alongside the core, it includes an extension that handles the entire frontend to demonstrate customizeablity. By doing this, I thought it would make it easier to understand how the whole thing fits together and how you might structure your own setup.

Repository layout

The template pulls in both the backend core and the default frontend extension as Git submodules:

Cloning this template for a new project now looks like this:

git clone --recursive git@codeberg.org:akkiirah/frgmnt-template.git my-new-site
or, when you've already cloned it without --recursive:
git submodule update --init --recursive

Keeping the core/frontend in their own repos makes it explicit when you need to pull updates (git submodule update --remote).

Most of the surrounding pieces are required to run the app anyway. The only part that isn't strictly tied to the CMS itself is that base extension. The idea is to make upgrading the core easier by keeping your own changes outside of it. Though I'm sure the setup is still far from perfect.

If you're a mad person curious enough to check this CMS out, you can head over to
https://dstwre.sh/projects/__frgmnt.

There you'll find an explanation of how things are set up and what you need to do to get it running yourself. The UX is probably absolutly horrendous, since this CMS is primarily built for my own workflow rather than broad public use. That said, if there's genuine interest in using it, I'm open to improving the setup workflow and making it more friendly to others.

License

This project is licensed under JNK 1.1 - an Anti-Capitalist, Share-Alike, Post-Open-Source license.

Use it, remix it, break it, rebuild it, make something your own and share it with the world.
Just dont sell it. Dont lock it behind paywalls. Dont wrap it in ads, NFTs, AI scraping, or subscription garbage.

If you extend or modify this work, release your version under the same license.
Keep it free, keep it open, and link back to the source.

This license exists to protect a space where creative work stays public and freely shared,
instead of getting buried in products or turned into someones revenue stream.

See LICENSE for full details.