Where the project comes from
Why I am building Aries.
I started out in computer hardware and now work as a business software consultant. Aries is my personal way of returning to more direct computing: fewer layers, readable files and a tool I can still understand months later.
“I would rather add fewer things and know why each one is there.”— Nicolas Gouraud
From hardware to a lighter web.
Hardware taught me to look at what is actually inside a machine. Consulting around EBP taught me that a useful tool must remain understandable to the person using it. Aries connects those two experiences.
A direction, not a label.
I favour readable files, system fonts and local media. I use low-tech inspiration and digital sobriety as directions; without a complete measurement, I do not claim that Aries is inherently “green”.
What this means in practice
- No SQL database to create or administer.
- Pages composed with native blocks.
- Documentation that also explains failures and limits.
- Downloadable backups to keep away from the server.
- No remote fonts or audience tracking added to this demo.
The size and impact of a site also depend on its images, videos and use. These are design choices, not a claim about a measured environmental footprint.
A deliberate scope
Aries is intended for small websites, personal projects and journals. It has one administration account and built-in blocks. Shops, visitor accounts, a plugin ecosystem and automatic static export are outside the scope of this version.
Look at how it actually works.
The workshop shows the blocks in context and the documentation explains how to reproduce them.