aframevr / aframevr/aframe

Export all glitches before 8th July

Open
#5,737 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
17.6k
Forks
4.4k
PR merge metrics
No merged PRs in 30d

Description

List of glitches used in documentation

hello world template:

  • https://glitch.com/~aframe in README.md docs/introduction/hosting-and-publishing.md (removed in #5762) docs/introduction/index.md CONTRIBUTING.md and in src/_data/examples.yml aframe-site -> replace with https://krabbel.dev

aframe-registry and aincraft, the examples were already ported in the repo, need to fix those links:

naf:

animated lights:

interactions-and-controllers:

systems:

animation:

material:

modify-model-material:

geometry:

sky:

misc:

All those can be exported in a single repo aframevr/glitch-examples for example and we can update the urls in the doc to use:
https://stackblitz.com/github/aframevr/glitch-examples/tree/main/ex-2c-animating-shapes

@dmarcos what are the glitches you have access to so you can easily click on the Download button in the dashboard?
Otherwise we need to download each file one by one.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the unchecked Glitch links in the listed files under docs/, especially docs/components/, docs/introduction/, docs/core/, and docs/primitives/. Start by determining which exported examples are available, then follow the proposed aframevr/glitch-examples repository and StackBlitz URL pattern. Done means the remaining documentation links and referenced example entries use the replacement locations, with the listed test and example URL changes accounted for.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.