Merge branch 'main' into v1/add-research-cycle

Author: NeuroShepherd

.github/_name_checker.py

@@ -31,28 +31,28 @@
     print()
     errors_found = True
 
-# Check 2: Files containing hyphens instead of underscores
-files_with_hyphens = [name for name in names_from_files if '-' in name]
-if files_with_hyphens:
-    print("ERROR: Profile names with hyphens found (use underscores instead):")
-    for name in files_with_hyphens:
+# Check 2: Files containing underscores instead of hyphens
+files_with_underscores = [name for name in names_from_files if '_' in name]
+if files_with_underscores:
+    print("ERROR: Profile names with underscores found (use hyphens instead):")
+    for name in files_with_underscores:
         print(f"  - {name}")
     print()
     errors_found = True
 
 # Check 3: Files containing spaces
 files_with_spaces = [name for name in names_from_files if ' ' in name]
 if files_with_spaces:
-    print("ERROR: Profile names with spaces found (use underscores instead):")
+    print("ERROR: Profile names with spaces found (use hyphens instead):")
     for name in files_with_spaces:
         print(f"  - {name}")
     print()
     errors_found = True
 
 # Check 4: Files containing non-ASCII characters (umlauts, etc.)
-files_with_special_chars = [name for name in names_from_files if not re.match(r'^[a-zA-Z0-9_]+$', name)]
+files_with_special_chars = [name for name in names_from_files if not re.match(r'^[a-zA-Z0-9-]+$', name)]
 if files_with_special_chars:
-    print("ERROR: Profile names with special characters found (use only a-z, A-Z, 0-9, and underscores):")
+    print("ERROR: Profile names with special characters found (use only a-z, A-Z, 0-9, and hyphens):")
     for name in files_with_special_chars:
         print(f"  - {name}")
     print()
@@ -62,12 +62,12 @@
 if errors_found:
     print("Profile naming convention checks FAILED.")
     print("Please ensure profile filenames:")
-    print("  - Use underscores (_) instead of hyphens or spaces")
-    print("  - Contain only ASCII characters (a-z, A-Z, 0-9, _)")
+    print("  - Use hyphens (-) instead of underscores or spaces")
+    print("  - Contain only ASCII characters (a-z, A-Z, 0-9, -)")
     print("  - Are unique (no duplicates)")
     print("If there are duplicate names, consider adding middle initials to differentiate them.")
     print("If middle initials are already used, consider adding full middle names.")
-    print("The final option, if needed, is to append a numeric suffix (e.g., _1, _2) to make names unique.")
+    print("The final option, if needed, is to append a numeric suffix (e.g., -1, -2) to make names unique.")
     sys.exit(1)
 else:
     print("All profile naming convention checks PASSED.")

.github/add-new-year-to-events.md

@@ -0,0 +1,62 @@
+---
+title: Add new year to events page
+labels: Events
+---
+
+Each year, a new listing for Past events needs to be added to the Events page here:
+
+https://github.com/lmu-osc/lmu-osc.github.io/blob/main/events/index.qmd
+
+The code that needs to be added looks like this:
+
+```yaml
+listing:
+  - id: upcoming-events
+    template: upcoming-events-template.ejs
+    contents: events/
+    sort-ui: [title, date]
+    sort: "date desc"
+    filter-ui: true
+    page-size: 999
+    categories: unnumbered
+  - id: year_2025
+    contents: events/ 
+    sort: "date desc"
+    page-size: 999
+    template: past-events-template.ejs
+    template-params:
+      year: 2025
+  - id: year_2024
+    contents: events/ 
+    sort: "date desc"
+    page-size: 999
+    template: past-events-template.ejs
+    template-params:
+        year: 2024
+...
+```
+
+Simply insert another chunk of this code with updated years:
+
+```yaml
+  - id: year_2024
+    contents: events/ 
+    sort: "date desc"
+    page-size: 999
+    template: past-events-template.ejs
+    template-params:
+        year: 2024
+```
+
+And then updated the page below to look like this:
+
+```
+## Past Events
+
+### New year here
+
+::: {#year_YYYY}
+:::
+
+...
+```

.github/workflows/add-new-year-to-events.yml

@@ -0,0 +1,20 @@
+on:
+  repository_dispatch:
+  workflow_dispatch:
+  schedule:
+    - cron: "0 0 1 1 *"
+
+jobs:
+  linkChecker:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write # required for peter-evans/create-issue-from-file
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+      - name: Create issue
+        uses: JasonEtco/create-an-issue@v2
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          filename: .github/add-new-year-to-events.md

.github/workflows/publish.yml

@@ -12,9 +12,20 @@ jobs:
     runs-on: ubuntu-latest
     permissions:
       contents: write
+    env:
+      RENV_CONFIG_AUTO_SNAPSHOT: "false"
+      RENV_CONFIG_SNAPSHOT_TYPE: "explicit"
     steps:
       - name: Check out repository
         uses: actions/checkout@v4
+
+      - name: Install system dependencies
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y --no-install-recommends \
+            libcurl4-openssl-dev \
+            libssl-dev \
+            libxml2-dev
       
       - name: Install R
         uses: r-lib/actions/setup-r@v2

.gitignore

@@ -53,8 +53,8 @@ rsconnect/
 _site/
 _freeze/
 
-# Quarto LMU Open Science Center templates
-lmu-osc-custom.scss
 
 **/*.quarto_ipynb
 quick_notes.md
+
+/.luarc.json

.lycheeignore

@@ -1,3 +1,42 @@
 https://lists.lrz.de/mailman/listinfo/lmu-osc
 https://www.psy.lmu.de/
-https://lmu-munich.zoom.us/
+https://lmu-munich.zoom.us/
+https://lmu-munich.zoom-x.de
+https://*.zoom.us*
+https://*.zoom-x.us*
+https://*.zoom.de*
+https://*.zoom-x.de*
+https://tellmi.psy.lmu.de/formr/*
+https://www.linkedin.com/*
+https://doi.org/*
+https://www.researchgate.net/profile/*
+
+
+
+
+
+
+https://jobs.zeit.de/jobs/muenchen_professur_w2_fuer_klinische_psychologie_und_psychotherapie_152537.html?wt_zmc=nl.int.zonpmr.jobnewsletter.2018-01-18.stellenmarkt.textlink.selektion.x&c=429152&si=qBad04Sbm08t1mUV5uQYKWEdSm6es4egoFdnXVrU2mTUNSSUSKLgArjblpxl2ksMcXOIIG9zq0W8AQNhqqMvw&utm_medium=nl&utm_campaign=jobnewsletter&utm_source=2018-01-18&wt_cc1=static.6
+
+https://akademie-soziologie.de/wp-content/uploads/2018/03/20180308_Stellungnahme-zu-Replikation.pdf
+https://ub.fau.de/schulungen/a-short-introduction-to-data-publishing-and-data-journals/
+https://ub.fau.de/schulungen/a-short-introduction-to-data-publishing-and-data-journals/
+https://www.br.de/radio/br24/sendungen/campusmagazin/campus-gespraech-felix-schoenbrodt-open-science-center-lmu-100.html
+https://www.uni-muenchen.de/aktuelles/preise/2020/hochschulperle.html
+https://www.youtube.com/watch?v=Fo7GP95Fs2w&list=PLgqUxMeOmFHz3dxbD-zR7kbuaJbeB9SWD&index=2
+https://www.youtube.com/watch?v=YaHlcwyn2Jk&feature=youtu.be
+https://zeitung.faz.net/faz/geisteswissenschaften/2021-05-26/276e8404c41a1bbca09960cbd628341f/?GEPC=s5
+https://conferences.leibniz-psychology.org/index.php/openscience/os2019
+https://www.graduatecenter.uni-muenchen.de/veranstaltungen/kurzbuendig/open_science/index.html
+https://www.graduatecenter.uni-muenchen.de/veranstaltungen/kurzbuendig/open_science/index.html
+https://www.open-science-conference.eu/registration/
+
+
+https://christina-peter.jimdosite.com/
+https://leibniz-psychology.org/en/services/media-center/
+https://www.berlin-university-alliance.de/
+https://www.edu.lmu.de/lbp/personen/lehrstuhlinhaber/gebhardt/index.html
+https://www.edu.lmu.de/lernbehindertenpaedagogik/personen/wiss_ma/ebenbeck/index.html
+https://www.fu-berlin.de/sites/open-science/index.html
+https://www.mzes.uni-mannheim.de/openscience/
+https://www.taisukeimai.com/*

README.md

@@ -1,57 +1,92 @@
-# LMU Open Science Center Home Page
+# LMU Open Science Center Website
+
+TL;DR: Run these commands to download the project, and build the first time.
+
+```bash
+git clone git@github.com:lmu-osc/lmu-osc.github.io.git
+cd lmu-osc.github.io
+R -e "renv::restore()"  
+quarto preview
+```
+
+The `renv:restore()` and `quarto preview` processes might take a bit to run the first time so go brew a ☕.
 
 ## Overview
 
-This repository hosts the OSC's home webpage where content from workshops, other websites, and related information is organized/linked to.
+This repository contains the source for the LMU Open Science Center website.
 
-## Updating this Page
+The site is built with [Quarto](https://quarto.org/) as a multi-page website and combines hand-authored content, reusable templates, custom styling, and a small amount of automation for publishing and maintenance.
 
-A CI/CD pipeline for automatically rendering and redeploying the website has been set up using GitHub Actions. What does this mean? TL;DR only changes to `.qmd` files (and `_quarto.yml`) should be made, and users who wish to make changes will need to make a new branch, push that branch to this repo, and open a pull request for their changes.
+At a high level, this repository contains the public-facing OSC website content, the navigation and page structure across the main site sections, the reusable templates and styling that support them, and the automation used for publishing and lightweight repository checks.
 
-### Detailed Explanation
+## Tech Stack
 
-High-level: the GitHub Action is configured to automatically rebuild and redeploy the site whenever a push is made to the `main` branch of this repository. There is a branch protection rule preventing direct pushes to `main` so pull requests for changes are required. The GH Action rebuilds the website on the `gh-pages` branch of this repo, and the GitHub Pages configuration is currently set to deploy the website from this branch in the Settings -> Pages repo section.
+The site is built with [Quarto](https://quarto.org/) and uses R with `renv` for reproducible dependency management. Content is primarily authored in YAML, Markdown, and `.qmd` files, with styling handled through SCSS and CSS. Deployment and repository checks are automated through GitHub Actions. The main Quarto configuration lives in `_quarto.yml`, rendered output is written to `_site/`, and Quarto caching is stored in `_freeze/`.
 
-### Making Changes
+## Repository Structure
 
-If you don't already have the repository on your system, clone a copy.
+The most important top-level directories are:
 
-```
-git clone git@github.com:lmu-osc/lmu-osc.github.io.git
-```
+- `about/`: About pages and organizational information
+- `assets/`: shared images, JavaScript, Bootstrap, and Font Awesome assets
+- `events/`: event pages, templates, and helper scripts
+- `footer/`: footer markup and footer-specific styling
+- `news/`: news pages and metadata
+- `partners/`: partner and institutional member pages
+- `people/`: people pages, profile data, and listing templates
+- `training/`: training catalog, tutorials, and training-track content
+- `scripts/`: helper scripts used during site maintenance
+- `renv/`: project-local R environment management
+- \*`_site/`: rendered website output
+- \*`_freeze/`: Quarto execution cache
 
-If you cloned a while ago or your copy is otherwise likely to be behind the code on GitHub, you'll want to pull the changes to your computer. (This is equivalent to fetching the changes *and* merging them.)
+The main entry point for the site is `index.qmd`.
 
-```
-git pull
-```
+\* These files will appear locally, but do not and should not be on the GitHub repo.
 
-Note that this will only integrate the changes for the branch you currently have checked out. If you want to pull changes for **all** of the branches you have locally and that have changes on GitHub, run `git pull --all` instead.
+## Content Organization
 
-At this point, your local copy should be synced up with the remote repository on GitHub. To make changes, you will now need to create a new branch and checkout that new branch so you are working on it.
+Most pages in the repository are written as `.qmd` files. Section folders typically contain a landing page such as `index.qmd`, individual content pages, and any templates, metadata files, stylesheets, or helper scripts that are specific to that section. Some areas have their own internal documentation or specialized workflows. For example, `people/` contains profile pages, listing templates, and its own README for the people-page data model, while `events/` and `news/` include helper scripts for creating, migrating, or transferring content. In general, source content should be edited in the section folders rather than in `_site/`.
 
-```
-git branch <new_branch>
-git checkout <new_branch>
-```
+## Local Development
 
-Make any desired changes and commit them. You can use the template code below or use your GUI for this easily.
+### Prerequisites
 
-```
-git add -A
-git commit -m "Your message here"
-```
+To work on this site locally, you should have Quarto, R, the project dependencies restored via `renv`, and `curl` available on your system. An IDE such as RStudio or VS Code is helpful, but not required.
+
+### Initial Setup
 
-If this is a new branch, you will need to push the branch to GitHub.
+Clone the repository, open the project, and restore the R dependencies.
 
+In R:
+
+```r
+renv::restore()
 ```
-git push -u origin <new_branch>
+
+This project uses a project-local `renv` library so builds are reproducible across machines and CI.
+
+### Previewing the Site
+
+To preview the site locally, run:
+
+```bash
+quarto preview
 ```
 
-Now, there should be a notification on the repo page that a new branch has been pushed, and it should also ask if you would like to open a pull request. Follow this link, write an informative title and description of the pull request, and open it for review. (Ideally, someone else will be able to review your changes, but self-approvals are also fine if needed.) Following review, there are generally 3 options for pull requests: squashing, merging, and rebasing. I've disabled rebasing in this repo, and one should squash commits. (Squashing basically collapses all of the commits on your working branch e.g. `<new_branch>` into a single commit. It's a method to keep the commit history relatively clean and clear.)
+This starts a local preview server so you can inspect changes before committing them. Quarto writes the rendered output to `_site/`.
+
+## Contribution Guidance
+
+When contributing to the site, edit source files such as `.qmd`, `.yml`, `.css`, and templates—not directly in `_site/`, which is rendered output and should not be treated as the source of truth. Changes made directly to `_site/` will not be reflected in the final published website.
+
+Preview the affected pages locally using `quarto preview` before opening a pull request, and keep section-specific changes inside the relevant folder when possible. If working on structured sections such as `people/`, check whether that directory already has its own README or templates before inventing a new pattern.
+
+
+## Deployment
+
+On pushes to `main`, the `publish.yml` workflow restores dependencies, renders the site, and publishes to GitHub Pages. The repository also includes automated checks for links, profile naming conventions, and other maintenance tasks.
 
-After the PR has been completed, the GH Action will take effect and the website should be updated within 5-10 minutes. You may need to view the page in incognito mode or force refresh multiple times as your browser will likely have an older cached version of the page.
 
-Finally, you'll want to update your own local copy of this repository by returning to the beginning of these instructions (i.e. run `git pull`).