Homepage | WebRing Code | Site Design | Quakers on the Web
We're working to develop some consistency in the presentation of graphics and links from one page to the next around the ring, but we don't expect to see it for awhile. As long as the links work, and they're on the main page of a site, that's all we ask for now.
There are two considerations in placing the code for the Quaker WebRing links -- where to put it, and what code to use.
Most simply, the code goes in the HTML document, determining where the package of links and graphics should come up.
The package should appear:
- On the main page of a site.
- Usually toward or at the bottom of the page.
Further considerations on location:
The basic concept of a web-ring is that people touring the ring can go "around" the ring, moving from one site to the next. So, not only is the ring in place in order to guide visitors to a specific site (i.e, to your site, if it's on the ring), but also it is intended to take them to the next site around the ring. Some site owners forget this part.
- Obviously, the links need to come up, and they need to work. This requires working code (see below for that).
- The WebRing links should be easily found and cannot be mixed among other web-rings and web links, graphics, and gadgetry.
- Someone exploring a site on the ring should be able easily to find his or her way back to the main page, in order to move on from there to the next site around the ring.
- The next site around the ring must replace the previous site, in the same window (not a new window).
- In a site using frames, the next site around the ring must replace all of the previous site, and not appear in part of the frame.
In a site using frames, the links package should appear on the main page that comes up when someone first reaches the site, and not in the menu part of the frame. There may be reasons to make an exception, but this must be worked out with the manager of the ring.
Also, as was mentioned elsewhere, the main page should present the site as "Quaker." In other words, a visitor arriving at the main page of a site on the ring should be able to discern why this site is on the Quaker WebRing. If the answer isn't clear, then the question becomes why is this site on the ring. Again, this may need to be worked out in the process of joining the ring.
What code to put
The ring includes sites that use logo-and-links set-ups developed in the early days of the Quaker WebRing, with other sites that follow code specifications suggested 2-3 years ago, and with sites that have the code automatically generated for their page by the web-ring software.
Every site must have a set of links including
- A link to the "Next" site on the ring,
- A link to the "Previous" site, and
- A link to the hub of the ring.
Also, a "Random" link is nice, but not required, and a "Next 10" link gives someone touring the ring a way to leap-frog over one or more sites that may not be coming up as the "Next" site or that don't show a link to the site "Next" after them around the ring, for some reason.
How you get these links depends on the approach you take, HTML or SSNB.
- HTML - HTML coding is recommended, for those who can tailor the links for their sites.
Looking at the URLs in any set of webring logo-and-links on this page, you may notice the string "ring=quakers&id=16." The ring is "quakers" and
the ID for this particular site (Quaker WebRing Homepage) is "16." Each site on the ring has its own ID number. With that information, it's simple to construct a working set of links.
Note the string in each of the links, "ring=quakers&id=NN." NN is the Site "id" number, which varies from site to site and is used to determine sequence around the ring.
The result looks like this:
You also have to save a copy of the logo "qwr.gif" from this page onto your own computer, use that copy for your page, and upload it to the server alongside your page on the web.
HTML - a narrower variation
In recent years, many sites on the ring have added navigational columns and have wanted to put a narrower HTML version of the logo-and-links there. The following is offered as one example:
The result looks like this:
As before, note that for most of the links, "ring=quakers&id=NN," where NN is the Site "id" number, which varies from site to site.
If the main page of a website is very long (more than 3 or 4 screens down to the bottom), it is expected that the wider version of the logo-and-links package (HTML or SSNB) will be included near the bottom of the page, in addition to the narrower one in the navigational column. [See the Quaker WebRing blog for an example and for further discussion.]
Note that "USERNAME" and "SSNB_NUMBER" vary for each User and Site, and must be established in the process of joining the ring.
This approach works, most of the time, and is probably the easiest to add to the page. The result, when this approach works, looks something like this:
Cascading Style Sheets and QWR Logo-and-Links
We've found in some cases that CSS which is already built into the site will sometimes affect how the QWR logo-and-links code presents itself. Sometimes the colors of links are affected, which is generally okay, but sometimes the width and layout of tables can be altered to the point where the whole package is mangled. The HTML versions of the code are probably more stable, so if you're having problems, it's another reason to consider using the HTML rather than the SSNB approach.
The ring includes a few sites that are "grandfathered in," which have older code (still working). Grandfathered site owners who want to establish their account with the new WebRing company -- in order to access the suggested code, change the designated URL, or whatever -- please see the Site Migration page.
Site design considerations -