# Learning Portal Spec — Fortinet NOC Bootcamp

## Goal

Сначала собрать полноценный обучающий портал и программу подготовки. VPS/lab automation — последний этап после того, как структура обучения, теория, вопросы, Academy track и сценарии готовы.

## Portal sections

1. **Dashboard** — что делать сегодня, прогресс, слабые зоны.
2. **7-Day Plan** — день → теория → практика → Academy → mock interview.
3. **Trainer Council** — роли экспертов и кто за что отвечает.
4. **NOC Theory** — OSI/TCP-IP, DNS, routing, firewall, VPN, monitoring.
5. **Fortinet Academy Track** — какие курсы пройти, что пропустить, что даёт собесу.
6. **Interview Simulator** — вопросы, эталонные ответы, стресс-вопросы.
7. **RCA / Incident Templates** — шаблоны handover, update, RCA.
8. **Labs Backlog** — список будущих задач для VPS, пока без запуска.

## Current portal map

- `portal/index.html` — dashboard, navigation, build order, 7-day module entry points.
- `portal/modules/day-1.html` — NOC baseline and troubleshooting method.
- `portal/modules/day-2.html` — Linux troubleshooting for NOC.
- `portal/modules/day-3.html` — routing, NAT and stateful firewall flow.
- `portal/modules/day-4.html` — FortiGate concepts and Sophos → Fortinet mapping.
- `portal/modules/day-5.html` — IPsec / SSL VPN troubleshooting.
- `portal/modules/day-6.html` — monitoring, severity, escalation, RCA.
- `portal/modules/day-7.html` — full mock interview and weak-spot patch.
- `portal/daily-checklist.html` — repeatable day checklist: theory, lab, Academy, RCA, mock.
- `portal/progress.html` — readiness scoring model tied to the NOC scorecard.
- `docs/academy-inspection-checklist.md` — Academy pre-login inspection route linked from the dashboard.
- `docs/day1-noc-baseline.md` — detailed Day 1 deep-dive linked from the D1 module card.

## Navigation rule

Every learner-facing page must make the next action obvious:

1. Start on dashboard.
2. Pick exactly one day module.
3. Use the daily checklist during work.
4. Update progress model / weak spot after work.
5. Return to dashboard for the next module.

Avoid orphan pages. If a new module or template is added, link it from the dashboard or from the relevant day module.

## Progress model

Progress is not “read the page”. A topic is ready only if Artur can:

- state the symptom and impact;
- propose a hypothesis-driven check order;
- collect evidence with allowed tools;
- explain the likely root cause and safe fix;
- validate the fix;
- translate the result into a concise interview answer;
- map firewall/security topics to Fortinet language where relevant.

Use the scorecard categories: Method, Linux CLI, Networking, Fortinet mapping, Evidence, Fix, Communication, Interview answer.

## Daily checklist model

Each day follows the same operating loop:

1. 30–60 min short theory.
2. 60–120 min hands-on task with scenario/symptom/allowed tools.
3. 30 min Fortinet Academy or personal notes.
4. 20 min incident update / RCA.
5. 20–40 min mock interview.
6. Scorecard update and one weak-spot action.

## Build order

### Phase 1 — Portal content first

- Create static portal shell.
- Fill Day 1–7 program.
- Create Day 1 module in detail.
- Create Fortinet Academy inspection checklist.
- Create question/answer bank.
- Create Sophos → Fortinet mapping.

### Phase 2 — Academy review

- User logs into Academy.
- Fortinet Academy Navigator inspects available courses/labs/eval.
- Update portal with exact course links/modules.

### Phase 3 — VPS/labs last

- Only after Phase 1 content is useful.
- Bootstrap disposable VPS.
- Implement scripted outages and grading.
- Every lab must already have scenario, symptom, allowed tools, expected fix, validation and grading rubric before touching the VPS.

## Non-goal right now

Do not start installing packages on VPS until the learning portal and curriculum skeleton are ready.