Older/newer posts label in blog plugin should be configurable

Have you read the Contributing Guidelines on issues?

• I have read the Contributing Guidelines on issues.

Prerequisites

• I’m using the latest version of Docusaurus.
• I have tried the npm run clear or yarn clear command.
• I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
• I have tried creating a repro with https://new.docusaurus.io.
• I have read the console error message carefully (if applicable).

Description

Older/newer posts label in blog plugin should be configurable. If you want to use the blog engine to post other content (like release notes), the term ‘post’ becomes irrelevant in this context.

Reproducible demo

No response

Steps to reproduce

Expected behavior

Configuration option (as described in https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-content-blog) should be possible.

Actual behavior

Not configurable.

Your environment

• Public source code:
• Public site URL:
• Docusaurus version used:
• Environment name and version (e.g. Chrome 89, Node.js 16.4):
• Operating system and version (e.g. Ubuntu 20.04.2 LTS):

Self-service

• I’d be willing to fix this bug myself.

[slorber]

You can try this conditional logic after swizzling the component:

import useRouteContext from '@docusaurus/useRouteContext';

export default function BlogListPaginator(props: Props): JSX.Element {
  const isReleaseNotes = useRouteContext().plugin.id === "release-notes"

  return (
       isReleaseNotes ? 
            <Translate
                id="MY_ID">
                MY_CUSTOM_MESSAGE
            </Translate>
		       : 
            <Translate
                id="theme.blog.paginator.olderEntries"
                description="The label used to navigate to the older blog posts page (next page)">
                Older Entries
            </Translate>
     );
}

useRouteContext is experimental/undocumented for now but we’ll likely keep this feature even if it’s refactored.

You can also use useLocation().pathname.startsWith("/release-notes/") or whatever else makes sense for your use-case

[wgruszczyk]

Thank you for the hints! Probably at the moment the most sensible and safe solution will be to translate it permanently to something more general like Next/Previous.