qdrant / landing_page Goto Github PK
View Code? Open in Web Editor NEWLanding page for qdrant.tech
Landing page for qdrant.tech
Status | Count |
---|---|
๐ Total | 14049 |
โ Successful | 13343 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 664 |
โ Unknown | 9 |
๐ซ Errors | 33 |
We have two types of warning notices status and alert
Currently, only "status" is showing.
I tried to put an alert on this page: https://qdrant.tech/documentation/tutorials/create-snapshot/
It isn't rendering and the code around it isn't showing either.
I think we should have a single location for educational content like case studies, articles, presentations.
Also, the visitor should pick from tags so they don't have to scroll all the way through.
There would be a checklist on the left sidebar where the visitor would check off the content. Is that possible?
Status | Count |
---|---|
๐ Total | 12443 |
โ Successful | 11820 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 604 |
โ Unknown | 11 |
๐ซ Errors | 8 |
Status | Count |
---|---|
๐ Total | 14225 |
โ Successful | 13545 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 666 |
โ Unknown | 9 |
๐ซ Errors | 5 |
We have an issue in python-client repository: qdrant/qdrant-client#296
I believe it might be caused by the lack of some details in "Lookup in groups" documentation
with_lookup
is not noticeable, I think it should be moved closer to the image with collections.lookup_from
behaviour is missing. It should be described because it might be complicated to understand it without just trying out experiments. (We take vector ids from positives
and negatives
, extract vectors from lookup collection by these ids, construct our "search_vector" and search with it in the "main" collection)It might also be useful to mention that this lookup collection can be treated as pure payload collection, i.e. it is not necessary to store some meaningful vectors in it, however vector configuration should be set during collection creation and field with something during upload (e.g. None
or [0]
)
I run the first couple of steps in the Quickstart guide. I successfully get access to qdrant at http://localhost:6333.
However, the Quickstart says nothing about where to Initialize The Client.
I research, I find https://qdrant.tech/documentation/quick-start/#initialize-the-client. I successfully install the client. I still don't know how/where to run the commands to set up the client. The pip
in the client installation command suggests that I need to use Python. But what then? Do I create a .py file? How do I proceed?
With a Quickstart, I shouldn't have to do all of this research.
Status | Count |
---|---|
๐ Total | 11410 |
โ Successful | 10490 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 573 |
โ Unknown | 24 |
๐ซ Errors | 323 |
Please create a contributing.md file which helps Open source contributors to contribute to this code base.
Define the tools and stack which was used to create this project or website/
Guidelines to setup this project locally
When browsing the documentation, we often want to share the links to specific sections, for example:
https://qdrant.tech/documentation/concepts/collections/#collections
However, if we first use the search bar to look for stuff, a query param selector
is added to the URL, and any further sections that we select will also have the big selector string
https://qdrant.tech/documentation/concepts/collections/?selector=aHRtbCA%2BIGJvZHkgPiBkaXY6bnRoLW9mLXR5cGUoMSkgPiBzZWN0aW9uID4gZGl2ID4gZGl2ID4gZGl2ID4gYXJ0aWNsZSA%2BIGgx#collections
It would make our life easier if we could just copy the URL without cleaning it afterwards for sharing it. Note that including the selector does not make the link unusable, but it makes the URL harder to read when pasted in chats.
Links from the search bar should omit the selector
query param
Another solution would be that clicking on the link icon of each title should remove the selector
query param.
We have warnings from highlight.js about unescaped HTML, so we should wrap code blocks in the htmlEscape
Hugo function.
Status | Count |
---|---|
๐ Total | 13384 |
โ Successful | 12734 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 638 |
โ Unknown | 7 |
๐ซ Errors | 5 |
Status | Count |
---|---|
๐ Total | 12366 |
โ Successful | 11573 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 767 |
โ Unknown | 21 |
๐ซ Errors | 5 |
Status | Count |
---|---|
๐ Total | 11259 |
โ Successful | 10700 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 549 |
โ Unknown | 3 |
๐ซ Errors | 7 |
Duplicate CSS rules for the img
tag.
landing_page/qdrant-landing/themes/qdrant/static/css/_reset.scss
Lines 128 to 141 in 765cb29
Remove the duplicate rules.
Our distributed deployment relies on the Raft consensus algorithm.
With Raft, it is necessary to get a majority of vote to elect a new leader.
In case of 2 nodes cluster, it is not possible to so do in case of node in case of failure.
We should warn users to use a minimum of 3 nodes for their clusters.
Status | Count |
---|---|
๐ Total | 14135 |
โ Successful | 13404 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 663 |
โ Unknown | 8 |
๐ซ Errors | 60 |
https://qdrant.tech/documentation/cloud/ page
Ubuntu; [
Settings:
Resolution: 2560 x 1440;
Scale: 125%;
Fractional Scaling: On
]
Google Chrome;
Users are often asking how to upgrade an existing qdrant deployment to a new version.
It does not seem documented anywhere.
The official answer is to upgrade the minor versions sequentially.
Implement all as a separate PRs
Status | Count |
---|---|
๐ Total | 13384 |
โ Successful | 12734 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 638 |
โ Unknown | 7 |
๐ซ Errors | 5 |
Status | Count |
---|---|
๐ Total | 12363 |
โ Successful | 11572 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 766 |
โ Unknown | 21 |
๐ซ Errors | 4 |
The 'capacity planning' link on webpage https://qdrant.tech/documentation/cloud/, returns a 404. See the screenshot below.
It happened due to incorrect reference to the documentation/cloud/capacity-sizing.md
file.
Put correct reference to the Markdown file.
I am astonished as to how the link checker GitHub action didn't catch this. This URL is not reported in the last linkcheck issue. Shall we use https://github.com/filiph/linkcheck/ in addition to lychee?
Update:
I ran filiph/linkcheck locally. It successfully identified the 404 link.
http://localhost:1313/documentation/cloud/
- (1178:174) 'capacity..' => http://localhost:1313/documentation/capacity/ (HTTP 404)
Status | Count |
---|---|
๐ Total | 12089 |
โ Successful | 11305 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 758 |
โ Unknown | 23 |
๐ซ Errors | 3 |
When browsing the documentation, we normally have http / python versions of each example. But the http example is always selected by default, and when we switch to python, only the example we switched is changed, which is a bit cumbersome for a user that is only using the python client.
It would make sense for a python user who is browsing the docs, to only have to make the switch once, and have all the examples switch to the python version.
Status | Count |
---|---|
๐ Total | 12363 |
โ Successful | 11577 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 766 |
โ Unknown | 16 |
๐ซ Errors | 4 |
Status | Count |
---|---|
๐ Total | 11270 |
โ Successful | 10679 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 563 |
โ Unknown | 13 |
๐ซ Errors | 15 |
Duplicate CSS rules in:
landing_page/qdrant-landing/themes/qdrant/static/css/custom-animate.css
Lines 262 to 280 in 765cb29
Looking at the other keyframes rules, I feel that adding the -webkit-
prefix could be the fix.
Based on preliminary inspection, I see that qdrant-landing/themes/qdrant/static/css/custom-animate.css
is not being used on the website. So, the website is not impacted by this bug.
Status | Count |
---|---|
๐ Total | 12011 |
โ Successful | 11406 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 589 |
โ Unknown | 13 |
๐ซ Errors | 3 |
Status | Count |
---|---|
๐ Total | 11138 |
โ Successful | 10571 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 528 |
โ Unknown | 20 |
๐ซ Errors | 19 |
landing_page/qdrant-landing/README.md
Lines 7 to 21 in 765cb29
We can do away with the requirement of using SASS from NPM. The Hugo extended version can transpile Sass to CSS using the embedded LibSass transpiler. Hugo can watch for changes and provide minified output.
landing_page/qdrant-landing/README.md
Lines 59 to 63 in 765cb29
We can do away with the requirement of using cwebp. The Hugo extended version can convert images to webp.
Hugo image processing can also crop from center:
When using the Crop or Fill method, the anchor determines the placement of the crop box. You may specify TopLeft, Top, TopRight, Left, Center, Right, BottomLeft, Bottom, BottomRight, or Smart.
Some benefits of doing it the Hugo way:
landing_page/qdrant-landing/README.md
Line 57 in 765cb29
This is a purely optional upgrade due to the following reason:
However, Hugo can perfectly do, what this repo is trying to achieve with bash & ImageMagick. These include:
With Hugo we can use native methods like {{ .Title }}
, {{ .Section }}
instead of bash methods grep
, head
& sed
. I don't have a performance comparison (regarding time, resources used) between Hugo & ImageMagick.
I see that this repo was created in March 2021, when Hugo didn't support webp. It was added in May 2021 in v0.83.0. I also understand that there can be certain reasons (which I may have missed) due to which the maintainers prefer to use these tools.
I am interested in hearing from the maintainers about their perspective on these upgrades.
Edit on GitHub link at the bottom of the webpage needs the path variable updated.
We just created new folders and the link to repo doesnt work for docs inside of folders....only for docs on the first level of the directory.
Try to edit http://qdrant.tech/documentation/concepts/collections/
It doesn't lead to the right folder in the repo.
Landing container padding
Details card seperation ( adding border and box shadow can work)
Making a single design for buttons and button-containers and using it throughout the page for uniformity
Margin for company logos in here
We can add padding left and right to the container in mobile view and also improve the font size
There are multiple issues in file css/blocks/_forms.scss
.
font-weight
CSS rule at 2 places:landing_page/qdrant-landing/themes/qdrant/static/css/blocks/_forms.scss
Lines 187 to 207 in 765cb29
landing_page/qdrant-landing/themes/qdrant/static/css/blocks/_forms.scss
Lines 284 to 299 in 765cb29
Maintainers can decide which rule to use.
.styled-form .form-group .radio-box label
and styleslanding_page/qdrant-landing/themes/qdrant/static/css/blocks/_forms.scss
Lines 134 to 158 in 765cb29
.styled-form .form-group .check-box label
and styleslanding_page/qdrant-landing/themes/qdrant/static/css/blocks/_forms.scss
Lines 231 to 255 in 765cb29
Remove duplicate color: var(--brand-secondary)
rule. Consolidate CSS rules. I have opened a PR to fix this.
Status | Count |
---|---|
๐ Total | 85 |
โ Successful | 82 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 2 |
โ Unknown | 1 |
๐ซ Errors | 0 |
Full Github Actions output |
Status | Count |
---|---|
๐ Total | 14050 |
โ Successful | 13336 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 667 |
โ Unknown | 10 |
๐ซ Errors | 37 |
Status | Count |
---|---|
๐ Total | 12825 |
โ Successful | 12195 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 618 |
โ Unknown | 7 |
๐ซ Errors | 5 |
Status | Count |
---|---|
๐ Total | 12516 |
โ Successful | 11893 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 608 |
โ Unknown | 11 |
๐ซ Errors | 4 |
Status | Count |
---|---|
๐ Total | 11138 |
โ Successful | 10567 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 544 |
โ Unknown | 24 |
๐ซ Errors | 3 |
Status | Count |
---|---|
๐ Total | 11069 |
โ Successful | 10494 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 546 |
โ Unknown | 23 |
๐ซ Errors | 6 |
Status | Count |
---|---|
๐ Total | 14135 |
โ Successful | 13470 |
โณ Timeouts | 0 |
๐ Redirected | 0 |
๐ป Excluded | 663 |
โ Unknown | 0 |
๐ซ Errors | 2 |
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.