Gremus.it
What was the problem?
Gremus was born from two interests that have been part of my story for a long time: music and popularization.
Those who want to approach music often encounter two extremes. On one hand, very simplified content; on the other, academic explanations that presuppose prior knowledge.
Music theory is a clear example: relatively simple concepts can become difficult when they are presented through abstract definitions before they are even experienced.
The same happens with classical music and opera. You don't need to be a musicologist to appreciate them, but a few interpretive keys can radically transform the way you listen to them.
Gremus was born to occupy this space: to tell and explain music with rigor, but from the point of view of those who want to understand it, listen to it, or start practicing it.
How did I reason through it?
Over the years, Gremus has grown as an independent publishing project, gathering content on music reading, musical instruments, practice, history, listening, and opera.
The approach has deliberately remained accessible.
When I explain a theoretical concept, I try to start from musical experience before the definition. When I talk about an opera, the goal is not only to recount its plot or history, but to provide tools that allow one to listen to it differently.
An article dedicated to opera, for example, starts from the relationship between word, music, and stage to show how these can simultaneously build different levels of narrative; interpretation then becomes a further element that makes each performance different.
Articles dedicated to instruments also seek to answer the concrete questions of those who want to begin: how to choose an instrument, how to study it, what difficulties to expect, and what path to follow.
The site has therefore grown not around a single software function, but around a content architecture designed to accompany different ways of approaching music.
What changed?
Gremus has over time become an archive of musical content that continues to be found and read even after long periods without regular publication.
The most significant part of this outcome is the longevity of the content.
Articles dedicated to music reading, theory, instruments and opera continue to answer questions that do not depend on current events: how to read notes on the staff, understand a rhythm, begin studying an instrument, or approach opera. The current structure of the site clearly preserves these different entry points.
Today Gremus also represents for me an editorial heritage on which it is possible to build again: new content, exercises, learning materials and, potentially, versions in other languages.
But above all it is one of my longest-lived projects and it tells of a principle that I continue to apply in software too: explaining a problem well often means removing complexity, not adding it.
Measurable outcomes