Skip to content

docs: document Studio frontend build step for source installs#72

Merged
miguelgfierro merged 2 commits into
mainfrom
docs/studio-source-build
Apr 27, 2026
Merged

docs: document Studio frontend build step for source installs#72
miguelgfierro merged 2 commits into
mainfrom
docs/studio-source-build

Conversation

@javier-alvarez
Copy link
Copy Markdown
Contributor

@javier-alvarez javier-alvarez commented Apr 27, 2026

Summary

  • A fresh git clone doesn't ship the pre-built Studio SPA, so firefly studio returns {"detail":"Not Found"} on every page until the frontend is built.
  • scripts/build_studio.py already automates the build (it's wired into the desktop and release CI workflows), but no contributor-facing doc pointed at it — source users had to figure this out themselves.
  • This PR documents the requirement in CONTRIBUTING.md and adds a callout + updated dev section in docs/studio.md.

Changes

  • CONTRIBUTING.md — add Node.js 20+ to prerequisites and a new "Building the Studio Frontend (source installs only)" subsection pointing at uv run python scripts/build_studio.py.
  • docs/studio.md — scope the "pre-built and bundled… no Node.js required" claim to the published wheel, add a source-checkout callout under Installation, and promote the helper script as the recommended path in the Frontend Development section (manual npm steps kept as the equivalent fallback).

No code or behavior changes; docs only.

Test plan

  • CONTRIBUTING.md renders cleanly on GitHub
  • docs/studio.md renders cleanly and the in-page anchor #frontend-development still resolves
  • On a fresh clone: uv sync --all-extras && uv run python scripts/build_studio.py && firefly studio serves the UI (no {"detail":"Not Found"})

🤖 Generated with Claude Code

Javier Alvarez-Valle and others added 2 commits April 27, 2026 14:50
A fresh `git clone` does not include the pre-built Studio SPA, so running
`firefly studio` from source returns `{"detail":"Not Found"}` until the
frontend is built. The `scripts/build_studio.py` helper already exists
(used by the desktop and release CI workflows) but was not referenced
from CONTRIBUTING.md or docs/studio.md, leaving source users to discover
the requirement by hand.

- CONTRIBUTING.md: add Node.js 20+ to prerequisites and a "Building the
  Studio Frontend" subsection pointing at scripts/build_studio.py.
- docs/studio.md: scope the "pre-built and bundled" claim to the published
  wheel, add a callout for source checkouts, and promote the helper
  script in the Frontend Development section.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The helper script is the recommended path; listing the equivalent npm
commands underneath duplicates what the script already does. Keep the
docs minimal.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@miguelgfierro miguelgfierro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@miguelgfierro miguelgfierro merged commit 5c96318 into main Apr 27, 2026
7 checks passed
@miguelgfierro miguelgfierro deleted the docs/studio-source-build branch April 27, 2026 16:35
ancongui pushed a commit that referenced this pull request May 31, 2026
docs: document Studio frontend build step for source installs
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