Skip to content

Commit

Permalink
fix: updating the templates page (#2273)
Browse files Browse the repository at this point in the history
* fix: updating the templates page

The templates page needs some work. The first thing I saw is that it alluded to being able to create a crawler. As a docsearch user, this is confusing. We automatically create a crawler for the user, additional crawlers get confusing for the user.

Provide additional information about updating templates, as we're talking about templates here.

Verify the current templates, I see the default one isn't quite right.

Given that we use the same template for Docusaurus v2 and v3 combine those.

Add the Starlight template.

* Combined Docusaurus v2 and v3 templates

Its confusing to have two separate sections that are exactly the same

* added astro starlight template

* remove pkgdown and add starlight

pkgdown no longer references Algolia
added starlight as an integration partner
  • Loading branch information
randombeeper authored Jul 11, 2024
1 parent cdfa993 commit 4aa0c2c
Show file tree
Hide file tree
Showing 2 changed files with 52 additions and 45 deletions.
6 changes: 3 additions & 3 deletions packages/website/docs/integrations.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ So, if you're using one of the following tools, checkout their documentation to
- [Docusaurus v2 & v3][3] - [Using Algolia DocSearch][4]
- [VuePress][5] - [Algolia Search][6]
- [VitePress][21] - [Search][22]
- [pkgdown][7] - [DocSearch indexing][8]
- [Starlight][7] - [Algolia Search][8]
- [LaRecipe][9] - [Algolia Search][10]
- [Orchid][11] - [Algolia Search][12]
- [Smooth DOC][13] - [DocSearch][14]
Expand All @@ -28,8 +28,8 @@ If you're maintaining a similar tool and want us to add you to the list, [feel f
[4]: https://docusaurus.io/docs/search#using-algolia-docsearch
[5]: https://vuepress.vuejs.org/
[6]: https://vuepress.vuejs.org/theme/default-theme-config.html#algolia-search
[7]: https://pkgdown.r-lib.org/
[8]: https://pkgdown.r-lib.org/articles/search.html#bootstrap-3-algolia
[7]: https://starlight.astro.build/
[8]: https://starlight.astro.build/guides/site-search/#algolia-docsearch
[9]: https://larecipe.saleem.dev/docs/2.2/overview
[10]: https://larecipe.saleem.dev/docs/2.2/search#available-engines
[11]: https://orchid.run
Expand Down
91 changes: 49 additions & 42 deletions packages/website/docs/templates.mdx
Original file line number Diff line number Diff line change
@@ -1,25 +1,22 @@
---
title: Config templates
title: Config Templates
---

import useBaseUrl from '@docusaurus/useBaseUrl';

To help you create the best search experience for your users, we provide config templates for multiple websites generators. If you'd like to add a new template to our list, or believe we should update an existing one, please [send us an email][1] or [open a pull request][2].
To help you create the best search experience for your users, we provide out-of-the-box crawler config templates for multiple websites generators. If you'd like to add a new template to our list, or believe we should update an existing one, please [let us know on Discord][1] or [open a pull request][2].

> If you want to better understand the default parameters of the configs below, you can take a look at the [Crawler documentation](https://www.algolia.com/doc/tools/crawler/apis/configuration/).
> If you want to better understand the default parameters of the configs below, take a look at the [Crawler documentation](https://www.algolia.com/doc/tools/crawler/apis/configuration/).
## From the Crawler UI
## Getting Started

Templates are available when you [create a new Crawler](https://crawler.algolia.com/admin/crawlers/create). They will automatically be filled with your website URL, Algolia credentials and index name.
Once approved for DocSearch, we will automatically create a Crawler on your behalf, include your URL, and the Algolia creditials for your appId, apiKey, and indexName. If we detected that you are using any of the predefined generators, we'll attempt to automatically assign the proper template that matches your generator. However, this is not gauranteed. If no specific generator is detected, we will apply the default template seen below.

<div className="uil-ta-center">
<img
src={useBaseUrl('img/assets/new-crawler-creation.png')}
alt="Algolia Crawler creation page"
/>
</div>
## Updating the Template

You can manually update the crawler template by going to dashboard.algolia.com, click "Data sources", select your crawler, and go to the editor page. From there you can edit the Javascript directly. Note that you can make draft changes without saving, test the changes using the "URL Tester", and then "Save" once you're happy with your changes.

## Default template
## Default Template

<details><summary>default.js</summary>
<div>
Expand Down Expand Up @@ -119,7 +116,7 @@ new Crawler({
</div>
</details>

## Docusaurus v1 template
## Docusaurus v1 Template

<details><summary>docusaurus-v1.js</summary>
<div>
Expand Down Expand Up @@ -275,7 +272,7 @@ new Crawler({
</div>
</details>

## Docusaurus v2 template
## Docusaurus v2 & v3 Template

<details><summary>docusaurus-v2.js</summary>
<div>
Expand Down Expand Up @@ -389,9 +386,9 @@ new Crawler({
</div>
</details>

## Docusaurus v3 template
## Astro Starlight Template

<details><summary>docusaurus-v3.js</summary>
<details><summary>starlight.js</summary>
<div>

```js
Expand All @@ -409,31 +406,47 @@ new Crawler({
indexName: 'YOUR_INDEX_NAME',
pathsToMatch: ['https://YOUR_WEBSITE_URL/**'],
recordExtractor: ({ $, helpers }) => {
// priority order: deepest active sub list header -> navbar active item -> 'Documentation'
// Get the top level menu item
const lvl0 =
$(
'.menu__link.menu__link--sublist.menu__link--active, .navbar__item.navbar__link--active'
)
.last()
.text() || 'Documentation';
$('details:has(a[aria-current="page"])')
.find("summary")
.find("span")
.text() || "Documentation";

// Get the second level menu item
var lvl1 = 'a[aria-current="page"] span';
var lvl2 = "main h1";
var lvl3 = "main h2";
var lvl4 = "main h3";
var lvl5 = "main h4";
var lvl6 = "main h5";

// If not able to get the menu item then make this generic
if (lvl0 === "Documentation") {
lvl1 = "main h1";
lvl2 = "main h2";
lvl3 = "main h3";
lvl4 = "main h4";
lvl5 = "main h5";
lvl6 = "main h6";
}

return helpers.docsearch({
recordProps: {
lvl0: {
selectors: '',
selectors: "",
defaultValue: lvl0,
},
lvl1: ['header h1', 'article h1'],
lvl2: 'article h2',
lvl3: 'article h3',
lvl4: 'article h4',
lvl5: 'article h5, article td:first-child',
lvl6: 'article h6',
content: 'article p, article li, article td:last-child',
lvl1: lvl1,
lvl2: lvl2,
lvl3: lvl3,
lvl4: lvl4,
lvl5: lvl5,
lvl6: lvl6,
content: "main p, main li",
},
indexHeadings: true,
aggregateContent: true,
recordVersion: 'v3',
});
},
},
Expand All @@ -443,17 +456,12 @@ new Crawler({
attributesForFaceting: [
'type',
'lang',
'language',
'version',
'docusaurus_tag',
],
attributesToRetrieve: [
'hierarchy',
'content',
'anchor',
'url',
'url_without_anchor',
'type',
],
attributesToHighlight: ['hierarchy', 'content'],
attributesToSnippet: ['content:10'],
Expand Down Expand Up @@ -494,7 +502,6 @@ new Crawler({
advancedSyntax: true,
attributeCriteriaComputedByMinProximity: true,
removeWordsIfNoResults: 'allOptional',
separatorsToIndex: '_',
},
},
});
Expand All @@ -503,7 +510,7 @@ new Crawler({
</div>
</details>

## Vuepress v1 template
## Vuepress v1 Template

<details><summary>vuepress-v1.js</summary>
<div>
Expand Down Expand Up @@ -614,7 +621,7 @@ new Crawler({
</div>
</details>

## Vuepress v2 template
## Vuepress v2 Template

<details><summary>vuepress-v2.js</summary>
<div>
Expand Down Expand Up @@ -705,7 +712,7 @@ new Crawler({
</div>
</details>

## Vitepress template
## Vitepress Template

<details><summary>vitepress.js</summary>
<div>
Expand Down Expand Up @@ -795,7 +802,7 @@ new Crawler({
</div>
</details>

## pkgdown template
## pkgdown Template

<details><summary>pkgdown.js</summary>
<div>
Expand Down Expand Up @@ -958,5 +965,5 @@ new Crawler({
</div>
</details>

[1]: mailto:[email protected]
[1]: https://alg.li/discord
[2]: https://github.com/algolia/docsearch

0 comments on commit 4aa0c2c

Please sign in to comment.