Frequently Asked Questions
What is Little Aspen and how it works?
Little Aspen is a software as a service (SaaS) that provides you document content composition, with content versioning, and record user acceptance of such document versions.
How my web application can use Little Aspen?
Through the web interface, you will manage the documents, versions, and content. Using our Developer API you can integrate your application to consume your content, record user acceptance, and other functionalities.
How much does Little Aspen cost?
Currently, Little Aspen is running in Beta Phase meaning no payment is required from any participating user while the Beta Phase is active. As a token of gratitude for all users in the Beta phase, Little Aspen will give an extra 90 days of user access with no payment required.
Once we move into Gold/Live, a 30 days trial will be offered for new users.
What use-cases my web application would take advantage of Little Aspen?
There are many use-cases where Little Aspen can enhance the overall user experience and transparency between your application and the users. Here are some examples:
When a user creates an account in your application, you collect some basic information such as name, email, and password, as part of the registration process. Alongside this, you provide a way for them to read/accept your Terms of Service. With integration with Little Aspen your application would be able to:
- get the content of any version of your Terms of Service document to present;
- record the acceptance of the specific version of your Terms of Service during the account creation process;
- verify if a specific user has or has not accepted yet the new changes;
- present the new changes and record user's acceptance for that particular version;
User Profile Page
As Little Aspen leverages document versioning and tracks user acceptance by version, you can present to the users all versions of all documents the user has accepted so far with details that include the document version content, date and time, and so on. This gives to the user a great transparency feeling, knowing that nothing is hidden from them.
Document Management Questions
What is a document?
What is a document version?
Each document content is called a version. As we know, document content changes over time, so it is important to keep the document content history available. For example, a Refund Policy document can have a version created in January 2017, and another one created in March 2020. Both belong to the same document but each version has its own content.
Why do I need document versions?
Your application changes, laws and regulations change, users create accounts or interact with your application in different timelines. The ability to verify if a specific user has or not accepted new changes so you can decide to record a new acceptance or not is really important. How many times your user was annoyed with Cookie Usage terms over and over, even if they accepted many times before? Little Aspen solves that problem with document versions.
What is a slug and how is it used?
A slug is a part of a URL that identifies a particular resource in a form readable by humans. Little Aspen use slugs to identify a document and a document version in our Developer API. For example, a Terms and Conditions document would have the slug terms-and-conditions. Slugs are automatically generated and displayed for you in the document management area.
Developer API Questions
How can I integrate my application with Little Aspen?
The integration between your application and Little Aspen is through our Developer API. You can find all the relevant information in the API Documentation page.