-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
site: add search function #446
Conversation
✅ Deploy Preview for kurator-dev ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
fb91808
to
d552a36
Compare
Signed-off-by: Xieql <[email protected]>
d552a36
to
29cddd7
Compare
/kind documentation |
/lgtm |
goog work /lgtm |
docs/config.toml
Outdated
@@ -60,6 +60,17 @@ path = "github.com/google/docsy/dependencies" | |||
|
|||
[params] | |||
copyright = "The Kurator Authors" | |||
|
|||
# Google Custom Search Engine ID. Remove or comment out to disable search. | |||
#gcs_engine_id = "d72aa9b2712488cc3" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we remove it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
Signed-off-by: Xieql <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hzxuzhonghu The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/label tide/merge-method-squash |
What type of PR is this?
/kind feature
What this PR does / why we need it:
site: add search function
Which issue(s) this PR fixes:
Fixes #380
Special notes for your reviewer:
Does this PR introduce a user-facing change?: