This follows the documentation writing guidelines, specifically
the "When to refer to a specific Godot version" section.
This also removes warning blocks for a known issue that was resolved in Godot 4.5.
Each page provides a list of all export options for the given platform,
which can be searched through using Ctrl + F. While this information
is also available in the editor by hovering export option names, it can't
be quickly searched through.
- Document no-threads web export and its limitations.
- Document sample-based audio playback and its limitations.
- Mention that threading issues can be worked around by exporting
as a progressive web app.
* Add hint reg. Safari audio autoplay restriction when exporting for the web
* Apply suggestions from code review
* Apply suggestions from code review
* Update tutorials/export/exporting_for_web.rst
Co-authored-by: Matthew <matthewehr@hotmail.com>
---------
Co-authored-by: Hugo Locurcio <hugo.locurcio@hugo.pro>
Co-authored-by: Max Hilbrunner <mhilbrunner@users.noreply.github.com>
Co-authored-by: Matthew <matthewehr@hotmail.com>
This isn't strictly related to compiling custom export templates,
but it's a neat trick to reduce the final distribution size that works
regardless of the export template binary used.
There's a lot of confusion between compiling Godot and exporting projects.
This aims to resolve part of the confusion by cross-linking other pages
for each platform.
* Improve the Exporting for the Web section.
Add "Export Type" options (threads, gdnative, regular).
Add warnings about "secure contexts" limitations.
Mentions threads and GDNative requirements.
Mention WebRTC as a networking API.
General refactor.
* Update compiling for the Web.
Bump emscripten requirements, mention threads, gdnative and editor
build.
Hugo Locurcio