[BLANK_AUDIO]

Often people when I talk to them about this,

I talk to all the clients I work with.

This is something I do on every single project now.

I can't even imagine not going atomic.

You know?

When we think about responsive or just web design, you know, we think

about how our content is gonna start to live across all these devices.

Well, that's a bit about what I'm gonna talk about today.

also, I'm Canadian, so I'm going to say about, and

I'm gonna say process cuz that's the way it's spelled.

>> [LAUGH]

>> I was mean making fun of America basically just so you know.

>> [LAUGH]

>> [LAUGH] this is probably a safe city to do that in, right?

Anyways, I am now at the Republic of Quality.

I left, the that company I was at over the last three years, I

was User Experience Director at a place called Yellow Pencil, they do great work.

But I started to do this type of work, more,more

and more until I still work with them and other companies.

But this is just a user experience and content strategy duo, its

my wife and I helping to make the web a better place.

So, this is me.

I forgot to bring my on brand tie.

But, you can find me on Twitter.

Twitter is by far the best way to get a hold of me at any time, honestly.

Just reach out to me.

If, if, for some reason, I don't follow you back right away,

just send me a really angry message, and that will work, for real.

Okay, so, first thing you should know is, I'm a great designer.

Yeah, that's funny.

no, but I am not good at this.

[LAUGH] Now it just gets better.

[LAUGH] And my daughter, we just bought this for her.

This is the first thing she did.

Hey.

[SOUND] Yeah.

>> Go!

>> It was, it was kinda this moment of huh, you know what?

And often we forget that the clients, the people

that we're working with if you're here as a

web designer, developer, agency, or maybe you are someone

that's looking to hire a web designer, developer, or agency.

That it's not always easy to just do these things, you know.

It doesn't always just make sense.

Sometimes we have to go through these things together.

I'm a big believer in collaboration and collaborative processes.

Cause that's a bit what we can talk about.

You need to know a little bit about me in case you don't.

This is my wife Shannon, she's the other half of Public with Quality.

She's fantastic, and she's got a great personality.

This is my daughter.

I occasionally put her to work as well.

That's not legal, but I do it.

She also has a fantastic personality.

She, she was just one of the photographers at the Dare Conference in

London, because one of the photographers said, here's a camera, and she loved it.

That was her first connection to a conference in the digital industry.

I also have a dog that comes to work with me.

This is how I wake up to her in the morning.

She's a puppy still.

She looks like a deer basically, and she also

has a personality of her own as well [LAUGH].

This is where I live and work.

So if you look, there's kinda this building with a

weird top on it way over there in the right.

That's really close to my office.

This is Vancouver, British Columbia.

It is a beautiful, beautiful place.

We can go snowboarding and skiing, hiking, you know, this is what it

looked like as I was looking for my home there two years ago.

I loved it, and then I moved there.

>> [LAUGH] >> Yeah.

It's actually in a rain forest.

It's in the Pacific Northwest, there.

But I, I love it.

I love to cycle camp.

I had very serious commuter bike that became a

bit more of a hipster commuter bike that became

a little bit more And then it became this

and I take very dangerous photos while I cycle.

I've never dropped my iPhone.

I was hit by an SUV once though, so I don't necessarily recommend that.

But, I love Vancouver so much that I created a website just for you.

So, it's haveaproblem.com.

Please visit it on your own time here.

but, enough about me.

Let's get back to work.

So, why, why are we here?

Like what, what is this thing, this atomic content?

Well, this past year, I had a conversation with Brad Frost at

South by Southwest, and later he wrote this piece on atomic web design.

I don't know if you've read it or not.

If you haven't, this is the URL.

It's really easy to find if you look up atomic design.

First you get kind of the technical atomic design like as in nuclear

but then you get his article [LAUGH], which

I thought was an interesting contrast but it's great.

He talks about all these pieces.

How we start with the smallest and work our

way up and, and the process that goes through there.

But there's this little bit of a problem that I have, not with his article, it's

great, but if I did a search for connection or humanity or heart or people

or anything like that, those terms don't exist in his blog post anywhere, right.

This is about the system, and that's great, but do you know what?

This is not the web.

The web is not machines.

Now technically that's where is hosted, but the web is us connecting with people.

The web is with people connecting to people.

So we need to remember that.

So when we start to think about web design, and thinking

about a multi device world, what, what does that actually mean, right?

How many of you are in the process

of redoing your sites so that it'll be responsive?

You just raise your hands real high.

I totally can't see you anyways.

How many of you are want do that but not quite there yet?

How many of you, your site is responsive, and you

feel like it's, like, exactly what you wish it could be.

Yeah, you're hadn went down after [UNKNOWN].

[LAUGH] You know, there's so

many complicated issues around responsive design.

How many of you don't care about responsive

at all, and are just in the wrong room?

No, that was another awkward Canadian joke.

Okay.

Well, I think that the problem is sometimes is we just jump

into these projects thinking about technology,

and we forget about the people.

The why, the why are we doing this, the how are we gonna connect?

One of my favorite TED talks is, it was

actually a TEDx talk, in 2009, by Simon Sinek.

Has anyone here, listened to the Golden Circle by Simon Sinek?

Few people.

Not very many.

Well here.

Here's your opportunity to learn about it.

This is basically what I base a lot of my work on.

And I get hired to help people connect to people

really, even though I'm a user experience designer content strategist.

So you've got these three concentric circles, and the outside circle is a what?

Everybody knows what they do.

Someone shout out what you do.

Like, what's your job title?

>> Event producer.

>> Even producer, [LAUGH], thank you.

what, what do you do?

>> Special events coordinator.

>> Special events coordinator, wow.

Okay.

You guys are sitting together.

You know it's easy to say what we do.

That's very easy.

It's easy for me to say I am an experienced architect, right.

100% of us can say that.

How it gets a little fuzzier, right.

Because how many of you have been in

a meeting, I think someone else talked about this.

Where your listening to a client or someone

else on your team say we really need

to do this and you just kind of nod and say oh that's a great idea.

We'll definitely do that, and as you walk away from that meeting and go

home that night you're thinking oh shit I have to learn how to do that.

Yeah that's happened so many times to me.

We need to figure out the how.

The how is kind of this bit of a fuzzier thing but then

there's the why, the central core that is fuzzy for almost all of us.

You know, and Simon Xena gives us great example, he gives a lot of examples.

He's got a website and a book on this now, too.

But when we think about this, this inner core, this why of a computer company.

So if you compared like a PC computer company with Apple computers.

I'm not saying that because I use Apple computers, I use everything.

But, you have the PC company saying what are we gonna do?

We're gonna produce a computer so that people can use it, you know.

How are we gonna do that?

Well we're gonna source parts from wherever we can, they're the

best parts we can acquire, they're a great cost, all these things.

Maybe we'll have a manufacturing place of our own, or, we won't.

Why are you gonna do it?

So people can use our computers so we can make money, right?

That may not be the whole story, but that's a bit of a summary that he gives.

He talks about Apple computers, and whether

you believe this or not about Apple computers.

But, how they start off by saying, we want to think differently.

We want to change the world.

Right, just give me a little bit because I was just thinking about that.

And then the how.

Well we are gonna start, you know, really thinking about computing from the

human perspective, you know, how is this device going to work for people.

And why or what, these things there are all around us, you know.

What if the iPhone hadn't come out, I'm sure another phone was on its way and

there, there were, but there are devices like

that that they produce that change the world.

Right?

And all of a sudden you connect that vision of the why to that.

And I'm far more compelled, suddenly, to buy an

Apple computer, because I wanna be part of that.

Now it may never have been more obvious that the

why may be missing a little bit in the now.

But we need to focus on the why of all of

our projects, and then build out to the how and the what.

So what is a responsive site?

You know.

I think we need to see the web differently, okay?

We need to put on different lenses that allow us to see the human web.

So a zombie alert.

I'm gonna show a zombie clip, I always do this, I always show something there.

It it's a little graphic, but that's okay.

Have any of you ever watched or know of The Walking Dead, the show?

Yeah, even though I can't see your hands, I'm assuming a few are up.

My wife and I watch it, which means I watch it and tell her about it afterwards.

Cause she watched the first few episode and she was like, oh this is too gross.

But, we both love it.

But here, here's something that I love.

I love that zombie movies tell the same story every single time.

Just variations of it.

They tell it in there own way.

You know?

Someone.

So if you've never seen a zombie show, movie,

never heard anything about it, probably someone will wake up

in a hospital, you know, maybe let's say 28 days

later, and there'll be no one around on the streets.

They'll somehow have survived whatever apocolypse has happened

that it caused everyone to evacuate, they're all gone.

They'll start wandering the streets and

then they'll encounter the undead, the zombies.

And they won't know what to do but, for some freakish way, they'll

like knock off one of their heads, and if they're that's how I survived.

They'll meet up with some other humans, they'll make friends.

They'll be in this together, probably most of them will die.

The hero will survive, and we don't know exactly how it will end after that, right.

But this is popular.

It's the same story over and over and over.

But it's told just a little differently each time.

[MUSIC]

[MUSIC]

[MUSIC]

[MUSIC]

So that's an alternate opening, from Great Arts if you go to

that link on Vimeo just search for it you'll find it very easily.

But it's so easy for us to focus on this.

What is happening around them, right?

This zombie apocalypse, and, you know what,

this is true about any disaster, right.

As a kid, I lived through a horrific

tornado, in the city of Edmonton in Canada.

It was a class five tornado, if

you know much about tornadoes, that's insane, right?

It, threw these giant oil drums that were hundreds and hundreds of feet across.

We would just pick em up and throw em across the city.

And it was terrifying.

but, and it was easy to focus on the disasters

of it, the destruction, the horror, and the death, right?

But, what, we start to see in the zombie

genre, and then these disasters is not this, it's this.

This is what zombie movies are about.

Humanity, our reaction to the apocalypse.

This is why I think they're beautiful,

even though they're a little disgusting too,right.

Is it that we see how, as people, we

will react in these dire circumstances and come together.

You see that all over the world when disasters happen, not to say

that they aren't horrific and awful, but is about our human interactions, you know.

When we think about the web we to think about

the humanity the face that we're putting on it right?

So really, its all about rocks.

Not this guy though, but maybe this, sorta.

So I'm gonna do something that I've never done before.

And this is actually a new talk, so this is interesting for me.

But I'm gonna do a physical demonstration.

So we need to start with the right stuff.

So if we can get the camera on the table, that would be great.

hopefully, yeah, look at that.

Power pose.

'kay, [SOUND].

Has anyone here read Steven Covey's book,

The Seven Habits of Highly Effective People?

You know I'm always surprised to how few people have read this book.

And it's not because I think that Steven Covey is a great, great author.

Or because, people must read this book.

But because of how impactful it was on my life.

And how whenever I interact with people that

are leading organizations and successful, they've read this book.

You know?

So he talks about, these four quadrants that are the I'm not about to

drink like a big cup of something here, this is, this is sand actually.

He talks about these four quadrants.

They are the urgent important, right?

And so, if this thing, if we don't do this thing someone will die, right?

The non urgent important.

See these are things in our life like

exercising, eating well, where they are really important

and they will transform us, but they don't

seem urgent because they don't transform us that day.

And then we've got the, urgent non-important, right.

So that may be you know, someone comes in

and says, hey there's doughnuts in the conference room.

Well its urgent, cuz those donuts will go bad, but I don't really need them.

And then the last quadrant is the non-urgent, non-important, right?

And that's probably wasting time on, like a television show, or something like that.

It's not to say that we shouldn't have things in all these

quadrants, but he talks about the

importance of focusing on the non-urgent, important.

The training ourselves, the taking care of ourselves.

So but there's this problem.

Right.

So let's say this pitcher is our web project okay.

And we're gonna put in, I think I'll even put in a little bit more sand.

I've got this giant Home Depot I was surprised

to find a Home Depot in Manhattan, that was awesome.

It wasn't fun carrying 10 pounds of sand around though.

So let's say we put the sand in first.

So maybe this is this is some of the RFP that's

come to us, you know, and all the features that might be

turned on on an Oracle site, and all these things that

aren't really all that important, but they start to take over, right?

And then we've got, maybe some smaller

colorful rocks that will go in here, right?

And so we've got other things that start to come up, you know,

different personalities, working their way out that allow us to start to think

about other features like the carousel on the homepage or how important the

homepage is to different people, even though

somehow we feel like it isn't important.

And then we get to slightly bigger rocks again.

Alright.

That's probably good enough.

Where, you know, these are the things that start to really matter.

You go, oh, okay.

Yeah, you know, we've got this messaging from

our marketing department but we also have this

messaging you know, for this core part of

our product that needs to make it out there.

oops, we gotta get those in there.

And then [SOUND], fresh from this street look who's here.

We've got our big rocks okay.

So these could be things like I don't know our content.

You know, our maybe it's actually how we're connecting to our users.

So we're gonna talk to our user research.

We decided to do testing at the end of the

project for some reason and forgot to do it all throughout.

You'd see my problem here, right.

I have run out of room for things in my web

project, and so somehow I need to reshuffle or maybe, maybe the

content needs to totally change, or maybe we don't talk to

our users at all, and we'll just leave that one over there.

It's a bit of bullshit, isn't it?

What if we took another jug, and instead of putting the sand in first,

[LAUGH] which I almost did, we'll grab some of the big rocks.

We think about our content, our message, and plop it in.

You know maybe this one is talking to our users

early and often, and for that a few different presentations.

What else, here we'll grab this one.

You know and maybe this is the vision of the project.

Alright, so we start to have these things and then

we can go back to our other rocks we say okay,

so we have our design principles our fundamentals that are coming

out of this, where we're trying to interact with people [SOUND].

You can see what's starting to happen here.

Alright.

I'm going to put a few of these in, [SOUND] they start to fit their way

around, oops, these big rocks in here, and then we start to get some of the features.

Some of the other things that we know are gonna be important.

You know but we've dealt with the vision, the

content, the users, maybe revisiting some of the user testing.

[SOUND] I hope you can see this.

And again the level hasn't gone above the top, big row yet.

Not even once.

What if we were to take some of these other things now, these things that

we knew at the start somehow didn't feel

right when we're putting into our web project.

[SOUND] You know, let's pile a little bit more

of these features, and some scopes on some of the stuff that we want in our project.

But weren't sure could fit, but because we had

this strong vision, first, we talked to our users.

We talked to people, we made our project human.

Hell, let's not stop at the sand, is what makes everyone nervous.

Let's get right into the water now.

Read into all these other things, you know,

that we can start to enhance our project with.

I recently was working with the government in Canada.

I'll let that settle a little bit.

And their IT manager was on the stakeholder group.

I don't know if you've ever worked with an IT

manager but often they see things in a particular light.

They're thinking about the technology.

And we're going through this process of atomic content modeling, and he started to

kind of laugh at one meeting and I thought oh-oh, [LAUGH] this is going horribly.

And I believe in addressing things right away, within

the meeting, you know, not letting elephants sneak around.

And so we talked about it and said well, well, what's funny right now?

And he looked at me, and no joke he was giggling like a little kid.

He said, I love this process so much.

My project suddenly makes sense to me, right?

And it was because he could see how people could connect to it.

So I could keep going here.

The water could keep sinking and settling in, and

it's because we started with the big rocks first.

I am not gonna leave, well, maybe I will.

Hopefully, I don't knock any of this over.

We can go back to the slides, though, now.

Thank you for that.

That was seamless.

So this was really powerful for me the first time I read about it.

And then I saw it, and I wanted to share it with you because sometimes

when we see these things physically they stick in our head, and we don't forget.

Maybe you won't have time to read that book, but you have a

bit of an understanding of why we start with the first things first.

You start with the right stuff.

So for that same government, we're looking at

their site and, my work is often quite messy.

I'm a big believer in digital prototypes, designing in the browser all these things.

But I also am a big believer in this, in us being together, sketching.

That it is not my job to do all the sketching, either.

That is everyone's job on the team.

So this is that same municipalities.

See, they want it to be a web first organization that empowered [INAUDIBLE].

right, but in the middle there, is a bit

of an example of a content model that failed.

And initially.

So, let's take a look at that one.

So this is loosely based off of

Starbucks when they relaunched their responsive site initially.

Right?

And so they had, if you haven't heard the

blob versus chunk argument from Karen McGreen please look that

up, but blobs are these giant blobs of HTML

content, where as junks are more discrete pieces of content.

And that's the way to go.

But let's say this is their initial site.

And we have a logo, site ID, navigation, you know, a

big blob of HTML content where their main body of stuff is.

What they call the sidebar, unless your using

WordPress please don't call that a sidebar though, footer.

And then they have this really important call-to-action, buy this product, right.

And it was right there.

And it's in a great spot for, a desktop or a large screen type like this, right.

But because they had these blobs of content, how do we thought about it.

Like how many of you use your phones when you're in Starbucks?

I see everyone that goes to Starbucks, we're on our phones.

So this what we call action, when I was

refactored, all of a sudden they have this giant

blobs, they haven't thought about pulling this out of

there, and so we've got this lost call of action.

It's so sad.

And then, what if we thought about it from chunks

instead of blobs, we still have our side idea logo.

Now were still over navigation, but maybe we've got

a title here, and maybe we've got a bit of

intro copy, clarity copy, debt copy, whatever you call it,

you know, maybe there is the rest of the body.

We've got this call to action, is a discreet piece of content,

but we have this secondary area and the reason why you shouldn't call

it a sidebar is because it won't live on the side on the

majority of devices accessing it because the majority of devices are now mobile.

And then we have this tertiary area, which is the footer.

If we refactor this, where the call action

was there, suddenly we can have this successful

call to action closer to the top, that allows us, I don't believe in the fold.

I think its just its so weird that we continue to use

terminology like that, although I get it, the sun doesn't rise and set.

you know that's old language but it makes sense to us now.

But we do see more conversions when we have this call

to action on the first screen if it's an important one.

You know so it's this happy moment.

This genuine surprise of how successful we can be.

So when I get in with a client, and then working on a project, this

is a, this is basically what the start of this atomic content molding process is.

Now I've done all the content audits, or someone has.

There's been inventories.

I know where the content lives.

We've actually talked through, at this point, the user experience

vision, or the vision for the project, we've designed principles established.

But when we get to here, we start to list out all the discrete pieces of content

that will live on every unique view, right, and

so, like this site had about 10,000 pages, right?

And we did not do this 10,000 times.

We did this 12 times, they had 12 unique

views that would handle the content across the entire site.

So we list out things like the navigation

the site ID, everything that was gonna be here.

Even if some of them, the related content thing, it got scratched off.

We realized, what, we don't need that, but we listed everything off.

Everything is then grouped, oops, you know what

I'm gonna come back to that, that's right.

Because often, I skipped a step here.

Often we think about what system is best for content like this.

I spent quite a few years working with Open Source Systems.

I helped work on some of the stuff for Drupal 7.

I, I loved working with Drupal.

So what system is best?

Well recently I saw this.

And and a client had forwarded it to me because

they said this is what I want where I work.

There's can't be anything

out there better than this.

[MUSIC]

[MUSIC]

[MUSIC]

[MUSIC]

[MUSIC]

>> So basically that's magic, right.

It's amazing, it looks great.

What about this?

If you thought about.

>> My name is John.

>> Web design and there's a zom, zombie.

>> Making what was once impossible.

>> My name is Anna, and this is my world.

>> Possible.

>> My name is Umico, and this is my world.

>> With technology advancing so rapidly today.

>> My name is Faye, and this is my world.

>> Imagine what our world would look like [SOUND] tomorrow.

[NOISE] [SOUND]

>> My name is Alice, and this is my world.

[MUSIC]

>> Okay.

No system is perfect.

That's all I'm saying.

[LAUGH] I'm actually not promoting nor saying you shouldn't use Squarespace.

I actually think it is a great system.

But, we need to know the limitations of our system, right?

And I have worked on so many projects where it's

brought in as an Oracle project, or a Drupal project.

And that's okay.

Those can still be successful.

But you know what the ones that inspire me are?

And they're usually a lot more successful?

Is when we start with the content.

Is when we start with the people, the humanity, and find what's going to

work with what messaging we need to get out there, how we're gonna connect.

So no system is perfect and we need

to understand how our content will live within it.

But many are great.

There are many great systems [INAUDIBLE] so if

you're not familiar with it, there is Squarespace.

You've probably seen this on Hulu, or something, as

a commercial You know, they've got really interesting commercials, Squarespace.

There's also Virt, you know, another similar type of, of system.

These are low cost, where you could do something on

WordPress.org, right, if you're doing a blog or something like that.

You could install your own version of

WordPress, and really customize and go with it.

You know, you can use Drupal.

I've worked on many enterprise, level client projects on Drupal.

A lot of your government sites here in the

United States run on Drupal, it's a great system.

You could also use Oracle.

They're sort of opposite of each other in philosophy but, you

know, Oracle like it or not is an incredibly powerful system.

And Iron Man uses it, so you know, that's pretty good.

But here's the thing.

A

website is a black hole without its content.

So I think that those people that build those system have one

of the hardest jobs out there cause they're trying to think of every

possible scenario, and they're trying to create an interface that would work for

you to build a new scenario even though they don't know your content.

And that's where this comes in, we're looking at the atomic piece.

So we're looking for that one piece that everything else will revolve around.

So on a food site, you know, that may be a recipe.

Sarah Waktabooker, really hope I got her name right, talks about this

in her book, and how there's this food site and they decided

that the recipe was for this central core piece of the content

modeling, and that everything else related to it, like the different ingredients.

So you could go to this food store to buy this ingredient, you go

to this recipe cause this or this

restaurant because this chef prepares this food.

And it became this community that's founded around recipes, not around

ingredients not around chef's that prepare these things, but the recipes themselves.

So we go back to this municipality and we zoom in a

little bit on this, we can see there's red and green stuff here.

So everyone on the project team at this point,

that's in this room, and there were six of us

had to prioritize everything into three different groups.

First group is essential, right.

The, this view can not exist without these things.

So we see things like navigation, you know,

the site ID, search falling into that group.

You know, but other things like audio, and social channels are not.

And then the second group is, this would be great to have.

This will enhance the experience This should be there if possible.

And the third group is, these are nice to haves, you know.

And we noticed that some of those get scratched off after a while, cause

we realize it's nice to have, but it actually takes away from the experience.

That's the easy part in putting those three groups up there.

Then everyone is forced to agree upon

the prioritization of everything within those groups.

So something in group number one is number one.

In this, where did they set it as?

Do we see it up there even?

it's, must be off the screen.

oh, set ID logo.

That's what they decided as a group there.

You know, but from that, we then start

to sketch out the possibilities within an interface.

Now, this is where I'm a huge believer that you

need to get into the browser as soon as possible.

If you can't do that on your own, team up with someone that can.

Because there's no way for me to fully represent in the, in sketches

like this, every scenario, because the site

responds at every different screen-size resolution, everything.

It's not just about the break points, right.

That's just where it totally breaks, and we need to

refactor to present our content properly and keep those priorities.

But, a good exercise to do is to just simply do

small screen and large screen, and start to think about those possibilities.

The amazing part is how this moves you into the next bit of your process.

So what we do is, we find this one piece of, for their site, for this

government site, it became the page title and

clarity copy was their atomic piece of content throughout.

Because people were looking for services.

You know, governments are, are service providers essentially.

They're connecting us to our services.

You think about a city and its website.

Like cities are content wide, and miles wide

and inch deep cuz they provide everything to everyone.

But you're coming to find that particular piece of content

you may be saying, I wanna find my dog laces.

Right?

And so, knowing that you're on the right page, the

right view, with a little bit of clarity copy became important.

So that all seems really great but how

does this help us fully on a responsive project.

Well it's interesting that Jacob mentioned this but this

is that Wikipedia page that he talked about in his.

So this is for just Android phones, this is actually from nine months ago now.

The first column is the name, second column is the

release date, then the Android version, then the screen size.

And so we're in HTC right now, if we start to scroll through this you can see

that every almost everyone is slightly different combination

of screen size and, and version of operating system.

Okay now we're in LG.

I don't know, can we see the scroll bar on the right?

See that's the problem If you look at the scroll bar, there's so much to this page.

We're in Motorola.

And, again, this is just Android.

Samsung devices, I'm using a Samsung phone today.

I love to use it when I travel.

Sony Ericsson, let's, we better get going really fast

here though, I don't wanna stay on this too long.

Let's get down further.

So we're getting into different kinds of devices and almost

now so e-readers netbooks, smart watch, future devices, oh interesting okay.

Future Android smart phones, tablets, rumored tablets.

Other future devices my favorite category of all of them.

You're like what do you do with this, right?

Can you start with a hm and you end up with a oh shit.

Because there are hundreds of android devices that have different options.

Right?

Different screen sizes, different versions of the operating system.

People could be using different browsers on those devices

if they wanted to, and that's just one platform.

Right.

What if we start to think about other things, where our content could live?

I've a couple other people were talking about

Google glass and different devices like that, you know.

We were caught off guard in 2007 when the iPhone came out, because we had started to

think about every year we'll get a little

bigger with our resolution, and it was like boom!

Totally changed.

You know, the real web is existing on smaller devices.

What about Google glass?

Or this even?

What would delivering your content to a

pebble watch, or something like that, smart watch.

Anything that's hooked up to your phone, or standalone device.

We don't know, we could be delivering our content

to a billboard, to a screen this size, right.

I was in a presentation and my site came up and

I got to see how it worked on a low resolution, projector.

Cause it needed to be responsive to work with that.

What if we are using a smart watch, which is too hard maybe

to read a lot of content on, but we have an audio device.

And so we can go, oh, I wanna hear that

email and we just have this little audio device, right here.

And so it reads our email to us and we can respond back and forth that way, right?

This is where we need to start to really document these models.

These are where these things start to help us.

If we understand what that discrete piece of content is, we can deliver it first.

We can prioritize it.

We can say, for them to understand this

particular view, we're gonna send out priority one, one.

And if we can, one, two, right.

These things start to get out there, they start to make sense.

So, how it helps you process, won't help you process though.

is, you could start to document these out this is

the notes that we took during that session for that

same city and I, I removed the city's name because

the project isn't done, they're okay with me sharing this.

I'm not like doing this without permission.

But these documented models become the annotations within

the wireframes, or at least some of them, right?

And we see these sketches, and we can start to build this system out, right?

And so there's in-browser wireframes.

I don't, I used OmniGraffle for years, and I have not touched it in two years.

I had to open it up at one point, it just

like, you know what, I can do this better in the browser.

So, this is that same government, that same municipality.

You know, representing their

there should be real content in here.

This is kind of the mistake with this

one, but their annotations, their content modeling is here.

They can start to see it and touch it and live with it and bring it up

on their phone, their tablet, you know, their computer,

whatever it happens to be, a movie theater screen.

They can see how it's going to respond.

Now the truth is only web designers stretch their screen back and forth.

right, cuz we think it's cool.

But, they can actually live with this and, and there's so many ah-hah moments that

I didn't experience doing things in a

static environment of Omnigraph or something like that.

So, these things begin to speed up my process because I spent more time

on the content and the Atomic Content

modeling at the start, and understanding it.

Everything else has gone faster for me.

I come in under budget on most things, allowed us

to do more, to fit more into our jug, right?

The big rocks went in first.

So what about the future?

Hm?

What is the future?

How does this impact our future?

This is great, this is practical, this is now actually.

And we've got this idea of this atomic content,

finding this nucleus that builds out everything else around it.

But then we also have this idea of heart, of humanity, of connection.

All right.

We wanna create this experience that goes beyond the technology,

beyond our content management systems, and connects with you and me.

[BLANK_AUDIO]

So what's the future of the web?

What are people wanting, needing, going to hear, was this atomic piece.

I think the future of the web is all of us

taking responsibility for the web, and building a whole hearted web.

I was just at another conference where they talked, or every speaker talked

in that way where they were talking about people as holistic Individuals, right?

Brune Brown does this great talk, which this phrase is from.

She talks about us being wholehearted.

But she also says that our stories, are data with a soul.

If you find all these databases, all these pieces

of content, all these things that live up there.

But they come out, and they tell the soul of who we are.

Alright?

That's why I get so excited about what I do, and why I

hope that you'll get really excited about doing some of what I do.

We start to connect people to people.

And we see the future of the web as being a wholehearted web.

Thanks.

[SOUND]