Skip to content

Explore transition to Mintlify - Tracking Issue #3163

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

Open
11 of 20 tasks
gmourier opened this issue Feb 13, 2025 · 0 comments · May be fixed by #3176
Open
11 of 20 tasks

Explore transition to Mintlify - Tracking Issue #3163

gmourier opened this issue Feb 13, 2025 · 0 comments · May be fixed by #3176
Assignees

Comments

@gmourier
Copy link
Member

gmourier commented Feb 13, 2025

Goal

Set up Mintlify to be on par with our current documentation system, enabling us to run a test phase before deciding to fully migrate.

TODO

Content & Sections

  • Learn Section
  • References Section
  • Guides Section
  • Remove "Meilisearch documentation" from all MDX title tags

Redirections

  • Move redirections.json into docs.json redirection objet

Components

Some components in our current base don't exist on Mintlify or are similar but named differently. We may need to find workarounds to achieve parity on some (e.g., the RouteHighlighter).

  • Replace MD images with the Frame component
  • NoticeTag
  • Capsule
  • RouteHighlighter
  • ButtonLink

Code Samples

  • Parse samples and create components in snippets folder
  • Update CI
  • IN PROGRESS: Import generated components

Search

  • IN PROGRESS: Explore a way to override the default search bar with the meilisearch one

Link Checker

Test the CI and simulate wrong links to see if we have a safety net and the right level of information to fix before publishing something wrong.

Cleaning

  • Clean non-needed past workflow
  • Ensure meilisearch.com repo is not affecting this one
  • Update readme instructions and past documentation for next.js based documentation

Domain setup

Other

@gmourier gmourier linked a pull request Mar 7, 2025 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants