your next library website in drupal 8 - drupalcamp michigan 2016

28
Your next library website in Drupal 8 Brad Czerniak

Upload: commercial-progression

Post on 22-Jan-2018

189 views

Category:

Technology


0 download

TRANSCRIPT

@comprodrupal

Your next library website in Drupal 8

Brad Czerniak

@comprodrupal

Discovery and planning process

@comprodrupal

Discovery gets everyone what they need to get to work

@comprodrupal

Sort of like this

Get info Synthesize Get approved

Design

Develop

Other stuff

Theme Etc.

Synthesize

Synthesize

@comprodrupal

Design

Branding

Mood

Client opinions/desires

Business needs

Vertical info

A description of the

client’s org

structure, filing

system, and reality

that can be turned

into a database

schema

Dev Other

Workflow

Copy

Strategies

Hocus-pocus?

Inputs

@comprodrupal

Design

Branding guide

Style tiles

Wireframes?

Entity doc

View doc

Block doc

Implementation notes*

Behat tests?

Dev Other

Project plan

Content strategy

SEO and marketing plan

Hocus-pocus?

Outputs

@comprodrupal

Make sure:1. Everyone has everything they need2. Stakeholders are all in contact

@comprodrupal

Oh!And that the client knows what they’re approving

@comprodrupal

Information architecture

@comprodrupal

Sites are satisfying when…

They’re consistent

They’re the right amount of simple

The powerful parts are easy

They come in ahead of schedule and/or under budget

@comprodrupal

Your sitemap is a very small forest

Between one and three trees

Each tree has between two and seven branches off the trunk

No more than three layers of branches

But leaves are okay!

[Smash the metaphor because the branches are also leaves, and the trees can

be rearranged with an administrative UI]

@comprodrupal@comprodrupal

Data Structures

They’re what site builders crave Event name [title]

Splash [image, single]

Description [long text, filtered]

Date [date, recurring]

Location [address]

@comprodrupal

Site structure should

semantically reflectreality

@comprodrupal

Architecture to implementation

If the architecture defines Views, blocks, taxonomies, entity types, relations,

and other implementation details, that’s what will get [designed and] built.

If things are open-ended, you’ll get Panels and hacks and technical debt.

Hire a good architect

@comprodrupal

Technical considerations

@comprodrupal

I have a confession…

@comprodrupal

Drupal 8 planning gotchas

@comprodrupal

That “wild west” time

Some good stuff is still pre-release

You’re going to make the wrong decision about something (and that’s okay!)

Plan for fixing stuff for major minor releases

Lip service for separation of concerns and “decoupling”

@comprodrupal

Atomic-ish design

@comprodrupal

Theme the small stuff first

Designthe small stuff first

@comprodrupal

What’s the small stuff?

HTML tags

Things that have ARIA roles

The “media object” (in OOCSS terms)

Stuff included in the Style Guide module

@comprodrupal

The designer must then usethe components when building up

@comprodrupal

Brad's opinions

@comprodrupal

Brad, these are things to mention?

Catalog search

Word choice

Don’t recommend services you don’t actually recommend

Front page hierarchy

Ranganathan

@comprodrupal

Extending the core experience

@comprodrupal

Conway’s law

Organizations which design systems … are constrained to produce designs

which are copies of the communication structures of these organizations

— M. Conway[3]

@comprodrupal

So, like, Summer Reading and stuff…

@comprodrupal

Thanks!

Questions? Comments?

https://goo.gl/DjcAyM

Brad Czerniak

@ao5357 everywhere

[email protected]

(248) 721-0350