Technical notes, decisions, experiments, and updates from Arqora.
A maintained record of how Arqora studies systems, makes technical decisions, documents experiments, and turns internal work into public software over time.
15 published notes
A technical note on making Arqora notes readable for people, search crawlers, and AI systems.
Arqora notes should be readable as normal pages and also understandable to automated systems.
Structured data, clean metadata, and stable routes help crawlers interpret the content correctly.
The goal is not to game indexing, but to make the project easier to understand.
An experiment note on shaping Arqora CMP around inbound messages, ticket history, and operational control.
Arqora CMP is being explored as a practical system for handling inbound communication and support workflows.
The important parts are tickets, message history, reply state, routing, and auditability.
The project is still experimental, so the design favors clarity over feature volume.
A decision note on keeping Arqora infrastructure simple while the project is still forming its core systems.
Arqora does not need heavy infrastructure before the product surface and workflows are clear.
Simple hosting, generated pages, and managed services reduce operational load at the early stage.
The system can still be designed with future migration paths in mind.
A note on separating public contact paths for general messages, security, legal, support, and partnerships.
Arqora separates public contact routes so different kinds of messages do not collapse into one inbox.
Clear addresses make security, legal, support, and partnership messages easier to triage.
The routing is simple today, but it leaves room for future ticketing and operational workflows.
A technical note on the early indexing, canonical, sitemap, and crawlability decisions behind arqora.be.
The first SEO work focused on making arqora.be crawlable without exposing duplicate deployment URLs.
Canonical URLs, sitemap entries, robots rules, and metadata were treated as infrastructure, not decoration.
The goal was to make the site understandable to crawlers before adding more public pages.
A design note on keeping the Arqora website clean, technical, and focused instead of overfilled.
The Arqora website is intentionally minimal so the technical content can stay readable.
A cleaner interface makes the project feel more deliberate and less like a generic landing page.
The design system should support trust without adding unnecessary visual noise.