WORK IN PROGRESS -- Not yet ready for sharing!
Implements web components under the 'disco-party' project name.
These components are intended to add a sense of translucency and presence to static webpages.
Right now there is:
- disco-room -- links internal to the site are badged with how many people are connected at the other end, and when another user follows a hypoerlink then it bounces for everyone else.
- disco-cursors -- shows other people's cursors on the page, as if behind frosted glass.
This component was created during Matt's summer 2023 residency. The purpose is to experiment with multiplayer interactions, and simultaneously see what PartyKit can do. It's called a sketch because it's lightweight and quick, and because we learn something in making it.
Build the components with npm run build and then copy the dist directory to your webroot.
Then, in the <head> of every page you want to use the components, add:
<script
type="module"
src="/path-to-your-disco-party-dist/disco-party.esm.js"
></script>Add the following to the <head> of every page you want to use the components:
<script type="module" src="https://unpkg.com/[email protected]"></script>The PartyKit server is your backend.
In the root of this repo, run:
npx partykit devThat will give you a host of 127.0.0.1:1999 (you'll need this later).
Or you can deploy the server publicly. Run:
npx partykit deployAnd your host will be something like disco-party.USERNAME.partykit.dev.
In your site template, wrap the content that you want to be part of the disco-room in a <disco-room> tag.
<disco-cursors host="127.0.0.1:1999"></disco-cursors>
<disco-room host="127.0.0.1:1999">
<h1>My disco room</h1>
<p>Some content</p>
<a href="/some-link">A link</a>
</disco-room>(You may need to put in empty tags to stop pre-processors collapsing them.)
Optionally: to include only some of the content inside the disco-room, wrap sections in <disco-include> tags. If you don't do this, then the entire disco-room will be included.
- Add documentation
- Add disco-presence to show how many people are on the page (this is hardcoded at the moment)
- Fix logic of where cursors appear given page scroll (given responsiveness they will never match up exactly)
- Add real-time shared text selection
- In page.tsx, debounce connection change updates (these can change frequently and shouldn't be sent more than once every 500ms, but must send eventually)
- In the partyserver, account for changes in a page's list of subscribed URLs (these can change up to daily)
- Add debug views to page and counter to validate data