The dig is how Daisy evaluates the content of your helpcenter and your application. For more information, see What is a dig.
You can configure your dig at https://app.alldaisy.com/setup.
Scheduling your dig
We run digs weekly. You get to decide when during the week it runs. For instance, if your team always releases new versions of the app at a scheduled time, it probably makes sense to run a dig right after that. On the other hand, if your team has a scheduled maintenance window, it's best to make sure you don't try to dig during that time.
Configuring your dig
In order to run a dig, we need to know a few things about your helpcenter/application. At a high level, we need to know:
- The URL where the content is accessible
- (Optional) How to log in to the site
- (Optional) Page naming scheme
URL
The URL can be found by navigating to the site in your browser and copying the address from your browser's navigation bar. A couple common gotchas:
- Make sure the scheme is included. In non-nerd speak, this means the URL should start with http:// or https://
- Make sure the path is as short as possible. In other words, make sure all the pages you want Daisy to look at have URLs that begin with the exact URL you've entered into Daisy. For instance, if you enter https://example.com/path, then your dig will cover pages https://example.com/path/page1 and https://example.com/path/page2, but not https://example.com/otherpath. In most cases, you should omit the path entirely and just enter a URL like https://example.com.
Log in
In order for the dig to audit logged-in content, we need to know how to log in to your target site. To do this, we need to know the URL of the login page (much like the target site URL), as well as CSS selectors for the username and password inputs. This can be tricky -- most browsers have tools to help you out. Here's an example using Chrome but most browsers are very similar.
Once you've got your login URL and selectors in place, we need a username and password. We require you to use an account that
- is free of any non-test data
- is not being accessed by any other people/tools
This helps us ensure that we only detect changes caused by changes to your application code, and helps keep your customer data secure.
Page naming scheme
By default, we will use the page title as the name of the page in Daisy. The page title is the text that shows up on your browser tab when you navigate to a site. However, for some sites, the page titles are all the same. In this case, we recommend you enable the option to derive page names from URL paths. This will ensure each page gets a unique title and you can easily tell them apart in the Daisy UI.