You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This pull request introduces a significant update to the site's branding, typography, and some UI/UX improvements, along with minor infrastructure and content changes. The most important changes are grouped below by theme.
Branding and Typography Updates:
Switched the primary site font from "Slfdreamer" to "Lexend" for body text, with "SLF Dreamer" now used only for the copyright/footer. All relevant font loading and CSS have been updated, and the brand guidelines page reflects this new hierarchy. (base.css, brand.html, [1][2][3][4][5][6][7]
Updated the brand wordmark in brand.html to visually distinguish "Tech" with lighter font weight, and clarified font usage in the typography section. (brand.html, [1][2]
UI/UX Improvements:
Refactored the theme toggle button to be injected by JavaScript (theme.js) rather than being statically present in the HTML, simplifying the markup in both apply.html and brand.html. (apply.html, [1][2]
Improved form and layout markup in apply.html for readability and maintainability, including better indentation, more semantic structure, and updated copy to be more inviting ("Have a project idea?"). (apply.html, [1][2][3][4][5]
Code and Style Quality:
Rewrote and expanded brand.css for clarity, maintainability, and consistency, including better codebox and tab styling, and improved code sample highlighting. (brand.css, [1][2]
Improved JavaScript in brand.html for robustness (e.g., using .replaceAll, better error handling, and using dataset), and made codebox and copy button markup more semantic. (brand.html, [1][2][3]
Infrastructure:
Added a .github/dependabot.yml configuration to enable weekly npm dependency updates. (.github/dependabot.yml, .github/dependabot.ymlR1-R11)
Content and Navigation:
Added new project redirects to _redirects for easier access to hosted projects. (_redirects, _redirectsL5-R13)
* Initial plan
* fix: follow system theme on donate page instead of forcing dark mode
Co-authored-by: kiyarose <75678535+kiyarose@users.noreply.github.com>
* Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* style: format code with Prettier and StandardJS
This commit fixes the style issues introduced in 04d1db2 according to the output
from Prettier and StandardJS.
Details: #21
* fix: head script uses only system theme, no localStorage, on donate page
Co-authored-by: kiyarose <75678535+kiyarose@users.noreply.github.com>
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: kiyarose <75678535+kiyarose@users.noreply.github.com>
Co-authored-by: Kiya Rose Ren-Miyakari <kiya.rose@sillylittle.tech>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: deepsource-autofix[bot] <62050782+deepsource-autofix[bot]@users.noreply.github.com>
* Switch primary font to Lexend and keep footer in SLF Dreamer
Co-authored-by: Kiya Rose Ren-Miyakari <kiya.rose@sillylittle.tech>
* Increase button font weight and lighten Tech wordmark
Co-authored-by: Kiya Rose Ren-Miyakari <kiya.rose@sillylittle.tech>
* style: format code with Prettier and StandardJS
This commit fixes the style issues introduced in 3e8c457 according to the output
from Prettier and StandardJS.
Details: #22
* Move Google Fonts to `<link>` preconnect and fix "Tech" wordmark font (#24)
* Initial plan
* perf: move Google Fonts to link preconnect and fix Tech wordmark font
Co-authored-by: kiyarose <75678535+kiyarose@users.noreply.github.com>
* docs: add comment to base.css noting Lexend must be loaded via link in HTML head
Co-authored-by: kiyarose <75678535+kiyarose@users.noreply.github.com>
* Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: kiyarose <75678535+kiyarose@users.noreply.github.com>
Co-authored-by: Kiya Rose Ren-Miyakari <kiya.rose@sillylittle.tech>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
---------
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: deepsource-autofix[bot] <62050782+deepsource-autofix[bot]@users.noreply.github.com>
Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
…rkup (#25)
* Initial plan
* fix: address regex security hotspot in brand.html and deduplicate theme-toggle markup
- brand.html: change lazy quantifier [^&]*? to greedy [^&]* in highlightHtml
regex; add comment noting input is machine-generated (not user input) so ReDoS
is not a concern
- theme.js: add injectThemeToggleButton() so the button is defined in one place;
init() now injects it automatically when #themeToggle is absent
- index.html, apply.html, donate.html, brand.html: remove 38-line duplicated
theme-toggle <button> block from each file (replaced with a brief comment)
Co-authored-by: kiyarose <75678535+kiyarose@users.noreply.github.com>
Agent-Logs-Url: https://github.com/SillyLittleTech/lander/sessions/d607b3be-436a-4aac-9f9f-13f8be74a195
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: kiyarose <75678535+kiyarose@users.noreply.github.com>
Apply page now better serves as a versatile contact us page.
The terminology on this page now better serves any possible reason for contact, and is welcoming to projects of all types.
We reviewed changes in 1769393...0c337cf on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.
The reason will be displayed to describe this comment to others. Learn more.
Documentation comment not found for function declaration `getSavedTheme`
It is recommended to have documentation comments above, or right inside a function/class declaration.
This helps developers, users and even the author understand the purpose of a code snippet or API function in the future.
NOTE: If you want to stop this issue from getting raised on certain constructs (arrow functions, class expressions, methods etc.), consider using the skip_doc_coverage option under the analyzers.meta property in your .deepsource.toml file.
For example, the following configuration will silence this issue for class expressions and method definitions:
The reason will be displayed to describe this comment to others. Learn more.
Documentation comment not found for function declaration `saveTheme`
It is recommended to have documentation comments above, or right inside a function/class declaration.
This helps developers, users and even the author understand the purpose of a code snippet or API function in the future.
NOTE: If you want to stop this issue from getting raised on certain constructs (arrow functions, class expressions, methods etc.), consider using the skip_doc_coverage option under the analyzers.meta property in your .deepsource.toml file.
For example, the following configuration will silence this issue for class expressions and method definitions:
The reason will be displayed to describe this comment to others. Learn more.
Documentation comment not found for function declaration `applyTheme`
It is recommended to have documentation comments above, or right inside a function/class declaration.
This helps developers, users and even the author understand the purpose of a code snippet or API function in the future.
NOTE: If you want to stop this issue from getting raised on certain constructs (arrow functions, class expressions, methods etc.), consider using the skip_doc_coverage option under the analyzers.meta property in your .deepsource.toml file.
For example, the following configuration will silence this issue for class expressions and method definitions:
The reason will be displayed to describe this comment to others. Learn more.
Documentation comment not found for function declaration `detectSystem`
It is recommended to have documentation comments above, or right inside a function/class declaration.
This helps developers, users and even the author understand the purpose of a code snippet or API function in the future.
NOTE: If you want to stop this issue from getting raised on certain constructs (arrow functions, class expressions, methods etc.), consider using the skip_doc_coverage option under the analyzers.meta property in your .deepsource.toml file.
For example, the following configuration will silence this issue for class expressions and method definitions:
The reason will be displayed to describe this comment to others. Learn more.
Documentation comment not found for function declaration `toggleTheme`
It is recommended to have documentation comments above, or right inside a function/class declaration.
This helps developers, users and even the author understand the purpose of a code snippet or API function in the future.
NOTE: If you want to stop this issue from getting raised on certain constructs (arrow functions, class expressions, methods etc.), consider using the skip_doc_coverage option under the analyzers.meta property in your .deepsource.toml file.
For example, the following configuration will silence this issue for class expressions and method definitions:
The reason will be displayed to describe this comment to others. Learn more.
Documentation comment not found for function declaration `init`
It is recommended to have documentation comments above, or right inside a function/class declaration.
This helps developers, users and even the author understand the purpose of a code snippet or API function in the future.
NOTE: If you want to stop this issue from getting raised on certain constructs (arrow functions, class expressions, methods etc.), consider using the skip_doc_coverage option under the analyzers.meta property in your .deepsource.toml file.
For example, the following configuration will silence this issue for class expressions and method definitions:
This file contains hidden or 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
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.
This pull request introduces a significant update to the site's branding, typography, and some UI/UX improvements, along with minor infrastructure and content changes. The most important changes are grouped below by theme.
Branding and Typography Updates:
base.css,brand.html, [1] [2] [3] [4] [5] [6] [7]brand.htmlto visually distinguish "Tech" with lighter font weight, and clarified font usage in the typography section. (brand.html, [1] [2]UI/UX Improvements:
theme.js) rather than being statically present in the HTML, simplifying the markup in bothapply.htmlandbrand.html. (apply.html, [1] [2]apply.htmlfor readability and maintainability, including better indentation, more semantic structure, and updated copy to be more inviting ("Have a project idea?"). (apply.html, [1] [2] [3] [4] [5]Code and Style Quality:
brand.cssfor clarity, maintainability, and consistency, including better codebox and tab styling, and improved code sample highlighting. (brand.css, [1] [2]brand.htmlfor robustness (e.g., using.replaceAll, better error handling, and usingdataset), and made codebox and copy button markup more semantic. (brand.html, [1] [2] [3]Infrastructure:
.github/dependabot.ymlconfiguration to enable weekly npm dependency updates. (.github/dependabot.yml, .github/dependabot.ymlR1-R11)Content and Navigation:
_redirectsfor easier access to hosted projects. (_redirects, _redirectsL5-R13)