TUTORIAL: SPLASH PAGE PT 2
Aug. 21st, 2026 12:08 amSplash patterns - advanced
This post is for when Standard Issue or Lock Set is not enough. New readers start at Splash patterns - start here, then Splash patterns - flow. Come here for Safety Lock, Cover Plate, and Front Panel.
Splash patterns - flow covers the two starter shells plus wrapper unlocking. If the theme and sticky are not set yet, that click-path is in the hub, not here.
Quick start
- Pick Safety Lock, Cover Plate, or Front Panel below.
- Copy the HTML block into a future-dated sticky entry (HTML mode, Disable auto-formatting on).
- Copy the matching CSS block into Customize > Custom CSS > Use embedded CSS.
- Test on your live journal, including mobile scroll and control strip overlap.
Overlay live checks
- Comments are not reachable by scrolling the front page. That is expected on Cover Plate and Front Panel.
- The page behind the cover should not scroll. If it does, the body lock is not applied.
- Test on a phone. Fixed layers behave differently there.
Why not the old sticky fallback?
Current Safari, Chrome, Firefox, and Edge all support :has(). The older no-:has() sticky fallback hides every Recent entry, then tries to reopen whatever looks sticky. It cannot see the splash root, so it can hide the wrong entry, stay locked after you unstick the splash, and misfire if you have more than one sticky. If a very old browser is a hard requirement, that is a compatibility test, not a first splash. These posts do not give it as a sixth copy-paste shell.
The five public patterns can see the splash. The old fallback cannot.
Patterns in this post
| Pattern | Class prefix | Best for |
|---|---|---|
| Safety Lock | .fs-hyb-* |
Locked front page with the least fragile selector structure |
| Cover Plate | .fs-fix-* |
Fixed full-screen overlay when wrapper unlock is not enough |
| Front Panel | .fs-ent-* |
Self-contained overlay with minimal wrapper dependency |