Cherry-pick docs commits to docs-v1.7.0 branch#5761
Cherry-pick docs commits to docs-v1.7.0 branch#5761dmarcos merged 13 commits intoaframevr:docs-v1.7.0from
Conversation
…of Slack (aframevr#5690) * Update contributing doc to point to Discord instead of Slack * Remove newsletter and slack, add WebXR Discord to the introduction doc
…-maintained list of components (aframevr#5695)
in the anchored documentation, added function el.components.anchored.createAnchor(position, quaternion) instead of el.components.createAnchor(position, quaternion)
* Update installation.md Python 3 command to `python3` When following the instructions on macOS, after installing the recommended version of Python from python.org, I found that the Python 3 executable is `python3`, not `python`. Some quick internet searching suggests that `python3` is probably the most reliable command to run across multiple OSes. * Update installation.md
fixing a minor typo with the logitech mx ink docs
* Point to aincraft in the repo instead of glitch * Remove not maintained networked-aframe glitch * Link to community-components in the repo instead of aframe-registry glitch * Replace a-watch glitch url by link in the repo * Replace glitch cdn url by aframe cdn for grip-compressed.glb * Remove cdn.glitch.com url in test * Link to 360-gallery in the repo instead of aframe-gallery glitch * Update link to Animated Lights example * Increase light intensity in dynamic-lights example * Remove dead examples in interactions-and-controllers * Add aframe-modify-model-material example in the repo * Remove dead Displacement Shader example
|
This is to address aframevr/aframe-site#556 |
|
Thank you! |
|
Can you please cherry-pick #5762 in the docs-v1.7.0 branch: and I think the doc build is triggered only on master? So we'll need a commit in master to trigger the rebuild of master and 1.7.0 documentation to trigger the commands https://github.com/supermedium/a-frobot/blob/4ce549b2fc83554a2f510590a254d073415d3535/lib/deployAframeSite.js#L26-L40 |
|
I still see glitch section on master doc https://aframe.io/docs/master/introduction/hosting-and-publishing.html I remember you once said you ran the build command manually on the aws instance, but that was before we update all the code to support latest node. I thought you put back the aframe bot to do it automatically since then, that's not the case? |
|
All docs are deployed manually at the moment. no bots |
Description:
Changes proposed: