1. Add the webring widget to your website HTML (template below). Generally, you should add it to the footer.
2. Clone this repo, branch, and add your information to the BOTTOM of webringData[] in index.html following this format:

   {
     "name": "Your Name",
     "website": "https://your-website.com",
     "year": "20XX"
   }

3. Submit a Pull Request! We'll try to review as fast as we can.

Since every website is unique, we suggest you add your own flair to the UTD emblem. We also know that design is hard, so here are some examples to get you started:

<div style="display: flex; align-items: center; gap: 8px;">
    <a href="https://ecs.utdring.com/#your-site-here?nav=prev">←</a>
    <a href="https://ecs.utdring.com/#your-site-here" target="">
        <img src="https://ecs.utdring.com/icon.black.svg" alt="ECS Webring" style="width: 24px; height: auto; opacity: 0.8;"/>
    </a>
    <a href="https://ecs.utdring.com/#your-site-here?nav=next">→</a>
</div>
<!-- Replace 'your-site-here' with your actual site URL -->

<div style={{ display: 'flex', alignItems: 'center', gap: '8px' }}>
    <a href='https://ecs.utdring.com/#your-site-here?nav=prev'>←</a>
    <a href='https://ecs.utdring.com/#your-site-here' target=''>
        <img
            src='https://ecs.utdring.com/icon.black.svg'
            alt='ECS Webring'
            style={{ width: '24px', height: 'auto', opacity: 0.8 }}
        />
    </a>
    <a href='https://ecs.utdring.com/#your-site-here?nav=next'>→</a>
</div>
// Replace 'your-site-here' with your actual site URL

For dark-themed websites, use icon.white.svg. Feel free to host the icon locally if you encounter HTTPS issues / styling issues.

• Black: https://ecs.utdring.com/icon.black.svg
• White: https://ecs.utdring.com/icon.white.svg
• Red: https://ecs.utdring.com/icon.red.svg

If none of these quite work for you, feel free to make your own. If you're using React, start with icon.custom.tsx.

A GitHub Action checks the ring each morning: every member site is reachable, the webring widget is in the page, the widget's #site fragment resolves to that member's own entry (so prev/next actually go somewhere), and the prev/next links don't open in a new tab — a ring is meant to be travelled in one. Findings land in an auto-updating issue labelled webring-health, which closes itself once the ring is healthy again.

If the widget isn't in the served HTML, the check reads the site's own JS bundles before saying anything, so React and other client-rendered sites are still verified. When it genuinely can't tell, it says so and asks a human to glance at it instead of failing.

It's advisory, not a gate. Opening a PR runs the same check against just the site the PR adds, annotates the diff inline, and never blocks the merge. Slow, rate-limited and CI-blocked sites are warnings, and warnings never fail anything — only a site that truly didn't respond or a widget whose links don't work does.

npm run check-webring          # check every site
npm test                       # test the checker (offline, stubbed fetch)

No :)

In all realness, this is the only existing webring at UT Dallas as far as I'm aware. They aren't too complex to make & can be a great way to connect with bright minds, so consider creating your own!

Yep, as long as you studied Computer Science or are currently studying it

👍

This project is (obviously) forked from the UWaterloo CS webring, so credit goes to them for creating such a well polished site!

I (Ryan) currently maintain the site, so if you see any bugs please let me know by making an issue. I'll try to respond as fast as I can :)