Commit 68b49ffe authored by Jamie Tanna's avatar Jamie Tanna

Announce `h-event` markup on /events/

As ever, I should be blogging about these additions to the site and my
IndieWeb journey!

As part of #395.
parent ab61c785
Pipeline #53273059 passed with stages
in 6 minutes and 34 seconds
......@@ -29,7 +29,9 @@ I spoke about how I [blog as a form of documentation]({{< ref 2017-06-25-blogume
To this, I'd recommend just setting your site up with a pre-built theme. Get the core content up there and then customise the theme after. __Unless__ you're trying to show off your design skills, in which case the reverse is true!
Before the next event I'm planning on creating a custom post type in Hugo to share out the new events - if you're interested [you can follow along on the issue](https://gitlab.com/jamietanna/jvt.me/issues/395).
<s>Before the next event I'm planning on creating a custom post type in Hugo to share out the new events - if you're interested [you can follow along on the issue](https://gitlab.com/jamietanna/jvt.me/issues/395).</s>
As per [_Marking up Events with Microformats_]({{< ref 2019-03-23-microformats-hevent >}}), I have created a custom events content type on this blog which renders the [`h-event`](http://microformats.org/wiki/h-event) markup on these events pages.
Something to think about for the next event is maybe more structure / agenda, although like other HWCs, I want to keep it less structured and more fluid for attendees.
......
---
title: "Marking up Events with Microformats"
description: "Announcing the events content type and their markup with `h-event`."
categories:
- announcement
- indieweb
- microformats
tags:
- indieweb
- microformats
license_code: Apache-2.0
license_prose: CC-BY-NC-SA-4.0
date: 2019-03-23
slug: "microformats-hevent"
image: /img/vendor/microformats-logo.png
---
As I called out in [_Homebrew Website Club: Nottingham, Session 1_]({{< ref 2019-03-20-hwc-nottingham-session-1 >}}), I wanted to have Microformats automagically generated for the content.
This was because I had manually hand-crafted this [`h-event`](http://microformats.org/wiki/h-event) for the [last event]({{< ref 2019-03-14-homebrew-website-club-nottingham >}}), which although perfectly fine was a bit more work than I'd want to do in the future, as well as duplicating a lot of the basics of the markup across many events.
However, before I did this, I needed to have a new content type in Hugo for these events, so I could render them differently than blog posts / content pages. This is as simple as creating a new folder in Hugo's directory structure, which is really nice, and then adding the relevant templates in my theme to render the `h-event`s.
The largest piece of work for this ([as with the work for `h-entry`s]({{< ref 2019-03-19-microformats-hentry >}})) was getting HTML-Proofer checks in place to verify that the content is well-formed and that I don't have regressions in the future.
This is very exciting for better interoperability with others!
posts:
- https://www.jvt.me/posts/2019/03/23/microformats-hevent/
- https://www.jvt.me/posts/2019/03/20/hwc-nottingham-session-1/
- https://www.jvt.me/posts/2019/03/20/git-rewrite-url-https-ssh/
- https://www.jvt.me/posts/2019/03/19/microformats-hentry/
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment