-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathindex.html
executable file
·421 lines (414 loc) · 20.4 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Firm Up that Backend: Easy Exercises for a Usable Admin Interface</title>
<meta name="description" content="For content maintainers, an uncustomized Drupal admin interface can be complicated, overwhelming, and downright scary. By making the system easier to use and more difficult to break, developers and site-builders can create better relationships with their content maintainers and ultimately their clients. There are a number of steps they can take to do this, ranging from installing and configuring modules that improve the interface, to customizing the permissions system to restrict access to areas of the site that can be unnecessarily confusing, to setting up more intuitive dashboards. Careful thought about what content maintainers need to do, and planning to help them to do it, helps them focus on their content and empowers them to take control of managing and maintaining their website with less developer assistance.">
<meta name="author" content="Lauren Byrwa">
<meta name="apple-mobile-web-app-capable" content="yes" />
<meta name="apple-mobile-web-app-status-bar-style" content="black-translucent" />
<meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=no, minimal-ui">
<link rel="stylesheet" href="css/reveal.css">
<link rel="stylesheet" href="palantirnet-theme/css/styles.css" id="theme">
<!-- Printing and PDF exports -->
<script>
var link = document.createElement( 'link' );
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = window.location.search.match( /print-pdf/gi ) ? 'palantirnet-theme/css/print/pdf.css' : 'palantirnet-theme/css/print/paper.css';
document.getElementsByTagName( 'head' )[0].appendChild( link );
</script>
<!--[if lt IE 9]>
<script src="lib/js/html5shiv.js"></script>
<![endif]-->
</head>
<body class="dark">
<div class="reveal">
<div class="slides">
<section>
<h1>Firm up that Backend</h1>
<h2>Easy Exercises for a Usable Admin Interface</h2>
<p>Lauren Byrwa | <a href="http://twitter.com/labbydev">@labbydev</a></p>
<p><small>Senior Front End Developer <a href="http://twitter.com/palantir">@Palantir.net</a></small></p>
<aside class="notes">Who are you? why are you talking? Why should people care?</aside>
</section>
<section>
<h3>What do you do with Drupal?</h3>
<ul>
<li class="fragment">Front-end?</li>
<li class="fragment">Site Building?</li>
<li class="fragment">Module Development?</li>
<li class="fragment">Content Administrators?</li>
<li class="fragment">Have you ever entered content into Drupal?</li>
</ul>
</section>
<section>
<h3>Why does it matter?</h3>
<ul>
<li class="fragment">Developers don't know what it's like to not be developers.</li>
<li class="fragment">Content administrators don't always know Drupal.</li>
<li class="fragment">The backend gets left behind.</li>
<li class="fragment">Content administrators don't have the confidence to do their job without assistance.</li>
</ul>
</section>
<section>
<section>
<h3>Warm ups</h3>
<ul>
<li class="fragment">Use the <a href="https://www.drupal.org/project/admin_menu">Administration Menu</a> (instead of the default Toolbar).</li>
<li class="fragment">Add help text</li>
<li class="fragment">Does your structure and naming make sense to people who don't know Drupal?</li>
</ul>
<aside class="notes">The best way to get started with anything is a good warm up. These are the things that I do on almost all of my projects.</aside>
</section>
<section>
<img src="images/admin_menu.png" alt="Screenshot of Admin menu dropdown in action." />
<p>Dropdowns allow users to easily and quickly get through the system</p>
<aside class="notes">It can take about 4-5 clicks/page loads just to add content. You can easily get around with a dropdown. You can integrate with permissions, so that clients can't get to pages they don't need to use.</aside>
</section>
<section>
<img src="images/help-text.png" alt="Screenshot of Drupal help text." />
<p>Adding help text on fields, and descriptions on content types, taxonomies and contexts</p>
</section>
</section>
<section>
<h3>Company Workflow</h3>
<ul>
<li class="fragment">Intake with the client to discuss their internal needs</li>
<li class="fragment">Create a custom workflow for those clients needs</li>
<li class="fragment">Determine number and needs of roles</li>
<li class="fragment">Craft permissions based on client needs and custom workflow</li>
</ul>
<aside class="notes">I have to talk to the client and figure out how they work. Custom workflow and options on CFA</aside>
</section>
<section>
<section>
<h3>Permissions</h3>
<ul>
<li class="fragment">Content administrators can focus on only the tasks that they need to complete.</li>
<li class="fragment">Prevent content maintainers from unintentionally breaking the website.</li>
<li class="fragment">Prevent unauthorized users from seeing parts of the site that they shouldn't.</li>
</ul>
<aside class="notes">Make the system less breakable and help them focus on what they need to get done.</aside>
</section>
<section>
<h4>Permissions by Role</h4>
<p>Tools to work out your permissions</p>
<ul>
<li class="fragment">Taxonomies: <a href="https://www.drupal.org/project/vppr">Vocabulary Permissions per Role</a></li>
<li class="fragment">Menus: <a href="https://www.drupal.org/project/menu_admin_per_menu">Menu Admin per Admin</a></li>
<li class="fragment">Fields: <a href="https://www.drupal.org/project/field_permissions">Field Permissions</a></li>
<li class="fragment">Content Types: <a href="https://www.drupal.org/project/content_access">Content Access</a></li>
</ul>
<p class="fragment">An easy exercise for role testing is to use <a href="https://www.drupal.org/project/masquerade">Masquarade</a>.</p>
<aside class="notes">Menu admin per admin - you may only want to let them edit certain parts of the menu or not edit the menu at all. Content access - set general rules for all the different content types, and you can override for particular nodes. Masquarade - allows to test permissions, but disable on live websites. FTC testing - Masquerade.</aside>
</section>
<section>
<h4>Permissions Before</h4>
<img src="images/admin_menu.png" alt="Screenshot of Drupal 7 Admin menu showing all possible links." />
<p>Too many options to distract Content administrators</p>
</section>
<section>
<h4>Permissions After</h4>
<img src="images/permissions-after.png" alt="Screenshot of Drupal 7 Admin menu showing only links that content administrators need." />
<p>Content administrators can focus on their tasks</p>
</section>
</section>
<section>
<section>
<h3>Admin Views with VBO</h3>
<div class="fragment">
<h4><a href="https://www.drupal.org/project/admin_views">Administration Views</a></h4>
<ul>
<li>Customizable view</li>
<li>Overrides the content, user and taxonomy system pages</li>
</ul>
</div>
<div class="fragment">
<h4><a href="https://www.drupal.org/project/views_bulk_operations">Views Bulk Operations (VBO)</a></h4>
<ul>
<li>Adds functionality to these views</li>
<li>Is useful when dealing with a lot of content</li>
</ul>
</div>
<aside class="notes">Replace default pages with custom views. Easily manipulate the options to the client needs.</aside>
</section>
<section>
<img src="images/content-before.png" alt="Screenshot of Drupal 7 content page filters." />
<div class="fragment">
<img src="images/content-after.png" alt="Screenshot of Drupal 7 content page use admin views and vbo to give more faceted search." />
</div>
</section>
</section>
<section>
<section>
<h3>Node/Entity Ordering</h3>
<div class="fragment">
<h4><a href="https://www.drupal.org/project/nodequeue">Nodequeue</a></h4>
<p>Adds easy drag-and-drop interface</p>
</div>
<div class="fragment">
<h4><a href="https://www.drupal.org/project/weight">Weight</a></h4>
<ul>
<li>Relatively lightweight module</li>
<li>Works like the weights already built into menu items</li>
</ul>
</div>
<small class="fragment"><a href="https://www.drupal.org/node/398508">more information on node ordering</a></small>
<aside class="notes">Clients want custom ordering. Editing the post date can be hard and counter intuitive</aside>
</section>
<section>
<h4>Nodequeue</h4>
<ul class="fragment">
<li>Supports translated nodes</li>
<li>Allows seperate permissions for editing and ordering</li>
</ul>
<img class="fragment" src="images/nodequeue.png" alt="Screenshot of a Drupal 7 nodequeue" />
<aside class="notes">Lists all the content. Drag and drop interface. Add content to the queue through the node page, or through the auto fill input here</aside>
</section>
<section>
<h4>Weight</h4>
<ul class="fragment">
<li>lightweight (only two additional database tables)</li>
<li>Uses core node edit page</li>
</ul>
<img class="fragment" src="images/weight.png" alt="Screenshot of a Drupal 7 node weight" />
<aside class="notes">works the same as weight on other fields, like menus and taxonomies</aside>
</section>
</section>
<section>
<section>
<h3>Content Interface</h3>
<h4>Exercise 1: Organize the Edit Page</h4>
<p class="fragment"><a href="https://www.drupal.org/project/ds">Display Suite</a> + <a href="https://www.drupal.org/project/field_group">Field Group</a></p>
<ul class="fragment">
<li>Clean up the node edit page</li>
<li>Divid fields into manageable chunks</li>
</ul>
<aside class="notes">default content interface is rather unwieldy</aside>
</section>
<section>
<img src="images/default-edit.png" alt="Screenshot of Drupal 7 node edit page" />
<p>Default node edit page</p>
<aside class="notes">default content interface is rather unwieldy</aside>
</section>
<section>
<img src="images/field_group-edit.png" alt="Screenshot of Drupal 7 node edit page after being organized with field group" />
<p>Node edit page after being field grouped</p>
<aside class="notes">tabs make it easy to think about</aside>
</section>
<section>
<h5><a href="https://www.drupal.org/project/conditional_fields">Conditional Fields</a></h5>
<p>Show and hides fields based on the values of other fields</p>
<ul class="fragment">
<li>Keeps edit page from becoming cumbersome</li>
<li>Great if you only need certain content in some instances</li>
<li>Helps keep the whole website unbreakable</li>
</ul>
</section>
<section>
<img src="images/conditional_fields-before.png" alt="Screenshot of Drupal 7 node edit page hiding fields with conditional fields" />
<p>When content isn't featured, no "Featured Image" upload appears</p>
</section>
<section>
<img src="images/conditional_fields-after.png" alt="Screenshot of Drupal 7 node edit page showing fields based on the status of another field" />
<p>When content is featured, "Featured Image" upload appears</p>
</section>
<section>
<h4>Exercise 2: Taming Images</h4>
<ul class="fragment">
<li><a href="https://www.drupal.org/project/insert">Insert</a> images into the WYSIWYG.</li>
<li>Create specific style options</li>
<li>Add additional CSS styles if required</li>
<li>Use alt and title text to encourage administrators to keep their content accessible.</li>
</ul>
</section>
<section>
<img src="images/images-wysiwyg.png" alt="Screenshot of Drupal 7 node page using Insert to add images to a WYSIWYG" />
</section>
<section>
<h5><a href="https://www.drupal.org/project/manualcrop">Manual Crop</a></h5>
<ul class="fragment">
<li>Administrators can crop images in the Drupal after uploading</li>
<li>Maintains aspect ratio</li>
<li>Links into image styles</li>
</ul>
<aside class="notes">Images scale correctly. Constrain the proportions to match the images style</aside>
</section>
<section>
<img src="images/manual-crop.png" alt="Screenshot of Drupal 7 manual crop interface" />
<p>Manual crop</p>
</section>
<section>
<h4>Exercise 3: Trim down the options</h4>
<div class="fragment">
<h5><a href="https://www.drupal.org/project/override_node_options">Override Node Options</a></h5>
<p>Hides default options like "Promote to front page"</p>
</div>
</section>
<section>
<h4>Exercise 4: User friendly select lists</h4>
<div class="fragment">
<h5><a href="https://www.drupal.org/project/chosen">Chosen</a></h5>
<ul>
<li>Turn select lists into auto complete tagging fields</li>
<li>Particularly useful on selects with over LOTS of options</li>
</ul>
</div>
<aside class="notes">uses chosen.js plugin</aside>
</section>
<section>
<img src="images/chosen.png" alt="Screenshot of Drupal 7 chosen interface" />
<p>Chosen</p>
</section>
<section>
<h4>Exercise 5: Character Counts</h4>
<div class="fragment">
<h5><a href="https://www.drupal.org/project/maxlength">Maxlength</a></h5>
<ul>
<li>Limits the ability to be too wordy</li>
<li>Avoids text breaking the design</li>
<li>Helpful countdown for administrative users</li>
</ul>
</div>
<aside class="notes">highlights in yellow or red, and shows when you start going over
works in javascript, and hooks into field API</aside>
</section>
<section>
<img src="images/maxlength.png" alt="Screenshot of Drupal 7 maxlength on WYSIWYG interface" />
<p>Maxlength</p>
</section>
<section>
<h4>Exercise 6: Updating and Reverting Content</h4>
<h5>Workbench Moderation</h5>
<p>Helps clients revert content to former versions</p>
</section>
<section>
<img src="images/workbench-moderation-screenshot.png" alt="Screenshot of Workbench Moderation" />
<p>Workbench Moderation</p>
</section>
<section>
<h5>Diff</h5>
<p>Illustrates what changes were made to the content.</p>
</section>
<section>
<img src="images/diff.png" alt="Screenshot of diff module" />
<p>Diff</p>
</section>
</section>
<section>
<section>
<h4>Configuring the WYSIWYG</h4>
<img class="fragment" src="images/wysiwyg-default.png" alt="Screenshot of the default WYSIWYG buttons" /><br />
<ul class="fragment">
<li>Get rid of unused buttons</li>
<li>Use the CKEditor module</li>
</ul>
<aside class="notes">You HAVE to limit the options of the WYISWYG in order to make it easier for the client. Not to mention that it becomes much less cumbersome and intimidating.</aside>
</section>
<section>
<img src="images/wysiwyg-configured.png" alt="Screenshot of WYSIWYG after you limit the buttons to only what content admins need" />
<p>The only options left here are bold, italicize, format, lists, links and images.</p>
</section>
</section>
<section>
<h4>Linkit</h4>
<ul class="fragment">
<li>Helps content editors link to internal content</li>
<li>Allows users to easily search for content on the system or link to a URL</li>
</ul>
<img class="fragment" src="images/linkit.png" alt="Screenshots of the WYSIWYG button for linkit and the interface to link items" />
</section>
<section>
<section>
<h3>Pushing it to the next level</h3>
<h4 class="fragment">Custom Dashboard</h4>
<div class="fragment">
<h5><a href="https://www.drupal.org/project/login_destination">Login Destination</a></h5>
<p>Redirects users on login</p>
</div>
<div class="fragment">
<h5><a href="https://www.drupal.org/project/workbench">Workbench</a></h5>
<p>The Workbench suite is modular, allowing site builders to build the workflow that best suits the content administrators on their site.</p>
</div>
</section>
<section>
<img src="images/workbench-screenshot.png" alt="Screenshot of Workbench dashboard" />
<p>The only options left here are bold, italicize, format, lists, links and images.</p>
</section>
</section>
<section>
<section>
<h3>Cool Down</h3>
<div class="fragment">
<h4>Admin Themes</h4>
<ul>
<li>Admin themes add a final polish to the administrative interface</li>
<li><a href="https://www.drupal.org/project/shiny">Shiny</a></li>
<li><a href="https://www.drupal.org/project/adminimal">Adminimal</a> (with <a href="adminimal_admin_menu">Adminimal Admin Menu</a>)</li>
<li><a href="https://www.drupal.org/project/ember">Ember</a></li>
</ul>
</div>
</section>
<section>
<h5>Shiny</h5>
<img src="images/shiny.png" alt="Screenshot of D7 content page using Shiny theme" />
<p>Shiny is very consistent with Seven, but with a larger font and more polished look and feel.</p>
</section>
<section>
<h5>Adminimal</h5>
<img src="images/adminimal.png" alt="Screenshot of D7 content page using Adminimal theme" />
<p>Adminimal uses flat UI, color coding, and responsive breakpoints. But, fieldsets are not the best.</p>
</section>
<section>
<h5>Ember</h5>
<img src="images/ember.png" alt="Screenshot of D7 content page using Ember theme" />
<p>Adminimal uses flat UI, navbar, and responsive breakpoints.</p>
</section>
</section>
<section>
<section>
<h3>Conclusion</h3>
<ul>
<li class="fragment">There are a lot of easy-to-add modules on d.o that can help content administrators streamline their workflow</li>
<li class="fragment">Consult a developer for recommendations about what is the best fit for your website and workflow</li>
</ul>
</section>
<section>
<h1>Questions?</h1>
<small>Lauren Byrwa | <a href="http://twitter.com/labbydev">@labbydev</a></small>
</section>
</section>
</div>
<footer class="footer">
<a class="logo-wrapper" href="https://www.palantir.net/" title="Link to Palantir.net's website">
<div class="logo">
<p>Palantir.net</p>
</div>
</a>
</footer>
</div>
<script src="lib/js/head.min.js"></script>
<script src="js/reveal.js"></script>
<script>
// Full list of configuration options available at:
// https://github.com/hakimel/reveal.js#configuration
Reveal.initialize({
controls: true,
progress: true,
history: true,
center: true,
transition: 'slide', // none/fade/slide/convex/concave/zoom
// Optional reveal.js plugins
dependencies: [
{ src: 'lib/js/classList.js', condition: function() { return !document.body.classList; } },
{ src: 'plugin/markdown/marked.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/markdown/markdown.js', condition: function() { return !!document.querySelector( '[data-markdown]' ); } },
{ src: 'plugin/highlight/highlight.js', async: true, condition: function() { return !!document.querySelector( 'pre code' ); }, callback: function() { hljs.initHighlightingOnLoad(); } },
{ src: 'plugin/zoom-js/zoom.js', async: true },
{ src: 'plugin/notes/notes.js', async: true }
]
});
</script>
</body>
</html>