[Question] Multiple authors config

[OCram85]

Hi Dean,
what do you think about extending the authors feature ?

Current state

It's possible to define one author and his details in the config.yml.

Possible Change

Extend the author config to work with more data (avatar link, name, description ... ) and multiple authors

How could this be done?

• Either stick with one author in the config.yml
• Using another file like authors.yml and define the data there 🗡️
• Pickup the author in the front matter section
• author details could be displayed in a post footer

Surplus

• beatuiful-jekyll could easily be used for sites with multiple contributors.
• This feature should be optional

[daattali]

I'm not sure if you mean:
a) multiple authors for a single post, or
b) just supporting having a different author for different posts, or
c) multiple authors in the footer of the page

Case b) is something that several people have asked me about and I would happily support (it's already very easy to do it). Which one do you mean?

[OCram85]

Hi Dean,

I tried to explain scenario b. 😃

[daattali]

In that case, one very simple option is to just support an author param in a page YAML, without a need to change the config or to add another file. Do you think a more complex solution is needed?

[OCram85]

You're right. simple yaml definition in the front matter part should do it. Maybe an additional global setup if you simple want to select the author in the page's yaml part like this:

Example page / post

author: "OCram85"

_config.yml

authors:
  OCram85:
    name: "OCram85"
    avatar: "/path/to/image.jpg"
    additional_params: ""
  daattali:
    name: "Dean"
    avatar: "/path/to/image2.jpg"
    additional_params: ""

[daattali]

What would additional params include? URL can perhaps be added

…

On Jun 18, 2018 02:47, "Marco Blessing" ***@***.***> wrote: You're right. simple yaml definition in the front matter part should do it. Maybe an additional global setup if you simple want to select the author in the page's yaml part like this: Example page / post author: "OCram85" _config.yml authors: OCram85: name: "OCram85" avatar: "/path/to/image.jpg" additional_params: "" daattali: name: "Dean" avatar: "/path/to/image2.jpg" additional_params: "" — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#367 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA6IFE9pUYyraFBml9YnAy2cNokovk8Cks5t900GgaJpZM4UpDVE> .

[OCram85]

I think it depends on whatever you would like to display. As you said, maybe an url, maybe a short description, avatar (picture path),...
Additionally it also depends on the where you would like to display the information. I'm thinking of adding a footer section, or maybe a simple include snippet which could easily added by other users when needed.

[daattali]

The philosophy of this theme is to be very simple, I try to fight feature creeping even when there are good ideas in order to maintain the simplicity. With that in mind, I prefer to only give options for very important things (I even regret adding custom google fonts as a feature because it doesn't seem to benefit many people). I prefer to simply force the author position at the top, probably on the same line as "Posted on ... by <author>". I was thinking if no name is provided then you keep the current behaviour. If a name is provided you add "by <author>" . If a name and URL are provided then ther author name becomes a link. If an image is provided as well then add a small circular photo. I don't think description or other parameters would be necessary.

…

On Jun 19, 2018 02:58, "Marco Blessing" ***@***.***> wrote: I think it depends on whatever you would like to display. As you said, maybe an url, maybe a short description, avatar (picture path),... Additionally it also depends on the where you would like to display the information. I'm thinking of adding a footer section, or maybe a simple include snippet which could easily added by other users when needed. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#367 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA6IFGNfph2vuLAWtliDcTU6NdGqnTEmks5t-KEtgaJpZM4UpDVE> .

[OCram85]

Maybe we should create a fork in @jekyll-collective and implement more complex / advanced stuff 😄

[daattali]

I don't know if that was a joke or not but I don't mind. I strongly want to keep this theme simple and very beginner-friendly so there will be features I'll want to keep away

…

On Jun 20, 2018 03:58, "Marco Blessing" ***@***.***> wrote: Maybe we should create a fork in @jekyll-collective <https://github.com/jekyll-collective> and implement more complex / advanced stuff 😄 — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#367 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA6IFBrseTMD4wCnD0HxyHoahYLbya1yks5t-gCKgaJpZM4UpDVE> .

[daattali]

Closing this as I decided not to implement this feature