Notebook / Service as Software
Why this website has no stock photos.
On 16 September 2026 we removed two 20-second films, three families of editorial images and several renders from this website. All of it was generated material. This note explains what is there instead and the rule we use to decide what gets published.
Author: Alfonso del Busto · Published: .
The problem with pretty pictures
We sell systems that can be reviewed: a route with states, owners and evidence. Illustrating that with an abstract film or a stock office contradicts what we say. And there is a more concrete problem: our product-state register forbids publishing screenshots of something that does not exist. A render of a “multi-client” panel that is not deployed is exactly that.
What is there now
- System plates. Diagrams with numbered nodes that show the real sequence of an engagement: input, rule, system, review, evidence. They are HTML and CSS, weigh under a kilobyte and read on a phone without cropping.
- Screenshots when the product exists. The KeneaFactu demo is synthetic and says so on screen; the screenshots in our proposals are taken from the real application running locally with sample data.
- Text with names, numbers and dates. A notebook where we say what we did and when, not articles about “digital transformation”.
What we measure
The site is static HTML generated with Astro. The home page loads about 13 KB of CSS and runs no JavaScript to render. In our Lighthouse measurements of 15 September 2026, the home page and the projects page scored 100 for performance, accessibility, best practices and SEO. Removing the videos made none of that worse; it made it better.
The rule
Before publishing an image, a number or a card, we ask what information it encodes. If it encodes none, it is not published. The same goes for numerals: three digits only for the project portfolio, two for the steps of a process, none for lists that are not a sequence. It is a boring rule. That is why it works.