Skip to content

Footer cleanup and piece-level contact links - #7

Merged
simoncos merged 1 commit into
masterfrom
cursor/footer-contact-piece-foot-8f50
Oct 16, 2026
Merged

simoncos merged 1 commit into
masterfrom
cursor/footer-contact-piece-foot-8f50

Conversation

@simoncos

Copy link
Copy Markdown
Owner

Summary

  1. Shell footer — Pages that already include the site header no longer show the redundant «← Back to simoncos.github.io» link. The shared footer keeps copyright, updated date, and RSS links. A footer_back page flag remains in render_footer_block if a future page needs the back link without the standard header.

  2. Piece contact foot — After article and work content, a shared render_piece_contact_foot() block (in scripts/piece_contact_foot.py) adds RSS plus follow links from data/site.json about.contacts and about.email, in the spirit of godobject’s post footer without copying its styling.

Where it applies

  • All blog posts via build_post_foot in article_render.py
  • Work pieces: Zhihu 2015 research, Endless Echoes, 晴天 (qingtian.html)
  • Styles: src/css/sections/piece-contact.css (bundled into styles.css)

Not in scope

  • About page Chinese bio copy (unchanged)
  • Hand-authored work pages without the shared shell (sleep study, interactive essays in gallery/sharing/, etc.) — still have their own back links where they had them before

Verification

  • make generate
  • make check-all
Open in Web Open in Cursor 

Shell pages with the site header no longer show «Back to simoncos.github.io».
Articles and shell-backed work pages get a shared piece-contact footer with
RSS and follow links from about.contacts and email.

Co-authored-by: Che ZHAO <simonzhao1024@gmail.com>
@simoncos
simoncos marked this pull request as ready for review October 16, 2026 10:07
@simoncos
simoncos merged commit 88f7738 into master Oct 16, 2026
2 checks passed
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