iterative
blog: automatically include admonitions with upcoming events
It would be nice to automatically include invitations for upcoming events as admonitions in blog posts. This would help people who read our blog to find out about office hours, meetups, and release parties we're planning.
Events are listed here: https://dvc.org/community#events Although the overview is currently empty.
It's really a good idea.
Regarding the approach, I think we can have a custom placeholder eg: <event> so that it can be placed in a suitable place on the blog. We could fetch random or specify a certain event. We can discuss further on level of customization we want. And, it can be hidden based on the date field.
WDYT?
It would be nice to automatically include invitations for upcoming events as admonitions in blog posts.
Great idea! A couple questions on this:
- Where exactly do we want the admonition to appear on a blog post? Do want it to appear in the beginning or end? Or maybe we want to the blog post writer to decide where they want an admonition?
- Do we want this admonition to appear on every blog post or only in certain ones?
- Should the admonition show the latest event, a random event, or should the blog post author specify the event?
My thoughts:
- I'd prefer the author to specify where the admonition is inserted
- As a result, the author can decide per blog post whether there should be an event admonition there at all
- I think by default the admonition should show the next upcoming event, with an option to specify a different one. Past events shouldn't be shown.
- I'd prefer the author to specify where the admonition is inserted
- As a result, the author can decide per blog post whether there should be an event admonition there at all
we can have a custom placeholder eg: <event> so that it can be placed in a suitable place on the blog
- I think by default the admonition should show the next upcoming event, with an option to specify a different one.
It's achievable. Our generated site is static. It will not be updated until the next build. So, we need to make sure it's built daily and that should be possible using the scheduled GitHub action we used recently to build the site on Heroku.
- (https://github.com/iterative/dvc.org/pull/3525)
Past events shouldn't be shown.
it can be hidden based on the date field.