http://www.freebeeperksgaming.verizon.com/
http://freebee.verizonwireless.com/
http://products.internetservices.verizon.com/

Verizon's product marketing organization was tasked with new product development, sharing, and market launching, and was accustomed to working with their design firms to design unique sites for each product. Sites were hard coded to implement this design, a process that led to a longer than desired site launch and update time.
To complete the Verizon project, Isovera worked closely with Acquia and Maark. The project goal was to decrease site production-to-market time and increase site usability on the end of the client- specifically the creation of new sites and pre-production site sharing security.

Why Drupal was chosen: 

Isovera specializes in Drupal solutions, and Verizon was already using Drupal, so Drupal as the CMS choice was a decidedly easy decision to make. In addition, Drupal’s flexibility, ease of integration, and versatility with commerce interactions make it an attractive in general.

Describe the project (goals, requirements and outcome): 

Milestones
Isovera was involved with Verizon for numerous months, seeing the project from start to finish.
Major project milestones included:
Ability for non-developers to create new sites
Ability to release a basic brand-standard site quickly
Ability to share pre-production sites with partners with password protection
Development of sites for the product organization have brand consistency
Portal 2.0 front-end migration to ACSF / Drupal

Challenges and Solutions
Reducing Time:
Originally, the process of creating a new site took weeks or months, so one of the key goals that Isovera worked on was expediting the website creation process, and reduce project to market time.
To expedite the amount of time a new website took to create, Isovera developed an “install profile” using Acquia’s Cloud Site Factory, which enabled the client to create a new site with the click of a button. In addition to an install profile, the updated site features site templates that can be built out with common content and features that can be used in multiple sites. The standardization of the templates means that site time to market can be significantly reduced from weeks or months to a day.

Reusing and Recycling Templates:
Before working with Isovera, Verizon’s non-developers were unable to make new sites for new products.
To address the usability issue, Isovera created templates to enable non-developers such as digital marketers to create new sites. By partnering with Maark, Isovera was able to design reusable components that the platform would offer to site builders. The reusable components not only decreased the time it took to launch new sites, but also enabled site builders to use predefined content modules as a template to create a new site. By giving site builders predefined reusable templates of content modules, site builders no longer needed to be coders; they could simply make changes in the web interface through dragging and dropping, or through the click of a mouse. In addition to creating reusable component templates, a library was developed for the components that can be used to recycle past layouts and also create new layout combinations, resulting in endless possibilities for potential content layouts for site builders to use.

Integrating:
At the beginning of the project, there was no ability to share pre-production sites between Verizon and its sales and business partners without needing multiple rounds of password protection.
To streamline the sharing process, Isovera was able to integrate Drupal 8 with the Verizon dashboard. The integration enabled Verizon partners to log into the Verizon dashboard and access pre-production websites from the dashboard without further rounds of authentication required, resulting in a simple and seamless transition between sites.

Key Metrics
As a result of using templates, the Verizon project cut a process that had taken weeks to months down to a process that could be done in as little as a day, leading to an expedited launch date ability. In addition, using templates allowed for non-developers to create websites, allowing for more sites to be spun up, and an increased ability to launch sites.

Organizations involved: 
Modules/Themes/Distributions
Why these modules/theme/distribution were chosen: 

Isovera used the Drupal contributed lightning distribution due to the enhanced authoring experience and media integration that met the clients requirements. The services module was chosen to expose entity representations via an API endpoint, so the Verizon development team could consume data from the site and use its data within other internal applications. The team relied heavily on the paragraphs module as the site was built based on reusable components. This type of architecture allowed Verizon's marketing team to construct highly complex pages without having any technical knowledge. The last major requirement that needed to be met was to allow Verizon users to authenticate into the Drupal application using a custom SAML IDP. This was achieved by using the samlauth module, as it gave fine-grain control over the authentication process so Isovera could provide custom parameters without much trouble.

Cloud API's Homepage
ThingSpace Page