deleted one letter

.github/workflows/ci.yaml

@@ -1,11 +1,33 @@
+name: CI
+
 on:
   push:
   pull_request:
     types: [opened, synchronize]
 jobs:
+  test-parse-script:
+    name: Test parse-past-meetings.sh
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, macos-latest]
+    steps:
+      - uses: actions/checkout@v2
+      - name: Test parse-past-meetings.sh
+        run: |
+          chmod +x script/parse-past-meetings.sh
+          script/parse-past-meetings.sh > /tmp/meetings-output.md
+          # Verify output contains expected content
+          if ! grep -q "## Past Meetings" /tmp/meetings-output.md; then
+            echo "Error: Output missing expected '## Past Meetings' header"
+            exit 1
+          fi
+          echo "✓ parse-past-meetings.sh executed successfully on ${{ matrix.os }}"
+
   build:
     runs-on: ubuntu-latest
     name: script/cibuild
+    needs: test-parse-script
     steps:
       - uses: actions/checkout@v2
       - uses: ruby/setup-ruby@v1
@@ -16,3 +38,9 @@ jobs:
         run: script/bootstrap
       - name: test
         run: script/cibuild
+      - name: Upload site artifact
+        if: success()
+        uses: actions/upload-artifact@v4
+        with:
+          name: site
+          path: _site

.github/workflows/crontab.yml

@@ -0,0 +1,50 @@
+name: Weekly Team Sync
+on:
+  schedule:
+    - cron: 07 00 1-7 * *
+
+jobs:
+  create_issue:
+    name: Rollover website after this month's club meeting
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+    steps:
+      - name: Create issue
+        run: |
+          if [ "$(date +%u)" = "1" ]; then
+            new_issue_url=$(gh issue create \
+              --title "$TITLE" \
+              --assignee "$ASSIGNEES" \
+              --label "$LABELS" \
+              --body "$BODY")
+            if [[ $PINNED == true ]]; then
+              gh issue pin "$new_issue_url"
+            fi
+          fi
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_REPO: ${{ github.repository }}
+          TITLE: Rollover website after this month's club meeting
+          ASSIGNEES: kn6yuh
+          LABELS: monthly-rollover
+          BODY: |
+
+            Each of the main steps can be executed by a different person. For simplicity, I'm just creating a single bug.
+
+            ### Rollover website
+            This requires running the followins script from a *nix machine:
+              `./script/rollover-to-next-month.sh`
+
+            ### Add YouTube video to the last meeting
+            1. Upload recording to shared drive
+            2. Edit the video
+            3. Upload the video to the YT channel
+            4. Link the video in the meeting page (see past meetings as examples)
+            5. Run the script to regenerate the index (`./script/parse-past-meetings.sh > _includes/meetings-template.md`)
+
+            Resolve the issue when both the rollover is done, and the YT video is uploaded and linked.
+
+          PINNED: false
+          CLOSE_PREVIOUS: false
+

.github/workflows/monthly-newsletter-reminder.yml

@@ -0,0 +1,33 @@
+name: Monthly Newsletter Reminder
+on:
+  schedule:
+    # Run at 00:07 UTC on the 1st of every month
+    - cron: 07 00 1 * *
+
+jobs:
+  create_issue:
+    name: Create PAARAgraphs newsletter reminder issue
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+    steps:
+      - name: Create issue
+        run: |
+          NEWSLETTER_MONTH=$(date -d "6 months ago" +"%B %Y")
+          gh issue create \
+            --title "Post $NEWSLETTER_MONTH PAARAgraphs newsletter" \
+            --label "$LABELS" \
+            --body "$(echo "$BODY" | sed "s/{month}/$NEWSLETTER_MONTH/g")"
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GH_REPO: ${{ github.repository }}
+          LABELS: monthly-rollover
+          BODY: |
+
+            @kn6yuh please comment with {month}'s PDF Google Drive link.
+
+            The instructions on how to do it are at https://github.com/PAARA-org/paara-org.github.io/blob/master/README.md#how-to-add-a-new-newsletter-paaragraphs-issue-via-script
+
+            #156 as an example of how it's been done in the past.
+
+            @PAARA-org/webmasters : would any of you want to work on this? Thanks!

.gitignore

@@ -3,3 +3,8 @@ _site
 Gemfile.lock
 *.gem
 .jekyll-cache
+.DS_Store
+.claude/
+vendor/
+.bundle/
+.ruby-version

ARCHITECT.md

@@ -0,0 +1,112 @@
+# The Architect theme
+
+*Architect is a Jekyll theme for GitHub Pages. You can [preview the theme to see what it looks like](http://pages-themes.github.io/architect), or even [use it today](#usage).*
+
+## Usage
+
+To use the Architect theme:
+
+1. Add the following to your site's `_config.yml`:
+
+    ```yml
+    remote_theme: pages-themes/architect@v0.2.0
+    plugins:
+    - jekyll-remote-theme # add this line to the plugins list if you already have one
+    ```
+
+2. Optionally, if you'd like to preview your site on your computer, add the following to your site's `Gemfile`:
+
+    ```ruby
+    gem "github-pages", group: :jekyll_plugins
+    ```
+
+## Customizing
+
+### Configuration variables
+
+Architect will respect the following variables, if set in your site's `_config.yml`:
+
+```yml
+title: [The title of your site]
+description: [A short description of your site's purpose]
+```
+
+Additionally, you may choose to set the following optional variables:
+
+```yml
+show_downloads: ["true" or "false" (unquoted) to indicate whether to provide a download URL]
+google_analytics: [Your Google Analytics tracking ID]
+```
+
+### Stylesheet
+
+If you'd like to add your own custom styles:
+
+1. Create a file called `/assets/css/style.scss` in your site
+2. Add the following content to the top of the file, exactly as shown:
+    ```scss
+    ---
+    ---
+
+    @import "{{ site.theme }}";
+    ```
+3. Add any custom CSS (or Sass, including imports) you'd like immediately after the `@import` line
+
+*Note: If you'd like to change the theme's Sass variables, you must set new values before the `@import` line in your stylesheet.*
+
+### Layouts
+
+If you'd like to change the theme's HTML layout:
+
+1. For some changes such as a custom `favicon`, you can add custom files in your local `_includes` folder. The files [provided with the theme](https://github.com/pages-themes/architect/tree/master/_includes) provide a starting point and are included by the [original layout template](https://github.com/pages-themes/architect/blob/master/_layouts/default.html).
+2. For more extensive changes, [copy the original template](https://github.com/pages-themes/architect/blob/master/_layouts/default.html) from the theme's repository<br />(*Pro-tip: click "raw" to make copying easier*)
+3. Create a file called `/_layouts/default.html` in your site
+4. Paste the default layout content copied in the first step
+5. Customize the layout as you'd like
+
+### Customizing Google Analytics code
+
+Google has released several iterations to their Google Analytics code over the years since this theme was first created. If you would like to take advantage of the latest code, paste it into `_includes/head-custom-google-analytics.html` in your Jekyll site.
+
+### Overriding GitHub-generated URLs
+
+Templates often rely on URLs supplied by GitHub such as links to your repository or links to download your project. If you'd like to override one or more default URLs:
+
+1. Look at [the template source](https://github.com/pages-themes/architect/blob/master/_layouts/default.html) to determine the name of the variable. It will be in the form of `{{ site.github.zip_url }}`.
+2. Specify the URL that you'd like the template to use in your site's `_config.yml`. For example, if the variable was `site.github.url`, you'd add the following:
+    ```yml
+    github:
+      zip_url: http://example.com/download.zip
+      another_url: another value
+    ```
+3. When your site is built, Jekyll will use the URL you specified, rather than the default one provided by GitHub.
+
+*Note: You must remove the `site.` prefix, and each variable name (after the `github.`) should be indent with two space below `github:`.*
+
+For more information, see [the Jekyll variables documentation](https://jekyllrb.com/docs/variables/).
+
+## Roadmap
+
+See the [open issues](https://github.com/pages-themes/architect/issues) for a list of proposed features (and known issues).
+
+## Project philosophy
+
+The Architect theme is intended to make it quick and easy for GitHub Pages users to create their first (or 100th) website. The theme should meet the vast majority of users' needs out of the box, erring on the side of simplicity rather than flexibility, and provide users the opportunity to opt-in to additional complexity if they have specific needs or wish to further customize their experience (such as adding custom CSS or modifying the default layout). It should also look great, but that goes without saying.
+
+## Contributing
+
+Interested in contributing to Architect? We'd love your help. Architect is an open source project, built one contribution at a time by users like you. See [the CONTRIBUTING file](docs/CONTRIBUTING.md) for instructions on how to contribute.
+
+### Previewing the theme locally
+
+If you'd like to preview the theme locally (for example, in the process of proposing a change):
+
+1. Clone down the theme's repository (`git clone https://github.com/pages-themes/architect`)
+2. `cd` into the theme's directory
+3. Run `script/bootstrap` to install the necessary dependencies
+4. Run `bundle exec jekyll serve` to start the preview server
+5. Visit localhost:4000 in your browser to preview the theme
+
+### Running tests
+
+The theme contains a minimal test suite, to ensure a site with the theme would build successfully. To run the tests, simply run `script/cibuild`. You'll need to run `script/bootstrap` once before the test script will work.

CNAME

@@ -0,0 +1 @@
+paara.org

Gemfile

@@ -2,4 +2,7 @@
 
 source "https://rubygems.org"
 
+gem "github-pages", group: :jekyll_plugins
+gem "jekyll-remote-theme", group: :jekyll_plugins
+
 gemspec

PREVIEW.md

@@ -0,0 +1,19 @@
+# Previewing the site locally
+
+## Prerequisites
+
+The following packages are required (correct for Ubuntu 24.04.4 — your distro may differ):
+
+```sh
+sudo apt install build-essential ruby3.2-dev
+```
+
+`ruby3.2-dev` pulls in `ruby3.2`. `build-essential` is needed to compile native gem extensions.
+
+## Usage
+
+```sh
+./preview.sh
+```
+
+Open http://localhost:4000. Jekyll auto-regenerates on file changes — just save and refresh.