I'm super excited to announce that I'm joining the organising team for https://phpminds.org/ !

Trawling back through the Meetup.com group for PHPMiNDS, I found the earliest time I marked myself as attending was November 2016.

I've never been a PHP dev, although I've dabbled for years. But I've always seen it as a great community, and have been attending for most months since then.

Attending tech meetups has always been about bettering myself, and learning more, and the talks at PHPMiNDS can absolutely be applied to my work, despite it being a different tech stack.

Before https://www.jvt.me/posts/2019/04/11/phpminds-april/ Shaun had mentioned to me about looking for another pair of hands with organising PHPMiNDS, and after a little bit of time to mull it over I decided I would definitely be interested in getting involved.

I'm really excited to start to help out Adoni (https://pavlakis.uk) and Shaun (https://shaunhare.co.uk) with organising the meetup, and I hope continue making it as awesome for others as it has been to me.

Welcome to my first https://indieweb.org/note ! Notes are short-form content that will be purely plain text (for now!) and are similar to tweets on Twitter or toots on Mastodon, but won't be size limited.

I've been wanting to creating other post types since starting to use https://indieweb.org/Microsub and having a social feed. I've found that I want to interact with other posts, such as like or repost others' content, much as I would do with Twitter.

Discoverability of notes currently aren't super amazing, but I'm tackling it as part of https://gitlab.com/jamietanna/jvt.me/issues/457 because adding these post types was a large enough piece of work.

With this note, I'll now be able to https://indieweb.org/bookmark , https://indieweb.org/like , https://indieweb.org/reply , https://indieweb.org/repost , and https://indieweb.org/rsvp .

RSVPs are an interesting one, because the end goal I want is for my RSVPs to be syndicated from this site to i.e. Meetup.com.

I'm hoping to work on bringing https://indieweb.org/Micropub support to this site, too, but as it's a static site with https://gohugo.io and hosted on https://gitlab.com with a full build/test/deploy pipeline, it'll be a little less straightforward, and slower, than other solutions.

I've designed the content schema to be Micropub-first, as I want to be writing these posts using a Micropub client, rather than my usual workflow. I've made the source files JSON files (which Hugo natively supports) which makes them easily machine writeable - hopefully it'll teach me to prioritise my Micropub support so I don't have to manually write JSON!

In terms of licensing, I'm going to start by them in line with my posts, as http://creativecommons.org/licenses/by-nc-sa/4.0/legalcode , but down the line I may look at other licenses.