Skip to content
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

Convert to Bridgetown #93

Merged
merged 2 commits into from
Jan 29, 2025
Merged

Convert to Bridgetown #93

merged 2 commits into from
Jan 29, 2025

Conversation

moonglum
Copy link
Member

@moonglum moonglum commented Jan 26, 2025

I could not get the setup to work, so I instead copied the setup from my homepage. This also updates some parts of the content (mainly legal stuff) and cleans up the CSS (also went from SCSS to CSS) and JS. Also uses Bridgetown Components.

@moonglum moonglum force-pushed the bridgetown branch 6 times, most recently from 52f3f79 to 9a25dfb Compare January 26, 2025 21:25
@@ -0,0 +1,109 @@
---
layout: default
title: "Impressum"
Copy link
Member Author

Choose a reason for hiding this comment

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

New file, this is a copy from my homepage

@moonglum
Copy link
Member Author

@FND This is the switch to bridgetown I did over the winter break (first commit). The second commit is what we discussed today. Feedback welcome!

Copy link
Contributor

@FND FND left a comment

Choose a reason for hiding this comment

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

Looks good to me - I think? It's a bit much to review 😅 , but I understand why that's inevitable.

I'm a bit wary of Ruby increasing the maintenance burden (techno mix and barrier to entry), but that's mostly a theoretical concern at this point: Your optimization here is perfectly understandable.

Anyway, thanks for doing this!

I could not get the setup to work

Not quite sure what this means or implies...


&:focus {
.skip:focus {
Copy link
Contributor

Choose a reason for hiding this comment

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

If you're using PostCSS and esbuild anyway, why not have either convert nested CSS during deployment?

Copy link
Member Author

Choose a reason for hiding this comment

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

Good point, I will take a look

Copy link
Member Author

Choose a reason for hiding this comment

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

Noted as #94

@moonglum
Copy link
Member Author

I could not get the setup to work

That I invested an hour to get our old setup to work, but after everything exploded in my face multiple times, I gave up, copied my homepage, replaced the content and CSS, and was ready to go 😂

I could not get the setup to work, so I instead copied the setup from my
homepage. This also updates some parts of the content (mainly legal
stuff) and cleans up the CSS and JS.
@moonglum moonglum merged commit 91c70d7 into main Jan 29, 2025
1 check passed
@moonglum moonglum deleted the bridgetown branch January 29, 2025 07:32
@moonglum
Copy link
Member Author

Merged and deployed ✔️

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