The goal of Lunch Club is to preserve, bolster, and advance Digital's culture of excellence and innovation by sharing stuff that we love as often as possible, with as little friction, pomp, and ceremony as possible.
Any person at any location can share. Scrounge up and/or synthesize something awesome and share it!
WARNING
This repo is public. DO NOT put any webs confidential information in here!
Almost anything is acceptable.
Content that challenges and/or bolsters our 'best practices', technologies, architecture, software design patterns, culture, etc is encouraged.
See CONTENT_EXAMPLES.md for examples (or add some of your own).
Date | Title | Duration | Resources |
---|---|---|---|
Fri Mar 6 | Rich Hickey: Simple Made Easy | 60 min | Link |
Fri Mar 20 | [who was present for this?] | ||
Wed Mar 23 | Gary Bernhard Medley | 40 min | Link |
Fri Mar 27 | Bill Scott: Bringing Change To Life | 60 min | Link |
Fri Apr 3 | Performance Talk Combo (HTTP/2, Chrome Profiling) | 30m+30m | Link |
Fri Apr 10 | Getting familiar with the VP GTM Process | 60 mins | Link |
Fri Apr 17 | - | ||
Mon Apr 20 | Contributing to medium-editor: What we've learned | 60 min | Link |
Fri Apr 24 | The Basics of Nodejs | 60 min | Link |
Mon Apr 27 | Implementing gratuitously animated UIs | 60 min | Link |
Fri May 01 | the JVM in the 21st century | 60 min | Link |
Mon May 04 | Pycon talk: The average programmer | 45 min | Video |
Wed May 13 | How We React | 60 min | Link |
Fri May 15 | - | ||
Mon May 18 | tpope and Vim | 60 min | Link |
Fri May 22 | Douglas Adams's Hyperland | 50 min | Link |
Wed May 27 | The Soul of Software | 45 min | Link |
Fri Jun 05 | Building Better UIs | 60 min | Link |
Mon Jun 15 | v0.1.0 of Our Semantic Versioning Knowledge | 45 min | Link |
- "Be Excellent To Each Other"
Make a pull request against the repo and publicize your intent to share something!
It's completely OK to introduce tentative entries with a 'TBD' date (imagine a scenario where you want to share something, but you aren't ready to commit to a date yet).
See CONTRIBUTING.md for more information.
If your discussion requires a presentation, the README.md
can be used to automagically
generate and open a presentation via npm's start
task with some additional parameters.
Presentations are powered by the awesome reveal.js
library which is a dependency of this repo - be sure to npm install
if you plan to present.
The start
task takes the following arguments:
presentationFile
(required) which needs to be a root-relative path to the markdown file
containing the "slides".
revealOptions
(optional) is escaped JSON which is passed to the reveal.js presenter.
Here are the options.
theme
(optional) is a root-relative path to the stylesheet to use for the presentation.
When this option is omitted, the presenter will first look for a stylesheet adjacent to the passed
presentationFile
. If nothing is given or found, this will default to reveal.js's black
theme.
Example:
npm start presentationFile="resources/2015-04-20/README.md"
In the example above, since resources/2015-04-20/README.md
has an adjacent style.css
, it will render
a special stylesheet without needing an additional theme=
parameter to be passed.
A number of themes are available through the reveal.js dependency that will not
require any additional CSS to be written. Just pass a path to the theme
argument,
e.g. theme="./node_modules/reveal.js/css/theme/white.css"
.
PDFs can be generated from presentations with the ?print-pdf
query param.
In presentations, two line breaks will create a new vertical slide. Three line breaks will create a new horizontal slide.
Often times markup-like code is added to the presentations to allow for things like slide "fragments".
"Fragments" are revealed when the presenter wants to show them (instead of everything being displayed at once when the slide is presented).
If you're just reading the content of the slides you probably want to remove that extra code.
You can view the notes without that extra code with something like this:
sed s/\<\!--\.\*--\>//g resources/2015-05-01/README.md | less
And here's an example for vim with Markdown syntax highlighting:
sed s/\<\!--\.\*--\>//g resources/2015-05-01/README.md | vim - -c "set syntax=markdown"