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

Separating past events from future events #7

Open
notexactlyawe opened this issue Feb 28, 2017 · 1 comment
Open

Separating past events from future events #7

notexactlyawe opened this issue Feb 28, 2017 · 1 comment
Assignees

Comments

@notexactlyawe
Copy link
Contributor

There should be some visual separation of past events from events that have not happened yet. This could be in the form of a separate archive page or even a simple line. This can probably be done within jinja

@notexactlyawe
Copy link
Contributor Author

I feel like this can be done with three changes:

  • An archive page that will host past events. (this should have all events put into it in the template)
  • A change to the template on index to only include events future of build time.
  • A script on the page that hides any events that have elapsed at the time of viewing.

The script on its own is a bad solution, since you are bloating the pages with every event that has ever happened. This is solved by removing all past ones from index at build time, and assuming we update the website occasionally (we will every time there is a new event), these two will work together as well as a static site can handle.

@notexactlyawe notexactlyawe self-assigned this Mar 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

1 participant