The document discusses building mobile websites using SDL Tridion. It describes a project to build mobile sites for a software company, including content workshops, templates, and blueprint modifications. It outlines problems with content not fitting mobile devices and a tightly coupled blueprint. The presentation emphasizes the importance of blueprint structure for flexible content between web and mobile, and provides examples of ideal blueprint scenarios. It also discusses options for mobile development and tools like NetBiscuits and SDL Tridion Mobile Preview.

1. Tridion
Toronto
User
Group
Building
mobile
websites
plus
some
other
helpful
and
cool
SDL
Tridion
stuff

2. Hello
and
Thank
you
• We
are
Content
Bloom
• Offices
in
Canada
and
Belgium
• Core
team
made
up
of
experienced
SDL
Tridion
consultants
• contentbloom.com
&
@contentbloom

3. We’ll
be
talking
about
• A
liJle
about
what
we
did
(don’t
worry
it
wont
be
a
sales
pitch)
• The
main
problems
we
faced
• Important
points
for
geNng
started
• Some
cool
SDL
Tridion
stuff
we
wish
we
had
the
opportunity
to
use

4. We
won’t
have
Pme
for
• How
to
technically
build
mobile
websites
• Sniffing
devices,
Mobile
OS
differences
• Business
requirements
• What
should
a
mobile
site
do
versus
other
channels
e.g.
Desktop
Later
over
drinks,
we
can
talk
about
whatever
you
like!

5. What
we
recently
did
• Built
and
developed
mobile
websites
for
a
global
soUware
company
– Partner
agency
built
mobile
skin
and
defined
requirements
– We
did
all
the
SDL
Tridion
development
stuff
• Content
workshops
–
what’s
relevant
for
mobile
• Templates
• Blueprint
modificaPons

6. Problems
we
had
• Some
content
didn’t
fit
for
mobile
devices
– 4500+
Video
conversaPons
(FLV
to
MP4)
– Modal
windows
– Image
sizing
for
mobile
pla`orms
– BluePrint…

7. Tightly
coupled
Blueprint
• Content
and
Root
structure
created
at
the
same
level
in
the
Schema
blueprint
Design & Layout
Content and
Structure

8. BluePrint
–
What
that
means
Root
Schema
All
or
nothing
technical
stuff

Design & Layout
Website
content
and
Localised Content and structure
created
in
the
Mobile design Structure same
publicaPon

Stuff
we
added

Mobile website

9. The
most
important
point
• To
allow
flexible
structuring
of
content
between
web
and
mobile
devices
• The
BluePrint
structure
is
key
to
enabling
this..

10. Ideal
BluePrint
scenario
Root
01 Schema
Shared
stuff
02 Common
02 Master content
design
03 Browser
03 Browser design 03 Mobile content 03 Mobile design
content
Browser
stuff
04 Browser Mobile
stuff
04 Mobile website
website

11. If
you
have
nothing,
what
next?
• OpPons
for
development
– Cheapest
OpPon
• Do
absolutely
nothing,
phones
are
capable
of
displaying
most
mobile
websites
• Flash
excepPons
of
course!
– Small
budget
• Making
some
minor
tweaks
maybe
some
responsive
design
-­‐
will
do
for
now
Pll
we
build
something
beJer
– All
the
money
in
the
world!!
• Full
scale
operaPon

12. All
the
money
in
the
world
• Number
of
devices
conPnues
to
grow
• Development
frameworks,
technologies
and
best
pracPces
are
constantly
evolving
• SDL
has
some
tools
to
help
make
life
easier.

13. SDL
Tools
:
Netbiscuits
• Net
Biscuits:
– Mark-­‐up
language
and
tools
to
ensure
the
site
looks
great
on
preJy
much
anything.
– Helps
keep
the
BluePrint
structure
under
control
02 Common
02 Master content
design
03 Browser
03 Browser design 03 Mobile content 03 Mobile design
content
04 Browser
04 Mobile website
website

14. SDL
Tridion
Mobile
Preview
• Mobile
preview
– Allows
content
authors
to
view
the
site
on
a
mobile
device
before
publishing.
– Latest
version
of
SDL
Tridion
required


15. QuesPons
and
more
thanks!
• Anything
I’ve
not
covered?
• Thanks
&
keep
in
touch
– john@contentbloom.com