Curio Lane


A managed server for accessing your project data across the web.

Your project's web server makes it easier to embed your data in websites or custom applications. It offers a public, read-only view of your project, but you can manage the services that are available from it or require authentication for it. You can also disable the server entirely if, for example, you only want to access your project through the Editor.

You can view current settings via the Editor by navigating to the Web Server topic of the sidebar.

Each project is automatically configured with a Publishing Domain using a subdomain of and requires no additional setup. For advanced requirements, you can take additional steps to set up a Custom Publishing Domain.

Publishing Links are a combination of your project's Publishing Domain and a conventional path for accessing the data you need. Within the Editor look for a Publishing Links section or Share icon with common links that you can easily copy and paste directly into your own applications and tools. If you are integrating with existing tools, be sure to review our documentation on our supported paths and APIs, such as the Content Services API.

Example. The media embedded in our documentation is hosted using a standard project. The following are live examples (and feel free to inspect inline images that you see):

Content Services API

Most projects will use Content Services, such as the IIIF Image Service, to access optimized versions of files. We provide Publishing Links within the Editor for easy copy/paste of common links, but if you end up constructing your own links, there are a few conventions to be familiar with:

  • Path Prefix the path should always follow the pattern of /content/{SERVICE-ALIAS}/.
  • Service-specific Path each service documents its own path conventions or API. Refer to the individual documentation pages for full details.
  • Bucket-Object-Ref Parameter the path will typically reference an individual project file using a specialized pattern. See the Bucket-Object-Ref Parameter topic for more details on encoding references.

Here's an annotated example...

v Publishing Server -------------------------- v Path Prefix ---- v Service-specific Path ----------------------------------;key=54bb4b0a-8f3d-43a3-a7d8-72d7ab8f3a2e/info.json
                                                                  ^ Bucket-Object-Ref Parameter ------------------