Difference between pages "Presenters Resource Page" and "Tutorials/d8otb/outline"

From LCA2015 Delegate wiki
(Difference between pages)
Jump to: navigation, search
 
(Building a website with Drupal 8)
 
Line 1: Line 1:
Page of resources for miniconf organisers and presenters at miniconfs
+
{{Trail|Programme|Tutorials|Tutorials/Drupal8 outta the box}}
  
  
=== [http://linux.conf.au/programme/presenter_faq Presenters FAQ] ===
+
= Planning to build a website =
  
=== lca2015 logos ===
+
We won't be going through this section in detail in the tutorial.  We'll be building a sample site with a lot of this thinking already done. But if you want to use your own sample content, have a think about these things and come prepared!
  
[http://lca2015.linux.org.au/wiki/File:LCA_2015_logo-xparent.png lca2015 logo on transparent background], 
+
Or if you want to choose your own dummy content, rather than use the samples provided... here's some fun sites to peruse.
[http://lca2015.linux.org.au/wiki/File:LCA_2015_logo-reverse.png lca2015 logo in reverse], and
+
[http://lca2015.linux.org.au/wiki/File:LCA_2015_logo-reverse-xparent.png lca2015 logo in reverse + transparent background]
+
  
Links above are to the page with the image. We're not displaying images here as we don't want them loading each time visit this page. Please don't change the links above to display the images on this page. Thanks
+
'''Words'''
  
=== Links to lca2015 website or wiki ===
+
* http://mashable.com/2013/07/11/lorem-ipsum/
 +
* http://www.cupcakeipsum.com/ -- Cupcake ipsum is my favourite.
  
When linking to any page on the lca2015 website or wiki, please use <nowiki>http://lca2015.linux.org.au/</nowiki> instead of <nowiki>http://linux.conf.au/ </nowiki>.  <nowiki>http://</nowiki> instead of <nowiki>http://</nowiki> and <nowiki>lca2015.linux.org.au instead of <nowiki>linux.conf.au</nowiki> 
+
'''Pictures'''
  
This ensures links will continue to work in future, when the wiki + website is archived. At some point later in 2015 linux.conf.au will be used as the url for lca2016 conference.
+
* http://placehold.it/
 +
* https://placekitten.com/
  
website: <nowiki>http://lca2015.linux.org.au/</nowiki> or wiki <nowiki>http://lca2015.linux.org.au/wiki</nowiki>.
+
=== Purpose ===
  
Example:
 
  
The Astronomy miniconf wiki page, please use <nowiki>http://lca2015.linux.org.au</nowiki>/wiki/Astronomy_Miniconf  instead of <nowiki>https://linux.conf.au/wiki/Astronomy_Miniconf</nowiki>
+
What job will this site have?
 +
* sell stuff?
 +
* build a community?
 +
* documentation?
 +
* record an event?
  
URL for Monday's schedule <nowiki>http://lca2015.linux.org.au/programme/schedule/monday</nowiki> instead of <nowiki>https://linux.conf.au/programme/schedule/monday</nowiki>
 
Abstract <nowiki>http://lca2015.linux.org.au/schedule/30081/view_talk?day=monday</nowiki> instead of <nowiki>https://linux.conf.au/schedule/30081/view_talk?day=monday</nowiki>
 
  
 +
=== Audience ===
  
  
=== Slide Lint ===
+
Who will visit the website?
 +
* Personas
 +
* Demographics
 +
* Language / Geography
 +
* Devices / Browsers
  
* 2 versions: Web called [http://slidelint.net/ slidelint site] and command line, called slidelint.
 
* Both by Tim 'mithro' Ansell.
 
  
* Slidelint site:
 
** Newer + better version than slidelint.
 
** No installations required.
 
** [http://youtu.be/io9P5fZdqcE Tim's lightning talk at PyconAu 2014]. First 1:25 is on slidelint site.
 
  
* Slidelint:
+
=== Content ===
** [http://lists.lca2015.linux.org.au/pipermail/chat/2014-December/000042.html Info] why it was created, how to install + use.
+
** [http://youtu.be/1bkbyfP--BM lca2014 lightning talk on slidelint]
+
  
* GitHub for [https://github.com/mithro/slidelint slidelint] and [https://github.com/timvideos/slidelint_site slidelint site].
+
Getting the information architecture right from the start is important.
 +
* Content Modelling
 +
* Navigation
 +
* Search
 +
* Taxonomy
  
=== Web based lightning talk timer ===
+
This is the stuff your website is all about.  Here's some resources on creating compelling content for the web.
* Tim Ansell's web based lightning talk timer http://lightningtimer.info/ or http://lightningtimer.cc/ or http://lightningtimer.io/ 
+
* [https://github.com/mithro/lightningtimer GitHub] page has info on how to use it.
+
  
 +
http://www.squiz.net/au/stories/insights/10-commandments-for-content-creation
  
=== About the AV Systems in-room ===
+
=== Style / Design / Mockups / Wireframes ===
  
We are using the University of Auckland facilities for this, which are all very modern and widely compatible with the majority of systems. We are the taking both SD and in some cases HD feeds, to enable the recording and streaming requirements of the presentations.
+
We're using D8 Outta the box, so we'll be using Bartik.  Not doing a lot of design, but still, need to think about colour, images, logo.
 +
* Logo
 +
* Colour
 +
* Images
 +
* Layout
  
All speakers must have their own laptop to present on. If you do not have one or have an unexpected issue, please liaise with the NOC-AV team and we can probably help you (by exception).
+
Resources
  
Please expect to provide a VGA output. The Native Resolution of the system is 720p (1280x720).  Other resolutions are likely to work, but these are not officially supported by the AV team.  Experience to-date suggests most standard video resolutions will work OK, but YMMV.
+
https://wireframe.cc/
  
There is an analogue audio (3.5mm) jack available for guest connections if you require the sound of your PC to be heard in the room on the PA systemEach room has a lecturn (goose-neck) Mic, at least one lapel radio mic and at least one handheld radio mic.  Please use the Microphones and the audio inputs etc, to ensure your audio is captured for the stream and for the recordings.
+
=== Planning Tools ===
 +
There's a range of tools out there to help you plan your site.  (know any others? Add them here.)
  
There is a document camera available in each room, which can be used to show hard-copy, tablet/phone screens or other physical hardware items for presentation purposes.
+
* https://www.jumpchart.com/
 +
 
 +
== Join the community ==
 +
We'll be working with Drupal8.  The training sites we're using were built against HEAD late last week.  So they're a little bit behind the bleeding edge, and they're very much in BETA.  So we're likely to hit some rough edges.  If you do, report them.  To do that, you'll need to have an account on Drupal.org
 +
 
 +
 
 +
=== Go to https://www.drupal.org/user/register ===
 +
 
 +
It looks like this.
 +
 
 +
 
 +
 
 +
 
 +
== Building a website with Drupal 8 ==
 +
 
 +
=== Basic site configuration ===
 +
[[File:D8otb-siteinfo.png|right]]
 +
* Site name
 +
* Site slogan
 +
* Email address
 +
* Default front page, and error pages
 +
 
 +
=== Nodes and other entities ===
 +
 
 +
==== Default content types ====
 +
 
 +
* Article
 +
* Basic Page
 +
 
 +
Go to SITEURL/node/add to add content
 +
 
 +
==== Custom content types ====
 +
 
 +
Go to SITEURL/admin/structure/types/add
 +
 
 +
==== Users ====
 +
 
 +
* anon
 +
* auth
 +
* admin
 +
 
 +
===== Roles =====
 +
 
 +
===== Permissions =====
 +
 
 +
==== Taxonomy ====
 +
 
 +
=== Menus ===
 +
[[File:d8otc-menus.png|right|400px]]
 +
We get a few menus out of the box
 +
 
 +
But we can also add menus of our own
 +
 
 +
=== Views ===
 +
 
 +
Views.  The single most popular module for previous versions of Drupal, is now in core. It's a powerhouse. But complex. We'll start simple.
 +
Views is a list maker, a query generator. It lets you slice and dice your content in all sorts of wonderful ways.
 +
 
 +
=== Blocks ===
 +
 
 +
 
 +
 
 +
=== Wysiwyg ===
 +
 
 +
 
 +
 
 +
=== Mobile ===
 +
 
 +
 
 +
 
 +
=== RSS, Json and other feeds and streams ===

Revision as of 09:50, 12 January 2015

< Main Page < Programme < Tutorials < Tutorials/Drupal8 outta the box


Planning to build a website

We won't be going through this section in detail in the tutorial. We'll be building a sample site with a lot of this thinking already done. But if you want to use your own sample content, have a think about these things and come prepared!

Or if you want to choose your own dummy content, rather than use the samples provided... here's some fun sites to peruse.

Words

Pictures

Purpose

What job will this site have?

  • sell stuff?
  • build a community?
  • documentation?
  • record an event?


Audience

Who will visit the website?

  • Personas
  • Demographics
  • Language / Geography
  • Devices / Browsers


Content

Getting the information architecture right from the start is important.

  • Content Modelling
  • Navigation
  • Search
  • Taxonomy

This is the stuff your website is all about. Here's some resources on creating compelling content for the web.

http://www.squiz.net/au/stories/insights/10-commandments-for-content-creation

Style / Design / Mockups / Wireframes

We're using D8 Outta the box, so we'll be using Bartik. Not doing a lot of design, but still, need to think about colour, images, logo.

  • Logo
  • Colour
  • Images
  • Layout

Resources

https://wireframe.cc/

Planning Tools

There's a range of tools out there to help you plan your site. (know any others? Add them here.)

Join the community

We'll be working with Drupal8. The training sites we're using were built against HEAD late last week. So they're a little bit behind the bleeding edge, and they're very much in BETA. So we're likely to hit some rough edges. If you do, report them. To do that, you'll need to have an account on Drupal.org


Go to https://www.drupal.org/user/register

It looks like this.



Building a website with Drupal 8

Basic site configuration

D8otb-siteinfo.png
  • Site name
  • Site slogan
  • Email address
  • Default front page, and error pages

Nodes and other entities

Default content types

  • Article
  • Basic Page

Go to SITEURL/node/add to add content

Custom content types

Go to SITEURL/admin/structure/types/add

Users

  • anon
  • auth
  • admin
Roles
Permissions

Taxonomy

Menus

d8otc-menus.png

We get a few menus out of the box

But we can also add menus of our own

Views

Views. The single most popular module for previous versions of Drupal, is now in core. It's a powerhouse. But complex. We'll start simple. Views is a list maker, a query generator. It lets you slice and dice your content in all sorts of wonderful ways.

Blocks

Wysiwyg

Mobile

RSS, Json and other feeds and streams