skypress/src/styles/ at f66ea2e20195ec5d15d5e2d41a8bf2e3406cd114 · jeremy.herve.bzh/skypress · Tangled

jeremy.herve.bzh / skypress

0

A calm place to write long-form, and publish it to the open social web. skypress.blog/

0

skypress / src / styles /

at f66ea2e20195ec5d15d5e2d41a8bf2e3406cd114 7 files

Jeremy Herve Give the record JSON modal a fixed dark theme (theme-independent contrast) 16d ago

Give the record JSON modal a fixed dark theme (theme-independent contrast)

2 weeks ago

editor-chrome.css

Fix publish pill losing its styling to a premature CSS comment close A `*/` inside the comment above `.studio__published` (in `--sun*/--ink`) closed the comment early, so the trailing prose plus the selector collapsed into one invalid rule that every CSS parser discards. The publish notice rendered as an unstyled full-width paragraph instead of the centred sunrise pill. Reword the comment to drop the literal `*/`. Add a PostCSS-based regression test that asserts the rule survives parsing.

2 weeks ago

editor-chrome.test.ts

Fix publish pill losing its styling to a premature CSS comment close A `*/` inside the comment above `.studio__published` (in `--sun*/--ink`) closed the comment early, so the trailing prose plus the selector collapsed into one invalid rule that every CSS parser discards. The publish notice rendered as an unstyled full-width paragraph instead of the centred sunrise pill. Reword the comment to drop the literal `*/`. Add a PostCSS-based regression test that asserts the rule survives parsing.

2 weeks ago

Add sky-phase theme picker to the publication form

2 weeks ago

Share sign-in form styles between dashboard and editor The signed-out LoginForm renders on both /editor and /dashboard, but its `login__*` rules lived only in editor-chrome.css (imported by editor.astro). The dashboard never imported them, so the same form appeared unstyled there. Extract the form rules into a shared src/styles/login.css and import it from both pages, so the sign-in form looks identical wherever a signed-out visitor lands. The editor-specific `.studio__login`/`.studio__error` rules stay in editor-chrome.css.

2 weeks ago

post-actions.css

Add like/repost/quote/reply actions to reader article pages Readers can now react to a published article from the bottom of the post. Each action writes a native app.bsky.feed.* record to the reader's own PDS, targeting the article's companion Bluesky post (bskyPostRef) so the reply threads under it and the like/repost show on Bluesky: - like -> app.bsky.feed.like - repost -> app.bsky.feed.repost - reply -> app.bsky.feed.post with reply.{root,parent} = companion post - quote -> app.bsky.feed.post embedding the companion post Replies are app.bsky.feed.post (not a site.standard.* record) because only app.bsky.* records thread/federate on Bluesky; that caps replies at 300 graphemes, so a plain composer with an Intl.Segmenter counter replaces the block editor for replies (Decision 0015). A client:only PostActions island reuses the existing OAuth AuthProvider to sign readers in; the read path still imports no @wordpress/*. No new OAuth scope (transition:generic already covers app.bsky.feed.* writes). Actions are disclosed as public Bluesky actions. The bar is omitted for legacy documents without a bskyPostRef.

2 weeks ago

record-json.css

Give the record JSON modal a fixed dark theme (theme-independent contrast)

2 weeks ago