Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Search autocomplete #47

Closed
wants to merge 1 commit into from
Closed

Search autocomplete #47

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
94 changes: 94 additions & 0 deletions docs/components/search-autocomplete.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,94 @@
---
# This file is a template to document a new component within the GOV.UK Design Library website.
layout: component-documentation
sectionKey: Components
eleventyNavigation:
parent: Components

# Step 1: Duplicate and rename this file to the proposed component you want to include in the Design Library website.
# When duplicating and renaming this file use lowercase and replace any spaces with a dash (ie. -)

# Step 2: Set "eleventyExcludeFromCollections" to "false". This will ensure that the code snippet is commented out and this page will be display withinin the design library.
eleventyExcludeFromCollections: false

# Step 3: Input data points according to fields below to the best of your ability. Any fields without any data points will not be displayed on the website.

# Name of the component
# This is the name of the component (ex. Attachment). It is required to display the title on the page, in the meta data, and in the left-hand navigation menu of the components page.
title: Search Autocomplete

# Description of the component
# This briefly describes what the component is. It is required to display the description on the page, and in the <head> meta description.
description: #Delete this comment before entering the description of the component.

# When to use this component
# Briefly describe the situation(s) when to use this component.
# You MUST wrap this in double quotation marks (ie. " "), since markdown can be used to enter this information. To create a heading, use three hashes (ie. ###).
whenToUse:
#Delete this comment before entering when to use this component.

# When not to use this component
# Briefly describe the situation(s) when not to use this component.
# You MUST wrap this in double quotation marks (ie. " "), since markdown can be used to enter this information. To create a heading, use three hashes (ie. ###).
whenNotToUse:
#Delete this comment before entering when not to use this component.

# Accessibilty criteria for this component
# List out the accessibility for this component.
# You MUST wrap this in double quotation marks (ie. " "), since markdown can be used to enter this information. To create a heading, use three hashes (ie. ###).
accessibilty:
#Delete this comment before entering the accessibility criteria for this component.

# How the component works
# Briefly descibe how this component works. For instance, listing out what happens when an end-user interacts with this component.
# You MUST wrap this in double quotation marks (ie. " "), since markdown can be used to enter this information. To create a heading, use three hashes (ie. ###).
howItWorks:
#Delete this comment before entering how this component works.

# Variations for this component
# List out any variations that exist for this component by providing (1) the name of said variation and (2) a brief description of that variation.
variations:
# To add additional variations duplicate the the fields below (adhering to the formating) but increase the count by one integer.
0:
title: #Delete this comment before entering the name of the variation that exists for this component.
description:
# You MUST wrap this in double quotation marks (ie. " "), since markdown can be used to enter this information. To create a heading, use three hashes (ie. ###).
#Delete this comment before entering a description of variation.

# Evidence and insights for this component
# List out all past documentation/supporting material with regards to or realted to this component. It can include (1) past design documentation, (2) research findings, and (3) presentations.
insights:
# To add additional insights duplicate the the fields below (adhering to the formating) but increase the count by one integer.
0:
# Both title and link are REQUIRED in order for this information to render on the page.
title: #Delete this comment before entering the name of the insight document.
link: #Delete this comment before entering the URL of the insight document.
documentFormat: #Delete this comment before entering the format of the insight document. Example: (1) Google Doc, (2) Google Sheets, and (3) Google Slides.
description:
# You MUST wrap this in double quotation marks (ie. " "), since markdown can be used to enter this information. To create a heading, use three hashes (ie. ###).
#Delete this comment before entering a brief summary about the document being referred.
date: #Delete this comment before entering the date when the document was published.

# Other design libraries
# List out all the other design libraries that have documented this exact same component. This includes the GOV.UK Design System, along with other UK government departments.
designLibraries:
# To add additional design libraries duplicate the the fields below (adhering to the formating) but increase the count by one integer.
0:
# Both title and link are REQUIRED in order to display this information on the page.
title: #Delete this comment before entering the name of the design library.
link: #Delete this comment before entering the URL of the corresponding design library.

# How to report an issue with this component
# This will display instrucions on how to report an issue via GitHub.
# Consult with a developer to confirm the GitHub where the component's codebase exists.
githubIssueLink: #Delete this comment before entering the URL of the page to create a new GitHub issue.

# Existing issues with this component
# List of all the issues that are associated with this component, (1) containing the title used to describe the issue on GitHub, and (2) the link to the GitHub issue itself.
issues:
# To add additional issues duplicate the the fields below (adhering to the formating) but increase the count by one integer.
0:
# Both title and link are REQUIRED in order to display this information on the page.
title: #Delete this comment before entering the title of the GitHub issue.
link: #Delete this comment before entering the URL of the corresponding GitHub issue.
---