Manual sub-page blogpost

[dire pollen]

Hi guys, as I read the Astro's docs that we should have a layout for blog post page, and Astro will automatically use it for any post in our collection. But is there anyway to code the blog post manually? Let's take an example of UX study case portfolio, which potentially will have different behaviour and different features on each post. What do you think guys?

This website is the perfect example of what i meant https://fireart.studio/cases/

[brisk monolith]

You sure can! Simply create another .Astro file in your pages folder and write any code you want in it.

[dire pollen]

Oh ok thanks Geoffrey. I also think the same, but how did if I will get all my post to show them in a list on "all blog/articles" page?

[brisk monolith]

Then if you want something neat and easy to query, you can use content collection with mdx files. Mdx is more flexible than md, so you can customise your content with components etc.

[ocean creek]

Totally get wanting more control—especially for UX case studies where each post needs its own layout or behavior. Going manual with .astro pages makes sense when you want each post to feel like a mini product, not just a templated blog.

If you're staying in Astro:

• You can handcraft each post as a standalone .astro file
• Still use content collections for metadata and build a hybrid listing page

If you're exploring outside Astro, curious what stack you'd prefer? Some async-fit options for manual control:

• Next.js – great for custom layouts and React components
• Vite + React – lightweight and fast
• SvelteKit – if you like Svelte’s syntax
• Plain HTML/CSS/JS – full control, minimal tooling

Curious—are you planning to mix formats (like dev logs + case studies), or is each post a bespoke UX experience like Fireart’s?

[dire pollen]

That was nice, I will give it a shot. Thanks Geoffrey

[dire pollen]

Your advice ar truly on point as Geoffrey. I had 2 options to experiment with, thanks bud.

Mine actually both in dev's and UX, but the way FIreart's presenting their works is great and clear, so I want to convey mine(either code or design stuff) in that way

[ocean creek]

Glad it landed! Loved your Fireart reference—clear presentation really does shift how dev + UX vibes are received. If you end up experimenting with those two options, I’d be curious what you discover.

[ember dawn]

If your issue is resolved, please help by doing the following two steps:

1. From the ellipses (3-dot menu) in the top-right corner of the post (not the first message), edit the tags to include the Solved tag.
2. From the same ellipses, select Close Post.
   Your post will still be available to search and can be re-opened simply by replying in it. Closing a post moves it down with older posts, so we can more easily focus on issues that still need to be resolved.
   Thank you for your help!