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 walks the ring every morning: each member site must respond, reference the webring, and point its widget at its own entry so prev/next actually go somewhere. Sites that render client-side are checked via their JS bundles. Anything broken lands in a single auto-updating issue labelled webring-health, which closes itself once the ring is healthy again. It also opens (never merges) a PR that comments the failing sites out of index.html and closes the issue; review it before merging, since the checker can misread a site. Removed sites stay on the daily walk, and once one passes again a second PR puts it back.

npm run check-webring          # walk 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 :)