People, Stories, Photos: One Interlinked Archive

A family history that lives across a dozen disconnected places — some stories in a shared document, some photos in a phone’s camera roll, a couple of details only one relative remembers — isn’t really preserved. It’s scattered, and scattered things get lost. MyBloodlines is built around a single idea: people, stories, and photos should never be islands. Each one should lead directly to the others.

Stories as their own entities, not notes on a profile

In a lot of family history tools, a story ends up buried as a text field on one person’s page — a paragraph about a childhood memory sitting under their birth date. That works fine as long as the story only involves one person. Most stories don’t.

In MyBloodlines, a story is its own entity, independent of any single profile. When you record the story of a family’s migration, or how two grandparents met, or the year a family business was started, that story gets written once and linked to everyone who was actually part of it — not copied into each of their profiles separately, and not flattened down into whichever single person’s page felt like the “owner.” A migration story linked to four family members shows up, in full, on all four of their profiles, because it genuinely belongs to all of them.

The real value of this structure shows up in how you move through it. Open a person’s profile, and alongside their core details and photo, you’ll see the full list of stories they’re connected to. Click into one, and you get the complete narrative — not a summary, but the actual account, along with a list of every other person involved in it, each one linking straight back to their own profile. From that story, click through to a photo attached to it, and you’ll see who’s pictured and which other stories that same photo is linked to.

Follow that loop for a few minutes and you start to see why it matters: a photograph of a family gathering isn’t just an image sitting alone. It connects to the story of that gathering, which connects to everyone who attended, each of whom connects to their own stories and photos in turn. Nothing dead-ends. There’s always another person, another story, or another photo to click into next. That continuous loop is what turns a set of disconnected facts into something that actually reads like a family’s history, rather than a pile of index cards.

Navigating the loop is how you explore; global search is how you jump. When you already know what you’re after, you can type a name or a few words from a story and MyBloodlines instantly returns any matching person or story within the part of the graph you’re allowed to see — no clicking through the graph to get there. Exploration and search are the whole payoff of recording: the reason to write all of this down is so that anyone in the family, now or a generation from now, can come back and actually find and follow it.

Single source of truth, not five conflicting copies

This interlinking only works because of something more structural underneath it: every person in MyBloodlines exists exactly once, as a single canonical record, not as a separate copy sitting inside each relative’s private version of “the family tree.” When your aunt looks at your grandmother’s profile and you look at it, you’re both looking at the same record — the same stories, the same photos, the same details — not two different versions that happened to be entered independently and might quietly disagree with each other.

That matters because the interconnection described above only holds together if there’s exactly one of each person to link to. If five relatives each kept their own separate copy of a grandmother’s profile, a story linked to her would have to somehow exist across all five copies, or worse, only in one of them — and the whole idea of clicking from a story to “everyone involved” would fall apart the moment two of those copies disagreed about who she even was. One canonical person, contributed to by everyone who has something to add, is what makes the whole archive navigable rather than fragmented. How that shared, single-copy structure gets built and maintained collaboratively is covered in one shared family history: how relatives record together.

Why this makes the archive last

An archive that dead-ends is an archive people stop using. If clicking on a story doesn’t lead anywhere, or a photo sits with no context about who’s in it, the record quietly becomes less useful every year, as the people who could have supplied that missing context are no longer around to ask. MyBloodlines is built so that every piece — every person, every story, every photo — carries its own connections with it permanently, so a grandchild looking at a photo decades from now can still click through to the story behind it and the people who lived it, without needing anyone alive to explain the context by hand.

That’s the real measure of an archive meant to be permanent: not how much it holds on day one, but how much of it still makes sense, unaided, generations later. For the broader picture of what MyBloodlines is trying to be and why it’s built this way from the ground up, start with what is MyBloodlines? Record your family history. And for the reasoning behind the one relationship rule that keeps every person’s record internally consistent as the bloodline grows, see why MyBloodlines only records parent-child ties. For how this interlinked approach sits alongside the rest of the family history category, see the best family history & genealogy apps compared.

Getting your first stories and photos connected

None of this requires doing everything at once. A single story, linked to the two or three people who were part of it, with one photo attached, is enough to start the loop — profile leads to story, story leads to photo, photo leads back to people. A practical walkthrough of writing your first story and linking it to everyone involved is covered in how to write a family story and link everyone in it.

Start recording your bloodline Claim your profile and begin at MyBloodlines →