Currently, if the main branch is updated, it'll generate a new WASM and publish to github pages. Which can be unnecessary, because some changes are not related to 3D model or internal logic.

Although PR #10 closed issue #4, the camera position was hardcoded. The camera spawn position needs to be configurable.
The camera should be "adjustable" to some extent, because new 3D models can be loaded into the software and the camera position should be able to show it all.

Proposal:

• Add cartesian (x, y, z) or spherical (ρ, θ, φ) coordinates
• Add camera projection direction hint, such as coordinate origin or geometrical center of model

These configurations should be avaible through graphical interface.

There's a nice project that keeps growing and got my attention for physics simulation: https://github.com/Jondolf/avian. I think worth checking the feasibility of swapping to this new project.

The new Bevy 0.14 release contains a grid, which can be used to replace bevy_infinite_grid. This will remove one chained dependency, because bevy_infinite_grid depends on Bevy as well.
Ref.: https://bevyengine.org/news/bevy-0-14/#more-gizmos

When a previous CI build is not successful, the internal cache somehow keeps breaking the pipeline.

Create a configuration file manager, which can be useful not only for the application (assignment of port, keybindings and etc.) but also for the 3D model (if .glb model can't provide such "physical" informations, such as mass, length, inertial moment and etc.).

The model is currently being designed on Blender and there's a lot of physics features for simulation.
The constraints such as translation and rotation of bodies such be reflected exactly the same in Bevy.

Use protobuf to define message and make it available for controller to communicate with it.
Candidate crate: https://github.com/tokio-rs/prost

Move all 3D models to a new git repository and add it here as git submodule.

There's a minor change set that should be performed to bump to Bevy 0.12, but we rely upon smol-rs/async-executor#72 for delivery

Currently the project is only releasing a WASM of the application, but it should also contain the documentation generated.
Ideally we would have a homepage with a explanation of the project and a link to the documentation and another for the application.

Add camera reset, so the model can be seen again. Accidently, sometimes the model goes away.

Describe how user input can be used to control the software.