[ note ] Case note · 2026-09-06

Ala del Mar: a 27-page home for a life's work.

Antonio López Sánchez is a Cuban heroic fantasy novelist, poet, and cultural journalist. He writes from Alamar, the Havana neighborhood facing the sea, and closes his books with a formula of his own: "Hallado en Ala del Mar. bene scriptus". His body of work spans decades; what it lacked was a home on the internet. This note tells how antoniolopezsanchez.art was built, and why every technical decision came from one very concrete condition: the site had to run on its own.

[01] The brief

A client who can't administer anything.

The author lives in Cuba, with an unstable connection, and his craft is writing, not configuring dashboards. That ruled out, from the start, everything that demands maintenance from the owner: no WordPress, no plugins, no databases, no subscriptions to renew. The answer was our usual architecture taken to its logical extreme: pure static HTML, self-hosted fonts, WebP images, and a custom generator that turns one data file per book into its complete page. Adding book fifteen will mean editing a text file and running a script. The writer writes; the house takes care of itself.

[02] The numbers

Measured today, verifiable by anyone.

27 indexable pages. 14 books, each with its own page: synopsis, excerpt, and edition data. 7 documented awards, 10 poems, and 2 readings in the author's voice. The homepage weighs 10 KB of HTML and the whole site, fonts and images included, 315 KB: less than a single phone photo. Desktop Lighthouse: 100 performance, 100 accessibility, 100 best practices, 100 SEO, with zero layout shift (CLS 0). The same numbers anyone can check with Google's public tool.

For humans

The writer's desk

Navy and gold, classic book typography, the author's seal as a signature. No generic author template: the visual world comes from his own books and from the way he closes them. The literary texts are always published in Spanish, their original language; that's an editorial decision, not a technical one.

For machines

The author as an entity

53 structured data blocks across 27 pages: the person with his awards, each book as a work, breadcrumbs on every route. Plus an llms.txt with the author's citable facts, a robots.txt that welcomes AI assistants, IndexNow, and verification on Google and Bing. When someone asks about him, the source exists and is in order.

[03] AEO for a person

Positioning an author means positioning an entity.

Almost everything written about AEO talks about local businesses. This case is something else: a person with a body of work. The underlying job was the same, telling machines who he is, what he has done, and where to verify it, but the material is biography, bibliography, and awards instead of opening hours and service areas. Each book has its own page because each book is a question someone may ask, and AIs cite clean answers, not walls of text. It's the doors-not-walls architecture, applied to a lifetime of work.

[04] The door with a handle

The high-intent detail.

There's a discreet line on every book page: the rights for editions and translations outside Cuba are available, with a directory that says exactly who to write to. It's the principle of fewer clicks, better clicks applied to the publishing world: the visitor who truly matters here is an editor or a translator who already knows the work, and when they arrive, the page can close on its own: the answer, the proof, and the path to contact, without friction. An author website is not a display case; it's a rights office open 24 hours a day.

[ related ] To follow the thread

The live site: antoniolopezsanchez.art. This case's sibling format: 07 Sound Solution, the 14 KB credential. And the doctrine behind the rights detail: Fewer clicks, better clicks.

[ → ] And your work?

If your work deserves a home, make it one that runs on its own.

Writers, musicians, professionals: an author website that's fast, ordered, and readable by the machines that now answer for you.

Let's talk