๐๐๐๐ฟ๐ผ ๐ฑ ๐๐ผ๐ป๐๐ฒ๐ป๐ ๐๐ผ๐น๐น๐ฒ๐ฐ๐๐ถ๐ผ๐ป๐ ๐ณ๐ผ๐ฟ ๐๐ฑ๐ถ๐๐ผ๐ฟ๐ถ๐ฎ๐น ๐๐ฎ๐๐ฒ๐ฟ๐
Programmatic sites often face a problem. Every page looks the same. They use the same templates and the same data sources. If your pages lack human judgment, they look like scraped mirrors.
I used Astro 5 content collections to solve this. I added an editorial layer to my programmatic site.
How it works:
Astro 5 uses content collections to manage Markdown or data files. You define a Zod schema in your config file. Astro validates every file during the build. This ensures your data is correct before your site goes live.
The main benefit is the getEntry() function. This function returns undefined if an entry is missing. You do not need complex error handling or file checks.
You can render editorial sections only when they exist. If a page has an editorial take, it shows the section. If it does not, the page renders normally. The site remains fast and clean.
When to use this pattern:
โข Use it when content is optional. If every page needs the same info, add it to your main database. Use collections only when some pages have extra depth and others do not.
โข Use it for unstructured prose. If you have ratings or dates, put them in your main database. Use content collections for Markdown that does not fit a strict schema.
โข Use it when you have real expertise. Writing a bad take is worse than having no take. Accuracy provides the value.
The setup takes 30 minutes. The actual work takes hours. Writing a quality editorial take requires deep research. I had to verify specific license terms and GitHub star counts.
The infrastructure is ready. I add content when the research is done. I do not follow a rigid publishing schedule. This approach keeps the site high quality without forcing content that is not ready.