-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Block: Author Bio #1844
Comments
#1516 mentions bio, but not specifically saying about an author bio. I do wonder if it needs to be called out explicitly. I can see users wanting that. It is also something I have seen people switch themes just to have - so to me a good thing to have as a block. @melchoyce maybe worth considering with an author widget block? My not fully formed thinking could be that the inspector could pick how many authors and it could show just current one or actually show a list of authors. I may be merging too many things though. |
I have earlier made a tutorial for creating an author box. Here are some of the screenshots. As one would need to include social links (+ icons) in the right sidebar block settings. Social links that could also be used for a social sharing block. It could be a bit heavy. As one could add a new social link then add the icon to it. Giving the option to clicks a + sign to add another social link. As many as one chooses to link to whichever social profile. |
I see now problem with User profile. Not a small one.
|
@paaljoachim I think using what already is in the system over adding more fields would be preferable, at least for a v1. |
Here is a suggestion as to how we could have an author/authors block - the default is author. Props to @melchoyce for helping me with iterations. |
Thinking a bit more about it — I think it might make sense to split these into two blocks: an author bio block, and an author list block. I can see both blocks being useful in different contexts. Author bio is great to add to the bottom of your posts, while you likely won't want a list of every author on your site on every posts. However, you might want a list of all your authors on an About page, or on archive pages. |
That's a good point about how much we should combine functionality in a block. I can see a point for doing both. In the case you are suggesting then I imagine we'd have two blocks called 'authors list' and simply 'author'. The UI translates to both, if we decide to go that route. Here are those split: |
Looks good. Maybe a dropdown in the author block to select other authors if you have multiple? On a post it can be the post author by default, but I can also see this used on a Team or About Us page to display bios. |
Would there be anyway, from the user interface, to have the author bio always show on a post? For instance, on a multi-author blog it'd be nice to have that be automatic, and not manually added each time. This could either be territory for "templates" with reusable blocks (#1516) or might just need to be handled by the theme. |
I don't think showing always on a post is a good idea, for example when working on themes it was a common request to remove. Having this able to be somehow set in a theme could work but again it's a common thing to remove. I would think off by default is the way to go. |
As the project moves towards merge proposal, we are moving issues that aren't needed for that to projects. This doesn't mean they won't get done, they totally can and that's why we're moving to projects. This allows us to focus on the issues that have to happen to Gutenberg. I am closing this but it will live in projects. |
I dont know if it is already mentioned with different name. Sorry if it is, be free to close issue.
Seems as you forgot this very fine block used everywhere.
Just to exclude my subjective and personal opinion about it, to state one fact. I never used it on any website done by me, not once, zero. If my memory serves me well.
But I see this block is very popular. Wherever you turn on net, Blogs, news portals, have this Author Bio block inside Posts.
The text was updated successfully, but these errors were encountered: