remove Decap CMS instructions from readme

Author: ritamtbsilva

README.md

@@ -791,105 +791,6 @@ The News section automatically fetches the most recent posts from `@nmoraislab.b
 
 ---
 
-## Visual content editor (Decap CMS) - optional setup
-
-> **What this gives you:** a web interface at `https://diseasetranscriptomicslab.github.io/admin/` where anyone with GitHub access can edit site content (news, team members, publications) through forms - no git knowledge or terminal needed. Changes are committed directly to GitHub and deploy automatically.
-
-This is optional. The site works fine without it. Set it up when you're ready to let non-technical collaborators edit content.
-
----
-
-### Step 1 - Create the GitHub OAuth App
-
-GitHub OAuth is what lets Decap log people in using their GitHub account.
-
-1. Go to **GitHub → Settings → Developer settings → OAuth Apps → New OAuth App** (direct link: <https://github.com/settings/developers>).
-2. Fill in:
-   - **Application name:** `Disease Transcriptomics Lab CMS`
-   - **Homepage URL:** `https://diseasetranscriptomicslab.github.io`
-   - **Authorization callback URL:** `https://api.netlify.com/auth/done`
-3. Click **Register application**.
-4. On the next page, copy the **Client ID** and click **Generate a new client secret** - copy that too. Keep both safe.
-
----
-
-### Step 2 - Connect Netlify as the OAuth broker
-
-Decap uses Netlify purely as an OAuth middleman (free, no hosting required).
-
-1. Create a free account at <https://app.netlify.com> if you don't have one.
-2. Go to **Sites → Add new site → Deploy manually** and drag any dummy folder to create a placeholder site. The site URL doesn't matter.
-3. Go to **Site configuration → Access & security → OAuth**.
-4. Under **Authentication providers**, click **Install provider → GitHub**.
-5. Paste your **Client ID** and **Client secret** from Step 1, then click **Install**.
-
----
-
-### Step 3 - Add the `admin/` folder to this repo
-
-Create these two files and commit them (to a branch, then PR into `main`):
-
-**`admin/index.html`** - the CMS entry point:
-
-```html
-<!doctype html>
-<html>
-<head>
-  <meta charset="utf-8" />
-  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-  <title>Disease Transcriptomics Lab CMS</title>
-</head>
-<body>
-  <script src="https://unpkg.com/decap-cms@^3.0.0/dist/decap-cms.js"></script>
-</body>
-</html>
-```
-
-**`admin/config.yml`** - tells Decap which files to edit:
-
-```yaml
-backend:
-  name: github
-  repo: YOUR-ORG/nmoraislab.github.io   # ← replace with actual repo path
-  branch: main
-
-media_folder: assets/news
-public_folder: assets/news
-
-collections:
-  - name: news
-    label: Lab News
-    folder: _data/news
-    create: true
-    slug: "{{year}}-{{month}}-{{slug}}"
-    fields:
-      - { label: Title,   name: title,   widget: string }
-      - { label: Date,    name: date,    widget: string, hint: "e.g. June 2026" }
-      - { label: Summary, name: summary, widget: text }
-      - { label: Content, name: content, widget: markdown }
-      - { label: Image,   name: image,   widget: image, required: false }
-```
-
-> **Note:** Decap works best when content is stored as Markdown/YAML files. Adapting the current JavaScript-array format (`js/news-data.js`) to file-based content requires a small migration - contact the person who built the site for help with that step.
-
----
-
-### Step 4 - Open the editor
-
-Once the `admin/` folder is live on GitHub Pages:
-
-1. Visit `https://diseasetranscriptomicslab.github.io/admin/`
-2. Click **Login with GitHub** and authorise.
-3. You'll see the content collections. Edit, save - changes commit to the repo and deploy automatically.
-
----
-
-### Access control
-
-Only GitHub accounts that have **read access to this repository** can log in via Decap. Manage collaborators under **GitHub → Repository → Settings → Collaborators and teams**. There is no separate Decap user list.
-
----
-
 ## Analytics
 
 The site runs **Google Analytics 4**, property Measurement ID **`G-6FLD1GNCMB`**. The Measurement ID is not a secret - it's meant to appear in public page source, and on its own can't be used to read the analytics dashboard or modify the site (only Google accounts granted access to the GA property can view data).