Preserving the iMIS Upgrade Path
•Descargar como PPTX, PDF•
0 recomendaciones•525 vistas
Follow these best practices to build your iMIS website in a way that is easily upgradable and adheres to best practices.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a Preserving the iMIS Upgrade Path
Similar a Preserving the iMIS Upgrade Path (20)
Más de Andrea Robertson
Más de Andrea Robertson (11)
Último
Último (20)
Preserving the iMIS Upgrade Path
- 1. Upgradeable Public Websites Jeffrey Skillman Andrea Robertson
- 2. 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?
- 3. 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
- 4. iMIS website vs. Customer website 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
- 5. Core Content vs. Shared Content 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
- 6. 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.
- 7. Copying a Website • What is copied – Website definition – Sitemap – Website-specific content • What is not copied – Core content – Shared content – Shortcuts – Master page – Theme
- 8. 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
- 9. Managing Themes • Use UltraWave! – Import UltraWave files using @import or <link> statements • On upgrade copy .skin files and images from original theme
- 10. What’s Next? • Easy sitemap management • Let’s get sassy!
Notas del editor
- Website Defines a front-end URL for targeted users Provide a unique look & feel (branding) Restrict access to specific users/groups Provide a unique navigation structure Sitemap One sitemap per website Can provide different navigation for different user groups – within the same website (e.g., Staff/Authenticated/Unauthenticated) Map navigation to different content for different user groups Override behavior of shared content (iParts) when accessed via specific navigation Override ContentArea source folder (look & feel elements) Content Core – standard out-of-the-box iMIS pages providing core functionality (are generally shared across multiple websites) Shared – pages that are shared across multiple websites so layout and content changes can be made in one place Website-specific – pages that are designed specifically for the needs of a single website (may still be shared with others) Shortcuts Provide friendly URLs (e.g., www.MyOrg.org/AnnualConference, www.MyOrg.org/Events, www.MyOrg.org/Join) Frequently-access system pages (e.g., SignIn, EventDisplay, ItemDisplay, AccountPage) Provided out-of-the-box – can be edited but not deleted Default to All Sites (shared) but can be Site-specific Client-defined (can be All Sites or Site-specific)
- All system websites will be overwritten by Upgrade All Customer websites will be stored in the root Websites folder and will not be affected by upgrades The iMIS Web View will not be a Core website and will not be updated by upgrade
- Website-specific pages used by customer-created websites should be saved in the website-specific content folders
- No new shortcuts will be added and existing shortcuts will not be modified.
- Provide friendly URLs (e.g., www.MyOrg.org/AnnualConference, www.MyOrg.org/Events, www.MyOrg.org/Join) Frequently-access system pages (e.g., SignIn, EventDisplay, ItemDisplay, AccountPage) Provided out-of-the-box – can be edited but not deleted Default to All Sites (shared) but can be Site-specific Client-defined (e.g., Professional Biographies) Any All Sites shortcuts will not be changed by upgrade
- Provide friendly URLs (e.g., www.MyOrg.org/AnnualConference, www.MyOrg.org/Events, www.MyOrg.org/Join) Frequently-access system pages (e.g., SignIn, EventDisplay, ItemDisplay, AccountPage) Provided out-of-the-box – can be edited but not deleted Default to All Sites (shared) but can be Site-specific Client-defined (e.g., Professional Biographies) Any All Sites shortcuts will not be changed by upgrade
- Provide friendly URLs (e.g., www.MyOrg.org/AnnualConference, www.MyOrg.org/Events, www.MyOrg.org/Join) Frequently-access system pages (e.g., SignIn, EventDisplay, ItemDisplay, AccountPage) Provided out-of-the-box – can be edited but not deleted Default to All Sites (shared) but can be Site-specific Client-defined (e.g., Professional Biographies) Any All Sites shortcuts will not be changed by upgrade