WordPress · Genealogy · Custom Domains · Private Family Portals · Email Hosting · Reusable Deployment Model
A reusable online genealogy and family-identity solution developed from approximately 2023 onward for large extended families, including family trees with 500+ members, custom surname domains, private member directories, multi-generation relationships, collaborative data verification, and real mailbox accounts such as
firstname@familyname.com.
1. Project Overview
This project began around 2023 as a repeatable solution for families who wanted their own permanent online family presence.
The typical request was:
Register a domain under our family name, build our family tree online, and give family members their own family-domain email addresses.
Rather than building every site from zero, I created a reusable WordPress-based genealogy setup that could be adapted and deployed independently for different families.
The system supports:
- large family trees,
- hundreds of family members,
- multi-generation relationships,
- member search,
- private family directories,
- structured family-member profiles,
- custom surname domains,
- and real individual mailbox accounts.
Some deployments contain more than 500 family members.
2. Product Concept
The project can be summarized as:
Family / Clan
↓
Surname Domain
↓
Genealogy Website
↓
Family Member Directory
↓
Multi-Generation Relationships
↓
Private Family Access
↓
Custom Email Identity
firstname@familyname.com
This is more than a family-tree page.
It creates a persistent digital identity around the family name.
3. Period
2023 – Present
The solution is still evolving.
Over time, the architecture has gradually moved from repeated independent WordPress deployments toward a more reusable multi-family / multi-instance model.
It should not yet be described as a fully mature multi-tenant SaaS unless that architecture is completed.
4. Typical Customer Request
Families usually wanted:
- a domain based on the family surname,
- an online genealogy tree,
- profiles for family members,
- parent/child relationships,
- private access,
- and optionally custom email accounts.
Example:
familyname.com
with mailboxes such as:
ali@familyname.com
sara@familyname.com
reza@familyname.com
5. Large Family Trees
The system has been used for large extended families.
Some family databases exceed:
500 members
The genealogy model can continue as far as sufficient family data is available.
In practice, families commonly provide enough information to connect members across approximately three to four generations or more.
6. Relationship Model
The core information model connects people through family relationships.
Typical links include:
Parent
↓
Child
and the resulting tree can expand across generations.
The system is not limited to a fixed number of generations.
Its practical depth depends on the information supplied by the family.
7. Example Family Profile
A member profile contains core identifying genealogy data such as:
- photograph,
- first name,
- surname,
- birth information,
- family relationships,
- and other basic personal details required by the tree.
The current implementation is intentionally focused on genealogy.
It does not currently function as a full biography archive with:
- memories,
- long-form biographies,
- personal galleries,
- or historical stories.
This boundary is intentional.
8. Member Directory
The front end provides a visual directory of family members.
Known capabilities include:
- member cards,
- photographs,
- names,
- birth years,
- search,
- sorting,
- and navigation into individual member pages.
This gives users two views of the family:
Directory View
+
Relationship View
9. Search
The directory allows family members to be searched.
This becomes especially important once a tree grows to hundreds of people.
Instead of manually browsing the genealogy structure, users can locate a member directly.
10. Sorting
The member listing can be organized using fields such as:
- birth date,
- first name,
- last name.
This helps navigate large family datasets.
11. Person Detail Page
Each family member can have a dedicated page.
The page can display:
- photograph,
- name,
- birth information,
- age where appropriate,
- parents,
- and connected family relationships.
The interface can visually link the person to their parents.
12. Multi-Generation Genealogy
The tree is not limited to showing one parent-child relationship.
As data is entered, the structure can connect:
Great-Grandparents
↓
Grandparents
↓
Parents
↓
Children
↓
Grandchildren
and continue according to the available genealogy data.
13. Data Collection Process
Family information was not simply entered from one unverified source.
For large families, multiple people contributed to confirming the information.
The workflow was closer to:
Family Members Provide Information
↓
Multiple People Cross-Check
↓
Conflicts / Missing Data Resolved
↓
I Register the Confirmed Data
↓
Tree Updated
This was important because family-history data often contains conflicting recollections.
14. Collaborative Verification
Although I remained the main system administrator, the information itself was often verified collectively.
This helped improve:
- relationship accuracy,
- names,
- dates,
- and family connections.
The platform therefore combined centralized administration with distributed family knowledge.
15. Administrative Model
I remain the primary technical administrator.
Responsibilities include:
- domain management,
- WordPress deployment,
- plugin configuration,
- genealogy configuration,
- account management,
- data entry,
- privacy settings,
- hosting,
- and email configuration.
16. WordPress Foundation
The genealogy system uses WordPress.
A genealogy plugin provided the initial family-tree functionality.
Rather than presenting the plugin unchanged, I customized it to fit the required deployment model and visual/operational workflow.
This is accurately described as:
WordPress genealogy implementation with customized plugin behavior and reusable deployment structure.
It should not be described as a genealogy engine written entirely from scratch.
17. Reusable Core
The important architectural idea is reuse.
Instead of creating each family portal independently from zero:
Reusable Base
↓
Clone / Configure
↓
Family-Specific Domain
↓
Family-Specific Data
↓
Family-Specific Privacy
↓
Family-Specific Mailboxes
This significantly reduces the cost of deploying the same solution repeatedly.
18. Productized Service Model
The project gradually became a repeatable service rather than a one-off website.
The reusable components include:
- WordPress structure,
- genealogy configuration,
- presentation,
- privacy model,
- domain setup,
- hosting workflow,
- and email provisioning.
Only family-specific data changes significantly between deployments.
19. Independent Deployments
Historically, deployments have been separate WordPress instances/sites rather than one mature shared SaaS database.
Therefore the accurate description is:
Reusable independently deployed genealogy solution
rather than:
fully multi-tenant SaaS
The architecture is now gradually moving toward a more unified multi-family model.
20. Evolution Toward Multi-Family Architecture
As more families requested the same system, repeating all infrastructure independently became less attractive.
This naturally created pressure toward:
Reusable Family Platform
↓
Multiple Family Domains
↓
Shared Deployment Logic
↓
Family-Specific Isolation
This is the beginning of a multi-family architecture.
21. Domain Identity
Each family can use its own surname-based domain.
For example:
familyname.com
The domain becomes a permanent digital identity for the extended family.
22. Email Identity
One of the most distinctive parts of the solution is custom email hosting.
Family members can receive real mailbox accounts such as:
firstname@familyname.com
These are not display aliases only.
They are actual mailboxes that can be accessed through mail clients or webmail depending on the hosting configuration.
23. Why Family-Domain Email Matters
This creates a stronger identity than using generic addresses such as:
name123@gmail.com
Instead:
firstname@familyname.com
connects each person directly to the family domain.
This turns the domain into more than a website.
It becomes part of the family’s digital identity infrastructure.
24. Family Digital Identity
The solution therefore combines two types of identity:
Genealogical Identity
+
Digital Communication Identity
The website answers:
“How are we related?”
The email domain answers:
“How do we represent ourselves online?”
25. Hosting Management
I manage the technical hosting side.
This includes:
- domains,
- WordPress,
- website configuration,
- mailbox provisioning,
- and general administration.
This gives the project end-to-end operational ownership.
26. Privacy Evolution
The family sites were initially public.
As the amount of personal information increased, families later requested that the genealogy portals become private.
The access model therefore evolved:
Public Genealogy
↓
Growing Personal Dataset
↓
Privacy Concerns
↓
Private / Restricted Access
This was an appropriate response to the sensitivity of family data.
27. Why Privacy Became Important
A genealogy database may contain:
- photographs,
- full names,
- dates of birth,
- parent relationships,
- and information about multiple generations.
As the database grows, this becomes personally sensitive information.
The move from public to private access reflects that reality.
28. Public vs Private Architecture
Early versions prioritized easy access.
Later versions prioritized controlled visibility.
A modern family deployment therefore needs to consider:
- authentication,
- member access,
- authorization,
- search-engine indexing,
- and visibility of living persons.
29. Data Sensitivity
Public portfolio material must never expose real family datasets without explicit permission.
Screenshots should use:
- synthetic names,
- sample photographs,
- or anonymized demo data.
The current portfolio screenshots use demonstration-style identities and are suitable as design examples rather than proof of specific real-family records.
30. Genealogy as a Data Problem
At first glance, genealogy appears to be mainly a visual tree.
In practice, the harder problem is the data model.
Each person becomes an entity connected to other entities:
Person
├── Parent
├── Parent
├── Children[]
└── Family Connections
As hundreds of people are added, relationship consistency becomes increasingly important.
31. Relationship Integrity
A single correction can affect many displayed relationships.
For example:
Incorrect Parent
↓
Incorrect Branch
↓
Incorrect Cousin Relationships
↓
Incorrect Multi-Generation Tree
This makes collaborative verification valuable.
32. Scale
A tree with more than 500 people creates substantially different requirements from a 20-person family tree.
At that scale:
- search matters,
- sorting matters,
- profile navigation matters,
- data consistency matters,
- and privacy matters.
This gives the project more architectural significance than a small personal genealogy page.
33. User Experience
The visual solution uses:
- photographic member cards,
- a family-oriented hero area,
- search,
- member sorting,
- individual profiles,
- and visually connected parent relationships.
The design aims to make large family datasets understandable to non-technical users.
34. Family Member Cards
A typical card displays:
Photo
Name
Birth Year
This provides a compact directory view.
35. Profile Relationship Visualization
On a person page, the user can see parental relationships visually.
Example:
Mother Father
\ /
\ /
Member
This gives immediate context without requiring the user to interpret database fields.
36. Data Entry Workflow
The data-entry process is centrally controlled.
A typical workflow:
Family supplies data
↓
Other relatives verify
↓
Corrections resolved
↓
Administrator enters record
↓
Relationships connected
↓
Website updated
This avoids uncontrolled editing by hundreds of users.
37. Why Centralized Editing
For genealogy, unrestricted editing can introduce conflicting branches.
Centralized administration with distributed verification offers a balance:
Many Sources of Knowledge
+
One Controlled Data Entry Process
38. Technology Stack
Confirmed:
- WordPress
- genealogy plugin
- plugin customization
- custom domains
- web hosting
- email hosting / mailbox provisioning
- website access control
The exact plugin/version/hosting technology should only be documented from the live configuration or source.
39. Operational Scope
The project includes more than application development.
It also covers:
- DNS/domain management,
- website deployment,
- CMS management,
- email provisioning,
- user access,
- privacy configuration,
- data administration,
- and support.
40. Service Lifecycle
A typical deployment follows:
Family Request
↓
Domain Registration
↓
Hosting Setup
↓
WordPress Deployment
↓
Genealogy Configuration
↓
Family Data Collection
↓
Verification
↓
Tree Population
↓
Mailbox Creation
↓
Privacy Configuration
↓
Ongoing Administration
41. Repeatability
The strongest engineering characteristic is repeatability.
The second family does not require rebuilding the whole product.
Neither does the third.
This shifts the work from:
Custom Website Development
toward:
Productized Deployment
42. Current Architectural Direction
The project is increasingly moving toward a model where common functionality can be shared while each family keeps:
- its own domain,
- its own members,
- its own permissions,
- and its own identity.
This is the natural path toward a multi-family platform.
43. Potential Multi-Tenant Model
A future architecture could become:
Genealogy Platform
│
┌──────────────────┼──────────────────┐
↓ ↓ ↓
Family A Family B Family C
surname-a.com surname-b.com surname-c.com
│ │ │
Members A Members B Members C
Mailboxes A Mailboxes B Mailboxes C
Each family remains logically isolated.
44. Future Identity Model
A mature platform could treat the family domain as a tenant identity.
Example:
Tenant
├── domain
├── family name
├── members
├── genealogy
├── administrators
├── privacy rules
└── email provisioning
This would formalize the current repeated-deployment model.
45. Future Access Control
A commercial version could support roles such as:
Platform Admin
Family Admin
Editor
Verified Family Member
Viewer
Different families could choose different privacy policies.
46. Future Collaborative Editing
Currently, information is collaboratively verified but centrally entered.
A future system could allow controlled contributions:
Member Suggests Change
↓
Family Admin Reviews
↓
Approve / Reject
↓
Genealogy Updated
This could preserve data integrity while reducing administrative workload.
47. Future Change History
Genealogy data benefits from audit history.
A future platform could record:
- who suggested a change,
- previous value,
- new value,
- approval date,
- reviewer.
This would make disputed family information easier to manage.
48. Future Source Attribution
Genealogy facts could optionally record sources.
Example:
Birth Date
├── Family Testimony
├── Certificate
└── Historical Record
This would strengthen long-term data quality.
49. Future Privacy by Person
A stronger privacy model could distinguish:
- living members,
- deceased members,
- minors,
- public profiles,
- family-only profiles.
This becomes important as the platform scales.
50. Future Mail Provisioning
Mailbox creation could eventually become automated.
Example:
Approved Member
↓
Create Site Account
↓
Provision Mailbox
↓
firstname@familyname.com
This would turn hosting operations into a more automated platform capability.
51. Product Positioning
Recommended project title:
Online Genealogy & Family Digital Identity Platform
Alternative:
Reusable WordPress Family Tree & Custom-Domain Identity Solution
The first is stronger for the website while still remaining accurate if the description explains that the current implementation is based on reusable WordPress deployments.
52. Portfolio Classification
Recommended primary categories:
- Genealogy
- Family Platform
- WordPress
- Digital Identity
- Hosting
Secondary:
- Custom Domains
- Email Hosting
- Data Management
- Privacy
- Information Architecture
53. Portfolio Tier
Recommended:
Tier B — Strong Productized Solution / Recurring Deployment
Reasons:
- repeated customer demand,
- reusable solution,
- 500+ member datasets,
- multi-generation relationships,
- custom domains,
- mailbox provisioning,
- privacy evolution,
- active administration,
- movement toward multi-family architecture.
It is stronger than a typical WordPress portfolio item.
54. Career Evidence
The project demonstrates:
- Productization
- WordPress Customization
- Reusable Deployment Architecture
- Genealogy Data Modeling
- Large Dataset Administration
- Domain Management
- Email Hosting
- Privacy Design
- Information Architecture
- Operational Ownership
- Customer Delivery
55. Website Hero
Online Genealogy & Family Digital Identity Platform
WordPress · Genealogy · Custom Domains · Private Family Portals · Email Hosting
Built a reusable online genealogy solution for large families, combining multi-generation family trees, searchable member directories, custom surname domains, private access, centralized data administration, and real mailbox accounts such as firstname@familyname.com.
56. Website Project Card
Family Genealogy & Digital Identity
WordPress · Genealogy · Custom Domains · Email
A reusable family platform supporting 500+ member trees, multi-generation relationships, private family directories, surname-based domains, and individual family-domain mailboxes.
57. Short Website Card
Online Family Tree Platform
Reusable private genealogy websites for large families with custom domains, searchable family trees, and real firstname@familyname.com email accounts.
58. One-Line Description
Built a reusable WordPress genealogy solution for large families, including 500+ member trees, private access, custom surname domains, and real family-domain mailboxes.
59. CV Entry
Online Genealogy & Family Digital Identity Platform — WordPress / Hosting / Email
Developed a reusable WordPress-based genealogy solution from 2023 onward for large extended families, including deployments with 500+ members. Customized an existing genealogy plugin, managed multi-generation relationship data, member search and profiles, custom surname domains, private-access conversion, hosting, and real mailbox provisioning such as firstname@familyname.com. Family data is collaboratively verified by multiple relatives and centrally administered for consistency. The solution is gradually evolving toward a more unified multi-family architecture.
60. Short CV Entry
Built reusable private genealogy portals for families with 500+ members, custom surname domains, relationship trees, hosting, and real family-domain email accounts.
61. Architecture-Focused CV Entry
Productized repeated WordPress genealogy deployments into a reusable family-identity solution combining genealogy data, per-family domains, privacy isolation, centralized administration, and mailbox provisioning.
62. Interview Story — Situation
Multiple families repeatedly asked for the same type of service:
- a domain using their surname,
- an online family tree,
- and family-specific email addresses.
63. Interview Story — Task
Avoid treating every request as a completely separate website project.
Create a reusable base that could be quickly adapted to each family.
64. Interview Story — Action
I built a reusable WordPress deployment around a genealogy plugin, customized the presentation and behavior, handled domains and hosting, populated multi-generation trees, centrally managed data validated by several relatives, and provisioned real email mailboxes on the family domain.
As databases became larger and more sensitive, I also migrated deployments from public access to private/restricted access.
65. Interview Story — Result
The same core solution can now be reused for multiple large families, including trees with more than 500 members.
Repeated demand is gradually pushing the architecture toward a unified multi-family model.
66. Technical Interview Version
“This started because several large families asked for essentially the same thing: register a domain under our surname, build our genealogy online, and give family members email addresses on that domain. I used WordPress and an existing genealogy plugin as the base, customized it, and turned it into a repeatable deployment model rather than rebuilding every site from zero. Some trees now exceed 500 people. Several relatives verify the genealogy data together, but I keep data entry centrally controlled so relationships stay consistent. I also manage the domains, hosting and real mailboxes such as
firstname@familyname.com. The early sites were public, but as the datasets grew, families asked me to make them private. The recurring deployment model is now gradually moving toward a more multi-family architecture.”
67. Product Lesson
The important evolution was:
One Website
↓
Repeated Demand
↓
Reusable Template
↓
Productized Service
↓
Multi-Family Direction
This is a natural productization path.
68. Architecture Lesson
The project also demonstrates:
Do not rewrite commodity functionality unnecessarily.
The genealogy plugin solved the basic tree problem.
My work focused on:
- customization,
- deployment,
- operations,
- privacy,
- domains,
- mail,
- and repeatability.
This was more efficient than writing an entire genealogy engine from scratch.
69. Privacy Lesson
A system can begin public and later become inappropriate for public access as its data grows.
The correct architecture must be able to evolve.
In this project:
More Data
↓
More Personal Detail
↓
Higher Privacy Risk
↓
Restricted Access
70. Data Governance Lesson
Family history is often disputed.
Centralized administration combined with multi-person verification reduces the risk of one person accidentally rewriting the family structure.
71. Commercial Potential
The recurring nature of the requests creates a plausible commercial product direction.
Potential product model:
Family Subscription
↓
Custom Domain
↓
Private Genealogy
↓
Storage
↓
Family Mailboxes
↓
Admin Tools
This is a future direction, not a claim about the current commercial model.
72. Suggested Tags
WordPress
Genealogy
Family Tree
Custom Domain
Email Hosting
Private Portal
Digital Identity
Hosting
Member Directory
Data Management
Relationship Modeling
Multi-Tenant Architecture
Productization
Privacy
73. Suggested Website Metadata
Page Title
Online Genealogy & Family Digital Identity Platform
Meta Description
A reusable WordPress genealogy solution for large families with 500+ member trees, multi-generation relationships, private member directories, surname-based domains, hosting, and real family-domain email accounts.
Suggested Slug
/online-genealogy-family-platform
74. Evidence Boundaries
Safe to claim:
- project started around 2023,
- recurring requests from multiple families,
- large family trees with 500+ members,
- WordPress,
- existing genealogy plugin customized by me,
- member photo/name/basic profile data,
- parent/child relationships,
- multi-generation trees,
- member search,
- data collaboratively verified,
- centralized administration by me,
- custom surname domains,
- real mailbox accounts,
- hosting/domain/email management by me,
- early public access,
- later conversion to private access,
- architecture gradually moving toward multi-family reuse.
Avoid claiming unless later implemented:
- fully multi-tenant SaaS,
- genealogy engine written from scratch,
- automatic relationship inference,
- biography/memory archive,
- member galleries,
- automated mailbox provisioning,
- public editing by family members,
- exact number of family deployments,
- exact total number of stored people across all deployments.
75. Final Portfolio Statement
Since approximately 2023, I have developed and operated a reusable WordPress-based genealogy and family digital-identity solution for large extended families. The same core setup can be independently deployed under a family’s surname domain and populated with multi-generation genealogy data, searchable member profiles, photographs, and parent/child relationships; individual family trees can exceed 500 members. I customized an existing genealogy plugin rather than rebuilding commodity tree functionality from scratch, and I manage the domains, hosting, privacy configuration, centralized data entry, and real mailbox accounts such as
firstname@familyname.com. Genealogy data is typically confirmed collaboratively by several relatives before being registered. The sites were initially public, but as personal datasets became larger, families requested private access. Repeated demand is now gradually pushing the solution toward a more unified multi-family architecture.
76. One-Line Summary
A reusable private genealogy and family-identity solution for 500+ member trees, combining WordPress, custom surname domains, hosting, and real family-domain email accounts.
77. Ultra-Short Portfolio Label
Family Genealogy Platform — WordPress · Custom Domains · Private Trees · Email Identity