winzik/docs/ide/publish.md
David Nurdin 7de153fc14 IDE documentation: one page per feature (docs/ide/, French in docs/ide/fr/) and a Doc browser inside the IDE
- docs/ide/: 49 user pages grouped in toc.json (editing, languages, run / test / debug, Git, web sites and Symfony, databases,
  Docker and SSH, games, AI, team, settings); pages of features still being built are "coming soon" stubs with a TODO list;
  15 pages translated into French; docs/ide.md and docs/ide.fr.md link to them.
- The Doc button at the top right of the IDE, Help > Documentation, Search Everywhere "Documentation" and a "?" in each tool
  window's header open the Doc browser (ide/ui/js/docs-browser.js): table of contents, rendered pages (pictures, code, tables,
  links between pages and to headings), full-text search, back / forward, the IDE's language with English as the fallback.
- ide/src/Docs/DocsLibrary.php (docs.index, docs.image): reads only the documentation folder (strict names, real path checked);
  the packaged copy ui/docs first, else the repository's docs/ide.
- Packaging: tools/stage-game.sh copies docs/ide into the exported IDE (its *.md exclusion would drop them), overlay-build.php
  puts them in code updates, bin/jumphp ide syncs them.
- Tests: docs-model.test.mjs (TOC, links, anchors, pictures, search; every page and picture of docs/ide exists), DocsLibraryTest
  (path traversal refused), the i18n test covers the new texts in 14 languages.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01JkYTqsvYu6AYr9yQ3Q4Nt6
2026-11-16 00:08:42 +01:00

28 lines
1.3 KiB
Markdown

# Publishing
## Git repository and jumphp.net
A new project lives on your computer only. **Publish** (the upload button of the tool bar) or **Create its Git repository…** makes
the repository on your Git account, commits and pushes everything, and puts the project on jumphp.net.
## The jumphp.net window
`Alt+J` (desktop, a project on jumphp.net):
- **Publish**: push and sync; errors and warnings of the publication.
- The game's settings: title, descriptions in every language, category, listed or not.
- Its numbers and the players' messages.
- Its web site (`bin/jumphp site:new`).
- The executables (Windows, Linux, macOS, Android) built and put on its page; the installer hosted on jumphp.net.
- The phone apps (Android, iPhone / iPad) with the store steps one by one.
## Installers
**Run > Create an Installer…** (also Find Action): choose the systems (Windows, Linux, macOS) and where it goes — jumphp.net, a release
of the project's repository, another web site (`dist/installer/` to upload), or **standalone** (the game inside each installer: no site,
no network). Then the links to give.
## Engine extensions and plugins
**Publish extension** puts an engine extension in its own repository (tagged) for Packagist; an IDE plugin is published from
Tools > Plugins….