It started with a gift for a friend.
She had spent the last two years teaching herself to code - evenings after work, weekends, online courses, side projects, the slow and unglamorous process of switching careers. She had just landed her first developer role after years in a completely different industry. We wanted to give her something that marked the moment. Something that said: the work you put in to get here was real, and it mattered.
We searched. We found services that print your GitHub contribution graph. Green squares on a poster. Some offered different colour schemes. Some put it on a mug.
We ordered one. It arrived. It was fine. The print quality was decent. The data was accurate. But when we held it up and imagined it on a wall - a living room wall, an office wall, a wall that guests would see - something felt off.
It looked like a screenshot.
A nicely printed screenshot, yes. But still recognisably a grid of coloured squares from a website. It belonged in a developer cave, next to the rubber ducks and the "there is no place like 127.0.0.1" poster. It did not belong in a living room. It did not belong in a frame next to actual art.
So we built one ourselves. Manually. We took her contribution data and rendered it as a star atlas - every day a star, bright days large, quiet days faint, the whole pattern mapped onto a vintage celestial chart. We printed it on archival paper, framed it, and gave it to her.
She liked it. But it was his reaction that stopped us. Her boyfriend - who had no idea what GitHub was, who had never seen a contribution graph, who could not tell Python from JavaScript - looked at it and said: "That is beautiful. That is going on the wall."
Her parents said the same thing. They saw a star chart. They saw something that looked like it belonged in a museum. They had no idea it was made from code.
That reaction made us think: if the people who do not understand the work respond like this, maybe we have built something worth sharing. So we built Codex Stellarum to make it available to everyone. Not because the existing products were bad - they are not - but because we wanted something different. Something that a non-developer would look at and say "that is stunning" before they understood what it represented.
THE QUESTION THAT STARTED EVERYTHING
The question was simple: what if contribution data was not displayed as a grid, but as a sky?
Astronomers have been mapping stars for four hundred years. The star atlases of the seventeenth and eighteenth centuries - Bayer's Uranometria, Flamsteed's Atlas Coelestis, Cellarius's Harmonia Macrocosmica - are among the most beautiful documents ever printed. Copper-engraved, hand-lettered, precise and ornate. They hang in museums today not because the astronomical data is still useful, but because the craft of rendering that data was extraordinary.
What if we applied that same philosophy to code? What if every day a developer wrote code became a star - bright days large and luminous, quiet days small and faint - and the whole pattern was rendered in the language of celestial cartography?
Not a graph. Not a chart. An atlas.
THE DIFFERENCE
There are good products that print GitHub contribution data. CodePrints is probably the best known. They have been around for years, they have a loyal community, and they do what they do well. If you want your green grid printed on quality paper, they are a solid choice.
But they are solving a different problem. They are making the contribution graph physical. We are making it invisible.
When you look at a CodePrints poster, you know immediately what it is. The grid is recognisable. The squares are familiar. A developer sees it and thinks "that is a GitHub contribution graph." A non-developer sees it and thinks "that is something from a computer."
When you look at a Codex Stellarum atlas, you see a star chart. You see constellations of light on a dark sky. You see something that looks like it belongs in an observatory or a cartography museum. A non-developer sees it and thinks "that is beautiful." A developer sees it and thinks "wait - those are my commits."
That gap - between "that is from a computer" and "that is beautiful" - is the entire reason Codex Stellarum exists.
WHAT WE CHANGED
Everything about the rendering is different.
The visual language. Contribution data is mapped onto three astronomical layouts. The Chronicle arranges time as a vertical celestial timeline. The Planisphere renders years as concentric rings on a circular star map. The Helix spirals through time like a galaxy arm. None of them look like a GitHub page. All of them look like something you would find in a rare book collection.
The typography. Every atlas uses period-appropriate lettering. Latin inscriptions. Small capitals. The kind of typography you see on eighteenth-century engravings, not on a SaaS dashboard. The developer's name is rendered as if they were a celestial body being catalogued for the first time.
The themes. Four palettes, each inspired by a different era of astronomical illustration. Observatory, with its warm gold stars on deep navy. Blueprint, recalling cyanotype technical drawings. Parchment, evoking hand-drawn manuscript charts. Minimalist, for those who prefer clean modern lines. None of them are green.
The detail. A magnitude legend in Latin. Coordinate markings around the border. The developer's GitHub URL rendered in the style of a plate inscription. Every element is designed to reward close inspection - the kind of print where you notice something new the third time you look at it.
The paper. Printed on 200gsm enhanced matte art paper using Giclee technique - the same archival process used by galleries and museums. These prints are designed to last decades, not years.
WHO THIS IS FOR
CodePrints is a great gift for a developer from a developer. You both know what the grid means. The green squares are a shared language. It is a fun, geeky piece of wall decor and there is nothing wrong with that.
Codex Stellarum is for a different moment. It is for when you want the gift to transcend the profession. When you want it on the living room wall, not just the home office. When you want guests to ask "what is that?" and the answer to start a conversation rather than require a technical explanation.
It is for the developer who has spent a decade building things and has nothing physical to show for it. It is for the partner who wants to say "I see how hard you work" in a language that does not require understanding what an API is. It is for the engineering leader who wants something on the office wall that represents the team's work without looking like a dashboard.
It is, in the end, for the wall. Not the developer cave wall. The real wall. The one everyone sees.
THE GIFT
We gave our friend the atlas the week she started her new role. Helix layout, observatory theme, two years of contributions spiralling outward like a galaxy. Every evening she had spent learning, every weekend project, every tentative first commit - all of it rendered as stars.
She did not say "cool print." She stared at it. She found the dense cluster from the month she built her first full-stack app. She found the quiet stretch from the winter she almost gave up. She found the burst of activity right before the job interviews started.
But it was not her reaction that confirmed we had built the right thing. It was his. He walked in, saw it leaning against the wall, and said: "Where are we hanging that?"
Not "what is that." Not "is that a computer thing." Just: where are we hanging that.
That is what we wanted. That is why we built it. Not a better contribution print. A different kind of object entirely.
Something worthy of the work.
See your own sky. Free to preview, prints from £25. codexstellarum.com
Write about developers or developer culture? Join our affiliate programme - 25% revenue share, 10% off for your audience.