The Stacks approach to implementation comes from years of experience including more than ten (10) years of software maintenance and support for organizations of all types including the Microsoft Library, California Institute of Technology (Caltech) Library and Singapore University of Technology and Design (SUTD) Library.

Timeline - Stacks can be deployed in as little as three (3) weeks during which training can be provided. Once training is completed, you will need to finalize site information architecture and create content (90 days on average).

Implementation - Through consultation, understanding, communication, training and execution, Stacks will deliver a web experience customized for the needs of your organization and users. The plan is comprised of the following steps:

1. Onboarding Checklist

The Onboarding Checklist is provided to each new Stacks customer and is designed to capture as much information about the organization as possible and covers details such as organizational information, system information, third-party integration details, authentication preferences, and more.

2. Website Set-Up

A website instance will be created while going through your Onboarding Checklist to verify all of the details required. This information will be used to set up initial integrations including authentication, reviews, book jackets, and recommendations. This phase can include setting up Google Analytics, Google Translate and Google Places, as well as activating site search and third party tools such as social media platforms

3. Training Portal

Stacks implementation includes the Stacks Academy training program and access to robust support materials. Three (3) training sessions will be held focusing on Administration, Content Editing and Content Best Practices. Training also includes access to user manuals, video tutorials, and the ticket support desk; all part of the comprehensive Stacks Training Portal that can be viewed at https://training.StackDiscovery.com.

4. Information Architecture

Before accessing the website itself, the Stacks team will provide a reference guide and resource list to help guide the design of a menu structure for the website. This material will help advise on how to create and structure content during training sessions.

5. Content Development

The customer is responsible for creating all content unless otherwise discussed. At the time of deployment, day-to-day maintenance, such as event postings, content updates, hours of operation, etc. will be managed by the customer through an easy-to-use dashboard. From one location, this dashboard offers access to all the product features and each user can adjust it to suit their preferred daily workflow.

6. Go-Live

Once the new website is populated with content, it’s time to launch the new website. The support team will work closely with the client when changing over DNS settings. We are also able to coordinate with PR and/or Marketing teams to time the Go-Live with important dates or events pertinent to your organization.