# Updating this site

This is a static, single-page website. There is no build step, no
framework, no database. To update content you edit plain HTML / CSS / JS
files and re-deploy.

All paths below are relative to the project root (`chelsie-lim-site/`).

```
chelsie-lim-site/
├── index.html        ← all copy and structure
├── styles.css        ← all visual styling (colors, type, spacing)
├── script.js         ← footer year
├── assets/
│   ├── favicon.svg
│   ├── portrait.jpg
│   └── portrait-placeholder.svg
├── UPDATE_INSTRUCTIONS.md  (this file)
└── README.md
```

---

## 1. Change your name

`index.html` — search for `Chelsie S. A. Lim` and replace every
occurrence. There are several places to update:

1. `<title>` tag (browser tab)
2. `<meta name="description">`
3. `<meta name="author">`
4. The `<span class="brand-name">` in the header
5. The JSON-LD structured data block (`"name": "Chelsie S. A. Lim"`)
6. The footer copyright line (`© ... Chelsie S. A. Lim`)

Optional: also update the `<meta property="og:title">` for social sharing.
The JSON-LD block also keeps `Chelsie Lim` as an `alternateName` to help
search engines associate both forms of the name.

## 2. Replace the photo

You have two options.

The site currently uses `assets/portrait.jpg`. To replace it later, save
the new photo with the same filename, ideally in a 3:4 portrait aspect
ratio such as 900 × 1200 px or larger. No HTML change is needed if the
filename stays the same.

If you want to use a different filename, in `index.html` find:

```html
<img
  src="assets/portrait.jpg"
  alt="Portrait of Chelsie S. A. Lim"
  ...
/>
```

and change the `src`, `width`, and `height` values to match the new file.
The original placeholder SVG remains in `assets/` as a fallback.

## 3. Change the LinkedIn URL

`index.html` — in the `<ul class="links">` block, find:

```html
<a class="link-card" href="https://www.linkedin.com/in/chelsielim/" ...>
```

Replace the `href` with your real LinkedIn URL. The visible host label
can stay as-is, or be updated to match the new profile URL.

To add a university profile later, copy the existing LinkedIn `<li>` block,
change the label to `University profile`, and replace the URL and visible
domain.

## 4. Update contact method

The contact section currently directs visitors to LinkedIn only. To add
an email address later, edit `<section id="contact">` in `index.html`
and add a `mailto:` link. To add a full contact form, you will need a
form service or backend.

## 5. Update talks, writing, and publications

`index.html` — section `<section id="writing">`. This section is named
“Talks & writing” so the page does not imply a publication record before
you have publications to list. Each entry is one `<li class="pub">` block:

```html
<li class="pub">
  <p class="pub-meta">2026 · Journal article</p>
  <p class="pub-title">Your article title goes here.</p>
  <p class="pub-cite">
    Lim, C. (2026). <em>Journal name</em>, vol(issue), pages.
    <a href="https://doi.org/...">DOI</a>.
  </p>
</li>
```

To add a new talk, conference paper, publication, or working paper, copy
an existing `<li>` block and edit. The newest item should appear first.
When you have several peer-reviewed publications, you can rename the
navigation label and section heading from “Talks & writing” to
“Publications & talks” or “Publications”.

The paragraph below the list currently explains that peer-reviewed
publications will be added as they become available. You can remove or
rewrite it once the section has enough formal outputs.

## 6. Update teaching, education, bio, and research copy

- **Bio** — `<section id="about">`. Three paragraphs of prose.
- **Education** — `<section id="education">`. Minimal degree entries, kept
  separate from the hero biography to avoid repetition.
- **Teaching** — `<section id="teaching">`. Each item is one
  `<article class="profile-item">` block.
- **Research summary** — `<section id="research">`. This section is
  currently aligned with the KCL research proposal on stratified
  reproduction, the “suitable parent”, AI in embryo selection, and
  justice-by-design regulation. Edit:
  - `<h3 class="research-title">` for the project title
  - The body paragraphs (`<p class="prose">`)
  - The pull-quote inside `<div class="pull">`
  - The four `<li>` items inside `<ul class="research-pillars">`

Treat HTML as prose: paragraphs go in `<p>`, italic words in `<em>`.
Don't worry about styling — `styles.css` does that for you.

## 7. Adjust colors or typography (optional)

`styles.css` — top of file, the `:root { ... }` block. The two values
most worth knowing:

```css
--accent: #6B1F2A;     /* oxblood, used for links, italic in title, mark */
--paper:  #F6F3EC;     /* warm off-white background */
```

Fonts are loaded from Google Fonts via the `<link>` tag in
`index.html` (Source Serif 4 for editorial, Inter for UI). If you swap
fonts, update both that `<link>` and the `--serif` / `--sans` variables
in `styles.css`.

---

## Deploying changes

This is a static site — any static host works (S3, Netlify, GitHub
Pages, your university web space). The directory contains no secrets
and no server code.

If you used the deploy tool that built this, re-running it on the same
project path replaces the existing site at the same URL.

## Versioning

Git is initialised in this folder. After making edits:

```sh
git add -A
git commit -m "Update bio and add 2027 article"
```

You can push to a private GitHub repository to back up your site.
