measure twice, cut once

DD.MM.YYYY at Venue/Customer First Last, Role

Measure Twice, Cut Once The Impact Detailed Planning and Execution May Have on Your CMS Project

1 Version 1.1 Magnolia is a registered trademark owned by Magnolia International Ltd.

SRA and NRG Edge Date: 2.19.2014

§  Abigail Barlow – SRA International

§  Senior Analyst §  SRA Magnolia project lead §  [email protected]

§  Lucero Carmona – NRG Edge

§  Web Developer

2

Introductions

Version 1.1 Magnolia is a registered trademark owned by Magnolia International Ltd.

§  Asking a Question…

§  Project overview and planning strategies

§  Creating an Answer…

§  Development strategies: STK custom extensions, themes, CSS

§  Custom development highlights

§  Best practices: Positioning the app for upgrade to 5.0

§  Site Demo

3

Agenda


§  Make a plan!

§  Don’t reinvent the wheel

§  Speak “Magnolia” in your requirements and specs

§  Prioritize elements from requirements

§  Extend as much as possible

4

Things to Take Away



Project Overview and Planning

§  Who are we?

§  Cyber Security – TSA SOC

§  What did we need?

§  Presentation layer

§  Multiple portals for multiple customers managed from one platform

§  Why Magnolia?

6

Use Case


§  Goal: Replace and improve current portal solution

§  Business Requirements §  Retrofit existing requirements and design enhancements

§  Caveat: No “customization”

§  Caveat: Accommodate rapid change (both content and context)

§  Development: partnership with NRG

§  Deployment: this project is ongoing as we roll out in multiple releases

7

Project Definition


§  Site Design

§  Information Architecture (IA)

§  Wireframes

§  User Experience (UX)

8

Site Planning and Site Design


§  Page Layout

§  Main Template

§  Page Design

§  Areas

9

Page Layout and Page Design


10

PSDs and Prototypes


§  Breaking down the STK

§  Create an STK Catalog

§  Reverse Engineer

§  Reconstructing the STK

§  Create Photoshop documents (PSD’s) and prototypes

§  Isolate any custom functionality

11

Requirements Development and Specs


§  PSD to Requirements

§  Speak “Magnolia”

§  Specs to development - NRG


Development

13

Requirements


§  Using existing STK CSS to accommodate and focus on:

§  Browser Requirements

§  Multisite

§  Responsive Design

14

Division of Stylesheets


§  Based on pop theme

§  Split main CSS into two concepts:

§  Unique color/images

§  Non-changing elements

§  Nine CSS Files

15

Themes


§  Creation of four themes

§  One default theme

§  Three subsite themes

§  Extends default theme

§  Declares unique styles

Templates

§  Total of 13 templates

§  Pages and components extended existing elements

§  Encouraged quick development

§  Good base for future upgrades


17

Public Login Page


§  Customized login component from stkPublicUserRegistration

§  Extended stkPURLoginForm component definition

§  Disable Page Navigation

§  Limit component availability to customized login form component

§  Extended RedirectClientCallback to direct user to correct login or forbidden page

18

Forbidden Page


§  Extension of stkPublicUserRegistration

§  Disabled Page Navigation

§  Limit component availability to Text and Image

19

Document Search


§  Extension of the SearchResultsModel

§  Allow for return search form entries

§  Criteria

§  Published on Date §  Range of Dates

§  File Name

§  Keyword or Phrase

§  Specific Folder in DMS

20

Structure of Website Tree


§  Root Nodes for each site

§  Content

§  Login

§  Forbidden Page

§  Security Purposes

§  Structure reflected in site definitions

21

Structure of Documents


§  One folder for each multisite

§  Security Purposes

§  Subfolder split into graphics and a deliverable library of searchable reports

22

User Permissions


§  Limiting access to particular site/dms

§  Creation of roles

§  Setting up of users

§  Process of Public Login

§  Redirects from Forbidden pages

23

Best Practices


§  Positioning for upgrading to Magnolia 5

§  Extension of base STK

§  Customized small amounts of templates

§  Heavily relied on themes for each subsite


Site Demo


Questions?

measure twice, cut once

Technology