-
Notifications
You must be signed in to change notification settings - Fork 6
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
Features of Docs/CMS #49
Comments
In the context of
This one's subjective but if you're speaking about the time-to-compile when running
Nextra integrates well with Git, GitHub, and GitLab for version control.
With
This requires additional implementation. Because
Same as above, it would need custom implementation or integration with a third-party solution. This may change with the release of
Image optimization can be achieved using Next.js' built-in features that
Nextra does not have a built-in WYSIWYG editor, markdown is used instead. I don't believe this is possible, it's too much of a shift.
Not supported out of the box; would require integration with a collaborative tool. But even then,
Nextra supports content embedding through markdown and custom components. So this should be doable.
Nextra generates valid HTML, and accessibility features can be implemented using best practices. We can further customize accessibility with custom components if needed (though reaching the
SEO optimization is possible using Next.js features and Nextra's default settings. Because
Nextra doesn't have built-in analytics, better to integrate with https://github.com/plausible/analytics or some other self-hosted alternative.
Not out-of-the-box, but should be possible. By using a
I'm not sure what this means. You mean optimizing SEO through keyword tagging to LLMs can crawl the site more easily for index? Or do you mean using an LLM to search the content better within the site? Since ... it should be possible to integrate with another client-side search alternative that leverages LLM. Or server-side, even (it is possible with Algolia).
I feel like the only way of achieving this is actually saving the history of changes per user on a database and put it behind an indexing/searching service (much like Algolia or any other) to fetch this information and return to the user.
Nextra supports i18n, but machine-driven translation and real-time updates would need custom integration that I think are not easily implementeable.
Nextra provides fast-loading static content suitable for mobile-first design with
Nextra can work without JavaScript for basic content delivery, so it should be suitable for e-readers.
Nextra's (powered by
Code examples can be embedded using markdown, but live execution would require additional setup (this is obviously beyond the supported highlighting provided by
The search component is an example of this is possible ( β + Z highlights the search bar to write ). So it should be possible to work on top of
PDF generation requires a separate tool or custom script, either client or server-side (e.g. https://stackoverflow.com/questions/70931969/how-can-i-export-a-nextjs-page-as-pdf).
Nextra supports custom theming with light and dark modes. More complex theming needs additional configuration. We can make a theme on our own, but that takes a lot of work.
Not built-in; would need to integrate third-party services.
Link validation requires additional tooling like
Requires custom implementation for reactions/emojis, which should be doable with a back-end service and a custom remote component with
Can be added with custom components or third-party integrations.
Nextra can generate a sitemap and configure
Docs are Markdown-based, not
RSS feed generation is possible with custom setup or plugins. It should be possible to work on top of |
@LuchoTurtle definitely wasn't expecting you go through the list π For me, the fact that Linking to the Being forced to have multiple The thing I would still like to implement in our |
π π π |
π―Visible view counter on page (or only visible as overlay based on Role).
The text was updated successfully, but these errors were encountered: