Replies: 1 comment
-
|
Customizing the order by swizzling the theme component is the way to choose the UX of your choice. Not everybody has to agree with our UX choice, and that's fine, as long as we give you the freedom to choose yours. I don't think it's worth clarifying in our docs, if we had to document each UX/UI decision, our docs would quickly become unmanageable, unmaintainable and very hard to read due to too much noise. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Docusaurus team,
(I only speak Japanese, so I used translation.)
While customizing the
BlogPostPaginator, I noticed that the default behavior seems reversed from what I expected.prevItemappears on the left, but it points to the newer post.nextItemappears on the right, but it points to the older post.Technically, this makes sense (since “next” = older in chronological order), but from a user-interface perspective, it can be confusing, because readers usually expect “newer” on the right and “older” on the left.
I understand this may be a design choice, not a bug.
However, it might be helpful to clarify this behavior in the documentation, or maybe consider making it configurable.
For reference, I temporarily reversed the order in my custom component like this:
It works for my case, but I think this behavior might surprise other developers too.
What do you think?
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions