Skip to content

Opt "About Me" into typography styles piecemeal #49

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

Merged
merged 4 commits into from
Apr 1, 2025

Conversation

john-kurkowski
Copy link
Owner

@john-kurkowski john-kurkowski commented Mar 27, 2025

Previously, with global styles, the custom "Experience" section of the "About Me" page was riddled with inconsistencies with the upstream resume, in presentation and code. Applying typography styles piecemeal allows the "About Me" page to better stay in sync.

Changes

  • Remove global paragraph style
  • Remove global style undo hack
  • Extract custom "Experience" section from Markdown to own component
  • Sync from upstream resume
  • Wrap Markdown content that should have the old styles in <div class="post">

* Remove global paragraph style
* Remove global style undo hack
* Sync from upstream resume
* Wrap Markdown content that should have the old styles in `<div
  class="post">`

Previously, with global styles, the custom "Experience" section of the
"About Me" page was riddled with inconsistencies with the upstream
resume, in presentation and code. Applying typography styles piecemeal
allows the "About Me" page to better stay in sync.
@@ -6,6 +6,8 @@ title: 'About Me'
import Experience from '../components/resume/experience.astro'
import Time from '../components/resume/time.astro'

<div class="post">
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scattering these <div>s is clumsy though. I wonder if that's the trade-off to accept, or if there's a better way.

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is an eject button, to override whenever Markdown encounters standard tags like p with a custom component. See this example with Tailwind classes in Astro.

It'd be a lot at the moment to port the global typography styles to that new way of doing things. So I'll stick with this line's CSS cascade for now.

@lost-pixel-signals
Copy link

Shot Type Count Status
Added 0 🟡
Deleted 0
Regression 0

Highlights this chunk of the "About Me" page as different. Removes the
need to escape the content as not Markdown, i.e. surround in curly braces.
@lost-pixel-signals
Copy link

Shot Type Count Status
Added 0 🟡
Deleted 0
Regression 2

❗ page/about__[w1280px]:

Before After

❗ page/about__[w414px]:

Before After

"Astro is not like JSX." This Prettier-style wrapping generated
unwanted additional link underline.
@lost-pixel-signals
Copy link

Shot Type Count Status
Added 0 🟡
Deleted 0
Regression 0

@john-kurkowski john-kurkowski merged commit 6a87b4c into master Apr 1, 2025
9 checks passed
@john-kurkowski john-kurkowski deleted the opt-about-into-post-styles branch April 1, 2025 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants