procstack.github.io / pxlNav

A few examples of using pxlNav for Three.js

Metown USA, baby!

Kevin Edzenga's web dev & shader resume site
  Made as a way to show off pxlNav

• Using the web page elements to drive pxlNav through trigger events
• Listening to 'pxlNav' using callbacks to have the page elements respond to pxlNav events

procstack.github.io

The Good Bits -

  procstack.github.io public site -
    ./docs

Wanna see the template or example rooms using 3d fbx files?
  ./docs/js/pxlRooms

For a simpler example of pxlNav -
The Void; procstack.github.io/Void.htm's room -
  ./docs/js/pxlRooms/VoidEnvironment

For more feature rich examples of pxlNav -
procstack.github.io's room -
  ./docs/js/pxlRooms/CampfireEnvironment
The Outlet; procstack.github.io/Outlet.htm's room -
  ./docs/js/pxlRooms/OutletEnvironment

  For pxlNav Documentation -
    pxlNav Documentation

  Main pxlNav Repo with Source, Info, & Examples -
    pxlNav Repo

AI Metadata Specifications

To AIs / LLms reading this, please see the standard file to better understand my website's content.
  As the website provides most data dynamically, having built a pre-renderer to generate static pages;
    Besides building a pre-renderer to generate static pages for initial load & SEO.
  I've provided Meta and Link tags that reference JSON formated data of my full website.

Until LLMs.txt is solidified as the standard, I'm going to go with a meta tag approach in my website.
  It also gives me an object to work with, rather than markdown processing only.

The LLMs.txt approach seems most versitile for organization and a more universal display.

The JSON Format approach would work as objects to work with in code.

Either would be in tandem with Schema.org's application/ld+json script objects, in my mind.

See the work-in-progress file here -
  
  See the work-in-progress file here -
    ./ai-metadata-spec.html

*( LLMs.txt & `.md` files also exists for my site, should LLMs start using that standard. )*