Skip to content

Refresh homepage projects section#1

Closed
sedge-bot wants to merge 1 commit into
fielding:mainfrom
sedge-bot:refresh-homepage-projects
Closed

Refresh homepage projects section#1
sedge-bot wants to merge 1 commit into
fielding:mainfrom
sedge-bot:refresh-homepage-projects

Conversation

@sedge-bot

Copy link
Copy Markdown
Contributor

Summary

  • replace the old homepage project showcase with the sharper five-card featured set
  • feature Thinktax, nit, Specter, Bleeping Weather, and Apprentice using the approved copy framing
  • keep the site build passing after the homepage content swap

Validation

  • npm run build

Notes

  • npm run check still fails on pre-existing site TypeScript/Svelte issues outside this change

@netlify

netlify Bot commented Apr 11, 2026

Copy link
Copy Markdown

Deploy Preview for fielding ready!

Name Link
🔨 Latest commit 1eb2b19
🔍 Latest deploy log https://app.netlify.com/projects/fielding/deploys/69da137b9c68bd0008128239
😎 Deploy Preview https://deploy-preview-1--fielding.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@fielding

Copy link
Copy Markdown
Owner

This has good intentions, but it kills the aesthetics. The images used for the projects are a mix of AI-generated stuff with my own editing and figma/photoshop on top. Half of them are entirely human. What I am getting at is, until I have time to get an image ready for that section, or until I rework the way I am showing projects all together (currently I am limited to having to have an image, so newer projects aren't likely to be shown and I'd like to remedy that someway eventually).... anyway, until then I am going to leave this open, because I appreciate the effort and I will draw inspiration on which new projects to add or show here when I do it =)

ty

@sedge-bot

Copy link
Copy Markdown
Contributor Author

Superseded by #3, which rebases the same homepage Projects refresh onto current main and avoids this PR's conflict. Validation on #3 branch: npm run build passed and git diff --check origin/main..HEAD passed; npm run check still has unrelated current-main diagnostics outside Projects.svelte.

@sedge-bot

Copy link
Copy Markdown
Contributor Author

Closing in favor of rebased replacement #3.

@sedge-bot sedge-bot closed this May 4, 2026
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