Skip to content

update htmly.php -> display categories on /category page; see #864 #883

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

Joduai
Copy link
Contributor

@Joduai Joduai commented Mar 6, 2025

Changes made to show categories with their descriptions on /category URI; thread #864
Additional main--categories.html.php file for themes (except tailwind), although not needed as categories will be gracefully listed in a manner of posts. This is also a fallback for custom themes that lacks this file, assuming loops for displaying posts in main.html.php were not customized.

@danpros
Copy link
Owner

danpros commented Mar 6, 2025

Hello,

Sorry but this will not added to the core, we have /tag/ /archive/ /type/ /search/ /author/ that doesn't point anywhere so there is no exception for /category/ 😃

@Joduai
Copy link
Contributor Author

Joduai commented Mar 6, 2025

oucha
I was actually going to digg into archives listing in a similar manner.
mmkay, gonna attach somehow this function in my instance when new updates arrive.

I didn't think about all URIs you listed, but I would firstly have to find a suitable use for them.
A page with tags that contains only dozen text links doesn't make sense, especially from SEO pov as it doesn't contain any text despite title. This could be enabled/disabled in control panel but would it be worth all the hassle?

/author? Well, for a bigger blog maintained by couple writers a list with short description about all of them, with link to full bio and article list, would be nice. But what if there's only 1 maintainer? Assuming such situation /author URI could redirect to /author/user. But there's a thread about hiding author's page so it's a tough nut to crack. This would need a global option to disable author pages completely, as for now it's more "security by obscurity" ;)

Never thought about /type as I've never seen any blog CMS that listed types of posts like those only with text, with image, video and so on. This reminds me that I wanted to add an extra column to show type of page in admin panel along with possibility to sort them. Maybe you already planned adding sort function to post list in admin panel?

As for /search that's a good one. Completely forgot about search option on my own page, and that it displays 404.
This one could be very useful, as I love when webapp supports searching with /search/phrase URL without complicated queries.

Anyway, I still want to implement an archive page listing all posts as when time passes, the archive widget in sidebar might become too big for my taste. Showing categories does have a sense, at least for me. After pushing PR I realized that I also wanted to show amount if post in every category.

Well, you might leave the PR as is. If somebody finds it suitable for own blog, he can always grab the code and use it.

@danpros
Copy link
Owner

danpros commented Mar 8, 2025

Never thought about /type as I've never seen any blog CMS that listed types of posts like those only with text, with image, video and so on. This reminds me that I wanted to add an extra column to show type of page in admin panel along with possibility to sort them. Maybe you already planned adding sort function to post list in admin panel?

The idea is like tumblr at first. and combined with the recent_type() function, we can display it for example recent featured image, or recent link, video etc. on sidebar.

Well, you might leave the PR as is. If somebody finds it suitable for own blog, he can always grab the code and use it.

Ok no problems with that 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants