Add basic print mode styles for resume format #3
No reviewers
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
javascript
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
thayen/thayen-dev!3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/print-mode-5503257500816862231"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds a dedicated print mode that strips away the parchment theme and styles the page like a clean, professional resume when printed or saved as a PDF. Links automatically display their URLs and keyword interactions are flattened for static reading.
PR created automatically by Jules for task 5503257500816862231 started by @N0tAI
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.
When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.
I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!
For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with
@jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!New to Jules? Learn more at jules.google/docs.
For security, I will only act on instructions from the user who triggered this task.
Code Review
This pull request introduces a dedicated print stylesheet,
src/styles/print.css, and integrates it into the site layout to optimize the page for printing. The new styles adjust colors for readability, hide interactive components like popups, and ensure that link URLs are visible on the printed page. Review feedback suggests removing redundant!importantdeclarations in the CSS to better leverage standard specificity and improve code maintainability.@ -0,0 +60,4 @@.keyword-display {color: #000000 !important;font-weight: bold !important;The
!importantdeclaration onfont-weightis redundant. The base style for.keyword-displayalready setsfont-weight: bold. While!importantis needed for thecolorproperty to override more specific:hoverstyles, it is not needed forfont-weightas it is not being changed in other states. Removing the unnecessary!importantimproves code clarity.@ -0,0 +78,4 @@}address a[href]::after {content: " - " attr(href) !important;The
!importantdeclaration on thecontentproperty is not necessary. The selectoraddress a[href]is more specific than the generala[href]selector defined on line 43, so this rule will take precedence naturally. The general rule does not use!importanteither. It's a good practice to rely on CSS specificity and avoid!importantwhere possible to make styles easier to manage.View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.