Transition guide

Moving between SSTIM Workbench sites

SSTIM Workbench is currently published at two addresses, built from the same source. Your work is stored in your browser, and browsers keep storage separate per address. So each site holds its own copy of everything, and nothing moves between them on its own. Carrying it across takes two clicks and a file.

The two addresses

labiosyncare.github.io
The original site, and where the persistent w3id.org identifiers still resolve today.
w3c-cg.github.io/sstim
The Community Group site, published from the same source and the long-term home.

Both stay reachable. Nothing is being switched off, and you do not have to move today.

Carry your data across

On the site that has your work, open Settings, find Data & privacy, and choose Export browser data. The file is assembled locally in your browser and downloaded; nothing is uploaded anywhere.
Open the other site and go to its Settings, same section.
Choose Restore from file, pick the file you just downloaded, review what it says it will do, and confirm. Reload afterwards so open screens pick up the restored data.

Do this in one direction only, and treat the site you exported from as the copy of record until you are satisfied. Restoring an old export over newer work would replace it.

What travels, and what does not

Travels

Logbook entries
Local annotations
Saved Patch Studio patches
Your profile
Appearance preference

Does not travel

Sign-in identity. Entries are exported by scope and re-keyed to whoever imports them, so if you sign in before restoring, account entries land in that account; if you do not, they arrive as anonymous entries.
The installed app, for the reason below.

If your appearance preference does not come across, set it again in Settings. Everything else is carried in the file and verified by a checksum before it is applied.

If you installed the app

An installed web app belongs to the address it was installed from. That installation is state held by your browser and operating system, and there is no web API that can read, move or recreate it, so no export could include it however much we wanted it to.

Install again from the other site, then carry your data across with the steps above. The data does travel; the installation does not. You can keep both installed if you like, but they will not share anything.