Add ability to generate per-{year, month, day} archives

[yacoob]

I'm in process of migrating a blogger based blog to hugo. Compare blogger site to hugo-backed site (source here).

One thing that I'll lose as a result of this migration is an archive of posts (like this one). I don't really care all that much, and I'll most likely replace it with a list of all posts, with a different layout, generated from layouts/section/post.html. I'd like to ask you, however, to consider adding a capability for hugo to generate time-based archives. Such archives would most likely be useful to people who want to preserve their existing archive pages.

It'd generate content under public/<section>/2014/index.html for example, from layouts/post/list.html. It'd need to allow per-section and per-level (yearly, monthly, daily) control. It'd also need to play well with permalinks parameter from config.yaml - I don't really have a good idea how to address that.

Is such feature request a sensible one? :)

[yacoob]

An idea for implementation: Generate one index.html file for every level of date-related data present in permalinks from the config file. For example, with:

permalinks:
  post: /:year/:month/:slug

generate

• /2014/index.html from layouts/section/post.html with .Pages containing all 2014 posts;
• /2014/01/index.html from layouts/section/post.html with .Pages containing all January 2014 posts.
• etc.

This should require minimal new logic needed. Some sanity checking might be required, unless we want to allow things like /:month/:year. If you point me to the relevant bit of code where content/* → list of pages to be generated is devised, I might give it a try :)

[spf13]

I actually think this should be a bit different.

This assumes the year/month structure that Jekyll and others use.

I would prefer instead to register every directory and maintain a list of children content regardless of if it's using the permalinks structure or not.

This would not only give us what you need, but also support for subsections.

Does that make sense?

[yacoob]

It does make sense - the only question in this kind of schema is how do we decide whether or not render an index.html page? A user may simply not want a file there. Should it be generated by default, or should it be generated only if user asks for an index on given level?

[spf13]

I think by default. It doesn't hurt to have it and you don't need to link
to it. Plus all directories should have an index on the web if they have
content.

On Wednesday, September 3, 2014, Jakub Turski [email protected]
wrote:

It does make sense - the only question in this kind of schema is how do we
decide whether or not render an index.html page? A user may simply not
want a file there. Should it be generated by default, or should it be
generated only if user asks for an index on given level?

—
Reply to this email directly or view it on GitHub
#448 (comment).

Steve Francia
http://stevefrancia.com
http://spf13.com
http://twitter.com/spf13

[spf13]

I think this is related or the same as #465. Tying them together.

[matrixik]

Just for example from Wordpress:
https://wordpress.org/plugins/compact-archives/
http://www.wpbeginner.com/archives/

[AriaFallah]

Any progress on this or workarounds?

[vielmetti]

Any ideas on this one?

[yacoob]

FWIW, I've stopped using Hugo for the site that I wanted this feature for, so I'm muting this bug - don't expect any answers here :>

[mcliment]

I'm not a Hugo expert and my templates may have some newbie errors but I managed to make archives work using taxonomies.

Check out this repo: https://github.com/mcliment/f1blog-archived/ -there are taxonomies per year defined in config.toml and in every post there's the corresponding frontmatter information-.

The resulting site is here: http://f1blog.climens.net/ with most of the things I had in Wordpress.

[asmaier]

So in additional to prev/next on each pager...That seems a bit busy to me

You are right. I don't want additional navigation, but instead have a different alternative date based pagination instead of the normal pagination.

[asmaier]

@jmooring I found a way how to create the navigation between the date based sections of your example code as I imagined it. I opened a pull request jmooring/hugo-testing#4 . This might not be the perfect code, but maybe it helps to understand better what I want.

[22decembre]

Hello.

I have an interest in this issue. I see that solutions are being proposed. Does it means there will be such a thing in the near future ?

Thanks

[jmooring]

This uses a relatively simple module to create year, month, and day archive pages for one section of a site. The module leverages the content adapters feature introduced in v0.126.0.

The module itself requires v0.140.1 or later.

Example:

git clone --single-branch -b hugo-github-issue-448 https://github.com/jmooring/hugo-testing hugo-github-issue-448
cd hugo-github-issue-448
mkdir -p assets/data
hugo list published > assets/data/published-content.csv
hugo server

Details:
https://github.com/jmooring/hugo-module-archive

Note that this approach relies on the hugo list published command, for which there is no API promise. Although the output of this command is unlikely to change in a breaking fashion, such breakage is a possibility, and may require a change to the module in order to provide forward compatibility.

[raoulb]

Any updates on this? What are the current plans to get archives (without workarounds)?
Especially as #6992 was closed with reference to this issue here.