Structured Data for Personal Brands: Person, Article, and Breadcrumb

The setup

Before diving in, it helps to define what success looks like. For this project, success meant: predictable behavior, clean data, and the ability to change direction quickly when feedback arrived.

The approach

The first version focused on structure rather than features. A solid foundation means every feature added later slots in without forcing a rewrite.

- Small, focused modules instead of a single growing file. - Consistent patterns across routes, services, and repositories. - A shared view layer that keeps templates simple and reusable. - Clear conventions for naming, ordering, and error handling.

// Modular service layer keeps controllers thin

export async function getBlogIndex({ page = 1, search = "" }) {

  const [posts, total] = await Promise.all([

    findPublishedPosts({ page, limit: 9, search }),

    countPublishedPosts({ search })

  ]);



  return {

    posts,

    total,

    page,

    totalPages: Math.max(1, Math.ceil(total / 9)),

    search

  };

}

Results

The numbers that mattered most improved consistently: page load times dropped, the admin workflow became faster, and on-boarding a second developer stopped requiring a guided tour through undocumented corners of the codebase.

Final thoughts

Good architecture is invisible. Users notice speed and stability, developers notice clarity, and the codebase notices nothing at all — which is exactly the point. Build the boring foundation first, then layer the interesting stuff on top.