The full idea is much bigger than V1
Culture Atlas becomes enormous very quickly if I let every good idea into the first version.
I can imagine maps, timelines, audio, video, biographies, stories, historical regions, collections, school activities, translations, accounts, saved journeys, recommendations, community contributions and many other features. Almost all of those ideas could be useful. That is exactly the problem.
If I try to build all of them before anyone can use Culture Atlas, I may spend a very long time building features without learning whether the central idea works.
I need V1 to answer questions, not prove that I can add features
I have started thinking about the first version as an experiment. Its job is not to look like the final Culture Atlas. Its job is to help me learn whether the foundations are right.
There are five things I especially want to test.
1. Will a map actually make people curious?
I like the idea of entering through India because it gives people an immediate visual starting point. But liking the idea is not evidence that it works.
I need to see whether someone naturally clicks, explores and keeps moving—or whether the map looks impressive but does not actually help discovery.
2. Are my core record types useful?
Right now I am thinking about records such as Place, Language, Community, Tradition and Story, with people and sources connected through the system as well.
But a neat data model on paper can fail when it meets real cultural material. I need to add enough real records to discover where the categories become awkward, where something belongs in more than one place, and where I am missing an important type altogether.
3. Do relationships make exploration feel natural?
This is the main idea behind Culture Atlas, so V1 has to test it.
If I open one record, do the connections make me want to open another? Do I understand why the records are connected? Can I move between places, people, languages, traditions and stories without feeling lost?
If the answer is no, then having a technically correct graph is not enough.
4. Can sources remain visible without making the experience heavy?
I want evidence and further reading to stay connected to cultural records. But I also want Culture Atlas to feel inviting to a curious student or visitor who is exploring for the first time.
V1 needs to help me find that balance: sources should be easy to inspect without turning every page into a wall of citation details.
5. Can the Atlas grow without changing code for every record?
This is a practical requirement. If adding a new tradition or place means editing the website code each time, the project will become difficult to maintain very quickly.
The content needs to live as structured data that can be added and updated independently from the interface. The website should read from that structure rather than having cultural information hardcoded into individual pages.
That is less visible than a map or animation, but it may be one of the most important things V1 proves.
What I am deliberately leaving out
This is the harder list because “later” can feel like “no.” I am learning that they are not the same thing.
Accounts can wait. Saved collections can wait. Advanced timelines can wait. Recommendation systems can wait. Large media libraries can wait. Complicated contribution workflows can wait. Features designed for many different audiences can wait.
Some of these may become important. But none of them are necessary to answer the five questions above.
I am also leaving out false completeness
There is another kind of scope I need to control: content scope.
Culture Atlas cannot document all of India before it launches. Trying to make the first release look nationally complete would create pressure to add shallow records just to fill the map.
I would rather begin with a smaller set of records that are researched properly, connected meaningfully and sourced clearly. The goal of V1 is to prove the system, not to pretend the archive is finished.
What “done” means for the first version
V1 is not done when I have added every feature I can imagine.
It is done when another person can enter the Atlas, discover a real cultural record, follow meaningful connections, understand where important information came from, and continue exploring without me explaining how the product works.
That is a much harder test than a checklist of features, but it is also much more useful.
A smaller first version can teach me more
I used to think reducing scope meant reducing ambition. I now think it can protect the ambition.
If the central idea is strong, a smaller version gives me a way to discover what it needs next. If the central idea has problems, I want to learn that before building a large system around it.
Real use should decide what deserves to become V2.
V1 can still become an excuse
Calling something a “first version” is useful because it keeps the project small. But it can also become an excuse for confusing design, weak research or unfinished basics.
I want to separate features that can wait from foundations that cannot. A fancy recommendation system can wait. Clear navigation, honest sourcing and records that actually connect cannot.
I can treat V1 like an investigation
Instead of thinking of V1 as a smaller finished product, I can think of it more like a maths or I&S investigation. I begin with questions, decide what evidence would help answer them, test the system and then change my conclusion if the evidence does not support my first idea. That is more useful than adding features simply because they look impressive.
A first version should answer a question
Building Culture Atlas is not only about deciding what to make. It is also about deciding what not to make yet.
Every feature has a cost: time to design it, build it, test it, fill it with content and maintain it. Saying yes to everything would make it harder to learn anything clearly.
What I'm figuring out next
The next phase has to move from architecture to evidence.
I need to start putting real records through the system, see where the model breaks, test how the map and relationships feel, and document the decisions that change because of what I find.
That is where the journal should become more concrete too: not only what I think Culture Atlas should be, but what happens when I actually try to make it work.
Follow the build
This is the end of the first six entries: from the original question to the first-version plan. The next entries will follow the actual build, the records, the interface and the things I have to change once the idea meets real use.