-
Notifications
You must be signed in to change notification settings - Fork 483
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
[prod] Solution providers. #3485
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Font awesome has been updated since these were added. Having them in the assets/css folder is the correct placement. Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Formatted the frontmatter field for the opensearch tech into an array, and gave consistent tags across the board. Standardized spelling for tags to have capital first letter. Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Removed the brackets from the opensearch tech. Grouped and organized the search filters and tags together. Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
created the scroll to top component, the javascript and css files. Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
javascript turns it visible when you start to scroll. Finicky, still needs some work to get it working correctly. Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
…existing. Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Built custom scss components - both an accordion and button. These custom components were placed in a new scss folder labeled '/components/' Also, datafile was changed to put the Solutions Providers filtering categories, in alphabetical order. Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
- Style sheet was renamed from _partners.scss to _solutionsProviders.scss. The assets/css/output.scss was changed to input the renamed style sheet. - The collection was renamed from _partners/ to _solutionsProviders/. - Collection - Content in the [sample.md](http://sample.md) files were changed to reflect this change. - Image pathing for partners stays the same! this was too big of a change. it would have meant updating the image pathing on all existing partners, and renaming the assets/img/partners folder. It remains the same. - - in order to do this, the class styling needed to be changed. - Update to the pathing in footer and navbar - now links to the new solutionsProviders page instead of the non-existant partners page. This update took place in their respective datafiles. - Renamed the navbar ‘partners’ link in the community dropdown to ‘providers’ Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
This was a vulnerability for XXS attacks and it was not being used on the site. Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
Signed-off-by: kaimmej <[email protected]>
[FEATURE] Partner filtering. Collection renamed to SolutionsProviders
nateynateynate
requested review from
elfisher,
AMoo-Miki,
nknize,
krisfreedain,
peterzhuamazon,
CEHENKLE,
dtaivpp,
kolchfa-aws and
natebower
as code owners
December 9, 2024 18:18
krisfreedain
approved these changes
Dec 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds solution provider filtering to the solution providers page.
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.