docsearch is published on npm too, but it's a bit confusing that it's actually published as `docsearch.js`, so this should definitely be put somewhere in the README
The link used to point to the ruby explanations, but it didn’t exist at that id. Since it’s using js, I changed it to point to that point in the js documentation
* feat(dom): wrap separator with a span
* feat(option,dom): add debug to root class + add duplicate class on subcategory and title
* fix(dom): do not display content wrapper if there is nothing inside
Running `npm run serve` will watch for changes in the source files and
rebuild all `css` and `js` files accordingly in the `dist` folder. It
will also expose the same files on `http://localhost:8080/` (by
default, if port `8080` is already taken it will move to an available
one).
This will let developers use a specific branch/version of docsearch in
their projects. Just open a new tab and run `npm run serve` in the
docsearch repo, and you'll be able to include the scripts from the
running server in your HTML.
As files are automatically regenerated on disk whenever a change is
detected, you can also `require` files by targeting the `dist` folder.
- highlight background CSS rules was wrongly configured
- navbar-header text was black
- active links had a default black background
- fixed a few links using references instead of actual links (doesn't
work once extracted to documentation.md)
- use absolute image path
I've added a screencast in the readme, a screenshot of the default
colorscheme and a copy-paste of the CSS customization example.
The diff of the README is all red because I used
[formd](http://drbunsen.github.io/formd/) on the file to make the
links more readable (it simply uses reference instead of inlining).
