Never looked at the tutorial but it’s probably older and likely out of date, with updates to changes and rules/etc. (I think it’s using jQuery from a CDN which wouldn’t be allowed if submitted anyway)
If you have existing website knowledge you can skip the tutorial and go straight to building.
There only “rules”/requirements are present in my hello work example.
You must include the JS helper
You must call onAuthorised
onAuthorised is essentially “window has finished loading, everything is loaded and ready to go”
Yeah the rig will load from whereever.
But to test on Twitch when your state is “localtest” you’ll need a SSL Cert or suffer the “fun” of mixed content warnings (similar for self signed certs).
Some people use NGROK, some people reverse SSH proxies, others just upload their code to a web host (I have a test/debug extension that loads from GitHub pages for example).
XAMPP should throw a server up on http://127.0.0.1/ or whatever it’s configured to.
That will load in the rig.
But your HTML code will need to have the JS Helper and a call on onAuthoirsed via script file
The Extension docs are a bit here/there all over the place.
These days I’m only ever on the reference. And a lot of the time some of my extensions literally just load the token from onAuthorised and thats it (they punt that offsite to my EBS and the EBS does whatever)
These two cover the basics of most of the things/blockers
Depending on what you extension does/will do you might not need anything from Twitch Extension side of things beyond what I posted as the exmaple extension above. Then everything else is “make it work in the dimensions of the slot I’m working in” and handling any traffic to your EBS (Extension Backend Service)