Difference between revisions of "2017 Website Working Group Documents"

From Code4Lib
Jump to: navigation, search
(→‎Meeting Notes)
m
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
== Meeting Notes ==
+
= 2017 Website Working Group =
 +
This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).
  
−
September 8, 2016
+
== Committee Members ==
 +
* [mailto:JGomez@getty.edu Joshua Gomez] - Primary Contact aka Chair
 +
* Your Name Here - Secondary Contact aka Co-Chair
 +
* [mailto:robin.m.fay@gmail.com Robin Fay] - Local Planning Contact (Chattanooga)
 +
* Your Name Here - Documentarian
 +
* [mailto:steven-shelton@utc.edu Steven Shelton] - Volunteer
 +
* [mailto:shaune@princeton.edu Shaun Ellis] - Volunteer or Documentarian (will figure it out after initial call)
 +
* [mailto:phette23@gmail.com Eric Phetteplace] - Volunteer
 +
* [mailto:lukeaeschleman@gmail.com Luke Aeschleman] - Volunteer
 +
* [mailto:sgritz@lmu.edu Stephanie Gritz] - Volunteer
  
−
* Introductions
+
== Meeting Notes ==
−
* Organization
+
* September 8, 2016
−
** Joshua will continue to act as Chair and call meetings
+
** Introductions
−
** Will continue to use Google Hangouts for live meetings
+
** Organization
−
** But we will not have regular meetings. Instead...
+
*** Joshua will continue to act as Chair and call meetings
−
*** We will use Github to track issues: https://github.com/code4lib/2017.code4lib.org/issues
+
*** Will continue to use Google Hangouts for live meetings
−
*** Use Slack for discussions: https://code4lib.slack.com/messages/conference-website/
+
*** But we will not have regular meetings. Instead...
−
* Tech stack
+
**** We will use Github to track issues: https://github.com/code4lib/2017.code4lib.org/issues
−
** We will use the same code as last year, and just change the data
+
**** Use Slack for discussions: https://code4lib.slack.com/messages/conference-website/
−
** Luke gave an overview of the stack, which made use of Jekyll for static site generation and a script to convert Google Forms data.
+
** Tech stack
−
* Timeline
+
*** We will use the same code as last year, and just change the data
−
** Short notice gives us less time than last year, but we are not starting from scratch so it evens out
+
*** Luke gave an overview of the stack, which made use of Jekyll for static site generation and a script to convert Google Forms data.
−
** No details on conference date or venue yet, which actually gives us some breathing room
+
** Timeline
−
**  Last year's team got the site up fairly quickly thanks to divide and conquer approach to site pages
+
*** Short notice gives us less time than last year, but we are not starting from scratch so it evens out
−
* Primary tasks
+
*** No details on conference date or venue yet, which actually gives us some breathing room
−
** Luke will take the first ticket of stripping out the 2016 details from the repo
+
***  Last year's team got the site up fairly quickly thanks to divide and conquer approach to site pages
−
*** Will also set up stub pages so we don't have to "evolve" pages like last year
+
** Primary tasks
−
** Eric will tackle upgrading the site to Jekyll 3.2
+
*** Luke will take the first ticket of stripping out the 2016 details from the repo
−
** Joshua will contact Shaun about handling DNS
+
**** Will also set up stub pages so we don't have to "evolve" pages like last year
−
** Joshua will contact members from last years team about handling precon (C. Harlow) and presentation (D. Lacey) data
+
*** Eric will tackle upgrading the site to Jekyll 3.2
−
* Other notes
+
*** Joshua will contact Shaun about handling DNS
−
** We will use the same CSS and color pallette as last year for now. Will swap out background image.
+
*** Joshua will contact members from last years team about handling precon (C. Harlow) and presentation (D. Lacey) data
 +
** Other notes
 +
*** We will use the same CSS and color pallette as last year for now. Will swap out background image.
  
 +
== Additional Documentation ==
  
 
[[Category:Code4Lib2017]]
 
[[Category:Code4Lib2017]]

Latest revision as of 15:30, 11 September 2016

2017 Website Working Group

This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experience for users (i.e., on-site and remote attendees, speakers, potential sponsors, post-conference users).

Committee Members

Meeting Notes

  • September 8, 2016
    • Introductions
    • Organization
    • Tech stack
      • We will use the same code as last year, and just change the data
      • Luke gave an overview of the stack, which made use of Jekyll for static site generation and a script to convert Google Forms data.
    • Timeline
      • Short notice gives us less time than last year, but we are not starting from scratch so it evens out
      • No details on conference date or venue yet, which actually gives us some breathing room
      • Last year's team got the site up fairly quickly thanks to divide and conquer approach to site pages
    • Primary tasks
      • Luke will take the first ticket of stripping out the 2016 details from the repo
        • Will also set up stub pages so we don't have to "evolve" pages like last year
      • Eric will tackle upgrading the site to Jekyll 3.2
      • Joshua will contact Shaun about handling DNS
      • Joshua will contact members from last years team about handling precon (C. Harlow) and presentation (D. Lacey) data
    • Other notes
      • We will use the same CSS and color pallette as last year for now. Will swap out background image.

Additional Documentation

Retrieved from "https://wiki.code4lib.org/index.php?title=2017_Website_Working_Group_Documents&oldid=44371"