Embed Size (px)
Citation preview
How to become a hero to the marketing team (or business users)......by using the work of others
Daniel Lipp
Magnolia International Ltd.
378
2
AGENDA
> Virtual Presence
> How can it be achieved
> The technical Challenge
> See it with a fresh eye
> The Non-technical Challenge
> Conclusion
3
Intro
> Magnolia International Ltd.
– ~ 40 employees: Basel, US, Czech, Sweden, Spain…
– Open Source CMS since 2003
– Selection of Customers:
4
> There’s things you can do via the web
– But there’s others that you can’t yet
Physical vs. Virtual Presence
5
Virtual Presence Management
> What is it about
– Virtualize as much business services as possible
– Generate Business (surprise!)
> Benefits
– More convenient/efficient for the user
– Better scaling
– Bigger turnover
– Less “physical” costs
6
> Urge to increase Virtual Presence
– Marketing (and business users) want to offer more services via Web
– Integrating CMS and business Applications is a must
Development in Virtual Presence
7
CMS Application(s)
Integration options
8
> You might realize you
– Should re-style your app (one look and feel)
– Have to support many browsers
– Want to be benefit from search engines
– Want to use latest browser functions
– Want to have special treatments for Mobiles
The technical Challenge
APP
9
> Promising on a first sight
– But then…
Pimping the Apps
10
Wait a minute…
> CMS’s can…
– Handle JS, HTML5, CSS, SEO, Security,…
– Separate content from logic
> And have further features like
– Caching
– Mobile publishing
– Data storage
11
> Let’s change perspective
– How do things look from the other side?
See it with a fresh eye
12
CMS Application(s)
We were checking Integration options
13
> It should
– Use known technology stack
– Use a templating approach
– Support mobile publishing
– Have a plugin mechanism
– Offer multiple integration options
– Perform/scale well
Internals of an open, extendable CMS
14
> Technology stack
– Java, Servlet API
– Freemarker/JSP Templating
– Java Content Repository (JCR) Storage
– Soon: Vaadin Administration Console
Let‘s take the example of Magnolia CMS
15
Re-use business logic…
> Model based templating
16
Re-use business logic…
> Templating variations
– Define just the variations e.g. for mobile devices
websites
Mobile version of pages based on same content
17
Create Websites using Spring
> The Blossom module: turn Magnolia into a Spring App
– Create websites the Spring way
– Don’t configure but code your Dialogs
– Validate dialog input
– Create multi-step forms (Spring Web MVC)
– Reuse Spring controllers
– …
18
Embed whole Applications
> The OpenSocial Module: host an OpenSocial portal
– Add OpenSocial Container paragraph
– Converted GWT apps to OpenSocial Gadgets (few lines of XML)
– Add OpenSocial Container to the Webpage
– DONE!
19
Embed whole Applications…
> What’s OpenSocial?
– Pluggable gadget architecture + Social API
– Used by most major social networks
– Evolves in Enterprise direction
– A client-side Portal!
20
Embed whole Applications…
> Why a client-side portal?
– It’s more open!
21
> From a Developers Perspective
– Marketing requirements change frequently
> From a Marketing Perspective
– Releasing is just not fast enough
The Non-technical Challenge
22
Time for a
23
The Conclusion
> Using the right CMS you can
– Re-use business logic
– Embed whole Applications – the right way!
– Augment your organizations Virtual Presence
– Separate Content from Logic
– Optimize time & material
– Impress your Marketing and Business
24
THANK YOU FOR YOUR ATTENTION
