# TAMS Field Service Case

This repository now uses **Jekyll** so site pages can be authored in Markdown instead of raw HTML.

## Content structure

- `index.md` is the homepage.
- `docs/` contains additional Markdown sections and raw assets.
- `docs/pdfs/index.md` is a Markdown landing page for downloadable PDFs.
- `_layouts/default.html` provides the shared site chrome.
- `assets/css/site.css` keeps styling consistent across all generated pages.

## Adding a new page

1. Create a new Markdown file, for example `docs/troubleshooting.md`.
2. Add front matter to define the page title and optional hero content.
3. Write the body in Markdown.
4. Link to the new page from another Markdown page.

Example:

```md
---
title: Troubleshooting
lead: Common recovery steps for field technicians.
hero_actions:
  - label: Back to home
    url: /
    variant: secondary
---

## Restart sequence

Follow these steps before escalating the issue.
```

## Linking media files

You can mix Markdown pages with media assets stored anywhere in the repository:

- PDF link: `[Open FR201 manual]({{ '/docs/pdfs/FR201_manual.pdf' | relative_url }})`
- Image embed: `![Wiring diagram]({{ '/docs/images/wiring-diagram.png' | relative_url }})`
- JSON link: `[Download sample payload]({{ '/docs/data/sample.json' | relative_url }})`
- Optional HTML embed for PDFs or dashboards:

```html
<iframe
  src="{{ '/docs/pdfs/FR201_manual.pdf' | relative_url }}"
  width="100%"
  height="600"
></iframe>
```

## Local preview

If Ruby and Bundler are available, you can preview the site with Jekyll:

```bash
bundle exec jekyll serve
```

GitHub Pages will also build the site automatically from these Jekyll files.