Technical demonstration
The product in pictures, and the files behind it.
Everything on this page comes from native Aries blocks. The screenshots show RC20 running.
See the screensA ten-second tour
This external player stays blocked until you choose to open it. No request is sent to YouTube when the page loads.
A few RC20 screens



Content remains readable outside Aries.
A page keeps its metadata, blocks and translation in an ordinary JSON file. Media stays in uploads. It is less spectacular than an online service, but much easier to take over.
A page, in plain sight
{
"title": "My page",
"status": "published",
"builder": [
{ "type": "hero" },
{ "type": "text" },
{ "type": "gallery" }
]
}Aries
Storage: JSON files · Extensions: built-in scope · Updates: controlled ZIP archive · Intended use: independent showcase site.
Extensible CMS
Storage: often an SQL database · Extensions: module ecosystem · Updates: depends on the platform · Intended use: projects of every size.
This table does not try to declare a winner. It simply explains why Aries exists: some websites benefit from a smaller tool rather than a more extensible one.
This page is the best test.
Resize it, switch language and browse the blocks: the showcase is its own demonstration.