Skip to content

Feat: 2043 Meilisearch - #30

Merged
fonodi merged 7 commits into
mainfrom
feat/2043-meilisearch
May 5, 2026
Merged

fonodi merged 7 commits into
mainfrom
feat/2043-meilisearch

Conversation

@fonodi

@fonodi fonodi commented May 5, 2026 •

Copy link
Copy Markdown
Collaborator

Task Link

Task #

Description

Added Meilisearch to the project.

Indexed the following Collection types:

  • Pages
  • Case studies
  • Blog posts

Created server rendered list with the option to load more for:

  • User stories (/user-stories)
  • Features (/features)

Also added a global search, that can simultaneously search from:

  • Pages
  • Case studies
  • Blog posts
  • Strapi docs (different project)

TL;DR

Adds Meilisearch — paginated case-studies/features grids and a ⌘K global search across site + Strapi docs.

Screenshots/Videos

image image image

New environmental variables

UI

MEILISEARCH_PRODUCTION - boolean, must ONLY be true on production
MEILISEARCH_HOST - Project host URL
MEILISEARCH_DOCS_HOST - Docs project host URL
MEILISEARCH_API_KEY - Search API key
MEILISEARCH_DOCS_API_KEY - Docs Search API key

Strapi

MEILISEARCH_PRODUCTION - boolean, must ONLY be true on production
MEILISEARCH_HOST - Project host URL
MEILISEARCH_API_KEY - Admin API key

Checklist - author

  • Assignee is set (the active developer of this PR).
  • Reviewers are set (team members who will review the code).
  • PR is linked I have linked the PR to an issue in Jira.
  • Description I have described the changes proposed in the PR clearly and concisely (more important than what is why).
  • Screenshots/Videos I have added screenshots/videos or they were not needed.
  • Environmental variables are listed or they were not needed.
  • Unit/Integration tests are added for all utilities and business important logic
  • Labels I have added labels to the PR.
    • Use requires-env-vars when PR requires environmental variables
    • Use ready-for-review when PR is ready to be looked at
    • Use ready-to-merge when PR has a passing review
    • Use needs-revisions when PR has comments that block merge
    • Use do-not-review when PR is daft only and you don't want to get a review
  • [OPTIONAL] Conversation/documentation is started in places where the code is not self-explanatory

Before merging

  • PR is approved
  • All conversations are resolved
  • Pipelines are not failing

Checklist - reviewer

  • I understand all proposed changes.
  • Necessary after deploy steps are handled by someone (adding new env var, syncing config, running migration...)

@fonodi
fonodi requested a review from jsimck May 5, 2026 09:27
@fonodi fonodi self-assigned this May 5, 2026
@fonodi fonodi added the pr: feature New or updates to features label May 5, 2026
@vercel

vercel Bot commented May 5, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
website-ui Ready Ready Preview, Comment May 5, 2026 9:49am

Request Review

@fonodi
fonodi merged commit c756cce into main May 5, 2026
3 checks passed

This branch was successfully deployed

1 active deployment
Preview — 79efa2b2 Deployed May 5, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr: feature New or updates to features

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant