-
Notifications
You must be signed in to change notification settings - Fork 3
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
links to event assets don't work on home page #57
Comments
Makes sense, because the markdown is using relative links and the home page is rendering the content "out of context". @samwilson do you think there is a way to access the event page's path in order to repair the link in the home page template? We could use absolute paths in the markdown (starting with |
Could we put it in a block that only displays if it's on the event page rather than the home page? Because in practice we only put assets up once the event is over. In fact we could probably just make it a practice to remove the event from the home page when it's done... |
That sounds sensible too. Maybe we could be fancy - now that we have the dates stored as comparable values - and have an "upcoming" section with full descriptions, and a "recent" section with the latest one or two events, but only show the first paragraph or first x characters of the descriptions, and link to the page. |
I think we should add a "horizontal rule" Above the rule is the meat of my comment, and here I can link to random stuff and update historical stuff without effecting the thing I'm trying to describe above the line. |
That sounds good. Does Jekyll use the HR as a marker for |
In Jekyll, you can specify a custom separator for excerpts using the Let's go with something specific like a 5 dash excerpt_separator: ----- |
That sounds like a good idea. |
Something to do with the routing I think. Links work OK from the event page but not from the home page, where they give you this:
eg. one of the QGIS template links from this week's event resolves as follows:
The text was updated successfully, but these errors were encountered: