docusaurus-search-local
searchkit
docusaurus-search-local | searchkit | |
---|---|---|
3 | 5 | |
418 | 4,714 | |
- | 0.3% | |
2.4 | 7.6 | |
about 2 months ago | 5 days ago | |
JavaScript | TypeScript | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docusaurus-search-local
- Docusaurus failing to build
-
Ask HN: What do people use for documentation sites these days?
If & when relevant: from looking into self-hosted search options to accompany docusaurus, https://github.com/cmfcmf/docusaurus-search-local looks like one potential candidate (search is performed locally; so your mileage may vary based on the document set size).
-
Gatsby fixing errors, simple multilingual page
I found a way to fix the error editing the plugin itself. thanks to Shigeru-Sakurai
searchkit
-
Autocomplete – a JavaScript library for building autocomplete experiences
https://github.com/searchkit/searchkit is an instantsearch adapter for elasticsearch / opensearch
-
React.dev
One example of this pattern is Searchkit [0] which performs most of its logic inside a singleton Searchkit class which is instantiated and passed as a prop to the root React component. A bonus is that it's easier to implement bindings for Angular, Svelte, etc. since they can rely mostly on the class. For example, it looks like Searchkit now suggests using InstantSearch (react-instantsearch-dom) [1] from Algolia, i.e. an entirely different maintainer, and it creates the bindings with a `Client(new SearchKit(...))` adapter [2] around the class (see the code on the home page at [0]).
[0] https://www.searchkit.co/
[1] https://github.com/algolia/instantsearch
[2] https://github.com/searchkit/searchkit/blob/main/packages/se...
- I made Elasticsearch work with Algolia's Instantsearch
-
How to build an availability search UI with Elasticsearch
We will use React, Next.JS, Instantsearch and Searchkit to build a search UI.
-
Ask HN: Should I give up and get a job?
I think you are probably spending too much of your time on software and too little time on marketing.
When I look at an open-source project, I ask myself three things:
1) What does it do exactly?
2) Is this easy to get started with?
3) Does it have any documentation?
For example, I have a use case for wanting to use graphql to communicate with elasticsearch. I google "graphql + elasticsearch" and somewhere a link to https://www.searchkit.co/ comes up. I look at it and I find my answers within 60 seconds:
1) Top of the page I see "Searchkit is an open source library which helps you build a great search experience with Elasticsearch. Powered by Apollo GraphQL." This makes me think that yeah, it's probably looking to solve a similar problem to me. In case I had any doubts, there's a demo.
2) Yes, easy to get started. There's a big "get started" button at the top of the page. And a get-started-video link at the bottom of the homepage.
3) At a glance, yes, it has decent documentation.
Given that I quickly got answers to these 3 questions, yes, I might consider using this project, or at least trying it out.
When I go to your page, I see:
1) River DB is a Rust connection pool and middleware proxy... ok... why do i need that? What problem is this solving? There's a long paragraph I can read after that, but when i'm browsing the web i don't usually read long paragraphs, so you've lost me already.
2) I have no idea how to get started
3) Doesn't look like there's any docs
Given the above, why would I use your software?
Note that the above has nothing to do with your software quality. But people only care about your code if things are breaking. Marketing material is what gets them in the door. For example, I use React all the time. I have NO IDEA if the underlying code is any good. And I don't really care. What I care about is that it's easy to use.
Anyway, long story short... if you want to build a software business, coding is maybe 30-40% of the job. Marketing, sales, documentation and all that jazz is probably the majority of the work. If you don't want to do that and you just want to code, then great, get a job. People will pay you good money for that.
What are some alternatives?
docusaurus-lunr-search - Local / Offline Search for docusaurus
semantic-ui-react - The official Semantic-UI-React integration
OpenSearch-Dashboards - 📊 Open source visualization dashboards for OpenSearch.
sveltekit-graphql-github - Use Apollo Client with SvelteKit to Query a GraphQL API: we use the GitHub API to query our repos and learn a bit of SvelteKit along the way.
autocomplete - 🔮 Fast and full-featured autocomplete library
rctui - A collection of components for React, base on bootstrap 4.0.
docsearch - :blue_book: The easiest way to add search to your documentation.
pivotal-ui-react - Pivotal's design system & component library
docusaurus-plugin-remote-content - A Docusaurus plugin to download content from remote sources when it is needed.
cdbreact - Contrast Design Bootstrap : Elegant UI Kit and reusable components for building mobile-first, responsive websites and web apps
bemuse - ⬤▗▚▚▚ Web-based online rhythm action game. Based on HTML5 technologies, React, Redux and Pixi.js.
react-uikit-components - React UIkit Components for the UIKit CSS framework