Printed Pieces That Meet Multiple Needs

April 28, 2014
Fourth Draft - Sir Speedy

National and Local Site
Detailed Specifications
Document
www.sirspeedy.com
PRESENTED TO:
Christian Lau, Vice President - IT
Franchise Services, Inc.
PREPARED BY:
Andhita Primandini
Developer
Fig Leaf Software
aprimandini@figleaf.com
202.797.7711ext.133

1. TABLE OF CONTENTS
Executive Summary ...................................................................................................................... 1
Stakeholders ............................................................................................................................ 1
Change Log .............................................................................................................................. 1
1. Overview ..................................................................................................................................... 2
1.1 Purpose .................................................................................................................................. 2
1.2 Intended Audience ................................................................................................................. 2
1.3 Assumptions and Constraints ................................................................................................ 2
1.4 Definitions, Acronyms, Abbreviations .................................................................................... 2
2. Development .............................................................................................................................. 3
2.1 Architecture ............................................................................................................................ 3
2.2 Ektron ..................................................................................................................................... 3
2.2.1 User Roles .......................................................................................................................... 3
2.2.2 Content Workflow ................................................................................................................ 4
2.2.3 Content Creation and Editing .............................................................................................. 4
2.2 Custom Development ............................................................................................................ 8
2.3.1 Authentication ..................................................................................................................... 8
2.3.2 Site Statistics ...................................................................................................................... 8
2.3.3 Integration with Third Party APIs ........................................................................................ 9
2.3.3.1 Flickr................................................................................................................................ 9
2.3.3.2 Scribd .............................................................................................................................. 9
2.3.3.3 Dropbox ..........................................................................................................................10
2.3.3.4 Google Drive ...................................................................................................................10
2.3.3.5 Box ..................................................................................................................................11
2.3.3.6 Google Map ................................................................................................................... 11
2.3.4 Admin Screens .................................................................................................................. 12
3. User Interface Development ................................................................................................... 15
3.1 Navigation ............................................................................................................................ 15
3.1.1 Main Navigation ................................................................................................................ 15
3.1.2 Secondary Navigation ....................................................................................................... 15
3.1.3 Top Header Menu ............................................................................................................. 16
3.1.4 Footer Menu ...................................................................................................................... 17
3.2 Site Templates ..................................................................................................................... 18
3.2.1 National Global Elements ................................................................................................. 18
3.2.1.1 National Header ............................................................................................................. 18
3.2.1.1.1 Franchisee Opportunities ............................................................................................ 19
3.2.1.1.2 Request A Quote ........................................................................................................ 20
3.2.1.1.3 Send A File ................................................................................................................. 20
3.2.1.1.4 Social Media ............................................................................................................... 23
3.2.1.1.5 Find A Location ........................................................................................................... 23
3.2.1.1.6 Mega Menu ................................................................................................................. 24
3.2.1.1.6.a Products and Services ............................................................................................. 24
3.2.1.1.6.b About Us .................................................................................................................. 24
3.2.1.1.6.c Insights ..................................................................................................................... 26
3.2.1.1.6.d Join Our Team ......................................................................................................... 26
3.2.1.1.6.d Blog .......................................................................................................................... 27
3.2.1.2 National Footer .............................................................................................................. 28
3.2.2 National Unique Templates .............................................................................................. 30
3.2.2.1 Home Page .................................................................................................................... 30
3.2.2.2 Company Info Landing Page ......................................................................................... 41
3.2.2.3 Management Team Landing Page ................................................................................ 42
3.2.2.4 Individual Bio Landing Page .......................................................................................... 43
3.2.2.5 Partners Index landing page .......................................................................................... 44
3.2.3 Local (Model) Site Global Elements ................................................................................. 45
3.2.3.1 Local Site Header .......................................................................................................... 45
3.2.3.2 Local Site Footer ............................................................................................................ 48
3.2.4 Local Site Unique Template .............................................................................................. 49
3.2.4.1 Local Homepage ............................................................................................................ 49
3.2.4.2 About Sir Speedy Landing Page .................................................................................... 53
3.2.4.3 Why We Are Different Landing Page ............................................................................. 54
3.2.4.4 Testimonials landing Page ............................................................................................. 55
3.2.4.5 Portfolio Landing Page .................................................................................................. 56
3.2.5 General Page Templates .................................................................................................. 57
3.2.5.2 Products & Services Category Detail Landing Page ..................................................... 59
3.2.5.3 Products & Services Sub-Category Detail Landing Page .............................................. 61
3.2.5.4 News Index Landing Page ............................................................................................. 63
3.2.5.5 News Detail Page .......................................................................................................... 64
3.2.5.6 In The Media Index Page ............................................................................................... 65
3.2.5.7 Insights Whitepapers index Page .................................................................................. 66
3.2.5.8 Insights Whitepapers Detail Landing Page .................................................................... 67
3.2.5.9 Insights Case Studies Index Page ................................................................................. 68
3.2.5.10 Insights Case Studies Landing Page ........................................................................... 69
3.2.5.11 Jobs At Sir Speedy Landing Page ............................................................................... 70
3.2.5.12 Job Profiles Index Page ............................................................................................... 71
3.2.5.13 Job Profiles Landing Page ........................................................................................... 72
3.2.5.14 Privacy Policy Footer Content Landing Page .............................................................. 73
3.2.5.15 Terms & Conditions Footer Content Landing Page ..................................................... 73
3.2.5.16 Environmental Message Footer Content Landing Page .............................................. 75
3.2.5.17 SiteMap Footer Content Landing Page ....................................................................... 75
3.2.5.18 Register Landing Page ................................................................................................ 75
4. Additional Functionality .......................................................................................................... 77
4.1 Page Translation .................................................................................................................. 77
5. Development Requirements ................................................................................................... 78
5.1 Operational Requirements ................................................................................................... 78
5.2 Platforms and Browser Support ........................................................................................... 78
5.2.1 Authoring ........................................................................................................................... 78
5.2.2 Viewing/Browsing .............................................................................................................. 78
6. Document Approval ................................................................................................................ 79
Appendix A - ................................................................................................................................. 80

Fig Leaf Software Requirements Document ~ Franchise Services, Inc.

Fig Leaf Software 1 4/28/2014

EXECUTIVE SUMMARY
INTRODUCTION
This Detailed Specifications Document provides a clear, formal statement of the scope mutually
outlined in the functional requirements gathering session(s) by Franchise Services (FranServ)
and Fig Leaf Software, Inc. (Fig Leaf). It also may include suggested specifications required to
execute the implementation identified herein.

The Detailed Specifications Document outlines Fig Leaf recommendations for how FranServ
could implement the admin screens for its Sir Speedy website. The requirements described in this
document were gathered from reviewing the current Sir Speedy Management Console, and 2
days of meeting with FranServ and Fig Leaf.

Stakeholders
NAME ROLE COMPANY
David Robidoux VP of Marketing FranServ
Christian Lau VP of IT FranServ
Kristin Ausk Marketing Manager FranServ
Rebecca Sorensen Project Manager Fig Leaf
Robert Segal Business Analyst Fig Leaf
Tracey Dunn Creative Director Fig Leaf
Femi Osinowo Senior Developer Fig Leaf
Andhita Primandini J unior Developer Fig Leaf

Change Log
DATE AUTHORS COMMENTS
J anuary 27, 2014 Fig Leaf Software First Draft
February 25, 2014 Fig Leaf Software Second Draft Revision
based on the clients
review
April 3, 2014 Fig Leaf Software Third Draft remove a
sentence of
Additionally, template
changes made to the
model local site will
propagate to every local
site. From the section
2.1 Architecture
April 24, 2014 Fig Leaf Software Fourth Draft revise the
description of the
portfolio megamenu
(page 47) and portfolio
slider (page 52); revise
per clients request



1. OVERVIEW
1.1 Purpose
The purpose of this document is to fully describe the functionality requirements of the Sir Speedy
National and Local/Center site (the Site), and illustrate how those requirements will be satisfied
in the website. The website will serve as a centralized content management system as well as a
portal to all of the Sir Speedy information and member services. The site will be developed using
Ektron CMS (Ektron), a content management system software package running on the Microsoft
.Net Platform.

The customizations that will be applied to the SirSpeedy Site to meet FranServ's requirements
will also be discussed in this document.

This SirSpeedy General Requirements Document contains an extensive overview of the National
and Local Site and the agreed-upon specifications for the system, which is referred to by Fig Leaf
Softwares developers throughout the development process; Thus, it shall serve to identify the
scope of the project.

1.2 Intended Audience
This document is intended to guide implementation of the approved design. Its primary
audiences, therefore, are FransServs Administrators and Stakeholders, and Fig Leafs Web
Developers, Software Testers and Project Manager.

1.3 Assumptions and Constraints
he Site will be managed using Ektron version 9.0. The functionality of the main national site,
model site and all instances of local site will be implemented and managed within Ektron CMS
framework. Fig Leaf will provide standard templates for authoring new content pages and will
provide administrative tools necessary for changing text and links of navigation elements to be
displayed throughout the site.

The prototype delivered to, reviewed and approved by Franserv will represent the latest designs
and will take precedence over any designs represented in this document.

Also, Fig Leaf will have the search field CSS to be hidden during the site launch since FranServ
decided not to implement the search functionality at the moment.

1.4 Definitions, Acronyms, Abbreviations
FranServ Franchise Services
Workarea An area in Ektron where you can manage your website (content and
configuration)


2. DEVELOPMENT
2.1 Architecture
There will be 3 areas of the website, the National site, the model local site, and the instances of
the local site. When needed, a local site will be created by copying the model local site. Admins
and centers will be required to log in to get access to site content. Centers will only have access
to the admin interface created for them. National Admins will have access to their own admin
interface, all the center admin interfaces, and all the content pages on the admin and model local
sites (local admins will not be able to edit center page content directly). Changes to local site
templates will be made to the model local site by National Admins and will propagate to all
existing local sites.

Once a local site has been created, it will not be able to be renamed. National Admin will only be
able to make changes to certain things such as Header, Footer and All other general things that
will be propagated to all local sites through the assistance of a support engineer (developer).
Also, if any structural (templates) changes are made, these will be propagated to all local sites.
Content changes will not be propagated.
2.2 Ektron
Ektron Content Management System software package comes with a variety of built in functions
that can be customized as needed or used out-of-the-box. Additional features are purposefully
customizable in order to meet varying organizational needs and/or to integrate with external (third
party) systems.
2.2.1 User Roles
Superuser/National Administrator (National Admin)
Superusers are Sir Speedy national staff or National Admin are responsible for managing the
content of entire website and will have access to all screen in the workarea (National and Local).
As a national admin, a user can act as three different rules that will be established for editing and
managing content within the site. Management of user roles and permissions can be done using
the standard Ektron-provided tools. Fig Leaf will configure roles for the initial release. FranServ
will have the ability to change roles and permissions as needed.
2.2.1.1 Contributor
One or more Ektron users can be designated as a Contributor. Contributors will be allowed to
edit content and submit changes for approval. This role can be restricted to content within one or
more sub-folders or pages of the site. Contributors can also be given the ability to create new
pages within folders on the site and to edit links and wording on navigation elements.
Conrtibutors can propose changes to content/new content, but are not to approve these changes
for publication to the site.
2.2.1.2 Approver
One or more Ektron users can be designated as Approvers. Approvers have control over one or
more pages or folders within the site, and for pages under their control, Approvers can accept or
reject changes to a page. Approvers can also edit content, if desired. They will be able to change
and then approve their own changes. Multiple layers of approval can be configured within Ektron,
but this functionality will not be set up for FranServ at this time for they will only have one admin
that will manage their content approval nationally and locally.


2.2.1.3 Administrator
At least one user must be designated as an Administrator, and there can be multiple
Administrators if desired. Administrators will have all of the abilities of the other two roles
(contributor and approver), and will additionally be able to set/change the roles and permissions
of other users.
2.2.2 Content Workflow
A change to the content is defined as any of the following:
Creation of a new page by using a template available in the workarea
Editing one or more elements on an existing page
Editing the text or navigation links in the basic site navigation
A user with the necessary permission to perform any of these changes can edit and then submit
their change through the Ektron CMS. The change is then routed for review by Approvers.
Whenever a change is submitted, and email will be generated to content approvers. The change
will be in a pending state until it is approved or rejected.
The following figure illustrates the content approval workflow:

If a page that was submitted for approval is declined, it will be removed from the approval chain
and will need to be resubmitted. When a submission is declined, an email will be generated and
sent to the user who requested approval. Documentation for Ektron Approval workflow is
available from this url:
http://documentation.ektron.com/cms400/v802/WebHelp/Managing%20Folders/Approvals/Approv
als_intro.htm.
2.2.3 Content Creation and Editing
2.2.3.1 Standard Rich Text Editing Fields
Some templates will contain content areas that can be edited. The editor is opened from the Edit
button within Ektron, and resembles a standard word processing program, with rich-text editing
features:


Formatting of text can be done through this interface. Content editors will have an option to create
or edit HTML content such as images, tables, and hyperlinks if desired. Images, tables and
hyperlinks can be inserted into any text field. The editor links can optionally be opened in a pop-
up window if needed.

Some elements, such as fonts and colors, are controlled through the page template, and are not
changeable by the content editor. This is necessary so that the site maintains a consistent look
and feel.
2.2.3.2 Section 508 Compliance
All content created can be checked for 508 compliance if the option to validate the content for
accessibility is enabled. If this option is checked, the content will be validated for compliance. A
non-compliant page will not be submitted for approval and a message indicating non-compliance
will be displayed to the person editing the content.
Alternative Text for any images added will be provided through the editor:

The image alt text field can only either be made required for all users (contributors and
approvers) or optional for all users. The alt image field will be made optional for all users and it
will be a training issue that the approvers always make sure it is populated.



The table below lists dialog boxes in which accessibility information can be entered. This
information can be entered at the time the content is added. Fig Leaf recommends that this
information be entered whenever possible.
Dialog Field How Filled if no value exists
Image Properties Image Alt Text: Uses the images title
Table Wizard - Cell Properties Tab Abbreviation:
Categories:
Not automatically filled when no value exists
Table Wizard - Accessibility Tab Caption:
Summary:
Not automatically filled when no value exists
Hyperlink Manager
(Includes Quicklinks)
Tooltip: Contents of Link Text field copied

2.2.3.3 Site Content Format
a. Smart Forms
Smart Forms are used in Ektron to maintain and share structured information. During the
discovery phase, different types of content were identified to be implemented and managed as
Ektron Smart Forms.
A Smart Form can be defined by any number of fields. A Smart Form content instance is a
specific copy of a Smart Form with assigned properties. A Smart Form is similar to a database,
and a Smart Form Content instance is similar to a database record.
Once created, a Smart Form content instance can be displayed on multiple pages and in multiple
layout formats. Each layout format is called a C# control. C# Controls are small .net scripts that
are registered with the Ektron API and can be placed on the back-end of pages or templates to
control how a Smart Form instance is displayed on the site.
Smart Form content instance data can be displayed using different formats on multiple pages.
Once an admin creates an instance of a smart form, Ektron will generate a unique ID which will
allow the developer to access each instance to be displayed on the site. For example, HomePage
Banners will be listed on the home page showing only the background picture, picture, text and a
link. When the user clicks on the banner, they will redirected to another page based on the URL
that the content administrator entered into the smart form when she created an instance of the
homepage banner smart form.
b. Content Block
There are three (3) types of content blocks in Ektron: Static Content Block, Dynamic Content
Block, and XML content block. Static content blocks will be used to display one specified content
block on a web page; a dynamic content block will display the content block depending on the ID
number that is passed through a URL parameter. Lastly, XML content blocks will be used to
display the content from a piece of XML or XHTML code.
An Admin can create a content block through the workarea. Since static content blocks will not
offer the flexibility of changing the content of a webpage easily, Fig Leaf will be using dynamic
content blocks where possible. Once an admin creates a dynamic content block with an ID
number, the C# server control will be used in some specified templates to pull out the content
based on the content ID that is passed through URL parameter.



c. Menu Server Control
Admins can create menu items through the menu content tab in the workarea. Once a menu item
is created, it will generate an ID that can be called through the Menu Server Control on a
specified template. The following is an example of how a menu item ID will be used in Menu
Server Control:
<ektron:MenuModelSource ID="UxHeaderLinksModelSource" runat="server">
<TreeFilter Id="19"/> /** Menu Item ID = 19**/
</ektron:MenuModelSource>
<ektron:MenuView ID="uxHeaderLinks" runat="server"
ModelSourceID="UxHeaderLinksModelSource">
<ListTemplate>
<ul runat="server">
<asp:PlaceHolder ID="listPlaceholder" runat="server" />
</ul>
</ListTemplate>
<ItemTemplate>
<li>
<asp:HyperLink ID="nodeLink" runat="server" Text='<%# Eval("Text") %>'
NavigateUrl='<%# Eval("NavigateUrl") %>'/>
<asp:PlaceHolder ID="itemPlaceholder" runat="server" />
</li>
</ItemTemplate>
</ektron:MenuView>

Throughout the site, the Menu Server Control will be used on each landing page of the Mega
Menu. Note that the Mega Menu itself will not be implemented as Server Control, but a custom
C# control.
d. Ektron Form
Ektron allows you to create and manage forms within the CMS site. You can either save the
record into a database (by default) or email the record to a particular email address (by editing
the properties screen). However, FranServ has requested that some forms on the national site be
emailed to the local admin (franchisees) as .csv files, such as SubscriptionRequest-A-Quote and
Send-A-File form. No email will be sent to the local admin for Registration.
Furthermore, the data submitted from an Ektron form on the local sites will be saved in a backend
Franchises database, and be emailed to each related local admins email address. The submitted
form data can be managed in the admin area.
e. Taxonomy Control
Taxonomy in Ektron is a categorization system that uses one-to-many relationships to ease the
management of site content. Content could be categorized in the database by how each content
piece relates to multiple categories to allow multiple ways of accessing the content.
A taxonomy directory control allows automatic navigation creation on the site. Once the content is
tagged, it automatically shows up in the correct section of the site. This will allow the national
admin to create and manage content without worrying where the content is going to show up
throughout the site.
TAXONOMY SAMPLE CATEGORIES
Products &
Services
Categories
Printing & Copying, Direct Marketing, Signage, Creative Services, Online
Storefronts, MyDocs, Data, Mailing Services, Fulfillment Services, Finishing &
Binding, Promotional Products, Mobile Marketing, and Social Media
Department Sales, Customer Service, Graphic Design, PrePress, Executive


2.2 Custom Development
2.3.1 Authentication
FranServ customers will be able to login using their account information (username and
password). Upon login form submission, the information entered will be evaluated.
If one (1) record is found associated with a username that the customer entered, the
customers password will be used to determine if that customer should be authorized to
access particular content (for example, whitepapers).
If no records are found matching the username entered, a message will be displayed
indicating the member should attempt to re-log in with different username and password
or to register first.
Once Authenticated, a customer will not need to provide contact information anywhere on the site
until they close their browser or log out of the site.
A forgot password link will be displayed on the login form that, when clicked, will send a
temporary password to the email address associated with the account specified (based on the
username entered).
Besides authenticating against the custom user database, the site will also let the customers log
in by using their Social Media (Facebook, Twitter, Google or OpenId) accounts. Once a user
submits their Social Media login information, the browser will take the user from the site to the
social media providers website in a pop-up window. The Social Media site will then check the
users information against their database.
If the customer is authenticated against a social media site, then the social media site will
ask the customer to verify whether the customer wants to share the information with the
Sir Speedy Site. The Sir Speedy Site will then save the customer information in a custom
database in the SirSeedy site.
If the Social Media authentication fails, then the customer will be prompted to try re-log in
(against SirSpeedy customer database).
2.3.2 Site Statistics
Google Analytics code will be embedded within every site page in order to capture site usage
statistics. FranServ will need to provide Fig Leaf with their Google Analytics account information
in order for code to be generated to be included in the site templates. The Google Analytics code
will be active on the site when it launches.


2.3.3 Integration with Third party APIs
2.3.3.1 Flickr
Sir Speedy Site will be using Flickr API in order to display portfolios on the local sites. Each local
admin will be asked to provide a Flickr username and password, which will let each local site to
retrieve some data from his/her flickr account. Note that, each time the site make a HTTP (GET)
request, Flickr can only return 30 photos at a maximum.
The reference to the methods library for using Flickr API: http://www.flickr.com/services/api/

Figure: Portfolio Index Page which will be using Flickr API


2.3.3.2 Scribd
Both National and Local Sites will be using Scribd API to display Case Studies files. FranServ will
need to provide Fig Leaf with their Scribd credentials if they would like to use API Sessions and
The my_user_id parameter for authenticating FranServ user accounts.
The reference to Scribd API: http://www.scribd.com/developers/platform

Figure: Case Studies Landing Page which will utilize Scribd API


2.3.3.3 Dropbox
Fig Leaf will implement the Dropbox Core API in order to allow users to import their files from
their Dropbox account into the site server. The user will be prompted to the Dropbox
authentication window when they choose to upload a file from their Dropbox accounts. Fig Leaf
will then make an HTTP GET request in order to download the users file from the users Dropbox
account.
The reference to Dropbox Core API: https://www.dropbox.com/developers/core/docs
2.3.3.4 Google Drive
Fig Leaf will also implement the Google Drive API in order to allow the users to import their files
from their Google Drive account into the server. Fig Leaf will make a GET request to download a
file from a users Drive account.
Reference to Google Drive API: https://developers.google.com/drive/web/manage-downloads
2.3.3.5 Box
Fig Leaf will also implement the Box API to allow users to import a file from their Box accounts
into the server. The site will be downloading a file from a users box account into the server by
making a cURL request.
Reference to Box Developer API: http://developers.box.com/docs/ #files-download-a-file

Figure: Upload Files in Send-A-File Form which will use Dropbox, Box, and Google Drive API



2.3.3.6 Google Map
Fig Leaf will be using Google Map API in order to implement the Locator. In order to find Sir
Speedy locations a user need to enter a specified radius of a zip code and the location
information (city, state, zip and radius). If there is no Sir Speedy locations within the radius
specified, then radius will be incremented by 25 mile until at least one location is found. The code
that is used for the current site will be reused in the new site whenever possible.
The locator will be invoked on the following pages:
Request A Quote Form

Figure: Your Location on Request A Quote Form


Send-A-File Register Page and Submission Page

Figure: Your Location on Send A File Form


Find A Location in the top header of every page and Worldwide Locations area on the
national homepage (which will invoke the header Find A Location in the top header)

Figure: Find A Location on top header

Your Location on the local homepage

Figure: Your Location on the local homepage

2.3.3 Admin Screens
Refer to the Admin Screen Detailed Requirement Document (separate document)


3. USER INTERFACE DEVELOPMENT
This section will describe the pages created for the full sized (non-mobile) site. This section is
organized by the Mega Menu as the main navigation menu choice. Pages that need specific
programming to populate all, or part, of the pages content are listed under the mega menu as the
main navigation menu heading. Pages listed under each menu heading will not necessarily
appear in the menu or be directly accessible from the menu.
3.1 Navigation
3.1.1 Main Navigation
The Mega menu will act as the main navigation of the sites. The Mega Menu will appear on every
page (including the home page). Subdirectories will be created for each Mega Menu choice.
Clicking on a mega menu choice will display the corresponding secondary navigation choices
with images and some text.
National Mega Menu:
Products and Services
About Us
Insights
Join Our Team
Blog
Local Mega Menu:
Portfolio
About Us
Insights
Join Our Team
Blog
3.1.2 Secondary Navigation
The secondary Navigation choices will appear as sub-menus when a user clicks on a mega menu
choices and on top of the landing page screens.
3.1.2.1 National Site Secondary Navigation
MAIN MENU TEXT SECONDARY MENU CHOICES TERTIARY MENU CHOICES
Products and Services [products and services categories]
About Us Company Info
Management
Partners
History
News
In The Media
Insights Case Studies
Brief & Whitepapers
J oin Our Team J obs at Sir Speedy
J ob Profiles
[Available Job Categories, for example:
Sales, Customer Service, Graphic
Design, PrePress, Management]
J ob Search
Blog


3.1.2.2 Local Site Secondary Navigation
MAIN MENU TEXT SECONDARY MENU CHOICES TERTIARY MENU CHOICES
[available products and services
categories]

Portfolio - -
About Us About Sir Speedy
Why We Are Different
Our Team
Testimonials *
News
In The Media
Insights Case Studies
Brief & Whitepapers
J oin Our Team J obs at Sir Speedy
J ob Profiles
[Available Job Categories, for
example: Sales, Customer Service,
Graphic Design, PrePress,
Management]
J ob Search
Blog
*Testimonials will not be appeared on the mega menu, but it will appear on top of (About Us)
landing page
3.1.3 Top Header Menu
The top header menu will appear at the top of each page (above the SirSpeedy logo and Mega
Menu) and will contain the following:
National Header Menu
Franchise Opportunities
Request A Quote
Send A File
Social Media
Find A Location
Local Header Menu
Request A Quote
Send A File
Subscribe
Social Media
Contact Us
Shop



3.1.4 Footer Menu
The footer menu will be at the bottom of every site page, and will contain the following:
National Footer Menu:
Products & Services
Products & Services Categories - Link to each Products & Services category landing
pages
About Us
Company Info - Link to Company Info landing page
Management Team - Link to Management Team landing page
Franchise Opportunity - Link to Franchise Opportunity landing page
Partners - Link to Partners index page
News - Link to News index page
In The Media - Link to In The Media index page
Insights
Briefs & Whitepapers - Link to Whitepapers index page
Case Studies - Link to Case Studies index page
Join Our Team
Jobs at Sir Speedy - Link to Jobs At SirSpeedy landing page
Current Positions - Link to Job Search landing page
Follow Us
Social Medias Logo - Link to list of social media
Latest Tweets - display three (3) latest SirSpeedy Corporates Tweets
Speak With A Local Professional - Link to Find A Location at header
Learn About Franchise Opportunities
Partners Logo - Link to each partners site
Privacy Policy - Link to Privacy Policy landing page
Terms & Conditions - Link to Terms & Conditions landing page
Environmental Message - Link to Environmental Message landing page
SiteMap - Link to SiteMap landing page
Local Footer Menu:
Products & Services
Products & Services Categories - Link to each Products & Services category landing
pages
About Us
About Sir Speedy - Link to About Sir Speedy landing page
Why We Are different - Link to Why We Are different landing page
Testimonials - Link to Testimonials landing page
News - Link to news index page
In The Media - Link to In The Media index page
Portfolio
Our Portfolio - Link to Porfolio landing page



Insights
Briefs & Whitepapers - Link to Whitepapers index page
Case Studies - Link to Case Studies index page
Join Our Team
Jobs at Sir Speedy - Link to Jobs At SirSpeedy landing page
Job Profiles - Link to Job Profiles landing page
Current Positions - Link to Job Search landing page
Follow Us
Social Medias Logo - Link to list of social media
Latest Tweets - display three (3) latest SirSpeedy Franchisees Tweets or Corporate Tweets if the
franchise does not have a twitter account
Have Questions? Call Us Today
Stay Up To Date On News & Promotions - Link to Subscribe pop-up
Partners Logo - Link to each partners site
Privacy Policy - Link to Privacy Policy landing page
Terms & Conditions - Link to Terms & Conditions landing page
Environmental Message - Link to Environmental Message landing page
SiteMap - Link to SiteMap landing page
Language Flag - when clicked, will use Google Translate to display the page in the language
corresponding to the flag
3.2 Site Templates
SirSpeedy Templates will consist of National Template Pages and some model templates that
can be cloned to create an instance of center site.
3.2.1 National Global Elements
3.2.1.1 National Header
The header will be a fixed global element throughout the site. It will be featured atop the main
content area on all site pages, regardless of content layout. However, It may appear differently
based on the width of the display resolution of a users device and/or browser settings.
At widths of 1024 and 880 pixels, National Header will be a user control that will be included in
the Master Page. The Sir Speedy National Header consists of the Top Header Menu (Franchise
Opportunities, Request A Quotes, Send A File, Social Media, Search, and Find A Location) the
Sir Speedy Logo, and the National Mega Menu Elements.

Figure 1: Header at 1024 and 880



At widths of 760, 480 and 320 pixels, the national header will not have the mega menu as the
primary navigation of the site. The users will engage the primary navigation by using a tab list, as
shown in the design below.

Figure 2: Header at 760, 480, and 320

3.2.1.1.1 Franchisee Opportunities
Description
This element will be built as part of the Header as a smart form. An admin will be able to manage
its content by adding or editing an instance of the FranchiseOpportunities Smart Form. The
Franchise Opportunities element will only be displayed at widths of 1024 and 760 pixels.
Fields
1. Title (required)
2. Description (required)
3. Link (required)
4. Image (required)

Figure 3: Franchise Opportunities Top Menu in National Header at 1024 and 760


3.2.1.1.2 Request A Quote
Description
This element has two sub-elements: the search a center element and an HTML Ektron Form that
will allow the data that the user enters to be saved to a database or emailed to a particular email
address.
Center Search Fields
1. City, Search, Zip (required)
2. Distance (required)
Form Fields
1. FirstName (required)
2. LastName (required)
3. JobTitle
4. Company
5. EmailAddress (required)
6. PhoneNumber (required)
7. ProjectName
8. ProjectDescription
9. ProjectFiles
10. ProjectBudget

Figure 4: Request A Quote Top Menu in National Header
3.2.1.1.3 Send A File
Description
This element has three main sub-elements: login or sign in form for returning customers, sign up
area, and send files as a guest; all link to a landing page that contain ektron form for each
purpose.
Customers will be allowed to login using Facebook, Twitter, Google, LinkedIn or OpenId. If a
customer does not want to authenticate using the social media sites, they can register with the Sir
Speedy site and authenticate against a custom database setup for this purpose (this is the


customer database also available in the Administrator section to manage customers). Information
regarding customers who authenticate against social media will also be stored in this database.
At the end, Franchisees will also authenticate against the custom database.
Once a user is prompted to the Send A File Form, a user will need to enter some contact
information and to upload a file. The site will allow the user to upload a file by dragging and
dropping, browse local file or through third party internet storage such as Dropbox, Box and
Google Drive (details API implementation in section 2.3.3.3 to 2.3.3.5)
Sign in form fields
1. Connect With A Social Network options (sign in via facebook, twitter, google or openid
account)
2. Email Address - Ektron Form
3. Password - Ektron Form
4. Remember Me checkbox
5. Sign In Button
6. Forgot Username and/or Password link
Sign up area
1. Sign Up With A Social Network Options (via facebook, twitter, google or openid account)
2. Register Button/link that will redirect you to Register landing page - Ektron Form (details
in section 3.2.5.18)
Send Files As A Guest
1. Send Files As a Guest Button/link that will redirect you to an ektron HTML form page

Figure 5.1: Send A File Top Menu in National Header



Figure 5.2: Send A File Form



3.2.1.1.4 Social Media
Description
This element will consist of social media icons that will redirect the customer to a FranServ social
media site. The social media element will only be visible at the top menu at widths of 1024 pixels.
Social Media Icons as ImageLink
1. Facebook with link
2. Twitter with link
3. Google+ with link
4. LinkedIn with link
5. StumbleUpon with link
6. Flickr with link
7. Youtube with link
8. Marketing Tango with link

Figure 6: Social Media Top Menu in National Header at 1024
3.2.1.1.5 Find A Location
Description
This element will be used by customers to find Sir Speedy locations within a specified radius of a
zip code. When there are no Sir Speedy locations found within the specified radius, the radius will
be programmatically extended in 25 mile increments until at least one location is found. Fig Leaf
will be recycling the code used for the current site into the new site.
An Ektron form will be used to let the the customer enter the information to the site.
Fields
1. City, State, Zip Text Field
2. Distance as a dropdown

Figure 7: Find A Location on Top Menu of National Header at 1024


3.2.1.1.6 Mega Menu
The Mega Menu will serve as the site primary navigation and will only display at widths of 1024
and 872. This element consists of five (5) main menu options:
About Us
Insights
Join Our Team
Blog

3.2.1.1.6.a Products and Services
Description
The Products and Services in the mega menu will consist of multiple products and services
content types (smart form). The national admin will use the smart form in the Ektron workarea in
order to create an instance of products and services.
The element property that will show up in the mega menu will only be Title, Image, and URL, but
each instance of the products and services category will have more fields that will be used for
each products and services landing page.
Fields on MegaMenu
1. ProductsAndServices Title
2. ProductsAndServices Image
3. ProductsAndServices Url

Figure 8: Products and Services Mega Menu on National Header

3.2.1.1.6.b About Us
Description
The About Us in the mega menu will consist of six (6) different smart forms for Company Info,
Management, News, Partners, History and In the Media. The national admin will use the smart
form in the Ektron workarea in order to create an instance of each of these smart forms.
Each smart form will be bound to the About Us Mega Menu which will be controlled in the back-
end on the Header Template Code Behind. For example, for the Company Info section, only the


title, teaser, and the link to go to each landing page will be pulled out from the data that the
National Admin enters into the company info smartform.
Company Info Fields for Mega Menu:
1. Company Info Title
2. Company Info Teaser
3. Company Info Link
Partners Fields for Mega Menu:
1. Partners Images
2. Partners page links

Management Fields for Mega Menu:
1. Link to Management Team Index Page
2. UserProfiles Image
3. UserProfiles Name
4. UserProfiles link
History:
[pending] - waiting for clients advice -
News Fields for Mega Menu:
1. Link to News Index Page
2. News posted date
3. News City
4. News State
5. News Teaser
6. News Link
In The Media Fields for Mega Menu:
1. Link to InTheMedia Index Page
2. InTheMedia posted date
3. InTheMedia sourceName
4. InTheMedia Teaser
5. InTheMedia Link

Figure 9: About Us Mega Menu on National Header


3.2.1.1.6.c Insights
Description
The Insights in the mega menu will consist of two (2) different smart forms for Case Studies and
White Papers. Again, the national admin will use the smart form in the Ektron workarea in order to
create an instance of each of these smart forms.
Brief and WhitePapers Fields on MegaMenu:
1. BriefAndWhitePapers Title
2. BriedAndWhitePapers Teaser
3. BriefAndWhitePapers Image
4. BriefAndWhitePapers link
All Case Studies Fields on MegaMenu:
1. CaseStudies Title
2. CaseStudies Teaser
3. CaseStudies Image
4. CaseStudies link

Figure 10: Insights Mega Menu on National Header
3.2.1.1.6.d Join Our Team
Description
The Join Our Team in the mega menu consists of three (3) sub-menu that will be pulled out from
three (3) different smart form which are Jobs at SirSpeedy, Job profiles, and Job openings smart
forms. Again, the national admin will use the smart form in the Ektron workarea in order to create
an instance of each of these smart forms.
Why Work With Us Fields on the MegaMenu:
1. JobsAtSirSpeedy Sub-Title
2. JobsAtSirSpeedy Image
3. JobsAtSirSpeedy MegaMenu Teaser
4. JobsAtSirSpeedy Link
Job Profiles Fields on the MegaMenu:
1. Department Name
2. Department Description
3. Department Image
4. Department Link


Find A Job Fields on the MegaMenu:
- Recent Jobs:
1. JobOpenings posted date
2. JobOpenings city
3. JobOpenings state
4. JobOpenings Title
5. JobOpenings link
- Quotes (content block):
1. quotes text
2. link

Figure 11: Join Our Team mega menu on the National Header
3.2.1.1.6.d Blog
Description
The Blog on the mega menu has two sub-menu under blog which are About Marketing Tango
and Recent Posts. About Marketing Tango will be a content block with a link to go to the
Marketing Tango external website. The Recent Posts will be a C# control to display the three (3)
recent blog posts that comes from an RSS feed.
Fields
1. Blog Image
2. Blog Title
3. Blog Date
4. Blog Link


Figure 12: Blog Mega Menu on the National Header
3.2.1.2 National Footer
The footer will be a fixed global element throughout the site. The same concept as the header,
the footer will be featured below the main content area on all site pages, regardless of content
layout; it may appear differently based on the width of the display resolution of a users device
and/or browser settings.
The latest tweets element will be filled with the latest three (3) twitter feeds from the Sir Speedy
Corporate Twitter account (https://twitter.com/sirspeedycorp).

Figure 13 : National Footer at 1024


Figure 14: National Footer at 760

Figure 15: National Footer at 480 and 320


3.2.2 National Unique Templates
3.2.2.1 Home Page
The HomePage will consist of the following elements:
Banner Slider
Products And Services Slider
WorldWide Locations
Statement Area
Case Studies slider
Briefs and Whitepapers / Join Our Team / Marketing Tango / Recent Jobs Area
Banner Slider
The Banner content will be managed through an Ektron Smart Form. The admin will create the
banners that can be used in the rotation and each banner will consist of the following fields:
1. Banner Index
2. Banner Image
3. Banner Background Image
4. Banner Text
5. Banner Link
The display of the banner will be different depending on the resolution of the users screen. At
widths of 1024, 880 and 760 pixels, the banner image will be aligned with the text as shown on
the figure below.

Figure 16: Banner at 1024, 880 and 760 pixels
At widths of 480 and 320 pixels, the banner image will be on top of the text as illustrated below.

Figure 17: National Banner at 480 and 320 pixels


Products and Service Slider
The Products and Services slider content will be managed through the Products and Services
Smart Form. The admin will create the products and services instance through the Ektron
workarea, and a C# control will be used to pull out fields that will be used in the products and
services rotation. Each Product and Services slider will consist of the following fields:
1. ProductsAndServices Index
3. ProductsAndServices Abstract
The same responsive concept as the HomePage banner also applies to this slider, where the
display of this slider will be varied depending on the detected resolution of a users device. The
display will be changed on the total products and services instances that will show up on the
home page. At width of 1024 pixels, the slider will show four (4) Products and Services instances
each time the user rotates the slider.

Figure 18: Products and Services Slider at 1024 pixels

While at a width of 880 pixels, the user can rotate three products and services at a time.




At width of 760 pixels, the user can rotate two (2) products and services instance at a time with a
larger sized image.

At width of 480 and 320 pixels, the user can rotate two (2) products and services instance at a
time with images being shown in vertical order.

Figure 21: Products and Services Slider at 480 and 320 pixels



Worldwide Location
The worldwide location area will be a content block with a link that will redirect the user to open
the Find A Location on the top menu at the site header.
Tagline Area
This element will be a content block which the national admin can manage from the Ektron
workarea.

Figure 22: Worldwide Locations and Statement Area at 1024, 880, and 760 pixels

Figure 23: Worldwide Locations and Statement Area at 480 and 320 pixels



Case Studies Slider
The Case Studies slider content will be managed through the Case Studies Smart Form. The
admin will create the CaseStudies instance through the Ektron workarea, and a C# control will be
used to pull out fields that can be used in the CaseStudies rotation. Each CaseStudies slider will
consist of the following fields:
1. CaseStudies Index
3. CaseStudies Url/Scribd Link
At width of 1024 pixels, the slider will show four (4) case studies instances each time the user
rotates the slider.

Figure 24: Case Studies Slider at 1024 pixels

While at width of 880 and 760 pixels, the user can rotate through three (3) case studies at a time.

Figure 25: Case Studies Slider at 880 and 760 pixels



At width of 480 pixels, the user can rotate through two (2) case studies instance at a time with a
larger sized image.


At width of 320 pixels, the user can rotate two (2) case studies instance at a time with images
being shown in vertical order.




Brief and Whitepapers Area
This element will be a control which will be managed through the BriefAndWhitepapers Smart
Form. The admin will create the BriefAndWhitepapers instance through the Ektron workarea, and
a C# control will be used to pull out some fields that can be used in the BriefAndWhitepapers
Html Area. Each BriefAndWhitepapers instance in the homepage will consist of the following
fields:
1. BriefAndWhitepapers posted date
2. BriefAndWhitepapers Image
3. BriefAndWhitepapers Title
4. BriefAndWhitepapers Teaser
5. BriefAndWhitepapers Link
Join Our Team Area
This element will be a content block that will be managed through the workarea. The admin will
create the Join Our Team instance, and a C# control will pull out the data to be displayed on the
site. The Join Our Team smart form will consist of the fields below:
1. JoinOurTeam Description
2. JoinOurTeam Image
3. JoinOurTeam link
Recent Jobs Area
This element will be a C# control which will pull out the data of some fields from the jobOpening
smart form, and display those data on the homepage. The fields that will be pulled out are:
1. jobOpening posted date
2. jobOpening City
3. jobOpening State
4. jobOpening Title
5. jobOpening Link
Marketing Tango Area
The Marketing Tango element will also be a C# control. It will pull out two (2) most recent rssfeed
data from marketing tango, and will display the following fields:
1. Blog Image
2. Blog Posted Date
3. Blog Title
4. Blog Teaser
5. Blog Link


Figure 28: Whitepapers, Join Our Team, Recent Jobs and Marketing Tango at 1024 pixels



Figure 29: Whitepapers, Join Our Team, Recent Jobs and Marketing Tango at 880 and 760 pixels







3.2.2.2 Company Info Landing Page
Description
The Company Info content will be managed through the CompanyInfo Smart Form. The admin
will create the CompanyInfo instance through the Ektron workarea, and a C# control will be used
to pull out some fields that can be used in the Company Info Landing Page.
At the bottom of the landing page, they will have a slider that will display all the Sir Speedys
Awards Recognition.
Fields
1. CompanyInfo Tagline
2. CompanyInfo Abstract
3. CompanyInfo Content
4. CompanyInfo Media Upload file (file path)
5. CompanyInfo Quotes

Figure 32: Company Info Landing Page



3.2.2.3 Management Team Landing Page
Description
The Management Team content will also be managed through the UserProfiles Smart Form. The
admin will create the UserProfiles instance through the Ektron workarea, and a C# control will be
used to pull out some fields that can be used in the Management Team Landing Page. If there is
no image available for a particular person, then the gender field will be used to determine which
generic image placeholder will be displayed for that team member.
Fields
1. userProfiles Image
2. userProfiles FirstName
3. userProfiles LastName
4. userProfiles JobTitle
5. userProfiles Gender
6. userProfiles Landing Page Link

Figure 33: Management Team Index Page



3.2.2.4 Individual Bio Landing Page
Description
This element will be a C# control that pulls some fields from the userProfiles Smart Form.
Fields
1. userProfiles Image (required)
2. userProfiles FirstName (required)
3. userProfiles LastName (required)
4. userProfiles Gender (required)
5. userProfiles OfficePhone
6. userProfiles Fax
7. userProfiles MobilePhone
8. userProfiles Email
9. userProfiles JobTitle (required)
10. userProfiles Roles (required)
11. userProfiles Bio
12. userProfiles Abstract (required)
13. userProfiles Twitter
14. userProfiles LinkedIn
15. userProfiles Facebook

Figure 34: Individual Management Team Landing Page



3.2.2.5 Partners Index landing page
Description
The Partners Index content will also be managed through the Partner Smart Form. The admin will
create the partner instance through the Ektron workarea, and a C# control will be used to pull out
some fields that can be used in the Partner Index Landing Page.
Clicking on a partners logo from the Partners page on the national site will display additional
information regarding the partner, including a link to the partners website in a new window.
Fields
1. Partner Name
2. Partner Tagline
3. Partner Description
4. Partner link URL
5. Partner Website link text
6. Partner Logo/Image

Figure 35: Partners Landing Page


3.2.3 Local (Model) Site Global Elements
3.2.3.1 Local Site Header
The header will be a fixed global element throughout the local/model site. It may appear
differently based on the width of the display resolution of a users device and/or browser settings;
however, It will be featured atop the main content area on all local site pages.
The same idea as the national site, at widths of 1024 and 880 pixels, the Local Site Header will
be a user control that will be included in the Master Page. Sir Speedy Local Header consists of
Request A Quote, Send A File, Subscribe, Social Media, Search, Contact Us, Shop Online, Sir
Speedy Logo, and Local Mega Menu Elements.

Figure 36: Local Header at 1024 and 880
Some elements in the local headers are the same as the national header, but the content of the
local site header will be determined by unique centerIds and unique hostnames that are
generated during the local site cloning process through the admin screen (refer to the admin
screen functionality specification document). For example, the products and services category
(and sub-category) under the local site mega menu might be different from one local site to
another. The available products and services category of one local site will be managed by the
national admin through the admin screen, and it will be varied throughout all local sites, depended
on the available products and services that are offered in a specific centers location.
Additionally, the difference between the local site header and the national headers include the
following elements:
1. Request A Quote with specific location
2. Subscribe - Pop Up Register Page
3. Portfolio Mega Menu
4. Contact Us
5. Shop Online
Local Sites Request A Quote
Unlike the National sites Request-A-Quote where the user searches for a location first, the Local
sites Request-A-Quote specifies the location and displays it in a map. Also, if the user is already
logged in, the system will pre-fill the users contact information in the form.

Figure 37: Local Sites Request A Quote Display


Local Sites Subscribe
This element is optional for franchisees to display on their local sites. If a franchisee decides to
display this element, customers will be able to subscribe to that franchisees newsletter. Clicking
subscribe on the top menu will open an Ektron form where the customers can enter their contact
information. If a customer already logged in, then the contact information fields will be pre-filled by
the system.
When the form is submitted, an email will be sent to the local site with a .csv attachment
containing the submitted information. Eachh local site admin can decide what to do with the .csv
attachment including importing the information into constantcontact.com or another contact
management system.
Fields
1. Email
2. FirstName
3. LastName
4. Address
5. City
6. State
7. Zip
8. Online Subscription
9. Print Subscription

Figure 38: Local Sites Subscribe Prompt


Local Sites Portfolio Mega Menu
The Local Sites Mega Menu includes the Portfolio menu, which is not part of the National Sites
Mega Menu. Franchisees will be asked to create Flickr accounts, and the images on the Flickr
site will be retrieved to fill up the megamenu on the local site with the latest four (4) images (refer
to section 2.4 - Integration With Flickr for details).
Portfolio Mega Menu Fields
1. Portfolio Image
2. Portfolio Title
3. Portfolio Teaser
4. Portfolio Link

Figure 39: Local Sites Portfolio Mega Menu
Local Sites Contact Us Landing Page
The local sites contact us will have two elements: an Ektron form that will allow the customer to
enter metadata, and a content block that will display the franchisees contact information. Once
submitted, the customer information along with the message will be sent to the local admins
email address.
Contact Us Ektron Form Fields:
1. First Name
2. Last Name
3. Email
4. Message

Figure 40: Local Sites Contact Us


Local Sites Shop Online Landing Page
The content of shop online element is generated from Ektron Smart Form Instances. Admins will
create each shopOnline Instance (grow with signs, promotional items, postcards, etc), and the
national admin will assign the appropriate item to one, many or all franchisees.
shopOnline Fields:
1. shopOnline Title
2. shopOnline Image
3. shopOnline Description
4. shopOnline link

Figure 41: Local Sites Shop Online

3.2.3.2 Local Site Footer
The latest tweets element will display the latest three (3) twitter feeds from a specific Sir Speedy
Franchisees Twitter account. However, if any franchisee does not have a twitter account, the
feed from the Sir Speedy Corporate Twitter account will be displayed.
Also, the local sites footer will show a fixed number of logos, and is managed by the center
admin (franchisee). Clicking on any of the partners logos in the footer will open up the website
associated with that partner in a new browser window.


Figure 42: Local Sites Footer at 1024 and 880
3.2.4 Local Site Unique Template
3.2.4.1 Local Homepage
Description
Local Site Homepage will consist of seven (7) elements which are: Banner Slide, Tagline area,
Products and Services Slider, Local Promotion, Your Location, Portfolio Slider, and Whitepaper
and Marketing Tango Area.
Local Banner Slider
Fields
1. Banner Index
2. Banner Background
3. Banner Image
4. Banner Text

Figure 43: Local Sites Banner Slider at 1024 and 880
Local Tagline
This element will be a content block which the national admin can manage from the Ektron
workarea
Fields
1. Tagline Text


Local Products and Services
The same idea as the National Site, the Products and Services slider content in the local site
homepage will be managed through the Products and Services Smart Form. The admin will
create the products and services instances through the Ektron workarea, and a C# control will be
used to pull out some fields that can be used in the products and services rotation. Each Product
and Services slider will consist of the following fields:
3. ProductsAndServices Abstract

Figure 44: Local Sites Tagline and Products and Services at 1024



Local Promotions
On the left-side of each Local Homepage, the admin can decide whether to display one (1) large
image, or two (2) smaller images. The national admin can create and maintain the local
promotions through the Ektron workarea (the franchisee admin can make a request to the
national admin to create a LocalPromotion Instance). Franchisees will be able to choose from the
list of local promotions (through the admin screens) to be made available for their site.
On the right-side of each Local Homepage, a C# control will take data from the franchisee
database to fill up the local address, abstract, local phone number, and a link to the Request-A-
Quote areas.
Fields:
1. LocalPromotion Image
2. LocalPromotion Link
3. LocalPromotion Title

Figure 45: Local Sites Local Promotions at 1024

Your Location
This element will display the detailed location information of a franchisee along with its contact
information such as address, phone numbers, email address, fax number, store hours, social
media links and direction.

Figure 46: Local Sites Your Location at width of 1024



Our Portfolio Slider
The Portfolio slider content will be managed through Flickr. C# control will be used to retrieve
some info from the Flickr that can be used on the Portfolio slider. The order of the image will be
based on posted date, and the admin will not be able to modify it without the assistance from the
support engineer. Each Portfolio slider will consist of the following fields:
1. Portfolio Image
2. Portfolio Link

Figure 47: Local Sites our Portfolio at width of 1024
Marketing Tango Area
The Marketing Tango element will also be a C# control that will pull out two (2) most recent
rssfeed data from marketing tango and will display the following fields:
1. Blog Image
2. Blog Posted Date
3. Blog Title
4. Blog Teaser
5. Blog Link
Brief and Whitepapers Area
This element will be a control which will be managed through the BriefAndWhitepapers Smart
Form. The admin will create the BriefAndWhitepapers instance through the Ektron workarea, and
a C# control will be used to pull out some fields from two (2) BriefAndWhitepapers Instances that
can be used in this section. Each BriefAndWhitepapers instance in the local homepage will
consist of the following fields:
1. BriefAndWhitepapers posted date
2. BriefAndWhitepapers Image
3. BriefAndWhitepapers Title
4. BriefAndWhitepapers Teaser
5. BriefAndWhitepapers Link

Figure 48: Local Sites marketing Tango and Whitepapers area at 1024


3.2.4.2 About Sir Speedy Landing Page
Description
The About Sir Speedy content will be managed through the AboutSirSpeedy Smart Form. The
admin will create the AboutSirSpeedy instance through the Ektron workarea, and a C# control will
be used to pull out some fields that can be used in the About Sir Speedy Landing Page.
At the bottom of the landing page, they will have a slider that will display all the Sir Speedys
Awards Recognition.
About Sir Speedy Fields:
1. AboutSirSpeedy Tagline
2. AboutSirSpeedy Abstract
3. AboutSirSpeedy Content
4. AboutSirSpeedy Video Upload file (file path)
5. AboutSirSpeedy Quotes.
Awards Fields:
1. Awards Index
2. Awards Title
3. Awards Description

Figure 49: Local Sites About Sir Speedy Landing Page at 1024


3.2.4.3 Why We Are Different Landing Page
Description
The Why We Are Different content will be managed through the OurStory and UserProfiles Smart
Forms, and the OurLocation content block. The admin will create the OurStory and userProfiles
instances through the Ektron workarea, and a C# control will be used to pull out some fields that
can be used in the Why We Are Different Landing Page.
Our Story Fields:
1. OurStory Tagline
2. OurStory Abstract
3. OurStory Content
4. OurStory Video Upload file (file path)
Our Team Fields:
1. userProfiles Image
2. userProfiles FirstName
3. userProfiles LastName
4. userProfiles JobTitle
5. userProfiles Phone Number
6. userProfiles Fax Number
7. userProfiles Email
8. userProfiles Gender
9. userProfiles Landing Page Link

Figure 50: Local Sites Why We Are Different Landing Page at 1024


3.2.4.4 Testimonials landing Page
Description
This element will be created and managed as a smart form instance in Ektron. The admin will
create the Testimonials instance through the Ektron workarea, and a C# control will be used to
pull out some fields that can be used on Testimonials Landing Page.
Fields
1. Testimonials FirstName
2. Testimonials LastName
3. Testimonials Text
4. Testimonials Organization
5. Testimonials Image

Figure 51: Local Sites Testimonials Landing Page at 1024


3.2.4.5 Portfolio Landing Page
Description
This element will also be created and managed through Each Center Flickr account. All admin
tasks will be completed through Flickr API (details in 2.3.3.1). A C# control will be used to pull out
some fields that can be used on Portfolio Landing Page. Clicking on the picture will open the
detail portfolio page as a pop-up window which also a slider as you click the next or previous
arrow.
Fields
1. Portfolio Image
2. Portfolio Title
3. Portfolio Abstract
4. Portfolio Url

Figure 52: Local Site Portfolio Landing (Index) Page at 1024


Figure 53: Local Site Portfolio Prompt Page at 1024

3.2.5 General Page Templates
General templates are the templates that shared the same front-end design and back-end
structure. It may have different content depends on the Unique ID of each content in Ektron
Workarea. Also, for the following templates, Although they will have different content depend on
the locals availability of related site content, both National and Local site will use the same
template since they share the same design and functionality.


3.2.5.1 Products & Services Category Index Landing Page
Description
The products and services category index template will be filled with data from the
ProductsAndServices Smart Form Instances.

Figure 54: Products And Services Index Page at 1024


3.2.5.2 Products & Services Category Detail Landing Page
Description
This element will not only display the detail data related to each products & services category, but
also the related case studies, blog and whitepapers for each products & services category.
ProductsAndServices Fields:
2. ProductsAndServices Category Title
3. ProductsAndServices Category Sub-title
4. ProductsAndServices Category Image
5. ProductsAndServices Category Url
6. ProductsAndServices Category Tagline
7. ProductsAndServices Category Teaser
8. ProductsAndServices Category Content
9. ProductsAndServices Category Quotes
10. ProductsAndServices Category Quotes_By
11. ProductsAndServices Category Quotes_Organization
12. ProductsAndServices MarketingTango DisplayText and Link
13. ProductsAndServices Sub-Categories content type
14. ProductsAndServices Category Related Case-Studies


Figure 55: Products and Services Category Landing Page


3.2.5.3 Products & Services Sub-Category Detail Landing Page
Sub-Category Fields:
1. ProductsAndServices SubCategory Index
2. ProductsAndServices SubCategory Title
3. ProductsAndServices SubCategory Sub-title
4. ProductsAndServices SubCategory Image
5. ProductsAndServices SubCategory Tagline
6. ProductsAndServices SubCategory Teaser
7. ProductsAndServices SubCategory Content
8. ProductsAndServices SubCategory Quotes
9. ProductsAndServices SubCategory Marketing Tango Display Text and Link
10. ProductsAndServices SubCategory Related Case Studies


Figure 56: Products and Services Sub-Category Landing Page


3.2.5.4 News Index Landing Page
Description
The news index content will be managed through the News Smart Form. The admin will create
each news instance through the Ektron workarea, and a C# control will be used to pull out some
fields that can be used in the News Index Landing Page.
This page will list all the available news related to Sir Speedy. The customer can access each
news item by clicking on the read more button which will redirect them to that items news
landing page
Fields
1. News Title
2. News Posted Date
3. News Teaser
4. News Link
5. News City
6. News State
7. News Image

Figure 57: News Index Page


3.2.5.5 News Detail Page
Description
This page will display the detail content of each News Instance on the site.
The customers will be able to see the title of the next/previous news by hovering their cursor on
the arrow button.
Fields
1. News Title
2. News Teaser
3. News Content
4. News Posted Date
5. News Link
6. News City
7. News State
8. News Image

Figure 58: News Landing Page


3.2.5.6 In The Media Index Page
Description
The In The Media index content will be managed through the InTheMedia Smart Form. The
admin will create each InTheMedia instance through the Ektron workarea, and a C# control will
be used to pull out some fields that can be used in the InTheMedia Index Page.
This page will list all the available news in the published media related to Sir Speedy. Each
customer can access each news by clicking on the read more button that redirect them to each
Press Release In the Media.
Fields
1. InTheMedia Title (required)
2. InTheMedia Posted Date (required)
3. InTheMedia Source (required)
4. InTheMedia Link (required)
5. InTheMedia Image

Figure 59: In The Media Index Page


3.2.5.7 Insights Whitepapers index Page
Description
The Whitepapers index content will be managed through the Whitepapers Smart Form. The
admin will create each Whitepapers instance through the Ektron workarea, and a C# control will
be used to pull out some fields that can be used in the News Index Landing Page.
This page will list all the available whitepapers and the customer can access each whitepaper by
clicking on the read more button that redirects them to each whitepaper landing page.
Fields
1. Whitepapers Title
2. Whitepapers Abstract
3. Whitepapers Link
4. Whitepapers Image

Figure 60: Whitepaper Index Page


3.2.5.8 Insights Whitepapers Detail Landing Page
Description
This page will display the detail content of each Whitepapers instance on the site. Also, in order
to download whitepapers, the customer will be prompted to enter their information through an
Ektron form. If the customer already logged in, the contact information fields will be pre-filled by
the system. In the national site, if the form is submitted from the national site, the email containing
the form submission information will be sent to the national site.
There are two different forms that are available, the long form (Figure 61.b) and the short form
(Figure 61.a); but the system will only display one form depend on whether a user has visited the
whitepapers page. When a user first visits a whitepaper detail page, they see the long form. If the
user fills out the form and downloads any whitepaper, the short form will be displayed for that
particular user for the next 24 hours since his/her last download.
Fields
1. Whitepapers Title
2. Whitepapers Abstract
3. Whitepapers Description
4. Whitepapers Link
5. Whitepapers File
6. Whitepapers Image

Figure 61.a: Whitepaper Landing Page with Short Form



Figure 61.b: Whitepaper Landing Page with Long Form

3.2.5.9 Insights Case Studies Index Page
Description
The Case Studies index content will be managed through the CaseStudies Smart Form. The
admin will create each CaseStudies instance through the Ektron workarea, and a C# control will
be used to pull out some fields that can be used in the Case Studies Landing Page.
This page will list all the available case studies and the customer can access each case study by
clicking on the image that redirects them to each case studiess landing page.
Additionally, case studies will be able to be associated with one or more product categories
and/or subcategories. The national admin can manage the relation between product categories
and case studies through the admin area (refer to separate document - SirSpeedy Admin Screen
Detailed Requirement document). Case studies will be entered using Scribd and registered with


the Ektron CMS using a smart form so that the case study can be referenced and displayed on
the website. Case studies can also be associated with blog categories.
Fields
2. CaseStudies Abstract
3. CaseStudies Link

Figure 62: Case Studies Index Page
3.2.5.10 Insights Case Studies Landing Page
Description
This page will display the detail content of each CaseStudies Instance on the site and will be
displayed by using scribd.
Fields
2. CaseStudies Abstract
3. CaseStudies Link
5. CaseStudies File



Figure 63: Case Studies Landing Page

3.2.5.11 Jobs At Sir Speedy Landing Page
Description
This element will be managed through the Ektron workarea by maintaining JobsAtSirSpeedy and
the Department Smart form to fill up some elements on this page. A content block will be used to
fill the tagline area.
Fields
Why Work With Us Fields:
1. JobsAtSirSpeedy Sub-Title
2. JobsAtSirSpeedy Teaser
3. JobsAtSirSpeedy Content
Job Profiles Fields:
1. Department Name
3. Department Image
4. Department Link



Figure 64: Jobs at Sir Speedy Landing Page
3.2.5.12 Job Profiles Index Page
Description
This element will contain some fields of the Department smartform to define each Department
tab, two content blocks for the tagline, and a table that lists all current job openings based on
each department.
Clicking on each Job Opening will redirect the user to a Job Profiles Landing Page (detail in
3.2.5.13).
Fields
1. Department Name
3. Department Image
4. Department Link



Figure 65: Job Profiles Index Page
3.2.5.13 Job Profiles Landing Page
Description
The Job Profiles Landing Page content will be managed through the JobOpenings Smart Form.
The local admin (Franchisees) will create each JobOpenings instance through the Admin Screens
which will be treated as instances of JobOpenings smart form when national admin manage the
site through Ektron Workarea. A C# control will then be used to pull out some fields that can be
used on the Job Profiles Landing Page.
Fields
1. JobOpenings Title
2. JobOpenings Department
3. JobOpenings Overview
4. JobOpenings Posted date
5. JobOpenings Qualification


6. JobOpenings Skills
7. JobOpenings Salary
8. JobOpenings Address
9. JobOpenings City
10. JobOpenings State
11. JobOpenings Contact
12. JobOpenings Application Link

Figure 66: Job Profiles Landing Page
3.2.5.14 Privacy Policy Footer Content Landing Page
[pending]
3.2.5.15 Terms & Conditions Footer Content Landing Page
Description
The Terms & Conditions Footer Content will be managed as a content block. The admin will
create a content block instance through the Ektron workarea, and a C# control will be used to pull
out some fields that can be used on this Landing Page.


Figure 67: Terms & Condition Footer Landing Page



3.2.5.16 Environmental Message Footer Content Landing Page
[pending]
3.2.5.17 SiteMap Footer Content Landing Page
[pending]
3.2.5.18 Register Landing Page
Description
Any new customers, who would like to send-a-file for the first time, will have to either sign up
through their social media account or register by using their email address. Register landing page
will be the page where Fig Leaf will create an Ektron Form to allow the user enter their
information. The information will be save into the users customize database, which then will be
used to authenticate a user login.
Fields
1. Center Location
2. First Name (required)
3. Last Name (required)
4. Email Address (required)
5. Phone Number (required)
6. Job Title
7. Company
8. Worksite
9. Username (required)
10. Password (required)
11. Confirm Password (required)



Figure 5.3: Register Form



4. ADDITIONAL FUNCTIONALITY
4.1 Page Translation
Translation functionality should be available at the page level to allow content to choose the
language(s) into which any particular page could be translated. Google Translate API will be
used to translate the page in real time after the English version of the page has been displayed.


5. DEVELOPMENT REQUIREMENTS
5.1 Operational Requirements
The system will be developed by FranServ on servers provided by FranServ for the purpose of
hosting the new Ektron SirSpeedy website. Fig Leaf recommends the following software be
installed on these servers including the latest versions of .Net Framework (.Net 4.5), and SQL
server database software.

5.2 Platforms and Browser Support
5.2.1 Authoring
Ektron acknowledges the following browsers as those known to support ektrons core features.
OPERATING SYSTEM BROWSER VERSIONS
Windows XP Internet Explorer 8.0 or higher
Mozilla Firefox 10.0 or higher
Google Chrome 15.0 or higher
Windows Vista Internet Explorer 8.0 or higher
Windows 7 Internet Explorer 8.0 or higher
Mac OS X 10.6 or higher Mozilla Firefox 10.0 or higher
Safari 5.0 or higher

5.2.2 Viewing/Browsing
Use of the site will be supported for the following operating system and browser version
combinations.
OPERATING SYSTEM BROWSER VERSIONS
Windows XP Internet Explorer 8.x
Windows Vista Internet Explorer 8.0 or higher
Windows 7 Internet Explorer 8.0 or higher
Mac OS X 10.6 or higher Mozilla Firefox 15.0 or higher
Safari 5.0 or higher
Mobile Android 2.33
iPhone 3+



6. DOCUMENT APPROVAL
Upon signature below, FranServ and Fig Leaf fully accept the functional requirements and any
specifications documented herein, and authorize the initiation of work based on the development
guidelines they constitute.

Additionally, FranServ and Fig Leaf fully acknowledge and accept that changes to the functional
requirements and/or specifications described herein, or changes to design requirements that
affect these functional requirements and/or specifications, that are requested or made after
signature of these Requirements, may significantly affect any project timelines based upon this
document. Therefore, FranServ and Fig Leaf shall evaluate any such changes on a per-instance
basis to determine whether incorporation is acceptable, a modification order is warranted, and/or
adjusting the project timeline accordingly is required.

FIG LEAF SOFTWARE, INC. FRANCHISE SERVICES, INC.
Signature:
_______________________________

Name:
_______________________________

Title:
_______________________________

Date:
_______________________________
Signature:
_______________________________

Name:
_______________________________

Title:
_______________________________

Date:
_______________________________


APPENDIX A -

Printed Pieces That Meet Multiple Needs

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Printed Pieces That Meet Multiple Needs

Hochgeladen von

Copyright:

Verfügbare Formate

April 28, 2014

Fourth Draft - Sir Speedy

Das könnte Ihnen auch gefallen