NYRG Website Editing Guide (for collaborators)

This guide explains how to safely update the NYRG website. You do not need to be a developer to make most changes.

If something here feels unclear, stop and ask before editing.


Quick map: what to edit

Most collaborators will only touch these files:

Site-wide layout files (edit with care):

Generated data files (usually do not edit by hand):


What you can safely edit


What you should NOT edit (unless you are a maintainer)


1) Instagram posts on the Home page

You do NOT manually update Instagram embeds.

Instagram content is updated automatically using a script that:

The website then reads data/instagram.json at runtime and renders embeds with safe fallbacks (links), even if embeds are blocked.

If Instagram looks broken on the site

This can happen due to:

This is expected and OK.

Visitors will still see:

Do not try to “fix” this by editing HTML unless instructed.


You normally update gallery content by updating the Google Drive folders, then running the gallery JSON generator.

The Gallery page renders cards from: data/gallery.json

Folder naming recommendation (helps sorting)

Use a month + year in the folder name, for example:

Hiding a folder from the website

Prefix the folder name with:


3) Updating the Mentorship Google Form

File to edit:

Look for the <iframe> under the signup section.

How to update it

  1. Open the Google Form
  2. Click Send
  3. Choose the embed tab (<>)
  4. Copy the iframe src="..." URL
  5. Replace the existing src URL in the file

If the form looks cut off:


4) Updating Job Postings

Jobs are submitted via a Google Form and reviewed in a Google Sheet.

Important: the Jobs sheet uses a Google Apps Script layer to:

The site’s jobs board renders from: data/jobs.json (generated from the For Show tab).

Maintainer documentation:


5) Previewing your changes

If you push a branch (not main), GitHub Actions will deploy a preview at:

https://newyorkromaniangroup.github.io/<branch-name>/

This is the easiest way to review changes without affecting production.

Local preview (optional)

You can run Jekyll locally if you have Ruby/Jekyll installed. Maintainers can document that workflow as needed.


Final reminder

This site is designed to be:

If something feels risky, stop and ask before committing.