Adobe Experience Manager (AEM)as.nyu.edu/content/.../documents/AEM_Implementation... · Adobe...

Post on 05-Aug-2020

5 views 0 download

transcript

4/12/17 1

Adobe Experience Manager (AEM)

Before We Begin •  Please silence your devices •  Please refrain from checking email during the presentation

Objectives

2

4/12/17 3

Redesign & Migration Overview

NYU Faculty of Arts and Science current web presence:

•  Arts and Science umbrella site •  Graduate School of Arts and Science •  College of Arts and Science •  Liberal Studies

Redesign & Migration Overview

4

All sites in the following subdomains are migrating:

•  as.nyu.edu (name.as.nyu.edu) •  gsas.nyu.edu (name.gas.nyu.edu) •  cas.nyu.edu (name.cas.nyu.edu) •  ls.nyu.edu (name.ls.nyu.edu) •  fas.nyu.edu is no longer a valid subdomain

[update all communications]

Redesign & Migration Overview

5

Sites which will remain unchanged:

•  NYU WordPress sites (wp.nyu.edu/name) •  I4 server sites (nyu.edu/as/name) •  NYU blog sites (blogs.nyu.edu/name) – this service is retired •  All .org and .com sites

Redesign & Migration Overview

6

The Numbers

•  Approximately 100 websites that represent A&S departments, programs, centers, institutes and international houses

•  35,000 pages, give or take

Redesign & Migration Overview

7

The Redesigned Front End Includes…

Redesign & Migration Overview

8

…Integration of NYU visual identity guidelines and standards,

Redesign & Migration Overview

9

…Incorporation of NYU global navigation,

Redesign & Migration Overview

10

…Single site presence,

Redesign & Migration Overview

11

…and, Responsive design.

Redesign & Migration Overview

12

Timeline

Redesign completed Construction completed Content migration & “soft launch” completed Training January & February 2017 Content clean up January through May 2017 Launch of websites to public June 2017

Redesign & Migration Overview

13

Redesign & Migration Overview

14

Placeholders:

Please remove/update all placeholder content and imagery during site review!

Lorem ipsum dolor sit amet, consectetur adipiscing elit.

4/12/17 15

Fundamentals of AEM

What is Adobe Experience Manager (AEM)?

•  Part of Adobe Marketing Cloud •  A web-based system for content creation, management,

and publishing

Fundamentals of AEM

16

Compatible with all browsers:

We recommend Chrome!

Fundamentals of AEM

17

Fundamentals of AEM

18

Authors can create and edit content

Approvers review, activate and publish content in addition to

creating and editing

There are two role types in AEM:

Templates

17

Templates: •  Re-usable page layouts, i.e. Faculty Profile page •  Comprised of components that are built-in •  Some templates can be added customized with extra components •  Template assignments are permanent

Components

20

Components: Designed to present specific types of content including: •  Text Block •  Links •  News •  Images •  Videos

4/12/17 21

Site Architecture & Navigation

Site Architecture & Navigation

22

Parent Sites Individual Sites Child Pages

A&S sites are organized in a tree structure under the 4 Parent Sites: •  Arts & Science (A&S) •  Graduate School of Arts and Science (GSAS) •  College of Arts and Science (CAS) •  Liberal Studies

Site Architecture & Navigation

23

Parent and Child Pages

Site Architecture & Navigation

24

A page can be simultaneously a parent and a child. If a page is deleted or moved, so are all of its children.

Site Architecture & Navigation

25

Dynamic Navigation When a page is added to the tree, it is automatically added to the navigation

4/12/17 26

Digital Asset Management (DAM)

Digital Asset Management

27

Digital Asset Management (DAM) •  Images, videos, audio files, and

documents (including PDF, Excel, and Word) are called Assets which live in a centralized and shared repository

•  Once uploaded, an asset may be referenced many times

Organization is critical •  Use folders and create

subfolders as necessary

•  Use human-readable and searchable file names

•  Image and document files not larger than 2MB

Digital Asset Management

28

Demo: Sites/Assets Console UI Page Editor UI/Components Blank Page with Title Upload image to DAM Article Page Publish, Move/Rename, Hide, Delete

29

4/12/17 30

User Interface

User Interface

31

Sites Console

Action bar

Content area

Global navigation bar

Left Hand Rail

Content area

User Interface

32

Assets Console

Action bar

Global navigation bar

Left Hand Rail

4/12/17 33

Faculty Directory & Course Listing

Faculty Directory

Faculty Directory page Faculty Profile pages

55

Faculty Directory •  Contents automatically generated from central directory

•  Faculty profile pages are shared

•  Access to edit profile pages must be requested

Faculty Directory

35

Course Listing

52

Course Listing

53

Course Listings

•  Contents of Course Listing Page derived from its child pages

•  Course Detail Pages are automatically created using a daily query from UDW

•  These pages cannot be edited in AEM; updates must be made in Albert

4/12/17 38

Events

Events

Event Listing Page Event Detail Pages

111

Events created in AEM can be pushed to LiveWhale

Events

40

4/12/17 41

Best Practices

Content Creation for Mobile: •  The AEM sites support 3 breakpoints:

Desktop, Tablet, and Mobile •  Remember that mobile has limitations

(screen size and bandwidth) •  Prioritize content ruthlessly!

Best Practices

42

Best Practices

43

URL Nomenclature: •  Keep the URL short and lowercase •  No special characters •  Use dashes rather than underscores •  Try to keep the URL limited to a maximum of five levels •  Ensure the URL matches the directory structure •  Human-readable URLs are more likely to be listed at the top of search

results page

Do’s:

• Keep content as relevant and concise as possible• Leverage visuals• Be cognizant of page length• Reduce the amount of scrolling needed to access content• Keep formatting clean and simple• Think about where you put new pages in the content tree

Best Practices

44

Don’ts: •  Bring in inconsistent/foreign styling •  Use pages as a historical archive •  Use tables – these break down on mobile devices •  Use short text links rather than long URL paths:

i.e. ‘GSAS Standing Committees’ rather than ‘http://gsas.nyu.edu/page/grad.aboutgsas.standingcommittees’

Best Practices

45