Page/template logic

Weblog
,
1

This may be impossible currently without having logic available, but is there a way to filter and sort archives? Specifically I’d want to have something like:

2023
     June
          Title……….day
          Title……….day
     May
          Title……….day
          Title……….day
     …
2022
     …

Is this possible to achieve as things stand right now, or would it require more advanced template logic?

1 Like
2

Would a front-end solution be acceptable? With some creative semantic markup coming from the back-end, I think we could wind up with a nice front-end component that can handle filtering, sorting, and maybe even some optional progressive disclosure (e.g. for longer archives, having previous years/months be collapsed by default but expandable… or something along those lines…).

1 Like
3

Oh absolutely! Is that something that would still work with the git workflow?

1 Like
4

Shouldn’t be an issue with Git, since ultimately it would just be a chunk of JS (which would need to be added to your template or to your archive page) — I think it would be pretty straightforward. The hardest part will be writing the JS, heh… or rather finding the time to!

Which reminds me — totally unrelated to this particular topic, but very much related to finding time, I’m going to try to roll out some kind of sane way for feature requests to be voted on by the community, which should help me a lot with prioritization. Will hopefully have something to share related to that soon.

1 Like
5

Is there a way to do it without JS? If someone is browsing your blog archive with JS disabled, it would be broken. The ideal would be to have a logic-based native HTML solution.

Thoughts?

1 Like
6

Yeah, that’s a great point. The logic would have to be managed by the weblog.lol server, and it might be a little tricky finding the ideal UI output that isn’t overly restrictive with respect to the flexibility of the template system, but I think something could be done for sure. Let me noodle on it further… this is one of those things where a one-size-fits-all solution would be pretty straightforward, but it’s customizing the output that’s going to be a fun challenge.

Did you want to bump this into a full feature-request at this point?

1 Like
7

That sounds like a good idea, done!

1 Like