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

Birthday redesign #438

Closed
simonw opened this issue Jun 12, 2024 · 5 comments
Closed

Birthday redesign #438

simonw opened this issue Jun 12, 2024 · 5 comments

Comments

@simonw
Copy link
Owner

simonw commented Jun 12, 2024

Blog is 22 years old today!

The sidebar is no longer working now that I write longer blogmark entries (inspired by https://daringfireball.net/ ):

CleanShot 2024-06-12 at 12 36 33@2x

New design for homepage: mixed content on the left, links to long-form blog entries on the right.

@simonw
Copy link
Owner Author

simonw commented Jun 12, 2024

Got this working locally:

CleanShot 2024-06-12 at 12 37 06@2x

I'm going to ship it and see how it feels.

simonw added a commit that referenced this issue Jun 12, 2024
@simonw
Copy link
Owner Author

simonw commented Jun 12, 2024

Deployed: https://simonwillison.net/

CleanShot 2024-06-12 at 12 41 33@2x

@simonw
Copy link
Owner Author

simonw commented Jun 12, 2024

Blogged about this here: https://simonwillison.net/2024/Jun/12/homepage-redesign/

@simonw simonw closed this as completed Jun 12, 2024
@lambrospetrou
Copy link

There is a typo in The right hand column on my homepage now displays entries, quotations and blogmarks as a combined list, it should be The LEFT hand column :)

Love your website content!!!

@Marat-Tanalin
Copy link

Consider improving semantics by making the first-level heading on the page of each article the true first-level heading — h1 — instead of the logo wrongly being semantic h1 on each page instead of only being h1 on the home page, and the first-level heading wrongly marked-up as second-level heading h2. ;-) The logo can only sematically be h1 on homepage. On other pages, it should not even be a heading, strong is enough to make it somewhat special semantically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants