Full Glossary

URL

A Uniform Resource Locator (URL) is a web address that points toward a unique web resource.

A canonical URL is the single, official URL for a piece of content. In many cases, content can be accessed under more than one URL, or combination or querystring arguments. It’s important, then, to identify a single URL as the official address for that content – the shortest, most precise string of characters that will consistently return that content.

Related Chapter Sections:

  • The Content Inventory

    Chapter 7: Know Your Content

    How do you know what's really on your site? You inventory it. You CONTENT inventory it.

  • Users and URLs

    Chapter 21: Migrate and Populate the Content

    There are two specific situations that come up in enough migrations to be worth discussing separately: user migration and URL redirection

  • Templating and Output

    Chapter 20: Implement the Back-End Functionality

    Templating takes static HTML and mixes it with dynamic content. It's what makes a content management system work, and it's what we'll talk about here.

  • Final Launch Checklist

    Chapter 22: Test and Launch the Site

    A final launch checklist helps the project team ensure that all the “i”s are dotted and the “t”s are crossed.

  • Planning the Content Model

    Chapter 11: Model Your Content

    A content model is all about connecting objects and defining fields. Here, we'll start looking at what that means for you content and your system.

  • The Hosting Account

    Chapter 17: Plan for Hosting

    We’re going to roll up a lot of functionality and discussion into the idea of a hosting account. This is a service you purchase from some provider that allows you to run a website and expose it to the internet.

  • Inventory and Audit Maintenance: Keeping It Updated … or Not.

    Chapter 7: Know Your Content

    A content inventory or audit is a one-time item — it captures a moment in time. Decisions will need to be made around whether that moment needs to be kept recent, or let go.

  • Other Development Tasks

    Chapter 20: Implement the Back-End Functionality

    Beyond the main back-end development tasks there's quite a few other details to be handled.

  • The Procedural Question

    Chapter 21: Migrate and Populate the Content

    How will the actual bytes move from one disk to another, and what does the timing of that look like?

  • Testing the Site

    Chapter 22: Test and Launch the Site

    There are three axes that a QA issue can turn on when testing the site: public vs. private, absolute vs. partial, and uncontained vs. contained.