1. Go to https://www.lightningdesignsystem.com
2. Search for "tiles"

Expected: first results include a reference to https://www.lightningdesignsystem.com/components/tiles/

Actual

Expected

Do you know why the actual "Tiles" component doesn't rank higher than other components, considering the h1 of the component page says "Tiles"?

Do you want to request a feature or report a bug?

• Feature request
• index name: gitlab.json

What is the current behaviour?

The output of {{{_highlightResult.content.value}}} shows only text, as if the results were just a paragraph:

What is the expected behaviour?

• Show the headers:

• Display code in code blocks, like Algolia does for their docs:

What have you tried to solve it?

I don't know how to solve this, couldn't find anywhere - I'm probably searching for the wrong query.

@s-pace thoughts?

Hey, guys! I'm the maintainer of the babeljs.cn. I found that the docsearch of babeljs_cn was deleted, but I don 't know why. Please tell me why and how to solve it.
commit: e0cc0b8

http://docs.feathersjs.com/

As reported in tweet, configuration for Scalingo need an update.

https://www.freecodecamp.com/wiki/en/

There is a lot of nice content, but everything is hard to find.

https://getcomposer.org/

https://golang.org/

https://dev.to/ben/what-are-some-examples-of-great-documentation/comments

Interesting list for potential DocSearch candidates.

Hi,

Here is my config file: https://github.com/algolia/docsearch-configs/blob/master/configs/uniwebview.json

I've changed my domain from "unidocs.onevcat.com" to "docs.uniwebview.com" several days ago. However, the navigation destination of search result are still pointing to the old domain.

I guess it is due to the old index in using and the new ones are not valid yet.

I want to confirm is there anything like expiring duration for index? What is the reindex policy and is it possible to request a reindex immediately?

Thanks!

https://modernizr.com/docs

https://ux.mailchimp.com/patterns

https://docs.docker.com/

http://docs.unity3d.com/

http://docs.ansible.com/

http://ionicframework.com/docs/

http://guide.meteor.com/

https://support.gitkraken.com/

Suggested by @DirtyF

hey all, I was hoping for some help updating the indexing for the drone_io documentation. We have moved the documentation:

{
  "index_name": "drone_io",
  "start_urls": [
-   "http://readme.drone.io/"
+   "http://docs.drone.io/sitemap/"
  ],

We have also adjusted the structure. I was hoping that perhaps Algolia could crawl the documentation using the sitemap only (at http://docs.drone.io/sitemap/). This would allow us to make structural changes to the main documentation, without having to re-configure the crawling, since the sitemap structure would never change.

Do you think this would be possible?

I would offer to submit a pull request but was unsure if the below notation was correct, and I was having trouble setting up an environment to test myself (I will keep trying, though)

-    "lvl0": "header nav a.selected",
-    "lvl1": "main h1",
-    "lvl2": "main h2",
+    "lvl0": "body > ul > li > span",
+    "lvl1": "body > ul > li > ul > li > span",
+    "lvl2": "body > ul > li > ul > li > ul > li > a",

http://silex.sensiolabs.org/doc/master/

http://expressjs.com/

Moved to private repo

It would be useful for tracking and reporting purposes to have some fields in the configs that aren't necessarily used by the scraper. Immediately I'd like to add:

• name: Canonical, human-readable label (such as company or project name) for a given config.
• human_url: A URL that a human could go to and get the documentation site.
  I'm not married to those key names - suggestions welcome. 😄

https://atom.io/docs

The base reference manual: https://docs.puppet.com/puppet/latest

Note that Puppet Server, Hiera, and PuppetDB are split out into their own components (see https://docs.puppet.com/puppet/).

https://segment.com/docs

https://select2.github.io/

Do you want to request a feature or report a bug?

If it is a DocSearch index issue, what is the related index_name ?

index_name= pkgdown

What is the current behaviour?

Files that are not in the sitemap.xml are included in the index.

What is the expected behaviour?

Files that are not in the sitemap.xml should not be included in the index.

Summary

The pkgdown index includes the "Contributor Code of Conduct" page, which is not in the sitemap.xml.

To reproduce, go to the pkgdown website and search for "Contributor"; it's the first result.

The pkgdown config lists the sitemap.xml. Why is this page (and presumably other unwanted pages) included in the index?

From r-lib/pkgdown#626 (comment)

I am having a hard time figuring out what I need to configure so the scrapper can index the <code> block on my site.

This site is uses the same template as me, how would I index the code listed in it: https://myclabs.github.io/jquery.confirm/

https://lodash.com/docs

I love you for supporting nim-lang, but after trying the search I have to say: it's still not something that we can put on our website since the search results are too poor. For example, searching for 'split' doesn't contain a search result like http://nim-lang.org/docs/strutils.html#split,string,set[char],int

So lib.html is crawled, but none of actual Nim's stdlib. I would create a PR if only I knew how to do it.

http://electron.atom.io/docs/

Hi Algolia team !

I have a question about this configuration
https://github.com/algolia/docsearch-configs/blob/master/configs/akeneo.json

We will introduce a new design (same as https://api.akeneo.com/ ) for the v2.0 (the old design is still here : https://docs.akeneo.com/2.0/index.html)

So the parsing configuration between paths https://docs.akeneo.com/1.x/ and https://docs.akeneo.com/2.x/ will not be the same.

My question is: is it possible to have 2 configurations (one for 1.x and one for 2.x) ? If not, don't worry, we will bring back the new design for the previous 1.x paths.

Regars

Pierre
Akeneo

http://webpack.github.io/docs/

http://docs.videojs.com/

http://brunch.io/

It looks like a new parameter nb_hits_max has been introduced to the scraper. It would be great if information regarding this parameter is included in the documentation here 😄

For https://thumbprint.thumbtack.com our lvl0 selector looks like:

"lvl0": {
 "selector": "//*[@data-id='header__links']//a[@data-active='true']",
 "type": "xpath",
  "default_value": "Documentation"
},

https://github.com/algolia/docsearch-configs/blob/master/configs/thumbprint.json

When I search for the page title "Using Thumbprint in Sass" — https://thumbprint.thumbtack.com/guide/creating-pages/ — the search result correctly categorizes it under "Guide".

But if I search for the pages titles of the following pages:

• https://thumbprint.thumbtack.com/guide/utility-classes/
• https://thumbprint.thumbtack.com/guide/fonts/
• https://thumbprint.thumbtack.com/guide/philosophy/
• https://thumbprint.thumbtack.com/guide/creating-a-new-icon/

It categorizes them under "Documentation" instead of "Guide".

In this screenshot "https://thumbprint.thumbtack.com/guide/utility-classes/" is among the results, note that it's categorized under "Documentation"

I've confirmed the lvl0 xpath works on those pages so am not sure what would have caused it to fail. Maybe your crawler searched cached pages that didn't have this selector available?

http://vorlonjs.com/documentation/

http://leafletjs.com/reference.html

https://devcenter.heroku.com/

If it's an existing config, run that one and suggest to update the nbHits in a comment. You could use Danger for this, since it's an easy way to run some things and comment on GitHub.

Another thing that could be checked is whether it's valid JSON, and if it's a valid docsearch config (by checking if necessary keys are present, and if they have the right values)

http://api.jquery.com/

Search seems currently broken on https://ruby-doc.org/core/

If only they could add Docsearch to their build pipleline 🙏

https://nodejs.org/en/docs/

http://threejs.org/docs/index.html

http://momentjs.com/docs/

Do you want to request a feature or report a bug?

More feature than bug

If it is a DocSearch index issue, what is the related index_name ?

index_name= pkgdown

What is the current behaviour?

May R functions make use of ellipsis (...) to catch arguments in function calls. In a pkgdown documentation website these appear in the Argument list (see third argument on this page).

We capture most arguments and their values with the current docsearch pkgdown config, but ellipsis are not indexed because they are considered punctuation.

What is the expected behaviour?

I'd like ... to be included in search results as an argument value.

What have you tried to solve it?

I have tried including a period (.) in separatorsToIndex but the ellipsis are still not indexed.

http://docs.smooch.io/ios/