The Making of ricardopiana.com

The Making of ricardopiana.com

Ricardopiana.com was born for a reason that cannot be summed up in a line of "who I am" or in a list of accomplishments. It was born because, at a certain point, the sum of the fragments no longer holds: projects, notes, inventions, ironies, attempts, dignified failures, small flashes that last like matches and then ask for a place where they don't extinguish immediately.

It is born when you realize that you are speaking with many voices and that you don't want to reduce them to a single tone to please the market, the algorithm, the fear of being misunderstood. It is born when you get tired of being a "profile," and you want to return to being a "page." A page that does not scroll away as soon as you touch it, a page that is not a showcase, but a room. Here, first of all: ricardopiana.com wanted to be a livable room, not a billboard.

A place where time is not always fleeing, where thought can arrive late without apologizing.

The necessity is artistic before it is technical: it is the necessity of a rhythm. Social media teach you to speak in apnea, to say everything before the audience yawns, to break the sentence into quick touches as if you were throwing crumbs to pigeons. But art, even when made of technology, needs a different breath: a breath that is not measured in impressions but in resonance.

There are words that do not want to be "engaging," they want to be true. There are ideas that get offended if you confine them to a carousel. There are experiences that, if you package them in a consultant's headline, lose dignity and become merchandise of the soul.

The site was born to defend this simple and almost scandalous thing: that one can write and build without shouting.

Yet, to properly say what ricardopiana.com is, you must start from what it is not. It is not a portfolio, even if it contains traces of work and works. It is not a resume disguised as a story, even if a biography is inevitable, like dust on furniture. It is not a landing page with a knife between its teeth and a form lurking behind the curtain. It is not a "niche" blog because the idea of niche, on the web, is often just an elegant cage: you put yourself inside, then close it and say "positioning."

It is not a place where every page must have a call to action, as if the human being needed to be pushed to do anything, even think. It is not, above all, a declaration of war on the world. It did not want to become a monument to itself, which is the easiest thing: just write in a definitive tone, use big words, put a photo where you always look a bit more confident than you really are. Instead, no. Here the idea was the opposite: to leave space for doubt, and to make it comfortable.

To build such a space requires a map. Not a geographical map, but a moral map: where to place things without turning them into confusion, and without forcing them to become "brands." The solution came in the form of four words, simple and uncomfortable because they are not editorial labels, they are states of being: Systems, Story, Play, Products.

They are not drawers to stuff articles into; they are like four doors of the same house. If you enter through one or the other, you find the same person, but you find them in a different posture.

Story is the door of origin, of context, of flesh. It is where things are told because they happened, because they left marks, because a life is not a list but a trajectory.

Systems is the door of structure, of method, of invisible architectures: the way a project, a team, a thought, an idea that wants to become something stable is organized.

Play is the door of exploration, of deviation, of curiosity that does not yet have a contract with the world: experimentation, controlled risk, intuition that does not ask for permission.

Products is the door of the object that you can hold in your hand, use, adopt: not necessarily sell, but make available, transferable, replicable.

Four words that prevent you from doing the most common thing: mixing everything into a single lukewarm soup, where every content has the same face and the same "brand voice." Not here. Here, everything must declare in which state it is. If it is a story, let it not pretend to be a method. If it is a method, let it not disguise itself as poetry. If it is play, let it not justify itself as strategy. If it is a product, let it not hide behind the alibi of art.

This choice has a beautiful side effect: it forces you to respect time. Because each section lives with a different metabolism. Story is not in a hurry: it can stay there, motionless, like a photograph that does not age. Systems demands slowness and revision: you cannot talk about structures if you have not walked through the mud. Play, on the other hand, is quick, sprightly: it is born and dies, sometimes leaving only a note, a lab trace, a laugh. Products require maturation: you cannot call something a "product" that is still an idea with flat tires.

So ricardopiana.com, already in its architecture, rejects the unique time of the feed. It does not ask you to publish every day. It asks you to publish when you have something that holds.

The relationship with time, here, is almost a small revolt. The web asks you for continuity, as if continuity were a value in itself, and not a consequence of quality. But continuity, often, is just anxiety dressed as discipline. Ricardopiana.com is born from a different pact: to accept the unfinished as a legitimate phase, to accept that one section grows more than another, to accept that some texts are as short as a note, others long as a walk uphill. And above all, to accept that rereading is more important than immediate reaction.

That a piece of content, here, should not "perform" but should remain. To remain means: to still be valid in a year, in two, when you reopen it and do not feel ashamed.

At this point, technique enters, but it enters like a good theater technician: it must work a lot and be seen little. The choice to use Ghost, for example, is not a cult of the "new CMS" nor a geek's game. It is a choice of infrastructure: to write and publish with a clean, fast, manageable system that allows you to care for content and publishing without turning into the maintainer of your own voice. Ghost has been, in this sense, a piece of solid scenery: it allows you to have a readable, high-performing site, with good control over themes, tags, structure, and with the possibility of letting writing and distribution coexist without going crazy. But the technique remains underneath, because the ambition of the site is not to show the hardware. The ambition is that the hardware supports the weight of the house.

And here there is an important thing: technique is not just efficiency, it is respect. Performance, accessibility, SEO, not as a growth hack but as education. If you make a site that is all image and no text, you are telling a part of the world: "you do not enter." If you do not take care of alternative texts, semantic structure, readability, you are building a beautiful stage with broken stairs.

The site, therefore, had to make peace with a simple concept: beauty cannot be an obstacle. It must be an invitation. Even the architecture of tags and sections is born from this: to help the reader orient themselves, not to get lost. Which is a subtle difference, because getting lost can sometimes be fascinating, but only if you choose to do it, not if you are pushed into it.

Writing, then, required a decision almost musical. I didn't want textbook sentences, nor the air of a preacher. I wanted prose that could be witty and ironic without becoming elitist, that could use imagery without becoming hazy, that could afford technical precision when needed, but not turn into a disguised lecture.

Here, inevitably, influences come into play: I lived in Bologna for a long time, I was a poet, I can't help but think of Roversi for his moral density, for his ability to make thought resonate as matter, for that way of being within things without turning them into slogans; nor of Benni for his irony, for the grotesque distortion that saves from solemnity, for that lateral gesture that makes you see the world askew and therefore better. But "influence" does not mean imitation. Influence is like a wind: you feel it in the branches, but the tree remains yours.

Writing for ricardopiana.com also means rejecting the aesthetics of quick instruction. It is not an "educational" site in the sense of tutorials. It is a site that shares applied thought, distilled experience, and often leaves open questions. This is important: today, a lot is published, but little is questioned. The content is full of certainties because certainties sell. But a serious place, even if it plays, must know how to say "I don't know" without feeling defeated. The culture of the feed pushes you to be always definitive; the site allows you to be honest. And honesty, online, is a rarer technology than any LLM.

Then there is the question: who does this place speak to? Here it is wise to be ruthless, because sites that want to speak to everyone end up speaking to no one, and become digital decor. Ricardopiana.com is not designed for those looking for shortcuts, for those wanting "five tricks for," for those living off psychological templates and emotional optimizations. It is not for those who measure everything in conversions and consider anything that doesn't produce a number as wasted time.

It is for those dealing with complexity, with real work, with systems that must hold up, with creativity that does not want to become a mask. It is for those who feel that speed is not a value, it is a symptom. It is for those who seek direction, not noise.

And it is here that the site becomes a "product" in a particular sense. Not in the commercial sense, but in the sense of an editorial object built with intention. A minimal product, yes: pages, words, structure, a way of orienting. A product that is not sold like a vacuum cleaner, but that produces value because it exists and because it is readable. A product that, if it works, does not make you click more: it makes you think better. Which is a terrible goal to put in a KPI, and indeed it should not be put. It should be lived.

If in the future some parts of this site become truly adoptable products, good. Some content may transform into shareable systems, tools, services, things that others can use without having to go through your personal story. But not everything must transform. Some things will remain traces, notes, partial maps. And that is fine. The contemporary obsession is to turn everything into assets: every thought must be monetizable, every page must be a lever. Here, instead, there is the more sober and radical idea: that a part of human production has the right not to be converted. That it exists because it exists. Like a notebook, but with the door open.

This, after all, is the making of: not the chronicle of plugins and templates, not the behind-the-scenes of a fair, not the "success story" with a motivational soundtrack. It is the tale of a necessity: to put writing and construction back at the center as acts of care. Making a site today is a counter-intuitive, almost anachronistic gesture, because the web pushes you to dissolve into other people's platforms.

Making a site is saying: here is a home, and if you want to enter, come in without haste. I won't grab you by the neck. I won't sell you the moon. I offer you a room, a map, a bit of light, and also some shadows, because without shadows light becomes advertising.

And so yes: ricardopiana.com has a reason. Not a single reason, but a composed reason, like certain complex machines that work because each piece accepts not to be the protagonist. It is a center of gravity, a living archive, a room, a moral map.

It is a place where things can be Story without pretending to be Systems, can be Play without having to justify themselves, can become Products without betraying their origin.

And if this site has a future, it will be a slow future, growing in layers, like real cities, not like renderings. A future in which technique will continue to do its work below, silently, and art will continue to do its work above: bringing order to chaos without taking away chaos's energy. Because, in the end, the only thing truly worth building online is a place that resembles you a bit, but is also free enough to host others.

Is your project stuck at a technical hurdle?

Book 15 minutes