# Motolani Olaiya CV Template

Static HTML/SCSS resume project for Motolani Olaiya. The goal is a professional, editable CV that works both in the browser and as a print-friendly PDF.

## Structure

```text
motolani-cv-template/
├── index.html
├── index-recruiter.html
├── index-eu-2page.html
├── assets/
├── scss/
│   └── styles.scss
├── css/
│   ├── styles.css
│   └── print.css
└── README.md
```

## How to edit

1. Update the full version in `index.html`.
2. Update the one-page recruiter version in `index-recruiter.html`.
3. Update the strict 2-page European version in `index-eu-2page.html`.
4. Adjust visual styles in `scss/styles.scss`.
5. Keep `css/styles.css` in sync with the SCSS source if you change styling.
6. Use `css/print.css` for PDF/export-specific layout changes.

## Suggested content workflow

- Keep the summary short and concrete.
- Prefer measurable platform/project outcomes over broad adjectives.
- Lead with achievements, architecture decisions, and delivery impact instead of responsibility-only wording.
- Tailor the top headline and project emphasis for each target role:
  - Python Developer
  - Django Developer
  - Wagtail Developer
  - Django Oscar Developer
  - Backend Developer
  - Full Stack Developer
  - Ecommerce Developer
  - Software Engineer
  - Technical Founder
  - Technical Consultant

## Export to PDF

### Browser method

1. Open `index.html` in a browser.
2. Press `Cmd + P` on macOS or `Ctrl + P` on Windows/Linux.
3. Choose **Save as PDF**.
4. Keep background graphics enabled if the browser offers that option.

### Print guidance

- The layout already includes `@media print` support.
- Print output is designed for A4.
- If the content grows beyond two pages, reduce spacing or shorten project descriptions before exporting.

## Recommended usage

- Use `index-recruiter.html` as the primary one-page application version.
- Use `index-eu-2page.html` for senior European software roles that expect a fuller two-page CV.
- Use `index.html` when you want the fuller founder/platform narrative.

## Suggested measurable outcomes to add later

If you confirm them, these are the strongest metrics to add:

- Number of client or internal projects onboarded through the platform
- Reduction in manual setup time for new projects
- Deployment frequency or deployment time improvement
- Number of reusable plugins or shared modules created
- Search relevance or search coverage improvements
- Number of staging or production environments managed
- Reduction in onboarding or deployment failures after platform fixes
- Size or scope of multilingual / ecommerce implementations delivered

## Notes

- This version avoids JavaScript on purpose.
- The structure is ATS-friendly: semantic headings, readable lists, and plain text sections.
- Unknown or role-specific personal details such as exact graduation years or certification issue dates can be filled in without changing the layout.