Hi, in blog, sorting articles by date or name is fine, but it might be interesting to have other organisation options.
What improvements are planned for this great component?
We are working on support for tags and authors for our next release. What other improvements would you like to see?
Have a component similar to âBlog Loopâ with the content set up with a list of pages.
Parameters:
- A list of pages (with Blog Options) defined by the developer.
- The pages can belong to different folders containing Blog Options pages.
This would make it possible, for example, to highlight a few articles from different blogs on a home page.
Thatâs a great suggestion. We will add the ability to loop a custom list of pages in our next update.
It would be great to have custom attributes for the posts as well.
This way the âblogâ feature would become way more versatile and usable for other things like
- projects
- testimonials
- services
- teammembers
âŚ. anything where you have a âcollectionâ from with a similar pattern.
Those attributes could be just simple key:value pairs.
Furthermore there needs to be categories support included (not just tags)
Iâve experimented with the idea of this.
As an example:
https://www.example.com/blog/<tag>/<post-title>/
This helps me filter by tags specifically.
or for projects where âprojectâ is the tag:
https://www.example.com/projects/project-0.html
https://www.example.com/projects/project-1.html
for any available tags, it can be the same way for filtering.
You donât need categories necessarily. Using Tags to filter your Blog Loops for âProjectsâ, âTestimonialsâ, âServicesâ, âTeam membersâ would work. This is how Iâm currently using the filtering option available.
You have to be creative with the available options.
Itâs taken me months after this update to figure out the best ways to use it.
What youâre asking to be implemented is basically the same thing as tags, just adding an extra step.
Edit: You can also change the Blog Loop Source to âCustomâ and add individual Pages through the âBlog Loop Itemsâ for each category type. Where you have better control over which pages are shown in the Blog Loop.
Yes, of course you can abuse a lot of what exists, but it will always be a workaround.
I used to do only the layouts in studio and write the other stuff in astro.build
I actually never had the intention to use studio itself as a CMS or so⌠but since the feature is there now, why not using it for smaller projects just as is?
In those cases I would love to have things simple and fully working⌠and abusing the only existing collection for everything then doesnât feel right.
So for the time being I will stick to using studio only as a visual editor for the layouts while doing the real magic externally.