Skip to content

Commit d904ac6

Browse files
committed
Merge branch 'release/1.0.1'
2 parents af9f01e + 83a481e commit d904ac6

File tree

6 files changed

+51
-0
lines changed

6 files changed

+51
-0
lines changed

CHANGELOG.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# Change Log
2+
All notable changes to the REDCap CSS Injector module will be documented in this file.
3+
This project adheres to [Semantic Versioning](http://semver.org/).
4+
5+
## [1.0.1] - 2019-04-04
6+
### Added
7+
- Add CSS Samples and 'Writing CSS for the CSS Injector' (Philip Chase)
8+
9+
### Changed
10+
- Fixing REDCap minimal version on README. (Tiago Bember Simeao)
11+
12+
13+
## [1.0.0] - 2018-07-17
14+
### Summary
15+
- Created the REDCap CSS Injector module.

README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,3 +21,11 @@ The configuration form also provides an enable/disable switch for each one of yo
2121
If more than one style is applied to the same page, the CSS rules are applied in the order of appearance in the configuration form.
2222

2323
![Configuration screen](img/config.png)
24+
25+
## Sample CSS
26+
27+
For CSS ideas you could try in CSS injector see the [sample CSS files](samples/). These files were tested against surveys in REDCap 8.7.0. Please verify they work as desired in your REDCap before using them in production. Each is dependent on REDCap's style names. As those style names can change over time, they probably won't hold value forever.
28+
29+
## Writing CSS for the CSS Injector
30+
31+
To learn how to craft your own CSS for use in REDCap CSS Injector, you'll need to use the developer tools for your web browser. Chrome supports the [Chrome DevTools](https://developers.google.com/web/tools/chrome-devtools/). Firefox supports [Firefox Developer Tools](https://developer.mozilla.org/en-US/docs/Tools). Using one of these tools you can access a REDCap page and inspect an element of the page you want to change. The dev tools allow you to see what CSS controls an element's appearance. You can change the values you think might give you the effect you want and review the result in real time on that page. Once you get the result you like, copy that CSS, trim it down to the part you care about, and test it in CSS inspector.

samples/hide_reset_button.css

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
.resetLinkParent {
2+
visibility: hidden;
3+
}

samples/set_body_font.css

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
body * {
2+
font-family: 'Helvetica Neue', 'Helvetica', 'Arial',sans-serif !important;
3+
}

samples/set_text_color.css

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
body * {
2+
color: #666666 !important;
3+
}
4+
5+
button {
6+
color: #666666 !important;
7+
}

samples/unbold_surveys.css

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
.labelrc {
2+
font-weight: unset;
3+
}
4+
5+
#surveytitle {
6+
font-weight: unset;
7+
}
8+
9+
button {
10+
font-weight: unset;
11+
}
12+
13+
.header.toolbar {
14+
font-weight: unset;
15+
}

0 commit comments

Comments
 (0)