Preserving the iMIS Upgrade Path

10
Upgradeable Public Websites Jeffrey Skillman Andrea Robertson

Transcript of Preserving the iMIS Upgrade Path

Page 1: Preserving the iMIS Upgrade Path

Upgradeable Public Websites

Jeffrey Skillman

Andrea Robertson

Page 2: Preserving the iMIS Upgrade Path

Topics to discuss

• Concepts and Terminology• iMIS Sites vs. Customer Sites• System Content vs. Customer Content• Copying Websites• Using Shortcuts • Managing Themes• What’s Next?

Page 3: Preserving the iMIS Upgrade Path

Concepts & Terminology

• Website• Sitemap (Navigation)• Content

– System (Core and Samples – can only be copied)– Shared (single source used by multiple sites)– Website-specific (unique to one website)

• Shortcuts– All Sites– Site-specific

Page 4: Preserving the iMIS Upgrade Path

iMIS 20 ships with two folders for organizing system websites

Core Sites - generally staff-facing

Sample Sites – quick-start sites for easy creation of public sites

iMIS website vs. Customer website

Page 5: Preserving the iMIS Upgrade Path

iMIS 20 also ships with two folders for organizing system content

Core Content – common pages employing iMIS Dynamic Content Items for out-of-the-box iMIS functionality

Sample Websites – website-specific pages used by the out-of-the-box quick start sites

Shared Content – repository for customer-created shared pages

Core Content vs. Shared Content

Page 6: Preserving the iMIS Upgrade Path

Copying a Website

Copying a Sample Site provides clients with the fastest way to create a new functioning website.

If you do not need a starter website, you can create a new website from scratch.

Page 7: Preserving the iMIS Upgrade Path

• What is copied– Website definition– Sitemap– Website-specific

content

• What is not copied– Core content– Shared content– Shortcuts– Master page– Theme

Copying a Website

Page 8: Preserving the iMIS Upgrade Path

Shortcuts

• Provide friendly URLs• System-referenced pages

• Provided out-of-the-box – can be edited but not deleted

• Customer-defined• Can be defined for All Sites (default)

or site-specific

Page 9: Preserving the iMIS Upgrade Path

Managing Themes

• Use UltraWave!– Import UltraWave files using @import or

<link> statements

• On upgrade copy .skin files and images from original theme

Page 10: Preserving the iMIS Upgrade Path

What’s Next?

• Easy sitemap management• Let’s get sassy!