The concept above is an answer to the fact that each tile-based 'metaverse' will always turn into some kind of hypercentralized client-project. Instead, a visitor in the aframe-verse just teleports to other destinations and clusters.
When the visitor surfs to a cluster-client (index.html), it basically loads all components, which other linked experiences use.
This is a security-limitation and a performance-feature, because this:

• makes traveling between experiences (within a cluster) very fluid and fast.
• it creates a decentralized incentive between developer(s) to:
  • collaborate on a seamless & secure end-visitor cluster-client (index.html)
  • consistent UX because of:
    • shared components
    • shared global objects: wearables, UI, AR/VR controller-support e.g.

As an exception to the rule, the developer(s) (YOU) of a cluster-client (index.html) can load remote (trusted) components/scripts, which is demonstrated by aframe-verse-component-scripts.

Worstcase, a destination can be loaded in a new tab (newtab:true which exits immersive navigation ), which then basically becomes the new cluster.

In the example, only touch/mouse-events are supported.
By defining hrefEvents, you can trigger navigation for other events too:

<... aframe-verse="register: /yourverse.json; hrefEvents: click, mouseenter, collide, foobar">
   <a-box href="./show.html"/>  
</...>

Profit! Now navigation is triggered to show.html whenever it is clicked, mousehovered or colliding with another object

calling $('[aframe-verse] [href]').emit('foobar', {}) would trigger navigation too

You can control navigation-events by creating a custom component:

// use like: <a-entity aframe-verse="..." navigate></a-entity>

AFRAME.registerComponent('navigate', {
  init: function(){
    console.log("initing navigation")
    this.el.addEventListener('beforeNavigate', (e) => this.beforeNavigate(e) )
    this.el.addEventListener('navigate',       (e) => this.navigate(e) )
    this.el.addEventListener('loadHTML',       (e) => this.loadHTML(e) )
    this.el.addEventListener('registerJSON',   (e) => this.registerJSON(e) )
  }, 
  beforeNavigate(e){
    // let promise = e.detail.promise()   
    console.log("about to navigate to: "+e.detail.destination.url)
    // promise.resolve()
    // promise.reject("not going to happen")
  }, 
  navigate(e){
    // let promise = e.detail.promise()   
    console.log("navigating to: "+e.detail.destination.url)
    // promise.resolve()
    // promise.reject("not going to happen")
  }, 
  loadHTML(e){
    let newdom = e.detail.dom.querySelector("[aframe-verse]")
    // let promise = e.detail.promise()   
		console.log("loading html")
    // promise.resolve()
    // promise.reject("not going to happen")
  },
  registerJSON(e){
    let json = e.detail.json
    /* example: skip non-immersive navigation links */
    // json.destinations = json.destinations.filter( (d) => d.newtab ? null : d )
    /* example: launch external verses in a new tab (so its components get loaded too) */
    // json.destinations.map( (d) => d.url.match(/index\.html$/) ? d.newtab = true : null )
  }
})

This is the place to show a consent popup e.g. (most trusted experiences can do fine without that in the beginning).

For navigation, you can add external verses to the .verses-array in aframe-verse.json, that's all!
Optionally, you can secure the import-behaviour further using the registerJSON-event as shown above in 'Customizing navigation further'.

You can have multiple persisting verses at the same time. Usecases for this are: a menu system, mini-games, inventory or a teleporting-maze e.g.:

<a-entity aframe-verse="register: aframe-verse.json">
  ...
</a-entity>

<a-entity aframe-verse="register: menu.json; fade: 0">   <!-- NOTE: superfast fade in ms (0=off) -->
  ...
</a-entity>

NOTE: for heavy scenes you can set fade: 4000 (4seconds fade) e.g.

• click the fork-button on github or gitlab
• rename the repository to aframe-verse-* (aframe-verse-myorganisation e.g.) for easy discoverability
• github: go to settings-tab > enable github pages (use the main-branch)
• profit! your verse can now be accessed thru
  • github: https://yourusername.github.io/aframe-verse-myorganisation/apps
  • gitlab: https://yourusername.gitlab.io/aframe-verse-myorganisation/apps

• REMIX this glitch
• rename the project to aframe-verse-* (aframe-verse-myorganisation e.g.) for easy discoverability
• your verse can now be accessed thru https://aframe-verse-myorganisation.glitch.me/apps/

• download zip and unpack it in your apache/worpress dir e.g.