Merge branch 'master' into patch-1

Author: choldgraf

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,4 @@
+contact_links:
+  - name: Questions, discussions, or general ideas
+    url: https://github.com/executablebooks/meta/discussions
+    about: Use our Community Forum for general conversations that aren't meant for actionable Issues.

.github/ISSUE_TEMPLATE/team-meeting.md

@@ -0,0 +1,26 @@
+---
+name: Team Meeting 📅
+about: A team meeting
+title: 'EBP Team Meeting - {{ MONTH }}'
+labels: meeting
+assignees: ''
+---
+
+Hello @executablebooks/ebpteam! This is an issue to track the next Executable Books team meeting! Here's some relevant information:
+
+- **Date**: Sydney time at **7:00AM on {{ MMMM DD }}** (or the day before depending on your timezone).
+- [**Google Calendar Link**](https://calendar.google.com/calendar/embed?src=2nbh00hh9020u622nt0p5qhbek%40group.calendar.google.com&ctz=America%2FLos_Angeles).
+- [**Agenda+Video Links**](https://hackmd.io/THymMOAmSICp8rJdB6_Z1w?edit)
+
+If you'd like to discuss something at the meeting, please add an item to the agenda!
+
+### Before the meeting
+
+- [ ] Update dates and make sure HackMD information is correct.
+- [ ] Team members add agenda items.
+  
+### After the meeting
+
+- [ ] Turn any follow-ups into issues/comments/etc.
+- [ ] Copy the meeting notes to the docs.
+- [ ] Remove notes and clean up HackMD.

.github/workflows/create-meeting-issue.yml

@@ -0,0 +1,18 @@
+# Open up a Team Meeting issue to prep for the meeting
+name: Create an issue on push
+on:
+  schedule:
+    # 25th day of the month, so we have a bit of lead time before the next meeting
+    - cron: '0 0 25 * *'
+  workflow_dispatch:
+    
+jobs:
+  create-team-issue:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: JasonEtco/create-an-issue@v2
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          filename: .github/ISSUE_TEMPLATE/team-meeting.md

.github/workflows/linkcheck.yml

@@ -0,0 +1,37 @@
+name: Build documentation
+
+on:
+  pull_request:
+
+jobs:
+  check-links:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-python@v2
+        with:
+          python-version: '3.9'
+          cache: 'pip'
+
+      - name: Build the documentation
+        run: |
+          pip install -r requirements.txt
+          sphinx-build docs docs/_build/html
+
+      # ref: https://github.com/lycheeverse/lychee-action
+      # ref: https://github.com/lycheeverse/lychee#commandline-parameters
+      - name: Link Checker
+        uses: lycheeverse/lychee-action@v1.5.0
+        env:
+          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
+        with:
+          fail: true
+          # github.com link below: This is a known fail
+          args: >
+            docs/_build/**/*.html
+            --insecure
+            --max-retries 10
+            --exclude-link-local
+            --exclude mailto
+            --exclude https://github.com/executablebooks/meta/edit/master/docs/contributing.md
+          jobSummary: true

README.md

@@ -1,2 +1,33 @@
-# project.executable-book
-Initial Planning and Collaborative Space for Executable Book Project
+# Executable Books Meta Project
+
+This is a repository for team planning, coordination, and discussion that doesn't belong in any specific code repository.
+
+It also serves as documentation about the Executable Books Project itself.
+
+## Build the documentation
+
+To build the documentation the easiest thing to do is to use `tox`.
+This will automatically install the environment needed for the documentation each time you build it.
+
+Install `tox` with:
+
+```
+pip install tox
+```
+
+then navigate to `meta/` and run the following:
+
+```
+tox -e docs-update
+```
+
+this will install the necessary environment the first time, then build the documentation for you.
+
+**To use a live documentation preview** you may run the following command:
+
+```
+tox -e docs-live
+```
+
+Note that this documentation uses the GitHub API to pull data about issue voting.
+To use it, you should [generate a personal access token](https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token) and then assign it to the environment variable `GITHUB_TOKEN`.

docs/_static/custom.css

@@ -5,4 +5,8 @@ ul.postlist, ul.ablog-archive {
 ul.postlist > li > p:first-child {
     font-size: 1.3em;
     margin-top: 1em;
+}
+
+.landing-grid .sd-card-header {
+    background-color: #f3772638;
 }