Michael Grosser

Within Resumic we are thinking about having a Roles array to showcase your specific involvement, if it isn't just being an author and a coAuthor array to acknowledge them. Anything...

How about something along the lines of: ``` "references": { "additionalProperties": false, "description": "reference section with summary and list of references", "properties": { "references": { "description": "list of references", "items":...

> Very good suggestions. > > 1. We should try to re-use as many field names where it makes sense, so instead of `relation` or `role` we should use `position`...

education.grade -> education.score The rest I agree with or have no clear stance on.

This is what I tried before realizing it supports only one endpoint. ``` :8080 { mailout / { to [email protected] subject "Contact request from {{ .Form.Get \"site\" }}" body /etc/config/template.txt...

Don't stress yourself. One can already run multiple instances. Not perfect but manageable. If it can be done in the long term, it would make mailout match the other plugin...

There was quite a bit of discussion on this. My thinking currently is to have tags, that get shown as actual tags on themes etc. for the main sections etc.,...

@ArmanMazdaee I think this needs a bit more discussion. Let's jump into this in parallel. A few things that need to be cleared up first: * split tags and keywords?...

``` metadata.tags = [{ "pro-bono": { "references": [ "work['greenpeace']", ] }, { "greenpeace": { "references": [ "projects['volunteering party organization']", "events['demonstration 123'].talks['saving cats']" ] }] ```

What we currently have is keywords being public. The next step would be using a filter and tagging syntax within the meta section.