Thinkmill / Thinkmill/keystatic

Astro-keystatic editor not responsive, viewport missing from head.

Open
#760 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2.4k
Forks
159
Avg merge
21h 41m
Merged PRs (30d)
2

Description

The content pages editor is not responsive, this is because there is no meta data for viewport in the head. As far as I can see, there are only styles in the head. I can manually add a viewport, title and favicon via chrome developer tools.

I really really tried to track this down, but as I say I don't know enough. I hate to file a bug report without having at least some idea of a possible solution. The bug does not appear in the next JS version, which is fully responsive; it only seems to appear in the Astro version. I've tried assembling from source code in case it was a dependency problem and I've added Keystatic to an existing Astro project, with the same bug.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the missing viewport metadata in the Astro version of the content pages editor and inspect how its document head is assembled; the issue reports that the head currently contains only styles. Compare the Astro behavior with the responsive Next.js version, and consider the issue complete when the Astro editor includes the needed viewport metadata and is responsive without manual browser edits.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.