-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
Blog authors pages #9825
Comments
👍 looks like a useful feature, that I wanted to add already. I'm not a fan of your UI and API design, but we can iterate on that. IMHO we should generate an author page for all It's not clear to me what the UX should be to access an author page, considering we already have Your post has a missing screenshot but I guess you wanted to post this? This doesn't look like a great UX to me 😅 |
Sure, but we have to make the name mandatory, now it is not.
It isn't, the whole implementation was a copy/paste from the Tags code.
Sure, feel free to use a better solution. |
IMHO we'd rather first introduce the ability to have "social icons" next to the author's name, similar to what many blogs do: https://web.dev/blog/array-with This would enable us to be able to click on the author's name to access the author page and see a paginated list of posts for each author. Some other examples of sites having author pages: |
Sure, that's a nice improvement, however I'm not convinced that logically it is ok to mix social icons with posts grouping. From my point of view, the author pages are basically in the same logical class as the tags pages and the Archive page, they all show sub-lists of posts grouped by various criteria (year, tag, author name). Personally I like the layout used in the Archive page, and I'd prefer it in the Tags and Authors pages too, with the same 3 columns layout, and sub-lists with date and title, obviously with the year replaced by the tag label or author name. What do you think about such a consistent solution for all three grouping pages? |
Maybe this grouping makes sense for your case, but it is not the kind of experience you expect from a multi-author blog. See what popular multi-author blogs do: And I could show you many more similar examples. Note Chris Coyier wrote thousands of posts on the CSS Trick blog (he created it). Now I'm ok to let you have an option to disable pagination in author pages. We already have a
Why not Then you can swizzle the author page and decide to sort, group, and display the posts of that author the way you want. You can order the post by date, event_date, last update time or whatever you want, implement your own layout, and group the posts by whatever attribute or custom front matter. |
Hi Sébastien @slorber, do you have any estimate when the authors pages will be implemented? I saw a lot of new features in the latest releases, and I'm kind of stuck to my old fork, since updating my implementation for the authors pages would require some efforts, not justified if you'll reimplement them properly. |
Hi My apprentice @OzakIOne is working on a showcase plugin atm. Once it's ready we'll work on the blog authors plugin. I can't guarantee this will be implemented this month, but the goal is to ship it asap, likely this quarter. |
Have you read the Contributing Guidelines on issues?
Description
Similarly to tag grouping pages, generate
Also add a list of authors with links at the end of each post.
![authors2](https://github.com/facebook/docusaurus/assets/362732/6d476284-a961-4fe2feature, add -8532-fea4cdad4fbf)
Has this been requested on Canny?
No.
Motivation
For blogs with multiple authors, it is useful to identify posts contributed by each author.
API design
To control this new feature add a
generateAuthorsPages
option; when set to true, the authors pages are generated asblog/authors
andblog/authors/${name}
.Have you tried building it?
The functionality is implemented in cronica-it@7465833.
The implementation adds a
NamedAuthor
type, similar toTag
and the code is basically a duplicate of the tag logic.Self-service
The text was updated successfully, but these errors were encountered: