Skip to content
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

As a user, I want to look through archives of blog posts #52

Closed
3 tasks
li-kai opened this issue Jun 27, 2017 · 6 comments
Closed
3 tasks

As a user, I want to look through archives of blog posts #52

li-kai opened this issue Jun 27, 2017 · 6 comments
Assignees

Comments

@li-kai
Copy link
Member

li-kai commented Jun 27, 2017

Three separations - year, year/month & year/month/day

  • nushackers.org/2017
  • nushackers.org/2017/01
  • nushackers.org/2017/01/01
@jethrokuan jethrokuan added this to the 1.0 milestone Jun 27, 2017
@unusep
Copy link
Member

unusep commented Jul 19, 2017

hugo does not natively support archiving at the moment (hugo issue 448), so my current plan is to work around this by generating the archive pages in nushackers-site/_scripts/gen_fh.py

@jethrokuan
Copy link
Contributor

I don't see anyone going to these links though

@li-kai
Copy link
Member Author

li-kai commented Jul 22, 2017

I think discovery of these links aren't obvious.

@unusep I think hugo's filtering and grouping syntax is pretty powerful, could you do something like this?

@unusep
Copy link
Member

unusep commented Jul 25, 2017

@li-kai The problem is that (according to issue 448) Hugo does not automatically generate a daily/monthly/yearly archive page. We'll have to manually create one for each date interval (i.e. we need one .md file for /2017/, another for /2017/01, and another for /2017/02, etc.). I think the cleanest way to do that is by leveraging off the script that we (plan to?) run here:

About writing posts: https://gohugo.io/content/

If you are write those generic posts about Friday hacks, please run:

npm run friday-hacks <Title> <Your name>

If we want to do things natively without this workaround it's probably a better idea to have a single paginated /archives/ page like we had in our older jekyll-based page (with appropriate section headings like in the github code you linked). Let me know what you think and I'll implement whichever.

@unusep
Copy link
Member

unusep commented Aug 2, 2017

do we still want to do breakdowns by year, year/month and year/month/day? we can close this issue otherwise.

@advaypal
Copy link
Contributor

advaypal commented Aug 2, 2017

I think this isn't necessary, especially if we do (#55)

@unusep unusep closed this as completed Aug 2, 2017
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

No branches or pull requests

4 participants