Workshop site for Alshaya Property Development Co. and Al-Injaz Contracting Company.
| Dates | Tuesday 1 – Thursday 3 September 2026 |
| Timing | 09:00 – 13:00 daily · 12 hours total |
| Location | CODED Campus, Kuwait |
| Instructor | Ali Taqi |
| Trainees | 14, mixed departments — teams of two on Day 3 |
| Tool | Claude (plus Gamma for presentation variety on Day 2) |
| Level | Beginner-friendly · no coding |
Static site, no build step. Everything served from site/.
vercel.json sets outputDirectory: site and cleanUrls: true, so pages resolve at
/coded-alshaya-day-1 as well as /coded-alshaya-day-1.html.
If Vercel asks during import: Framework preset = Other, Output Directory = site,
Build Command = none.
| File | What it is |
|---|---|
index.html |
Landing page — hero and the three programme cards |
coded-alshaya-day-1.html |
Day 1 plan — brief, run of show, resources |
coded-alshaya-day-1-deck.html |
Day 1 deck · 52 slides |
coded-alshaya-day-1-lab.html |
Day 1 trainee lab · 6 tasks |
alshaya-quarterly-operations-report.pdf |
Day 1 exercise document · 5 pages, sample data |
coded-alshaya-day-2.html |
Day 2 plan |
coded-alshaya-day-2-deck.html |
Day 2 deck · 36 slides |
coded-alshaya-day-2-lab.html |
Day 2 trainee lab · 6 exercises |
alshaya-day-2-dataset.xlsx |
Day 2 dataset · 6 sheets, sample data |
coded-alshaya-day-3.html |
Day 3 plan — assessment, capstone, certificates |
coded-alshaya-day-3-deck.html |
Day 3 deck · 26 slides |
coded-alshaya-day-3-lab.html |
Day 3 capstone lab · 6 tasks, 7 team scenarios |
alshaya-capstone-s1.xlsx … s7.xlsx |
Day 3 scenario workbooks · one self-contained file per team |
Every page is a single self-contained HTML file — CSS and JS inline, logo as a data URI, fonts from Google. No bundler, no dependencies.
All figures across the PDF and the workbook describe one fictional three-property portfolio, and they reconcile with each other by design. Nothing here is an Alshaya or Al-Injaz record.
The quarterly report contains five deliberate factual faults for the Day 1 verification
exercise, and each Day 3 scenario workbook carries one planted inconsistency, catchable
inside the team's own file (trainees are told one exists, not what it is). Both sets are
documented in instructor/ — coded-alshaya-day-1-answer-key.html and
coded-alshaya-capstone-data-key.html — kept outside site/ on purpose, so they
never deploy and trainees cannot stumble on them. Open them locally for the debriefs.
instructor/coded-alshaya-map-test-key.html is the answer key for the pre/post knowledge test —
30 questions (10 true/false, 11 multiple choice, 9 scenarios), timed at 28m 25s against a 30-minute
slot, sat twice: Day 1 before teaching starts, and Day 3 before the capstone.
The test itself lives in the CODED portal as two published surveys, one per sitting. Both pages link
to theirs from the day page and the resources list.
| Survey | Linked from | Portal slug |
|---|---|---|
| MAP pre — Day 1, before class | coded-alshaya-day-1.html |
alshaya-map-test-ai-in-workflow-pre-copy |
| MAP post — Day 3, before the capstone | coded-alshaya-day-3.html |
alshaya-map-test-ai-in-workflow-pre-post |
| Workshop feedback — Day 3, at the close | coded-alshaya-day-3.html |
alshayaa-ai-for-workplace |
The feedback survey is a separate 16-question satisfaction form (overall experience, topic understanding, instructor, open comments), owned by yousif.d@joincoded.com — not one of the MAP pair.
Note that the portal's survey titles are the reverse of this mapping — the survey used on Day 1 is titled "(Post)" and vice versa. Rename them in the portal UI before Day 1, or trainees will see the wrong label at the top of the page.
The key stays outside site/ with the other instructor material, so it never deploys.
The generators in build/ produce the decks, labs and data files. They splice from the
CODED workshop-builder skill's reference build, so paths inside them are local to the
authoring machine.
python3 build/build-day-1-deck.py
python3 build/build-day-1-lab.py
python3 build/build-day-2-deck.py
python3 build/build-day-2-lab.py
python3 build/build-day-2-dataset.py # needs openpyxl
python3 build/build-ops-report.py # needs reportlab
python3 build/build-day-3-deck.py # clones the Day 2 deck shell
python3 build/build-day-3-lab.py # clones the Day 2 lab shell
python3 build/build-capstone-data.py # needs openpyxl; reads the Day 2 dataset09:00 final assessment (30 min) → 09:30 capstone build (7 teams of two, scenarios S1–S7,
four deliverables on timed blocks) → 11:45 six-minute team presentations → 12:30
certificates and close. Each team gets its own self-contained scenario workbook
(alshaya-capstone-s1.xlsx … s7.xlsx) — same fictional portfolio, but every team
uploads one file with everything its scenario needs.