Comments (5)
π 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 authors.yaml
authors by default, and have an option to opt-out.
It's not clear to me what the UX should be to access an author page, considering we already have author.url
Your post has a missing screenshot but I guess you wanted to post this?
This doesn't look like a great UX to me π
Authors are already presented at the beginning of blog posts so it's weird to add them at the bottom too IMHO.
from docusaurus.
IMHO we should generate an author page for all authors.yaml authors by default, and have an option to opt-out.
Sure, but we have to make the name mandatory, now it is not.
This doesn't look like a great UX to me
It isn't, the whole implementation was a copy/paste from the Tags code.
Authors are already presented at the beginning of blog posts so it's weird to add them at the bottom too IMHO.
Sure, feel free to use a better solution.
from docusaurus.
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:
from docusaurus.
we'd rather first introduce the ability to have "social icons" next to the author's name
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?
from docusaurus.
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).
Pagination is not really an option if we want to enable this kind of scale:
Now I'm ok to let you have an option to disable pagination in author pages.
We already have a postsPerPage
option: https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog#postsPerPage
Number of posts to show per page in the listing page. Use 'ALL' to display all posts on one listing page.
Why not postsPerAuthorPage: "ALL"
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.
from docusaurus.
Related Issues (20)
- Allow codeblocks to show only part of the content HOT 2
- Broken anchors: page not scroll to the right section HOT 8
- Index pages cannot be generated with an automatically generated siderbar HOT 1
- Document solution to "docs last update" date being rendered incorrectly when published through Vercel
- Customizing admonitions not work HOT 3
- When testing on StrictMode, the bar remains on the top HOT 1
- Node.js building getting stuck HOT 2
- Updating to @mdx-js/react 3.0.1 causes admonition blocks to stop rendering colored box HOT 8
- The <!--truncate--> line in my long blog post on the initialized website is not causing the blog post size to be limited. HOT 1
- Add trailing slash to auto generated sitemap.xml for directories only HOT 3
- blogTitle not working HOT 4
- Algolia Contextual Search Generates Incorrect FaceFilters HOT 6
- Multi-Instance Routes Not Working in v3.2.1 HOT 3
- Home page renders twice, one below the other. HOT 1
- Details elements aren't searchable - a11y issue HOT 8
- WARNβ 1 deprecated subdependencies found: [email protected] HOT 1
- npm run build fails when nmetadata are missing HOT 3
- Broken link transformation HOT 2
- Ability to Skip Homepage and Directly Access Feature Page HOT 1
- Light/Dark Mode issues on older versions of Safari 12,13, and 14 HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from docusaurus.