You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add the authors to the various blog posts, as done in our previous website, for example: https://correlaid.nl/blog/facilitating-collaborations/. The author descriptions are in the header of the markdown files for each blog post, stored in /_posts.
The text was updated successfully, but these errors were encountered:
I spent a spare half hour on this and found out the following. First, the template allows for a meta tag "author" (see for example this blog post rendered here) but this is (a) very bare bones and (b) actually does not display the author name on the post!
Instead, I believe we want to create an "include" (see _includes/_instruction.md) which we can just call at the end of each blog post and which should render the information we provide as information in the blog post md file (see for example here). I don't know how to access this information in the custom Syntax in which includes are written yet. To be continued.
Didn't notice this before I started working on it. I saw that the Vonge template just had an overall author who would be listed next to each post. This is of course a very shit design, since why the fuck would it not support multiple authors. Mindbogglingly crap design. At least good for the imposter syndrome, as someone made something this badly and was still happy to publish and share it. Anyway, I tweaked the core code of the template so that if you add an author tag to the header of the blog posts, it uses that to overwrite the global author setting for that post. A further improvement would be to have an image per blog poster, but that would take some more work.
Add the authors to the various blog posts, as done in our previous website, for example: https://correlaid.nl/blog/facilitating-collaborations/. The author descriptions are in the header of the markdown files for each blog post, stored in /_posts.
The text was updated successfully, but these errors were encountered: