Replaces the "other ways to donate" link with a
swappable translation token - allowing us to use
localised versions of the news article when
they are available.
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
Modifies the translation schema to allow the
footer links (such as `about`) to be replaced
based on the client locale. Updates the snapshot
for the `Footer` component to reflect the changes.
Signed-off-by: nhcarrigan <nhcarrigan@gmail.com>
* fixed issue offline warning message is hard to read in dark mode
* Update client/src/components/OfflineWarning/OfflineWarning.js
Co-authored-by: Nicholas Carrigan (he/him) <nhcarrigan@gmail.com>
* Update client/src/components/OfflineWarning/OfflineWarning.js
Co-authored-by: Nicholas Carrigan (he/him) <nhcarrigan@gmail.com>
Co-authored-by: Nicholas Carrigan (he/him) <nhcarrigan@gmail.com>
* #40220 Bug(learn) - List item's font size larger than surrounding text
* #40220 move description css in challenge-description.css
* Update client/src/templates/Challenges/components/challenge-description.css
Co-authored-by: Nicholas Carrigan (he/him) <nhcarrigan@gmail.com>
Co-authored-by: Nicholas Carrigan (he/him) <nhcarrigan@gmail.com>
* fix catastrophic backtracking when removing HTML comments
The regexp `/<!--(.|\s)*?-->/g` can experience catastrophic backtracking while matching a string like `<!-- -- >` (notice how it does not end with `-->`).
[You can see the catastrophic backtracking in action here](https://regex101.com/r/2jvwFi/1/debugger).
This is because both `.` and `\s` matches the space character, and there are therefore a large number of possible ways for `(.|\s)*` to match a long sequence of spaces.
The regexp evaluator is greedy, and the problem therefore only exists when the string does not match the regexp.
The fix is simply to remove the ambiguity such that there is only one possible way for the regexp to match a sequence of white-space.
* Update client/src/utils/curriculum-helpers.js
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>
* feat: add show solution button in TimeLine
* feat: added tests for CertificateSettings and TimeLine
* feat: view button only for projects
* feat: view button visible only for projects
* feat: get helpCategory from frontmatter
* DEBUG: sets all the projects to JavaScript
This is just so the tests pass, it'll need to go.
* fix: updated helpCategoryMap categories
* fix: added Python to helpCategory frontmatter key
Co-authored-by: Randell Dawson <rdawson@onepathtech.com>
First noticed on the challenge "Divide the Grid Into an Area Template", text is hard to read in night mode due to low contrast in the CSS code block. Problem was discussed in issue #39967, and this change was proposed to boost contrast above the minimum acceptable ratio of 4.5:1.
This change only targets CSS code blocks in night mode, and only strings. I could not find code blocks in other languages with this issue, but they may exist.
This also does not target `.token.operator`, `.token.entity`, or `.token.url`. There is no issue here with contrast, but these classes do not include a background. A proposed future change could be to remove the background from `.token.string` as well, but this change is not made here, as current style guides recommend the background.
