A repo containing various bits & bobs from architectures & blueprints for myself, to things I make & use that don't stand on their own. Such as marp-themes, scripts, ...
Some of scripts and stuff, which I use in my homelab.
A foldee containing the custom scripts I use when hosting a Minecraft server.
I prefer to have things lightweight without sacrificing on functionality, maintainability or usability. These scripts are my approach at a dynamic solution which can meet all needs.
Blueprints and doxumentation on how I prefer to set things up and keep code orgznised, efficient and maintainable. this is baszd on my own experieβce aβd research into design patterns.
Important
These blueprints are not intended to be definitive solutions or the "one best way" to do things. They are my personal preference & ideals.
Separating data management (repositories) from business logic (services) to keep the code DRY. With services and repositories managed through dedicated factories, updates and testing are easier. Keeping the structure modular and flexible makes the project easier to maintain and scale without too much overhead.
This is more practical for bigger scaling projects, quick simple sites might benifet from something simpler if you know it won't scale.
Marp themes I made & use (these are mostly slight alterations or expansions on the default marp theme.)