If you've previously used another system for managing the quality of your website, there are a few items that you may want to migrate over to Silktide. To begin, this can be a great time to make sure that your setup aligns with your current business needs. Are you scanning websites that are no longer online? Do you have users that are no longer with your organization, or maybe never logged in? Did you set up a policy to look for something on your site that is no longer a concern? This is a great time to review these kinds of things to see what you truly need. Cleaning up unnecessary items will give you a clean slate to start from with Silktide while also making your transition to Silktide much easier.
Websites
Naturally, one of the most important things to consider are the actual websites you test. In Silktide, you will define a website by identifying the homepage of the site as well as the URL patterns that should or should not be tested. So you could set up a website to test all pages where the URL begins with "https://silktide.com/", while excluding any page where the URL begins with "https://silktide.com/topSecret". It is generally best for all pages of a website in SIlktide to be written in the same language. If the different language versions of your site can be identified by a page's URL, you can create websites in Silktide for each language.
A website in Silktide can also be split into sections. Grouping similar pages together could help you see how the scores of those sections compare. Given the example above, you could set up a "Blog" section that contains all URLs that begin with "https://silktide.com/blog/". A user can have access to just a section rather than the full website, so this has the added benefit of allowing your "Blog" team to use Silktide and only see the pages they are in charge of.
To move your websites into Silktide, you will need the following information:
The name of your site, to help your users find it in your list of sites.
The homepage of your website.
The URL rules to define which pages should or shouldn't be tested.
How many pages and PDFs you want tested in the site. It's a good idea to make these values a little higher than how many pages or documents are currently on the site to give you room to test new content as the site grows.
Which users should be able to see, make decisions on, retest, and administer the site.
If the site is to contain any sections, we'd need generally the same information above for each section that needs to be in the site.
Users
Once you have websites in your account, you'd want to look at which users should be able to access your account. Silktide can work with your organization's single sign-on service, which can even be configured to create a user's Silktide account the first time they log in. Views within Silktide allow your users to see the checks most relevant to them based on their role within your organization. We offer granular controls over what users can do and see within Silktide, which can be set directly for the user or granted from a role the user is part of.
To move your users into Silktide, you will need the following information:
The user's name.
The user's email address.
What should the user be able to do in Silktide?
Which website(s) or section(s) should the user be able to see in Silktide?
Policies
In Silktide, policies are custom checks to look for content on your site that meets the criteria you define. Silktide offers many rules that you can include within a policy to identify content on a page: from simple searches for text or HTML tags on your site down to more complex rules using regex or XPath.
To more your policies into Silktide, you will need:
The title of your policy, which can help users understand what the policy is looking for.
The description of your policy, which can help users know why the policy exists and how to fix it.
Which area(s) within Silktide should the policy be a part of (Content, Marketing, Accessibility, etc).
The rules of the policy that define what the policy looks for.
Spelling Dictionary
Your organization likely has terms and acronyms that are not used outside of your work. These can be the names of programs, features, or initiatives that we might otherwise flag as being misspelled words. Your current solution may allow you to export a list of these words that you've added to your account dictionary or otherwise marked as being "approved" words.
We can import these terms into your Silktide account dictionary, as long as we have the following information:
The term to be added.
Is the term acceptable in all capitalizations, or is it case-sensitive?
Is the term acceptable in all languages we find on your site?
Reports
Do you need to deliver reports of your Silktide scores to anyone within your organization? Were you constantly referencing specific reports from your previous solution? The dashboards within Silktide allow you to see the progress your team has made in improving your websites. Silktide dashboards can present a live look at your websites or a snapshot of how your site looked from a specific point in time to show how far you've come. You can even set reports to deliver to internal or external users on a schedule.
To create dashboards in Silktide, you'll need the following:
What specific charts, tables, and informational text do you want to be included on the dashboard? You'll create a dashboard template that contains all of these elements.
If this dashboard should look at live data, you'll create a "dashboard".
If this should never change and serve as a static snapshot of how your site looks right now, this will be a "snapshot".
Do you want snapshots created automatically on a schedule? Do you want these scheduled reports to notify any internal or external users when they are made?