Skip to main content

Search

About 6 minFeatureFeatureSearch

The theme adds built-in support for @vuepress/plugin-docsearch, @vuepress/plugin-meilisearch, @vuepress/plugin-slimsearch and @vuepress/plugin-search. Just install the plugin you want and config it, you will get a search box in navbar.

Use @vuepress/plugin-docsearch

  1. You need to submit the URL of your site to join the DocSearch program.

    The DocSearch team will send apiKey and indexName to your email once the index is generated. Then you can configure this plugin to enable DocSearch in VuePress.

    Alternatively, you can run your own crawler to generate the index, and then use your own appId, apiKey and indexName to configure this plugin.

  2. Set up the Algolia Crawler correctly according to the following requirements. You should go to Algolia Crawler to update your crawler config.

    Setting Crawler Config

    Here are config options and descriptions:

    Warning

    initialIndexSettings.YOUR_INDEX_NAME.attributesForFaceting field must contain "lang", otherwise the plugin will not work properly.

  3. Install @vuepress/plugin-docsearch

    pnpm
    pnpm add -D @vuepress/plugin-docsearch@next

  4. Customize the plugin with plugins.docsearch in theme options.

    .vuepress/theme.ts
    import { 
    hopeTheme
     } from "vuepress-theme-hope";    

export default 
    hopeTheme
    ({    
  
    plugins
    : {    
    
    docsearch
    : {    
      // plugin options here
      // appId, apiKey and indexName are required
    },
  },
});

More

See plugin docs for how to use docsearch plugin and its available options.

Use @vuepress/plugin-slimsearch

  1. Install @vuepress/plugin-slimsearch

    pnpm
    pnpm add -D @vuepress/plugin-slimsearch@next

  2. Customize plugins.slimsearch in theme options.

    You can set plugins.slimsearch to true to enable it directly, or set it to an object to customize the plugin.

    .vuepress/theme.ts
    import { 
    hopeTheme
     } from "vuepress-theme-hope";    

export default 
    hopeTheme
    ({    
  
    plugins
    : {    
    
    slimsearch
    : {    
      // plugin options here
    },
    // or slimsearch: true,
  },
});

More

See plugin docs for available options.

Use @vuepress/plugin-meilisearch

Tips

This requires you to have a own server with docker to run MeiliSearch.

  1. First pull latest MeiliSearch docker image:

    docker pull getmeili/meilisearch:latest

  2. Start the docker:

    docker run -it --rm \
  # set container name to "MeiliSearch"
  --name MeiliSearch \
  # set your own master key
  # replace <YOUR_MASTER_KEY> with your own master key
  -e MEILI_MASTER_KEY='<YOUR_MASTER_KEY>' \
  # switch to production mode
  -e MEILI_ENV=production \
  # disable meilisearch analytics
  -e MEILI_NO_ANALYTICS=1 \
  # mapping 7700 port to host
  -p 7700:7700 \
  # mounting index database to host
  # you can change the path to anywhere you want
  -v $(pwd)/meili_data:/meili_data \
  getmeili/meilisearch:latest

    Here <YOUR_MASTER_KEY> is the master key for MeiliSearch that you should set yourself (required >= 16 bytes), which is used to access the MeiliSearch API.

    Never expose Master Key

    Search key can be generated for public access, which only allows search operations.

    Your Master Key should only be used for internal server access (including scraping), as it grants full operational permissions. Do not mix use them and never expose this key!

  3. Pull the latest MeiliSearch Scraper image:

    docker pull getmeili/docs-scraper:latest

  4. Create a scraper.json file with the following content on your sever:

    • index_uid should be a unique name for your index, which will be used to search.
    • start_urls and sitemap_urls (optional) shall be customized according to the website to be scraped.
    • selectors field can be customized according to third-party theme DOM structure.
    • You can add new fields to custom_settings according to your needs.

    Requirements for the configuration file

    To let the plugin work:

    • lang selector must be kept as is in selectors filed
    • All fields that are currently in custom_settings must not be removed.

  5. Make sure MeiliSearch is currently running, then start scraping the document by running the docker:

    docker run -t --rm \
  --network=host \
  -e MEILISEARCH_HOST_URL='<MEILISEARCH_HOST_URL>' \
  -e MEILISEARCH_API_KEY='<MEILISEARCH_MASTER_KEY>' \
  -v <absolute-path-to-your-config-file>:/docs-scraper/config.json \
  getmeili/docs-scraper:latest pipenv run ./docs_scraper config.json

    Here:

    • <MEILISEARCH_HOST_URL> should be the host URL of your MeiliSearch instance
    • <MEILISEARCH_MASTER_KEY> shall be the master key you provided.
    • <absolute-path-to-your-config-file> is the absolute path to the configuration file you created above.

    When the scraper completes, MeiliSearch will update the existing index with latest document content.

  6. Use the following command to create a search-only access key:

    curl \
  # Replace <YOUR_HOST> with your MeiliSearch host URL
  # You may need to bind a hostname and ssl certificate via reverse proxy
  -X POST '<YOUR_HOST>/keys' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer <MASTER_KEY>' \
  # description f
  --data-binary '{
    "indexes": ["<YOUR_INDEX_NAME>"],
    "actions": ["search"],
    "expiresAt": null,
    "description": "Search key for <YOUR_INDEX_NAME>"
  }'

    Here:

    • <YOUR_HOST> is the host URL of your MeiliSearch instance
    • <MASTER_KEY> is the master key generated by MeiliSearch
    • <YOUR_INDEX_NAME> is the name of the index you created
    • actions specifies the actions that this key can perform. In this case, it is set to ["search"], which means it can only perform search operations.
    • expiresAt sets the expiration date for the key, allowing you to control how long the key remains valid, null means it will never expire.

    If successful, the response would look like this:

    {
  "name": null,
  "description": "Search key for <YOUR_INDEX_NAME>",
  "key": "adaf72e2a6d6f428ec465bc786ec41de868bbd53121997e89ba2299e9566c88213",
  "uid": "b84d1be5-caa5-4752-b078-8f40be39051d",
  "actions": ["search"],
  "indexes": ["<YOUR_INDEX_NAME>"],
  "expiresAt": null,
  "createdAt": "2024-01-27T06:50:33.668329328Z",
  "updatedAt": "2024-01-27T06:50:33.668329328Z"
}

    Now, you can use the key in the plugin configuration

  7. Install @vuepress/plugin-meilisearch

    pnpm
    pnpm add -D @vuepress/plugin-meilisearch@next

  8. Set plugin options in theme config.

    .vuepress/theme.ts
    import { 
    hopeTheme
     } from "vuepress-theme-hope";    

export default 
    hopeTheme
    ({    
  
    plugins
    : {    
    
    meilisearch
    : {    
      
    host
    : "<MEILISEARCH_HOST_URL>",    
      
    apiKey
    : "<YOUR_SEARCH_ONLY_KEY>",    
      
    indexUid
    : "<YOUR_INDEX_NAME>",    
    },
  },
});

  9. Automatic Re-scraping with Github Actions

    Place your scraper config file somewhere in your project.

    Then go to Settings -> Secrets and variables -> Actions in your Github repository. Click New repository secret and set MEILISEARCH_MASTER_KEY with your meilisearch master key.

    Next add a new step scrape in your Github Actions workflow file, which will run after the deployment step. Here is an example of how to do this:

    Key for Scraper

    To secure your MeiliSearch instance, you can create a new key with limited permissions for the scraper. Similar to search key above, this key should only have access to these actions: ["indexes.create","indexes.delete","settings.update","documents.add"]

More

See plugin docs for available options.

  1. Install @vuepress/plugin-search

    pnpm
    pnpm add -D @vuepress/plugin-search@next

  2. Customize plugins.search in theme options.

    .vuepress/theme.ts
    import { 
    hopeTheme
     } from "vuepress-theme-hope";    

export default 
    hopeTheme
    ({    
  
    plugins
    : {    
    
    search
    : {    
      // plugin options here
    },
    // or search: true,
  },
});

More

See plugin docs for available options.

Changelog

7/9/25, 4:17 AM
View All Changelog
  • 05fbb-build: bump depson
  • efb50-feat(theme): add built-in support for meilisearchon
  • 2aada-docs: update docson
  • e639c-docs(theme): improve docson
  • 22787-feat!: replace plugins with official ones and rebuild markdown options (#4553)on
  • 2c32a-docs: update docson
  • a4c54-feat(theme): apply guidelineon
  • bdfcb-docs: update linkson
  • 7948f-docs(theme): update docsearch configon
  • b41c0-docs(theme): update docson
  • 0fe94-feat: use official copy-code, feed, seo and sitemap plugin (#3879)on
  • 54c46-docs: update docson
  • 497db-feat(theme): support redirect pluginon
  • 25d44-feat(theme): support built-in searchon
  • bac94-feat(md-enhance): support alerton
  • e8287-docs: update linkson
  • b54b7-docs: fix search proon
  • c8d60-docs: deploy docs at netlify (#2624)on
  • 77535-docs: fix typoson
  • 9a16a-docs: update docson
  • acd61-feat(search-pro): rename fullIndex to indexContenton
  • 57f4f-docs(theme): add docs for search-proon
  • 2243a-chore: fix typoson
  • 2fa50-feat: migrate to ESM (#2158)on
  • 223f7-style: fix linteron
  • 23515-docs: update codetabon
  • 9cdd7-feat(md-enhance): change @codetab to @tabon
  • 63d09-feat(md-enhance): rebuild codegroupon
  • 1ca3e-chore: fix typoson
  • ad52b-docs(theme): fix typoson
  • c73e6-docs(theme): add hint for searchon
  • cc994-docs(theme): update search plugin docson
  • fd395-docs: update related docson
  • 290ab-docs: update docson
  • 716f9-chore: add demoson
  • 0c093-docs: update docson
  • 60006-docs(theme): rename basicon
  • 4a252-docs: update docson
  • 1ed3a-docs(theme): add search docson
  • f6ff0-docs(theme): update categories and tagson

Contributors

Mr.Hope
MIT Licensed | Copyright © 2019-present Mr.Hope