-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat(links): secondary link class #63
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
.link-secondary { | ||
color: $link-color-secondary; | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -244,6 +244,8 @@ $link-hover-decoration: underline !default; | |
// Darken percentage for links with `.text-*` class (e.g. `.text-success`) | ||
$emphasized-link-hover-darken-percentage: 15% !default; | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. should these vars go here or in the new _links.scss file There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hmm, that's a good question, and one I'm not sure of the answer to. Not sure what is considered "best practice" for that. I assume all vars should live in the _variables file. 🤷♂️ There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. will keep it there for now, we have other vars we've added to this file. but when we upgrade we will have to resolve conflicts in this file. i think best practice is to have an override.scss |
||
$dark-blue: #0028A8 !default; | ||
$link-color-secondary: $dark-blue; | ||
// Paragraphs | ||
// | ||
// Style p element. | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -46,3 +46,4 @@ | |
@import "print"; | ||
@import "sprite"; | ||
@import "video-tile"; | ||
@import "links"; |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
layout: docs | ||
title: Links | ||
description: Anchor tags | ||
group: components | ||
--- | ||
This component does not exist in bootstrap by defeault. We could have overidden `text-secondary` in `Colors` but that would have affected all the components that use `text-secondary`, like `Buttons`. | ||
|
||
|
||
## Examples | ||
|
||
By default, a href tags are the primary theme color. | ||
|
||
{% capture example %} | ||
<a href="#">Default link</a> | ||
{% endcapture %} | ||
{% include example.html content=example %} | ||
|
||
Secondary links are anchor tags that have a secondary call to action. | ||
|
||
{% capture example %} | ||
<a href="#" class="link-secondary">Secondary link</a> | ||
{% endcapture %} | ||
{% include example.html content=example %} |
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.
should we git ignore this file? is it autogenerated?
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.
As y'all chatted about in Chapter meeting, this is a part of the Bootstrap build process. Technically this file has important configuration details in it and shouldn't be ignored. The changes to this file are done via The build script to hash the files (some of which we don't need). All that to say... For now I'd just leave it as modified because it doesn't hurt anything.
I'm excited about y'all investigating better improvements for this project. 😄