Add explicit fields for birth_year, birth_approximate (boolean), death_year, and death_approximate. Selector mapping renders the years with a c. prefix when the approximate flag is set, so the page reads "c. 369-286 BCE" instead of false precision. Sources that genuinely disagree can carry both candidates with a note column.

Yes. The concepts_developed array carries concept slugs. List mapping renders each as a link to /philosophy/concepts/{slug}/. Both sources should share a master slug list to prevent broken links. The reverse direction works the same way from the concepts sheet back to thinker pages.

Yes. Each URL is added to the SleekRank sitemap. The base template is excluded and noindexed. Submit the sitemap in Search Console and new thinkers get crawled within hours of cache flush. Well-known thinkers face high SERP competition; the long tail of less-famous thinkers is far easier and represents most of the corpus value.

Use slugs in the influences and influenced_by arrays rather than free-text names. When a thinker page is generated, the list mapping renders each slug as a link. If a slug does not match any row, the template can show a plain-text fallback so missing entries are visible without breaking the page.

Yes. Add a portrait_url column pointing to a public-domain image or a self-hosted file. Selector mapping injects it into the hero. For consistency across periods that pre-date photography, use engravings, busts, or commissioned line art with the same aspect ratio so the layout reads uniformly.

Use a primary_tradition column for the main badge and a traditions array column for filtering. Index pages read from the array so a thinker can appear in multiple tradition indexes without duplicating rows. The hero shows the primary tradition for visual clarity.

Yes. Store the biography as HTML in the sheet so anchor tags and footnote markers survive into the rendered page. A second array column can carry the footnote contents. List mapping renders them into a footnotes block at the bottom of the page.

Yes. Maintain language-specific columns or separate sources per language and route them via different URL patterns. For multilingual reference projects, separate sources scale better because translators can edit each independently without seeing the others.