simpleauthorityPotentially silly question, but when doing post type discovery (https://indieweb.org/post-type-discovery), this is only applicable if the type is h-entry right? If I have another "type" (i.e., h-event, h-card, etc), then I render/treat those as their own entity based on the documented properties thereof right?
btremI'm poking around micropub to see how I can make it work for my site. I would like to be able to create an h-entry post where the file name/slug is based on one of the properties. So e.g. `{"properties": {"content": ["hello world"], "number": 23}}` would be saved as `23.md`. I assume that's something I'd have to do on the client side, right?
btremOr am I hacking a micropub server to name the filename of the post based on a json value? Now that I think about it, that seems the likely path. In which case I'm hacking a micropub _server_.
btremYeah, I sort of realized that after my first query. But can I have the server generate a file base name by using a property of the micropub post as I outlined above?
aaronpktho if you want to use generic micropub clients, you should generate the name based on properties generic clients will send, not expect to be able to get a client to add a custom property to the request
btremAnd nothing happens. No image is generated. I have `failOnError` set to false because it crashes on old images that aren't where they are supposed to be. I'm hoping to avoid rewriting a bunch of old posts that had hard-coded images (for reasons I don't remember at the moment) before I commit to the new transform thing.
btremUpdate. I changed all images except my new post that I'm testing on to use `eleventy:optional`. And turned on `failOnError`. No error for the post, but no transform, either. Just an empty `<img>` element. I'm missing something here. :-(
barnaby, CrimeWave, DanQ and rgbivvv joined the channel