Apply the new design to the guidebook

.gitignore

@@ -0,0 +1,4 @@
+Gemfile.lock
+.jekyll-cache
+.jekyll-metadata
+_site

Gemfile

@@ -0,0 +1,26 @@
+source "https://rubygems.org"
+# Hello! This is where you manage which Jekyll version is used to run.
+# When you want to use a different version, change it below, save the
+# file and run `bundle install`. Run Jekyll with `bundle exec`, like so:
+#
+#     bundle exec jekyll serve
+#
+# This will help ensure the proper Jekyll version is running.
+# Happy Jekylling!
+gem "jekyll", "~> 4.1.0"
+# If you want to use GitHub Pages, remove the "gem "jekyll"" above and
+# uncomment the line below. To upgrade, run `bundle update github-pages`.
+#gem "github-pages", group: :jekyll_plugins
+
+# our markdown files don't have frontmatter
+group :jekyll_plugins do
+  gem 'jekyll-optional-front-matter'
+  gem "jekyll-readme-index"
+  gem "jekyll-titles-from-headings"
+  gem "jekyll-relative-links"
+  gem 'jekyll-commonmark'
+  gem 'jekyll-remote-theme'
+  gem 'jekyll-toc'
+  gem 'webrick'
+end
+

_config.yml

@@ -0,0 +1,19 @@
+title: W3C Guidebook
+baseurl: /guide
+remote_theme: w3c/w3c-jekyll-theme
+titles_from_headings:
+  enabled:     true
+  strip_title: true
+  collections: false
+defaults:
+  -
+    scope:
+      path: "" # an empty string here means all files in the project
+    values:
+      layout: "default"
+optional_front_matter:
+  remove_originals: true
+readme_index:
+  remove_originals: true
+toc:
+  max_level: 3

_data/navigation.yml

@@ -0,0 +1,25 @@
+pages:
+
+- title: W3C Guidebook
+  url: /guide/
+  html: /
+
+- title: Buddy System
+  url: /guide/chair/buddy.html
+  html: /chair/buddy.html
+
+- title: Document Review
+  url: /guide/documentreview/
+  html: /documentreview/
+
+- title: Manual of style
+  url: /guide/manual-of-style/
+  html: /manual-of-style/
+
+- title: Meetings
+  url: /guide/meetings/
+  html: /meetings/
+
+- title: Standards track
+  url: /guide/standards-track/
+  html: /standards-track/

_data/subpath.yml

@@ -0,0 +1,3 @@
+path:
+  - title: Home
+    url: /

_includes/prefooter.html

@@ -0,0 +1 @@
+<p>This <a href="https://github.com/w3c/Guide/">document lives in GitHub</a>, where changes can be tracked and pull requests are welcome. Feedback and comments are welcome. Please use <a href="https://github.com/w3c/Guide/issues">GitHub issues</a>.</p>

chair/buddy.md

@@ -0,0 +1,53 @@
+---
+title: W3C Chair Buddy System
+toc: true
+---
+
+The [Working Group effectiveness Task Force](https://github.com/w3c/wg-effectiveness) helped establish a Chair Buddy System by which experienced Chairs can volunteer as buddy-mentors to help buddy-mentees Chairs.
+
+Interested parties should subscribe to [[email protected]](mailto:[email protected]) ([Member-only archive](https://lists.w3.org/Archives/Member/member-chairbuddies/)[). Chairs have access to their contact information via the]() [Chairs group](https://www.w3.org/2000/09/dbwg/details?group=31972).
+
+## Principles
+
+- This program is under the responsibility of the [W3C Project Lead](https://www.w3.org/staff/project/).
+- W3C Chairs self-declare as Mentors or Mentees by writing to [[email protected]](mailto:[email protected]).
+
+  - Ideally, they add their names to this page by [editing it on GitHub](https://github.com/w3c/Guide/edit/main/chair/buddy.md).
+- The W3C Project Lead proceeds to pairing those who request to have a buddy, with those who volunteer to be a buddy.
+
+## Buddy-Mentors
+
+Thank-you for agreeing to be a W3C Chair Buddy! You should have been assigned your buddy-mentee and received their details from the W3C Team. If not, please ask the W3C Project Lead. Here are some resources and guidelines for helping you get started with being a buddy-mentor.
+
+- Email your buddy-mentee and introduce yourself! It helps if you give some details on your chair experience, some general W3C experience, and what groups you have interests in.
+- Arrange an initial meeting with your buddy-mentee. This can be a teleconference, or face-to-face if you're lucky to live in the same area or are participating in the same meeting.
+- Buddy meetings can be managed however you wish, some guidelines are given below:
+
+  - Ask questions such as "how long have you been chairing?", "what is the size of your group?", "how many chairs are there?", "what are you group working practices?", "how do you manage and conduct meetings?", "how many documents and editors do you have?", "what are your document timelines?", "tell me about your editors / participants", "where are your participants based?".
+  - Finding out as much as you can about your buddy-mentee will allow you to give the best advice!
+- Try to speak to your buddy-mentee every quarter. The job of arranging meetings should be with the buddy-mentee, but it doesn't hurt to send them a quick email every so often!
+
+Self-declared Buddy-Mentors:
+
+- [Anssi Kostiainen](https://github.com/anssiko)
+- [Léonie Watson](https://github.com/ljwatson)
+- [Charles Nevile](https://github.com/chaals)
+- [Nigel Megitt](https://github.com/nigelmegitt)
+
+## Buddy-Mentees
+
+Thank-you for joining the W3C Chair Buddy system! As a buddy-mentee you should have received details of your buddy. If you have not please ask the W3C Project Lead. Here are some guidelines for being a buddy-mentee.
+
+- Email your buddy-mentor and introduce yourself! Give details on the group you chair, whether you have a co-chair, and some quick details on the specs you're working on and the size of your group.
+- Arrange an initial meeting with your buddy-mentor. This can be a teleconference, or face-to-face if you're lucky to live in the same area or are participating in the same meeting.
+- Buddy meetings can be managed however you wish, some guidelines are given below:
+
+  - You should be giving your buddy-mentor as much information as possible about your current chairing situation, this will help them give you the best advice!
+  - You should also bring with you a list of your own questions, here are some examples: "how do you manage consensus when one or few people are blocking?", "how do you manage meetings when participants are so distributed?", "how can I help my editors get to work?", etc.
+- Try to speak to your buddy-mentor every quarter, but you may speak to them more infrequently or frequently depending on what works for you and your buddy-mentor. In yuor initial meeting try to discuss a schedule for meetings (even if you decide to do ad-hoc meetings) then arrange the meetings by sending calendar invites (or another method of your choosing).
+- It's up to you to arrange these meetings (buddy-mentors may have a few mentees, so it's best for buddy-mentees to arrange meetings).
+
+Self-declared Buddy-Mentees:
+
+- Karen Coyle (now associated with Léonie Watson)
+- Wendy Reid