Learning Strategy & Design

${toolName}

\n${pitch}\n

${isAida || isHolding ? \"\" : \"The Job Search Toolkits are opening soon. \"}Questions, or think you should have access? Email membersuccess@learningstrategyanddesign.com.

learningstrategyanddesign.com

`;\n}\n\nfunction indexPage(): string {\n const links = Object.keys(ROUTES)\n .filter((slug) => PUBLIC_INDEX.has(slug))\n .sort()\n .map((slug) => `

${ROUTES[slug].title.replace(/ [—|] (Learning Strategy & Design|LS&?D|AIDA)$/, \"\")}

`)\n .join(\"\\n\");\n return `LS&D Tools\n\n\n

Learning Strategy & Design Free Tools

\n${links}\n\n

Additional tools are available inside AIDA and the LS&D Job Search Toolkits.

\n`;\n}\n\n// SECURITY HEADERS (2026-08-14, matches jill1/ada + jill1/search-hq). Jill\n// confirmed nothing iframes the tool pages, so SAMEORIGIN is safe. No CSP:\n// tool fragments carry inline script/style.\nexport default async function (req: Request): Promise {\n const res = await routeRequest(req);\n try {\n res.headers.set(\"X-Content-Type-Options\", \"nosniff\");\n res.headers.set(\"Referrer-Policy\", \"strict-origin-when-cross-origin\");\n res.headers.set(\"X-Frame-Options\", \"SAMEORIGIN\");\n } catch { /* immutable headers on some platform responses; serve as-is */ }\n return res;\n}\n\nasync function routeRequest(req: Request): Promise {\n const url = new URL(req.url);\n const slug = url.pathname.replace(/^\\/+|\\/+$/g, \"\");\n const keys = configuredKeys();\n const master = keys.find((k) => k.name === \"master\");\n // Constant-time compare (2026-09-04 code review), so /stats and /access do not\n // leak the master key one byte at a time through response timing.\n const masterOk = !!master && (() => {\n const enc = new TextEncoder();\n const a = enc.encode(url.searchParams.get(\"k\") ?? \"\"), b = enc.encode(master.value);\n if (a.length !== b.length) return false;\n let d = 0;\n for (let i = 0; i < a.length; i++) d |= a[i] ^ b[i];\n return d === 0;\n })();\n\n if (slug === \"\") {\n return new Response(indexPage(), { headers: { \"Content-Type\": \"text/html;charset=UTF-8\" } });\n }\n\n // Tool shell assets (2026-09-15): the shared stylesheet every fragment links, and\n // the ONE LS&D wordmark every title bar uses. Both public, cached for a day so a\n // shell.css edit shows up within the hour without a redeploy of any tool.\n if (slug === \"shell.css\") {\n const css = await readFile(\"shell/shell.css\", import.meta.url);\n return new Response(css, {\n headers: { \"Content-Type\": \"text/css;charset=UTF-8\", \"Cache-Control\": \"public, max-age=3600\" },\n });\n }\n if (slug === \"lsd-logo-white.png\") {\n const bytes = Uint8Array.from(atob(LSD_LOGO_WHITE_B64), (c) => c.charCodeAt(0));\n return new Response(bytes, {\n headers: { \"Content-Type\": \"image/png\", \"Cache-Control\": \"public, max-age=86400\" },\n });\n }\n\n // Live access map (master-key-protected): GET /access?k=\n if (slug === \"access\") {\n if (!masterOk) return new Response(\"Not authorized.\", { status: 403 });\n const map = Object.keys(ROUTES).sort().map((s) => ({\n slug: s,\n title: ROUTES[s].title.replace(/ [—|] (Learning Strategy & Design|LS&?D|AIDA)$/, \"\"),\n access: GATED.has(s) ? \"GATED (key or app referer required)\" : \"OPEN\",\n indexable: !(GATED.has(s) || NOINDEX_EXTRA.has(s)),\n publicly_listed: PUBLIC_INDEX.has(s),\n risevip_key_unlocks: GATED.has(s) ? RISEVIP_SLUGS.has(s) : undefined,\n aida_key_unlocks: GATED.has(s) ? AIDA_SLUGS.has(s) : undefined,\n }));\n return new Response(JSON.stringify({ generated: \"live\", tools: map }, null, 2), {\n headers: { \"Content-Type\": \"application/json\" },\n });\n }\n\n // Usage stats (master-key-protected): GET /stats?k=\n if (slug === \"stats\") {\n if (!masterOk) return new Response(\"Not authorized.\", { status: 403 });\n try {\n const cutoff = new Date(Date.now() - 30 * 24 * 3600 * 1000).toISOString().slice(0, 10);\n const rows = await sqlite.execute({\n sql: `SELECT day, slug, outcome, n FROM lsd_tool_hits WHERE day >= ? ORDER BY day DESC, n DESC`,\n args: [cutoff],\n });\n const totals: Record> = {};\n for (const r of rows.rows as unknown as [string, string, string, number][]) {\n const [, s, outcome, n] = r;\n totals[s] = totals[s] || {};\n totals[s][outcome] = (totals[s][outcome] || 0) + n;\n }\n return new Response(JSON.stringify({ since: cutoff, totals, daily: rows.rows }, null, 2), {\n headers: { \"Content-Type\": \"application/json\" },\n });\n } catch (err) {\n return new Response(\"Stats error: \" + ((err as Error).message || \"unknown\"), { status: 500 });\n }\n }\n\n // 2026-07-18 the Scenario Studio absorbed the Storyline Scenario Builder and this slug\n // 302'd into the Studio. REVERSED 2026-07-23 (Jill, re-scope) and implemented 2026-07-26:\n // the Builder is the Storyline Revise shelf tool in AIDA HQ and stands on its own again,\n // while the Studio moves to the future advanced course. The Studio keeps its own slug and\n // stays reachable so existing member links do not break; it just is not on the HQ shelf.\n\n // Week in the Life 360 static images: /w360/Capture.JPG, /w360/Capture1.JPG.\n // Served out of project-scoped blob storage because they are binary and the\n // fragment loader (readFile) is text-only. Cached hard: these never change.\n if (slug.startsWith(\"w360/\")) {\n const name = slug.slice(\"w360/\".length);\n if (!W360_ASSETS.has(name)) return new Response(\"Not found.\", { status: 404 });\n try {\n const bytes = await blob.get(`w360/${name}`);\n return new Response(bytes.body, {\n headers: {\n \"Content-Type\": \"image/jpeg\",\n \"Cache-Control\": \"public, max-age=31536000, immutable\",\n },\n });\n } catch (err) {\n return new Response(\"Asset error: \" + ((err as Error).message || \"unknown\"), { status: 500 });\n }\n }\n\n // AIDA Directory same-origin API pass-through (2026-08-03). Some members'\n // network filters (work/school laptops) block the raw jill1--.web.val.run\n // backend host while allowing this domain, so the directory page saw\n // \"could not be reached\" failures for those members. The page now calls\n // /aida-directory-api/* on THIS host and the router forwards server-side to\n // the proxy val. The proxy's own origin allowlist + per-IP rate limit still\n // apply: we send an allowed Origin and pass the member's real IP through.\n // The old direct URL keeps working unchanged (the page falls back to it when\n // served from any other host).\n if (slug === \"aida-directory-api\" || slug.startsWith(\"aida-directory-api/\")) {\n const DIR_API = \"https://jill1--77d8d6246c1911f195ca1607ee4eb77e.web.val.run\";\n const sub = slug.slice(\"aida-directory-api\".length) || \"/\";\n const fwdHeaders: Record = {\n \"Content-Type\": req.headers.get(\"content-type\") || \"application/json\",\n \"Origin\": \"https://lsd-tools.val.run\",\n };\n const xff = req.headers.get(\"x-forwarded-for\");\n if (xff) fwdHeaders[\"x-forwarded-for\"] = xff;\n try {\n const resp = await fetch(DIR_API + sub, {\n method: req.method,\n headers: fwdHeaders,\n body: req.method === \"GET\" || req.method === \"HEAD\" || req.method === \"OPTIONS\"\n ? undefined\n : await req.text(),\n });\n const body = await resp.text();\n await tally(\"aida-directory-api\", resp.ok ? \"ok\" : \"err\" + resp.status);\n return new Response(body, {\n status: resp.status,\n headers: { \"Content-Type\": \"application/json\", \"X-Robots-Tag\": \"noindex, nofollow\" },\n });\n } catch (err) {\n await tally(\"aida-directory-api\", \"unreachable\");\n return new Response(\n JSON.stringify({ error: \"Directory backend unreachable: \" + ((err as Error).message || \"unknown\") }),\n { status: 502, headers: { \"Content-Type\": \"application/json\" } },\n );\n }\n }\n\n // GENERIC same-origin API pass-through (rollout approved 2026-08-03, built 2026-08-04).\n // Same class of fix as /aida-directory-api/* above, for every shelf tool: pages call\n // /api// on THIS host and the router forwards server-side to the\n // tool's backend val (API_BACKENDS map next to ROUTES). Differences from the\n // directory block, on purpose:\n // - resp.body is passed through UNTOUCHED — the AI proxies stream (SSE/chunked),\n // and buffering with resp.text() would break streaming\n // - Content-Type (and Cache-Control, for the /logo asset) copied from upstream,\n // not forced to application/json\n // The member's real IP is forwarded (x-forwarded-for) so backends that rate-limit\n // per IP keep limiting per member instead of pooling everyone into one bucket.\n // Old direct backend URLs keep working: pages only use /api/* when served from\n // lsd-tools.val.run / tools.learningstrategyanddesign.com, else fall back direct.\n if (slug === \"api\" || slug.startsWith(\"api/\")) {\n const parts = slug.split(\"/\"); // [\"api\", toolslug, ...rest]\n const toolslug = parts[1] || \"\";\n const base = API_BACKENDS[toolslug];\n if (!base) {\n await tally(\"api-unknown\", \"notfound\");\n return new Response(JSON.stringify({ error: \"Unknown API slug.\" }), {\n status: 404,\n headers: { \"Content-Type\": \"application/json\" },\n });\n }\n const sub = \"/\" + parts.slice(2).join(\"/\") + url.search;\n const fwdHeaders: Record = { \"Origin\": \"https://lsd-tools.val.run\" };\n for (const h of [\"content-type\", \"accept\", \"x-forwarded-for\"]) {\n const v = req.headers.get(h);\n if (v) fwdHeaders[h] = v;\n }\n try {\n const resp = await fetch(base + sub, {\n method: req.method,\n headers: fwdHeaders,\n body: req.method === \"GET\" || req.method === \"HEAD\" ? undefined : await req.arrayBuffer(),\n });\n await tally(toolslug + \"-api\", resp.ok ? \"ok\" : \"err\" + resp.status);\n const outHeaders: Record = { \"X-Robots-Tag\": \"noindex, nofollow\" };\n for (const h of [\"content-type\", \"cache-control\"]) {\n const v = resp.headers.get(h);\n if (v) outHeaders[h] = v;\n }\n return new Response(resp.body, { status: resp.status, headers: outHeaders });\n } catch (err) {\n await tally(toolslug + \"-api\", \"unreachable\");\n return new Response(\n JSON.stringify({ error: \"Tool backend unreachable: \" + ((err as Error).message || \"unknown\") }),\n { status: 502, headers: { \"Content-Type\": \"application/json\" } },\n );\n }\n }\n\n const route = ROUTES[slug];\n if (!route) {\n await tally(slug || \"(unknown)\", \"notfound\");\n return new Response(\"Not found. Visit / for the list of available tools.\", { status: 404 });\n }\n\n const isGated = GATED.has(slug);\n const noindex = isGated || NOINDEX_EXTRA.has(slug);\n let setCookie: string | null = null;\n let door = \"\";\n\n if (isGated) {\n const keyParam = url.searchParams.get(\"k\");\n const cookieVal = getCookie(req, \"lsdk\");\n const paramKey = keys.find((k) => k.value === keyParam && keyCovers(k, slug));\n const cookieKey = keys.find((k) => k.value === cookieVal && keyCovers(k, slug));\n const viaApp = refererAllowed(req);\n const appToken = master ? await appDoorToken(master) : null;\n const cookieIsAppDoor = !!appToken && cookieVal === appToken;\n\n if (paramKey) {\n setCookie = `lsdk=${paramKey.value}; Max-Age=${paramKey.cookieMaxAge}; Path=/; Secure; HttpOnly; SameSite=Lax`;\n door = \"@\" + paramKey.name;\n } else if (cookieKey) {\n door = \"@\" + cookieKey.name;\n } else if (cookieIsAppDoor) {\n door = \"@app\";\n } else if (viaApp && appToken) {\n setCookie = `lsdk=${appToken}; Max-Age=604800; Path=/; Secure; HttpOnly; SameSite=Lax`; // 7 days\n door = \"@app\";\n } else {\n await tally(slug, \"blocked\");\n return new Response(gatePage(route.title, AIDA_SLUGS.has(slug), HOLDING_SLUGS.has(slug)), {\n status: 403,\n headers: { \"Content-Type\": \"text/html;charset=UTF-8\", \"X-Robots-Tag\": \"noindex, nofollow\" },\n });\n }\n }\n\n try {\n let fragment = await readFile(`apps/${route.file}`, import.meta.url);\n // Member bypass for the Topic Generator's lead-gen email gate (Jill, 2026-07-31).\n // The tool is public and asks strangers for name + email (Kit signup) before it\n // unlocks. An AIDA member clicking it from the HQ shelf should not be treated\n // like a stranger, so a visit from an app surface (or carrying an app/key cookie)\n // gets a flag injected that the fragment reads to skip the form. A 7-day app\n // cookie rides along so her in-tool reloads keep skipping it.\n if (slug === \"portfolio-topic-generator\") {\n const cookieVal = getCookie(req, \"lsdk\");\n const appToken = master ? await appDoorToken(master) : null;\n const hasKeyCookie = keys.some((k) => k.value === cookieVal);\n const hasAppCookie = !!appToken && cookieVal === appToken;\n if (refererAllowed(req) || hasAppCookie || hasKeyCookie) {\n fragment = `\\n` + fragment;\n door = \"@app\";\n if (appToken && !hasAppCookie && !hasKeyCookie) {\n setCookie = `lsdk=${appToken}; Max-Age=604800; Path=/; Secure; HttpOnly; SameSite=Lax`;\n }\n }\n }\n // Scenario Studio v2 ships as patches over the base fragment (the file\n // outgrew the editing pipeline). Canonical merged copy: the workspace's\n // Tools/Interactive Apps/scenario-studio.html.\n if (slug === \"scenario-studio\") {\n for (const pair of STUDIO_V2_PATCHES) {\n const ix = fragment.indexOf(pair[0]);\n if (ix < 0) throw new Error(\"studio v2 patch failed to apply\");\n fragment = fragment.slice(0, ix) + pair[1] + fragment.slice(ix + pair[0].length);\n }\n }\n await tally(slug, \"view\" + door);\n const headers: Record = { \"Content-Type\": \"text/html;charset=UTF-8\" };\n if (noindex) headers[\"X-Robots-Tag\"] = \"noindex, nofollow\";\n if (setCookie) headers[\"Set-Cookie\"] = setCookie;\n return new Response(wrap(fragment, route.title, noindex), { headers });\n } catch (err) {\n await tally(slug, \"error\");\n return new Response(\"Error loading tool: \" + ((err as Error).message || \"unknown\"), { status: 500 });\n }\n}\n","children",[],[620],["D",1789504985065],[],[553,66],"10a64531-39b4-45ee-bd88-065a60190e2a","logo.ts","72ff1868-b145-11f1-b693-1607ee4eb77e",808,["D",1789504726522],"script","// LS&D white wordmark, 1000x199 PNG (4 KB). The ONE logo every tool uses,\n// served by the router at /lsd-logo-white.png (see main.ts). Added 2026-09-15\n// with the tool shell standard (Departments/career-services/reference/\n// tool-shell-standard.md). Was previously inlined as base64 in every fragment\n// in three different byte variants plus a 167 KB original.\nexport const LSD_LOGO_WHITE_B64 =\n \"iVBORw0KGgoAAAANSUhEUgAAA+gAAADHAgMAAAD335EJAAAADFBMVEXs8fT5+/zx9Pb////S35OIAAAAA3RSTlMAeNZyIEDBAAAPk0lEQVR42u2dPa/kyHWGX5KaS0AMmOwq2BswNRyofgJpGLADJ2Ngb7LJRlYgBfcnkHKq5AbrQJmCXUNqBevQH8AWoV9AR0oZjAVoFagh0AJn3OSroD5Y/Gj2NSDY6K4uYBY7nG52PayqU+85daoI3Mu93Mu93Mu93Mu93Mu9/H+VH5HjFz6CB1+TJF88RH8mSXIsvCOPya8Q/Ih85x265BdqvI++kT+a1pZsfGt009gJ3/tFnrA1hp70y9A9TyNc+NXjQ9voQMzeKyPnzuZ+2fiyc//Cyqf+7srXzOn9t2/fx7mu6/xBFzPWgCeP9EyzLW98GOpzEZP7I2qSRQfP/DHxojunan0b6oh59HSoI/RGysbD4oI/s1vWn3Xeb97KrYxa6Qu6bBAsJ3Y/yAMWSOcTufBkYo9GQNReaprkBJRz9JS1NwZeVgt0P8Jz+RFYdHBflGzZIljoOV+ULGuE9FLEB6xW6JEfIaqI6o+H/ks8qj8eoqeDt+jZCUgGL71W0auW9xA9P26hD54oGmQnL9Glv+hs1HifX/QBPWDtK3rICshX6D4E5yIWQN75iB4TvqInBFAevUQfN9F9MHOpx+gDAHn0UdJkJ63o/EMXHqP3ANj66LR6jJ532oWZq1uP0XtP0IPl6qIn6McN9MgLdNFuovuw+vJJAYRLdH9yozfQ/ckZrJaerC/o0Rq99RU99Rm98QZ9kR+ceZJBtYEufEb3ZRtEvET3Z/NLvMwGLv+c6cFv/o8ogj8LuiSA4PC/O7HjO9+x/zvrM+nGZ9UEEnzqfFx/++O3huTpafGlJ/1Pb4rN3wkL871PN+v38T+9dW7z5tNtdI4AMu2+/XCz8werq6n19gKStOG9tLAP1K5sKLGoU3jU1hv9MRMXDyT524UBUgcr5CTJI4CQdM4ZiCstTUmSaqIiaSTKozl9RfknYjyDPqiaqq/UwL+t0LOV1E1P2+hZNaGbepxm6DUApM0MPSM5M7YBqQ4VmKNPu3HTeg89kKZKsgeAXFUvWSwzBTwBMd9L9Ys1Av2BjwA8qNYRF9HNTfPGQdfPgxutfnTRA7fBtLgm2azRbV/L2j30xF7NnQewQg/ZAymrvAAeyQbRqPtMj0DfqjwCWfeaVi9bB11PHUo3zNFPLnpMQzrJLJL1Gt3WXTfGGfRn5yqAQDtoS/SIHSBGlAVQkoVGD8gRj/ox82if3Ab6t4fD4edm9Jj+IT8cDI26Nu/wdNEF+dUvZ8Kq5BePrAD85eGX/PbffwYg5LeHaVToJIHgcJAfDgcAyMbD4aCNNTke1G6mhAUQ6oos0WMeAXmCBAK+/8psB8vIEc86WMt2Gbd10d1BarukbK1LqK4t0GsHveQ74Nm9jeyB52Jmm0JWyGzXkCc33oj5Vq6QLPAwqG/X+j8b6AmPALuHEYjYAHg8qep8+Hmge1jAFonp0y976NMDkg0CHf5RXW/e4VVPUOhq+Wc2i7C1U3fkoE+nbEwrRhb95CB12lapbyR65C3T5lI2CNmKXi+/o+zNg4tGwQKqw6S9qnp03EOPbJVkY8eI6qYL9NOEHq4iZIEz8F10M2gRTKN+o9UdaR7wCGT6w0v0jDVi/oYtkA0AAvYAEvZA2mUsACRskHeqCskuemKrJBsg18OF7RqdE3qy8prdIJqLDtmZi9xp9XycDx09t63QBSskyhqLkz2uRbABRJOwAlCyhmxog7rn0VN7xI9s9P0ANSct0WuLnq6ciLPohjN2DN661V2LXA66H2+g5yyQqdrlJwAZO3NwiSxi1kBIVgErbZSrPfTMVkk2tiGUxViitxY9WyW0nOvwljMZ7MPZaHU32ChGI+nW6CUBoQ6ekycAJTs9lsIREWvgkayiUSmTgLsWXvy3qZKL/jWrJfrI3qKvstmmMb1CN+3X273o61Z3HxxSFtY4LtHlCIhRWbMBCPj5UeucpFc2X/6RRTIodLMR+gx62ZqfcdF/wnYlacoptyVfrwM4C0KbrS6OVjutW30Wbo9ZmbnNqTTszJKP1kbFgzjqGS9rEbJFyH9kkfUK3Wi6M+iyle16rP+K/QpdsDLo5ToYLqebztDNaUKizY9nWz2azzmNmdvW6CdlC4CMBLJOHHWoMq8RssXjEBHiCBYARLOLztrURLbWvLCW4wo9YavWANdpHgAE+20Lr4HLxpKu0WfBmIBtamzJIjE6YgeUWsWwgmxEq2dGKjEj24goG9Xq6wcY8HA4HCrzGEwGrjuv14LVEj1gv4P+ODlpm/M6a1sBiz4eDj/8xdo3lZ0YttGNjgXAz9kELESrNnaHAxDwGLKKCFYggHA84740Ju6XDbbVjVRhnbBduS/luIMeTp6Kix4bS8LKilKLbt2bOXp5MnPbEj1hq5snGlN28QmiVbYv6YGAx2xAzIAFWKhrm+itcUxN75ItHo2Gr0P2K/SMlUHfWAeQ1pOb0F/wrC+GnPjW6MkMXYxGBy3RU5qemfYx++wI0QI8afHCY9kiHqNR9XV75sE2ejLY35VTZIE15LhCj9k66OHk/BnN0i/RJzc4GqfA8hn0T4wXl06RgAW6GtU9ANGGHMsGolVitqwA8A+skIzJoCIOdhP0dofPTtbGzP11wWqJHrJ30GMuMnqeTY+foetr8TCtmp5BF07Yot5Gz1noVpc1JFlAqFGqxAv/ZwCSMe0BFtNQX/nr6gmL3lbJjdLUSNisQhVydMb6Cj0wunCG3k+/boBcM3eYzJygNonRpHkX6CW16I0JlBwA0SLmEdGgROgRSAZxBFjgsd/31/OjlVJObI41QnYrdMFqB92eejlDb6aJzBjHrcnNRQ8mT2eBroKSvbqesQOECjKknXU4kyFvAVk4x5tso8sPh4MGnqNDjiv0hFqXyOMWurHmM3Td0uLD4WDmubWai1k4HR7Sytf51heVL1ieAPlO55aIFoINysZ+Lx1kDcjCoTyDbgJpgGxNpAKsAcG/XaKH7BV62QHB0+enbR3vTG5/Y2hykubuZ9TcmyfbLfptdDX35oM6djHkCRBHlGz0Bn/ZKUtRAbJydsNuoiuL1xvE8jShJ/z1KiwpR43eb6hMq9zced3gStL2ki0N37hy4Ry6SqTJR2QsgIgjII4B2eidrzwqdAB55Xx1E13NPyeDqAP/0I7vCl1Q0alIwgq9XKPbh+kEgbc8t3aG3m2jqwhJxh+zN8GTrEvIRp3NprKrVFxO/JfjDG6iR06VZGtDEKwByDV6ogeH8tdfg64fZsDfHQ5fj+f99e416CqvINU2Kf89C6RjSf5GYWa61VUMY7wQkY1Hs9MCkA1i/S+sAYg1eqjRU768El0/zIiOXN2K0gyvQVdxx1jJj4B/p6JVv7bdU7d6Z8J1u+jpABv+lK2Nn7J2onbuEoTUEXq2rxzridKH0ei4phut/sxiG72bKxptnzoA0RixRkz+tbafITV0CyAYqwvo2WlyGWU7BaNrAOEGuqCOyL5foAcvU/K6i66i5WoHfrhE752u3L4CXU96qvHTPmSDgL2RUsmgLXyzt+ZWzW4dqcl35rRiOttNL0Gc4GTsSb7M9Ub0Hoj1j8ZrpzXtnTDUBnrCEQiMbz8Bz8JBwSw1WLQBW+D5BeV7fUF2W4kYQDoaLz3gP/9AK8iymw7jli2gHWX1bMS61R80es7x6TNX0iT8GZ71I41noYp+gtGtasI12fiDf/jpT190Z33/9DX30efRf1mZXvax9kFeZIf1mSbaMCpdGUwrfqoytD6JDrWqVk82lht1wzw6k6K5+++tlzaLzQ0TrQ5WzdwXIyrcpdt8Gz12l3bDcbE7JBqVpAn+9XXoWkrYNlFRfI2uj8OZoc/WS/vFGvOwEaDKOC3naqmyhZ69An02iuN+gZ72drnjNeg63VyJM9mYNTzjY32zGutmKUctCjfzSAU7rDu8epjq8emg5xZ66L7Y5UyHn501lx4X6GV7Fj3bQNeHlarlJtlaWaV/4/vrVg81+sMsWUQ3e7WBrmyo+icdCttCh+D0XhcH/bia28xn6vnGmIDVWfQ3T09PT08FADw9/f3T0xOAQKUCqZydjwubxHNQj/+7jhX57pfqNv+ib/e9wy/mlvST//jSZhiZxKLC+ctUPnrr1sjkJX32wb7E6c3bTXTprkeUxXzhIh7mazhXX2bos7ltXCTLZ916A+xVF3etI3QbNTwt4rhlc2Ot7qLP5raot76HHurFDaMnbv+Oj3bCsEP9dtGFq1DjFjODnnW3jD47MzlpbZaVHeq4qc0hLvosFy5pZ71ABeduC70947zE3YM71z0MU5jr9tCjubMyf5dj0t8y+szAI5zraNEu01JuCV3MQxDPH4q5837D6OXO+RxqZTG8AXS71cLNYdjbuB73N4L+ML2RdUIP9/RKqoOlV78Hblp3dNDjvSbNa0zh1WsuziacCT3b2+Ami9tAD6bsDgdd7By2Fgy4DfSI7x7dlOUNGbtp5eyy2fWWmFXwDRbo4d4ZFek7/cVr3/SZsMBfLNF3rZxOCE2uH93dFmCA08tWbpF9dzPo+Z6VM7tFbhN9z8pFJkHt6k/cdK2VQQ/3/NHE5uFdO7qbHC9rXJ63Mv18xNUfQOh6IUak7DZorh+LuP6j6BxHxaCXe1TSpB1fP7pj0jR6sCdoAtPP8+s/j80Zsxo92hvqoSEurx89Y4GHL1303RnbGPiza8xXVJ5ZmRQjjb7bnmm7thFXO6+zNdkFCn0/ymzf83f9sWhBdmZhXaE/7HqjeWH8/KtHJ+VgQrE6EWVXpn2zoQeuVdF02WgUrELfN92DVYHXHqRJWMWsTJ5ydbE5wxNeIXavY2obEfI/TXZ6dTEEEXVOiOP6BQ3/qCdyVhdVWnzErbjrogdKE41Wie+7ljttcCs+a94Bmd1wV1zsyFmNW/FZ885s4tDoF5CEPQLjdAvoNvQsi4tKJS9uRsLnPaZjOsrLhrvEzUh4cXJEzEf7Acm5mLt+CT/OXmcUX5Knk5i7+tX1lC/u+T3P4wWhcjtiDgnf49musD9cOg8+sKcyXP8xqyFJDiY/Sl5qS4ue3cArvyTJrlTIjxdf/RCaXpHfwGuABMmXR74H8AkvDuDIHpJ4A+/HeCAHhORv/+qzxf6aXfSbeEnE9w5vzTmbl8evcdzC28kSfSDnabAX0OMbOj39keSXlz8Wm+PZvDk9fdXqYoSv6HLwFT3w5i1Aq8kt9ualKA66au2ML96h6yVmf94RsUT35I30W6GK2EMrpzNphDfvP3JLWQEBPRzqap/Xo5dDHclYPNDDWd26eD72d/XalB5eFvEqv/42Rc10qsu93Mu93Mu93Mu93Mu93Fr5E5og7jLII0rcAAAAAElFTkSuQmCC\";\n",[],[553,633],"8143dd38-b664-4147-95a9-d409e6bf85c7",["D",1789504726522],"directory",[616,617],[553],"bc18c686-3f12-419e-9602-4ca351d11abe","studio-v2-patches.ts","eead9b88-826a-11f1-b344-1607ee4eb77e","be786689-317a-432b-8b2a-17317abec3ee",199,["D",1784353120699],"// Scenario Studio v2 (map canvas + epilogue + Rise export + logging) as\n// find/replace patches applied by main.ts over apps/scenario-studio.html.\n// Canonical merged file: workspace Tools/Interactive Apps/scenario-studio.html\n// (collapse these into the .html file whenever a bulk upload path exists).\nexport const STUDIO_V2_PATCHES: [string, string][] = [\n [\"#scenario-studio .mode-card p { font-size: 12px !important; color: #5a7383 !important; line-height: 1.55 !important; }\\n\\n#scenario-studio .pattern-pill {\\n display: inline-block !important; padding: 8px 15px !important; border-radius: 30px !important; margin: 0 8px 8px 0 !important;\\n\", \"#scenario-studio .mode-card p { font-size: 12px !important; color: #5a7383 !important; line-height: 1.55 !important; }\\n\\n/* scenario map */\\n#scenario-studio .map-col { display: flex !important; flex-direction: column !important; align-items: stretch !important; max-width: 640px !important; margin: 14px 0 0 !important; }\\n#scenario-studio .map-arrow { text-align: center !important; color: #1FC3CC !important; font-size: 18px !important; line-height: 1.4 !important; }\\n#scenario-studio .map-block { background: #ffffff !important; border: 2px solid #d0dde5 !important; border-radius: 12px !important; padding: 14px 16px !important; }\\n#scenario-studio .map-block .hint { margin: 4px 0 8px !important; }\\n#scenario-studio .map-conversation { border-color: #1FC3CC !important; background: #e9fafb !important; }\\n#scenario-studio .map-decision { border-color: #AC714D !important; background: #fdf3ec !important; }\\n#scenario-studio .map-epilogue { border-color: #223A4C !important; background: #eef3f6 !important; }\\n#scenario-studio .map-block-head { display: flex !important; justify-content: space-between !important; align-items: center !important; }\\n#scenario-studio .map-block-head b { font-family: 'Josefin Sans', sans-serif !important; font-size: 14px !important; }\\n#scenario-studio .map-tools button, #scenario-studio .map-x {\\n background: transparent !important; border: 1px solid #d0dde5 !important; border-radius: 6px !important;\\n cursor: pointer !important; font-size: 12px !important; color: #5a7383 !important; padding: 2px 8px !important; margin-left: 4px !important;\\n}\\n#scenario-studio .map-tools button:hover, #scenario-studio .map-x:hover { border-color: #1FC3CC !important; color: #0d6e74 !important; }\\n#scenario-studio .dec-opt { margin-top: 8px !important; padding: 8px !important; background: rgba(255,255,255,0.7) !important; border-radius: 8px !important; }\\n#scenario-studio .skipnote { background: #f4f8fa !important; border: 1.5px dashed #d0dde5 !important; border-radius: 12px !important; padding: 18px 22px !important; font-size: 13.5px !important; color: #5a7383 !important; }\\n\\n#scenario-studio .pattern-pill {\\n display: inline-block !important; padding: 8px 15px !important; border-radius: 30px !important; margin: 0 8px 8px 0 !important;\\n\"],\n [\"(function() {\\n var API = 'https://jill1--9c0cd124824611f1b3341607ee4eb77e.web.val.run';\\n var STORE_KEY = 'aida_scenario_studio_v1';\\n var ENGINE = 'https://jill1--e015758e820e11f1a4df1607ee4eb77e.web.val.run';\\n\\n\", \"(function() {\\n var API = 'https://jill1--9c0cd124824611f1b3341607ee4eb77e.web.val.run';\\n var STORE_KEY = 'aida_scenario_studio_v2';\\n var ENGINE = 'https://jill1--e015758e820e11f1a4df1607ee4eb77e.web.val.run';\\n\\n\"],\n [\" ];\\n\\n var STEPS = ['Mode', 'Situation', 'Character', 'Behavior', 'What Good Looks Like', 'Playtest', 'Theme', 'Publish'];\\n\\n var PATTERNS = [\\n\", \" ];\\n\\n var STEPS = ['Map', 'Mode', 'Situation', 'Character', 'Behavior', 'What Good Looks Like', 'Playtest', 'Theme', 'Publish'];\\n\\n var PATTERNS = [\\n\"],\n [\" difficultyOn: false,\\n theme: {}, headerTitle: '', logoOff: false,\\n simId: '', editToken: '', published: false, sceneReady: false\\n },\\n\\n init: function() {\\n this.loadState();\\n this.render();\\n },\\n save: function() { try { localStorage.setItem(STORE_KEY, JSON.stringify(this.state)); } catch(e) {} },\\n\", \" difficultyOn: false,\\n theme: {}, headerTitle: '', logoOff: false,\\n simId: '', editToken: '', published: false, sceneReady: false,\\n // Scenario map (the planning layer; one decision layer max)\\n map: null, // { blocks: [{kind, note, ...}] }; null until touched\\n decision: null, // { varName, prompt, options:[{label, correct, feedback}] }\\n epi: null, // { premise, takeaways, length, inputs:[{var, means, values}] }\\n packaging: 'storyline', // storyline | rise (self-contained)\\n askName: true, completionCode: '',\\n logResults: false,\\n epiSimId: '', epiEditToken: ''\\n },\\n\\n init: function() {\\n this.loadState();\\n this.render();\\n // Playtest helper: an epilogue has nothing to read outside a course, so\\n // when the playtest iframe announces ready we feed it SAMPLE choices\\n // (the first value of each input) to generate a real ending.\\n var self = this;\\n window.addEventListener('message', function(e) {\\n if (!e.data || e.data.type !== 'lsdsim:ready') return;\\n if (!self.isEpilogueOnly()) return;\\n var frame = document.querySelector('.playtest-frame');\\n if (!frame || !frame.contentWindow) return;\\n var vars = { LearnerName: 'Alex' };\\n var ins = (self.state.epi && self.state.epi.inputs && self.state.epi.inputs.length) ? self.state.epi.inputs : self.epiAutoInputs();\\n ins.forEach(function(inp) {\\n var keys = inp.values ? Object.keys(inp.values) : [];\\n vars[inp.var] = keys.length ? keys[0] : 'sample';\\n });\\n try { frame.contentWindow.postMessage({ type: 'lsdsim:init', vars: vars }, '*'); } catch(err) {}\\n });\\n },\\n save: function() { try { localStorage.setItem(STORE_KEY, JSON.stringify(this.state)); } catch(e) {} },\\n\"],\n [\" tabs.innerHTML = html;\\n var body = document.getElementById('ss-body');\\n var fn = ['rMode', 'rSituation', 'rCharacter', 'rBehavior', 'rGood', 'rPlaytest', 'rTheme', 'rPublish'][this.state.step];\\n body.innerHTML = this[fn]();\\n var post = ['pMode', null, null, null, null, 'pPlaytest', 'pTheme', 'pPublish'][this.state.step];\\n if (post && this[post]) this[post]();\\n },\\n\\n // ── STEP 0: MODE ──\\n rMode: function() {\\n var s = this.state;\\n var cards = [\\n\", \" tabs.innerHTML = html;\\n var body = document.getElementById('ss-body');\\n var fn = ['rMap', 'rMode', 'rSituation', 'rCharacter', 'rBehavior', 'rGood', 'rPlaytest', 'rTheme', 'rPublish'][this.state.step];\\n body.innerHTML = this[fn]();\\n var post = [null, 'pMode', null, null, null, null, 'pPlaytest', 'pTheme', 'pPublish'][this.state.step];\\n if (post && this[post]) this[post]();\\n },\\n\\n // ── STEP 0: MAP (the planning layer) ──\\n defaultMap: function() {\\n return { blocks: [\\n { kind: 'content', note: 'Set the scene: who the learner is, what just happened' },\\n { kind: 'conversation' }\\n ] };\\n },\\n getMap: function() {\\n if (!this.state.map || !Array.isArray(this.state.map.blocks)) this.state.map = this.defaultMap();\\n return this.state.map;\\n },\\n mapCounts: function() {\\n var c = { content: 0, conversation: 0, decision: 0, epilogue: 0 };\\n this.getMap().blocks.forEach(function(b) { c[b.kind] = (c[b.kind] || 0) + 1; });\\n return c;\\n },\\n isEpilogueOnly: function() {\\n var c = this.mapCounts();\\n return c.epilogue > 0 && c.conversation === 0;\\n },\\n hasConversation: function() { return this.mapCounts().conversation > 0; },\\n hasEpilogue: function() { return this.mapCounts().epilogue > 0; },\\n hasDecision: function() { return this.mapCounts().decision > 0; },\\n\\n addBlock: function(kind) {\\n var m = this.getMap(), c = this.mapCounts();\\n if (kind === 'conversation' && c.conversation >= 1) {\\n this.mapCoach('One live conversation per scene is the sweet spot. If your story truly needs a second one, build it as its own Studio sim and give it its own slide; each conversation gets its own URL.'); return;\\n }\\n if (kind === 'decision' && c.decision >= 1) {\\n this.mapCoach('One decision point is the limit, on purpose. Hiring managers do not spend a lot of time on your sample. One decision that fans into two or three endings shows your branching skills; a second layer just multiplies the slides you have to build without impressing anyone further.'); return;\\n }\\n if (kind === 'epilogue' && c.epilogue >= 1) {\\n this.mapCoach('The epilogue IS the ending; one per scenario.'); return;\\n }\\n var block = { kind: kind, note: '' };\\n if (kind === 'decision') {\\n if (!this.state.decision) this.state.decision = { varName: 'Choice_1', prompt: '', options: [ { label: '', correct: true, feedback: '' }, { label: '', correct: false, feedback: '' } ] };\\n }\\n if (kind === 'epilogue') {\\n if (!this.state.epi) this.state.epi = { premise: '', takeaways: true, inputs: null };\\n m.blocks.push(block); this.save(); this.render(); return; // always last\\n }\\n // insert before the epilogue if there is one\\n var epIx = -1;\\n m.blocks.forEach(function(b, i) { if (b.kind === 'epilogue') epIx = i; });\\n if (epIx >= 0) m.blocks.splice(epIx, 0, block); else m.blocks.push(block);\\n this.save(); this.render();\\n },\\n removeBlock: function(i) {\\n var m = this.getMap();\\n var b = m.blocks[i];\\n if (b && b.kind === 'decision') this.state.decision = null;\\n if (b && b.kind === 'epilogue') this.state.epi = null;\\n m.blocks.splice(i, 1); this.save(); this.render();\\n },\\n moveBlock: function(i, dir) {\\n var m = this.getMap(); var j = i + dir;\\n if (j < 0 || j >= m.blocks.length) return;\\n if (m.blocks[i].kind === 'epilogue' || m.blocks[j].kind === 'epilogue') return; // ending stays last\\n var t = m.blocks[i]; m.blocks[i] = m.blocks[j]; m.blocks[j] = t;\\n this.save(); this.render();\\n },\\n mapCoach: function(msg) {\\n var el = document.getElementById('map-coach');\\n if (el) el.innerHTML = '

Hold on. ' + this.esc(msg) + '

';\\n },\\n noteChanged: function(i) {\\n var el = document.getElementById('blk-note-' + i);\\n if (el) { this.getMap().blocks[i].note = el.value; this.save(); }\\n },\\n\\n decChanged: function() {\\n var d = this.state.decision; if (!d) return;\\n d.varName = (this.val('dec-var') || 'Choice_1').replace(/[^A-Za-z0-9_]/g, '');\\n d.prompt = this.val('dec-prompt');\\n for (var i = 0; i < d.options.length; i++) {\\n d.options[i].label = this.val('dec-opt-' + i);\\n d.options[i].feedback = this.val('dec-fb-' + i);\\n var r = document.getElementById('dec-cor-' + i);\\n d.options[i].correct = r ? r.checked : d.options[i].correct;\\n }\\n this.save();\\n },\\n decAddOption: function() {\\n var d = this.state.decision; if (!d || d.options.length >= 3) { this.mapCoach('Two or three ways it can go. More options means more branches to build for a sample nobody lingers on.'); return; }\\n this.decChanged(); d.options.push({ label: '', correct: false, feedback: '' }); this.save(); this.render();\\n },\\n decRemoveOption: function(i) {\\n var d = this.state.decision; if (!d || d.options.length <= 2) return;\\n this.decChanged(); d.options.splice(i, 1); this.save(); this.render();\\n },\\n draftDecision: function() {\\n var self = this; this.decChanged();\\n this.busy('map-coach', 'Drafting your decision point.');\\n this.coach('decision', {\\n situation: this.state.situation || this.state.intake,\\n sceneNotes: this.getMap().blocks.map(function(b) { return b.kind + ': ' + (b.note || ''); }).join(' | '),\\n designerIdea: this.state.decision ? this.state.decision.prompt : ''\\n }).then(function(r) {\\n if (r.pushback) { self.pushbackBox('map-coach', r.pushback); return; }\\n var d = self.state.decision;\\n d.prompt = r.prompt || d.prompt;\\n if (Array.isArray(r.options) && r.options.length >= 2) {\\n d.options = r.options.slice(0, 3).map(function(o) { return { label: o.label || '', correct: o.correct === true, feedback: o.feedback || '' }; });\\n }\\n self.save(); self.render();\\n }).catch(function(e) { self.fail('map-coach', e.message); });\\n },\\n\\n epiChanged: function() {\\n var e = this.state.epi; if (!e) return;\\n e.premise = this.val('epi-premise');\\n var t = document.getElementById('epi-take'); e.takeaways = t ? t.checked : true;\\n var box = document.getElementById('epi-inputs');\\n if (box && box.value.trim()) {\\n try { e.inputs = JSON.parse(box.value); box.style.borderColor = ''; }\\n catch(err) { box.style.borderColor = '#c0392b'; }\\n }\\n this.save();\\n },\\n epiAutoInputs: function() {\\n // Derived from the map: the decision's variable, plus the conversation's\\n // outcome variable when the mode classifies endings.\\n var ins = [];\\n var d = this.state.decision;\\n if (this.hasDecision() && d && this.state.packaging !== 'rise') {\\n var values = {};\\n (d.options || []).forEach(function(o) { if (o.label) values[o.label.toLowerCase().replace(/[^a-z0-9]+/g, '_').replace(/^_|_$/g, '').slice(0, 30)] = o.label; });\\n ins.push({ var: d.varName || 'Choice_1', means: d.prompt || 'The decision the learner made on the choice slide', values: values });\\n }\\n if (this.hasConversation() && this.state.outcomes && this.state.outcomes.length) {\\n var ov = {};\\n this.state.outcomes.forEach(function(o) { ov[o.id] = o.when; });\\n ins.push({ var: 'Practice_Outcome', means: 'How the learner handled the live conversation', values: ov });\\n }\\n return ins;\\n },\\n draftEpilogue: function() {\\n var self = this; this.epiChanged();\\n this.busy('map-coach', 'Drafting your epilogue premise.');\\n this.coach('epilogue', {\\n situation: this.state.situation || this.state.intake,\\n sceneNotes: this.getMap().blocks.map(function(b) { return b.kind + ': ' + (b.note || ''); }).join(' | '),\\n decision: this.state.decision,\\n outcomes: this.state.outcomes,\\n designerIdea: this.state.epi ? this.state.epi.premise : ''\\n }).then(function(r) {\\n if (r.pushback) { self.pushbackBox('map-coach', r.pushback); return; }\\n var e = self.state.epi;\\n e.premise = r.premise || e.premise;\\n if (Array.isArray(r.inputs) && r.inputs.length) e.inputs = r.inputs;\\n self.save(); self.render();\\n }).catch(function(e) { self.fail('map-coach', e.message); });\\n },\\n\\n rMap: function() {\\n var s = this.state, self = this;\\n var m = this.getMap();\\n var h = '

Map your scenario

'\\n + '

Lay out the arc of your scene before you build anything. The method is the product: AI blocks are options inside your scenario design, not the design itself. A strong portfolio sample is SHORT. Hiring managers do not spend a lot of time on your sample, so one contained scene that flows well beats a sprawling course every time.

'\\n + '

';\\n m.blocks.forEach(function(b, i) {\\n h += self.renderBlock(b, i);\\n if (i < m.blocks.length - 1) h += '

↓

';\\n });\\n h += '

'\\n + ''\\n + ''\\n + ''\\n + ''\\n + '

'\\n + '

The shape is yours: no branching at all is fine, and so is one decision that fans out. What the map will not let you do is nest branches inside branches; that is rabbit-hole territory for a sample.

'\\n + '

';\\n return h;\\n },\\n renderBlock: function(b, i) {\\n var self = this, s = this.state;\\n var titles = { content: 'Content slide', conversation: 'AI conversation', decision: 'Decision point', epilogue: 'Epilogue ending' };\\n var tips = {\\n content: 'A normal Storyline slide: context, information, whatever the learner needs before what comes next.',\\n conversation: 'The live AI block. You will design it step by step after this map (mode, character, behavior, scoring).',\\n decision: 'The learner makes a call. In Storyline this is normal buttons on a slide setting a variable; in a self-contained scene it happens inside the object.',\\n epilogue: 'The AI reads the choices made along the way and writes a personalized consequence story as the ending. Works even with zero other AI blocks.'\\n };\\n var h = '

' + titles[b.kind] + ''\\n + ''\\n + ''\\n + '

'\\n + '

' + tips[b.kind] + '

';\\n if (b.kind === 'content') {\\n h += '';\\n }\\n if (b.kind === 'decision' && s.decision) {\\n var d = s.decision;\\n h += '

The decision question (learner-facing)

';\\n d.options.forEach(function(o, j) {\\n h += '

'\\n + ''\\n + ''\\n + (d.options.length > 2 ? '' : '')\\n + '

';\\n });\\n h += '

'\\n + (d.options.length < 3 ? '' : '')\\n + '

'\\n + '

Storyline variable this decision sets (ignored in self-contained scenes)

'\\n + '

Mark the strong call with the radio button. Each option fans to its own consequence and they all meet at the ending; the map keeps it one layer deep on purpose.

';\\n }\\n if (b.kind === 'epilogue' && s.epi) {\\n var e = s.epi;\\n h += '

Epilogue premise (the world and time frame the ending plays out in)

'\\n + ' Add 2-3 short observations after the story'\\n + '

'\\n + '

Choices it reads (auto-built from your map; edit if your course tracks more)'\\n + '

';\\n }\\n h += '

';\\n return h;\\n },\\n mapNext: function() {\\n var c = this.mapCounts();\\n if (!c.conversation && !c.epilogue) {\\n this.mapCoach('This map has no AI block yet, so there is nothing for the Studio to build. Add an AI conversation or an epilogue ending; pure content-and-buttons scenarios are great, but you build those straight in Storyline.');\\n return;\\n }\\n if (this.hasDecision()) this.decChanged();\\n if (this.hasEpilogue()) this.epiChanged();\\n this.goStep(this.hasConversation() ? 1 : 2);\\n },\\n\\n // ── STEP 1: MODE ──\\n rMode: function() {\\n if (this.isEpilogueOnly()) {\\n return '

Skipped for this map

'\\n + '

Your map is an epilogue ending with no live conversation, so this step does not apply. The situation step gives the epilogue its context; everything else is already covered on your map.

'\\n + '

';\\n }\\n var s = this.state;\\n var cards = [\\n\"],\n [\" h += '

Also score it against a rubric (branch AND grade)

';\\n }\\n h += '

'\\n + '

Planning a full branching scenario with scripted choice slides too? That is the Storyline Scenario Builder\\\\'s job; this Studio builds the live conversation piece. They work together: plan the course there, build the conversation here, and branch on how it ends.

'\\n\", \" h += '

Also score it against a rubric (branch AND grade)

';\\n }\\n h += '

'\\n + '

'\\n\"],\n [\" + '

Describe the MOMENT it goes wrong

Not the topic. The scene. Who is standing where, saying what?

'\\n + '

What is at stake if it goes badly?

'\\n + '

';\\n\", \" + '

Describe the MOMENT it goes wrong

Not the topic. The scene. Who is standing where, saying what?

'\\n + '

What is at stake if it goes badly?

'\\n + '

';\\n\"],\n [\" stakes: this.val('inp-sc-stakes')\\n };\\n this.save(); this.goStep(2);\\n },\\n\\n // ── STEP 2: CHARACTER ──\\n rCharacter: function() {\\n var s = this.state;\\n var isWatch = s.mode === 'watch';\\n\", \" stakes: this.val('inp-sc-stakes')\\n };\\n this.save(); this.goStep(this.isEpilogueOnly() ? 6 : 3);\\n },\\n\\n // ── STEP 2: CHARACTER ──\\n rCharacter: function() {\\n if (this.isEpilogueOnly()) {\\n return '

Skipped for this map

'\\n + '

Your map is an epilogue ending with no live conversation, so this step does not apply. The situation step gives the epilogue its context; everything else is already covered on your map.

'\\n + '

';\\n }\\n var s = this.state;\\n var isWatch = s.mode === 'watch';\\n\"],\n [\" if (s.twoChars) h += this.charFields('B', isWatch ? 'The person they are dealing with' : 'The second character (when do they jump in?)', s.char2Input);\\n\\n h += '

'\\n + '

';\\n\", \" if (s.twoChars) h += this.charFields('B', isWatch ? 'The person they are dealing with' : 'The second character (when do they jump in?)', s.char2Input);\\n\\n h += '

'\\n + '

';\\n\"],\n [\" s.character = { name: this.val('inp-cname-a'), role: this.val('inp-crole-a'), persona: this.val('inp-cpersona-a'), openingLine: this.val('inp-copen'), voiceId: this.val('inp-cvoice-a') };\\n if (s.twoChars) s.character2 = { name: this.val('inp-cname-b'), role: this.val('inp-crole-b'), persona: this.val('inp-cpersona-b'), voiceId: this.val('inp-cvoice-b') };\\n this.save(); this.goStep(3);\\n },\\n\\n // ── STEP 3: BEHAVIOR (triggers + moods) ──\\n rBehavior: function() {\\n var s = this.state;\\n var mainChar = s.mode === 'watch' ? (s.character2 || s.character) : s.character;\\n\", \" s.character = { name: this.val('inp-cname-a'), role: this.val('inp-crole-a'), persona: this.val('inp-cpersona-a'), openingLine: this.val('inp-copen'), voiceId: this.val('inp-cvoice-a') };\\n if (s.twoChars) s.character2 = { name: this.val('inp-cname-b'), role: this.val('inp-crole-b'), persona: this.val('inp-cpersona-b'), voiceId: this.val('inp-cvoice-b') };\\n this.save(); this.goStep(4);\\n },\\n\\n // ── STEP 3: BEHAVIOR (triggers + moods) ──\\n rBehavior: function() {\\n if (this.isEpilogueOnly()) {\\n return '

Skipped for this map

'\\n + '

Your map is an epilogue ending with no live conversation, so this step does not apply. The situation step gives the epilogue its context; everything else is already covered on your map.

'\\n + '

';\\n }\\n var s = this.state;\\n var mainChar = s.mode === 'watch' ? (s.character2 || s.character) : s.character;\\n\"],\n [\" + '

They gradually open up or soften when the ' + (s.mode === 'watch' ? 'skilled person' : 'learner') + '...

'\\n + '

They stay closed, or get worse, when the ' + (s.mode === 'watch' ? 'skilled person' : 'learner') + '...

'\\n + '

';\\n\", \" + '

They gradually open up or soften when the ' + (s.mode === 'watch' ? 'skilled person' : 'learner') + '...

'\\n + '

They stay closed, or get worse, when the ' + (s.mode === 'watch' ? 'skilled person' : 'learner') + '...

'\\n + '

';\\n\"],\n [\" saveBehavior: function() {\\n this.state.behaviorRules = this.val('inp-rules') || this.state.behaviorRules;\\n this.save(); this.goStep(4);\\n },\\n\\n // ── STEP 4: WHAT GOOD LOOKS LIKE (mode-dependent) ──\\n rGood: function() {\\n var s = this.state;\\n var h = '

';\\n\", \" saveBehavior: function() {\\n this.state.behaviorRules = this.val('inp-rules') || this.state.behaviorRules;\\n this.save(); this.goStep(5);\\n },\\n\\n // ── STEP 4: WHAT GOOD LOOKS LIKE (mode-dependent) ──\\n rGood: function() {\\n if (this.isEpilogueOnly()) {\\n return '

Skipped for this map

'\\n + '

Your map is an epilogue ending with no live conversation, so this step does not apply. The situation step gives the epilogue its context; everything else is already covered on your map.

'\\n + '

';\\n }\\n var s = this.state;\\n var h = '

';\\n\"],\n [\" + '

Your learner watches this conversation. The premise is the arc the scene must follow; the pause points check whether they can spot the next good move while watching.

'\\n + '

In your words: what does the skilled person DO that makes this go well?

'\\n + '

';\\n if (s.premise) {\\n h += '

'\\n\", \" + '

Your learner watches this conversation. The premise is the arc the scene must follow; the pause points check whether they can spot the next good move while watching.

'\\n + '

In your words: what does the skilled person DO that makes this go well?

'\\n + '

';\\n if (s.premise) {\\n h += '

'\\n\"],\n [\" h += '

Write what a strong learner would actually SAY or DO. The coach turns it into scoring criteria and it will reject vibes: every criterion has to be observable in the learner\\\\'s own words.

'\\n + '

In your words, what separates a good run from a bad one?

'\\n + '

';\\n if (s.rubric) {\\n h += '

Criteria (edit inline)

';\\n\", \" h += '

Write what a strong learner would actually SAY or DO. The coach turns it into scoring criteria and it will reject vibes: every criterion has to be observable in the learner\\\\'s own words.

'\\n + '

In your words, what separates a good run from a bad one?

'\\n + '

';\\n if (s.rubric) {\\n h += '

Criteria (edit inline)

';\\n\"],\n [\" if (showOutcomes) {\\n h += (showRubric ? '' : '

No score here. The sim classifies how the conversation ENDED and hands Storyline the answer, so your course can branch on how the learner handled the human. The last ending is always the fallback.

'\\n + '

');\\n if (showRubric && !s.outcomes) h += '

';\\n if (s.outcomes) {\\n\", \" if (showOutcomes) {\\n h += (showRubric ? '' : '

No score here. The sim classifies how the conversation ENDED and hands Storyline the answer, so your course can branch on how the learner handled the human. The last ending is always the fallback.

'\\n + '

');\\n if (showRubric && !s.outcomes) h += '

';\\n if (s.outcomes) {\\n\"],\n [\" this.save();\\n },\\n saveGood: function() { this.saveGoodFields(); this.goStep(5); },\\n\\n // ── config assembly ──\\n\", \" this.save();\\n },\\n saveGood: function() { this.saveGoodFields(); this.goStep(6); },\\n\\n // ── config assembly ──\\n\"],\n [\" buildConfig: function() {\\n var s = this.state;\\n var c = {\\n scenarioTitle: s.situation ? s.situation.scenarioTitle : '',\\n\", \" buildConfig: function() {\\n var s = this.state;\\n // Epilogue-only map: the whole object IS the ending.\\n if (this.isEpilogueOnly()) return this.buildEpilogueConfig();\\n var c = {\\n scenarioTitle: s.situation ? s.situation.scenarioTitle : '',\\n\"],\n [\" openingLine: s.character ? s.character.openingLine : '',\\n maxTurns: s.maxTurns,\\n logResults: false\\n };\\n var personaA = (s.character ? s.character.persona : '') + (s.behaviorRules && !s.twoChars ? '\\\\n\\\\n' + s.behaviorRules : '');\\n\", \" openingLine: s.character ? s.character.openingLine : '',\\n maxTurns: s.maxTurns,\\n logResults: s.logResults === true\\n };\\n var personaA = (s.character ? s.character.persona : '') + (s.behaviorRules && !s.twoChars ? '\\\\n\\\\n' + s.behaviorRules : '');\\n\"],\n [\" if (s.twoChars && s.character2 && s.character2.voiceId) vv[s.character2.name] = s.character2.voiceId;\\n if (Object.keys(vv).length) c.voice = { enabled: true, voices: vv };\\n var t = {};\\n THEME_KEYS.forEach(function(k) { if (s.theme[k.k] && s.theme[k.k] !== k.def) t[k.k] = s.theme[k.k]; });\\n if (s.headerTitle) t.headerTitle = s.headerTitle;\\n if (s.logoOff) t.logoUrl = '';\\n if (Object.keys(t).length) c.theme = t;\\n return c;\\n\", \" if (s.twoChars && s.character2 && s.character2.voiceId) vv[s.character2.name] = s.character2.voiceId;\\n if (Object.keys(vv).length) c.voice = { enabled: true, voices: vv };\\n c.theme = this.buildTheme();\\n if (!Object.keys(c.theme).length) delete c.theme;\\n // Self-contained packaging: the whole map runs inside one embed.\\n if (s.packaging === 'rise') {\\n c.packaging = 'self-contained';\\n c.askName = s.askName !== false;\\n if (s.completionCode) c.completionCode = s.completionCode;\\n var phases = [];\\n if (this.hasConversation()) phases.push({ id: 'conv', type: 'conversation', title: c.scenarioTitle || 'The conversation' });\\n if (this.hasDecision() && s.decision && s.mode !== 'watch') {\\n phases.push({ id: 'decide', type: 'decision', title: 'Your call',\\n prompt: s.decision.prompt || '',\\n options: (s.decision.options || []).filter(function(o) { return o.label; }).map(function(o) {\\n var opt = { label: o.label };\\n if (o.correct) opt.correct = true;\\n if (o.feedback) opt.feedback = o.feedback;\\n if (SS.hasEpilogue()) opt.next = 'wrap';\\n return opt;\\n }) });\\n }\\n if (this.hasEpilogue() && s.epi && s.mode !== 'watch') {\\n phases.push({ id: 'wrap', type: 'epilogue', title: 'How it went' });\\n c.epilogue = { premise: s.epi.premise || '', takeaways: s.epi.takeaways !== false };\\n }\\n if (phases.length > 1) c.phases = phases;\\n }\\n return c;\\n },\\n buildTheme: function() {\\n var s = this.state, t = {};\\n THEME_KEYS.forEach(function(k) { if (s.theme[k.k] && s.theme[k.k] !== k.def) t[k.k] = s.theme[k.k]; });\\n if (s.headerTitle) t.headerTitle = s.headerTitle;\\n if (s.logoOff) t.logoUrl = '';\\n return t;\\n },\\n // The standalone epilogue web object (final slide). Used as the whole\\n // config for epilogue-only maps, and as the SECOND published sim when a\\n // Storyline-packaged map ends with an epilogue.\\n buildEpilogueConfig: function() {\\n var s = this.state, e = s.epi || {};\\n var title = s.situation && s.situation.scenarioTitle ? s.situation.scenarioTitle : 'How your story went';\\n var c = {\\n scenarioTitle: title,\\n learnerRole: s.situation ? s.situation.learnerRole : '',\\n brief: e.premise || '',\\n mode: 'epilogue',\\n epilogue: {\\n premise: e.premise || '',\\n takeaways: e.takeaways !== false,\\n inputs: (e.inputs && e.inputs.length ? e.inputs : this.epiAutoInputs())\\n },\\n logResults: false\\n };\\n var t = this.buildTheme();\\n if (Object.keys(t).length) c.theme = t;\\n return c;\\n\"],\n [\" rPlaytest: function() {\\n return '

Play your own sim

'\\n + '

This is the real thing, running on the same engine your learners will use. ' + (this.state.mode === 'watch' ? 'Watch it play out and answer your own pause points.' : 'Take the learner\\\\'s seat and try to pass your own rubric, then try to fail it.') + ' If something feels off, jump back to any step; your work is saved.

'\\n + '

'\\n + ''\\n + ''\\n + ''\\n + ''\\n + ''\\n + '

';\\n },\\n\", \" rPlaytest: function() {\\n return '

Play your own sim

'\\n + '

This is the real thing, running on the same engine your learners will use. ' + (this.isEpilogueOnly() ? 'The Studio feeds it sample choices so you can read a real generated ending; in your course it reads the learner\\\\'s actual variables.' : (this.state.mode === 'watch' ? 'Watch it play out and answer your own pause points.' : 'Take the learner\\\\'s seat and try to pass your own rubric, then try to fail it.')) + ' If something feels off, jump back to any step; your work is saved.

'\\n + '

'\\n + ''\\n + ''\\n + ''\\n + ''\\n + ''\\n + '

';\\n },\\n\"],\n [\" + '

Header title (blank keeps the default)

'\\n + '

Hide the AIDA logo (use your course\\\\'s look only)

'\\n + '

';\\n return h;\\n\", \" + '

Header title (blank keeps the default)

'\\n + '

Hide the AIDA logo (use your course\\\\'s look only)

'\\n + '

';\\n return h;\\n\"],\n [\"\\n // ── STEP 7: PUBLISH ──\\n rPublish: function() {\\n var s = this.state;\\n var url = s.simId ? API + '/s/' + s.simId : '';\\n var h = '

Publish

';\\n if (!s.published) {\\n h += '

Publishing gives your sim a permanent URL. You paste that URL into Storyline as a web object, and you are done: editing here later updates the same URL, no Storyline changes needed.

'\\n + '

';\\n } else {\\n h += '

Your sim is live. Here is everything you need.

'\\n + 'Your sim URL (this goes in Storyline: Insert, then Web Object)'\\n + '

' + this.esc(url) + '

'\\n + '

Implementation guide

Your exact variables, triggers, and bridge script, prefilled for THIS sim. Print it and follow it top to bottom.

'\\n + '

Scene Director brief

What to put AROUND the box: setting, character casting, layout, Content Library search terms.

'\\n + '

Portfolio design rationale

Turns your Studio answers into a printable case-study page: proof you designed this, not just used a tool.

'\\n + '

Your edit key

'\\n + '

This browser remembers your sim automatically. Save this key somewhere safe anyway; with the sim URL plus this key you can edit from any computer (support can help you restore it).

'\\n + '

' + this.esc(s.simId) + ' / ' + this.esc(s.editToken) + '

'\\n + '

Advanced: your config

'\\n + '

The same sim as a hand-editable config block, for the template workflow (adding phases, voice, or logging by hand).

'\\n + '

' + this.esc(JSON.stringify(this.buildConfig(), null, 1)) + '

'\\n + '

';\\n }\\n h += '

';\\n\", \"\\n // ── STEP 7: PUBLISH ──\\n needsEpiSim: function() {\\n // A Storyline-packaged map that ends with an epilogue publishes TWO web\\n // objects: the main sim and the final-slide epilogue.\\n return this.hasEpilogue() && !this.isEpilogueOnly() && this.state.packaging !== 'rise';\\n },\\n embedSnippet: function(url, title) {\\n return '';\\n },\\n riseWarnings: function() {\\n var w = [];\\n if (this.state.mode === 'watch' && this.hasEpilogue()) w.push('Watch mode cannot chain an in-object epilogue yet; the epilogue block will be skipped in this packaging.');\\n if (this.hasDecision() && this.state.mode === 'watch') w.push('Watch mode cannot include an in-object decision; the decision block will be skipped in this packaging.');\\n if (this.mapCounts().content > 0) w.push('Content slides on your map stay in your build plan; inside the embed the scene runs brief, conversation, decision, ending.');\\n if (this.hasDecision()) w.push('In this packaging the decision happens inside the object, so its Storyline variable is not used.');\\n return w;\\n },\\n buildPlanHtml: function() {\\n var self = this, s = this.state;\\n var rise = s.packaging === 'rise';\\n var rows = '';\\n var step = 0;\\n this.getMap().blocks.forEach(function(b) {\\n step++;\\n var what = '';\\n if (b.kind === 'content') what = 'Storyline slide. ' + (b.note ? self.esc(b.note) : 'Your content, built natively.');\\n else if (b.kind === 'conversation') what = rise\\n ? 'Runs inside the embed. The conversation opens the scene.'\\n : 'Sim slide. Web object with your sim URL; follow the implementation guide for variables, moods, and the bridge script.';\\n else if (b.kind === 'decision') what = rise\\n ? 'Runs inside the embed. The learner makes the call in-object and gets your feedback.'\\n : 'Choice slide. Normal Storyline buttons (' + (s.decision ? s.decision.options.filter(function(o) { return o.label; }).length : 2) + ' options). Each button sets ' + self.esc(s.decision ? s.decision.varName : 'Choice_1') + ' to its value and jumps to that option\\\\'s consequence slide. One decision layer: the branches meet again at the ending.';\\n else if (b.kind === 'epilogue') what = rise\\n ? 'Runs inside the embed. The ending writes itself from the choices made in the scene.'\\n : 'Ending slide. Web object with your epilogue URL; it reads the choice variables and writes the personalized ending. Follow the epilogue guide.';\\n rows += '' + step + '' + { content: 'Content', conversation: 'AI conversation', decision: 'Decision', epilogue: 'Epilogue' }[b.kind] + '' + what + '';\\n });\\n return '

Your build plan

'\\n + '

The map, translated to what you actually build' + (rise ? ' (self-contained: most of it lives inside the one embed)' : ' in Storyline') + '.

'\\n + ''\\n + ''\\n + rows.replace(/

#	Block	What you build
/g, '	')\\n + '

';\\n },\\n packChanged: function() {\\n var s = this.state, self = this;\\n var r = document.getElementById('pack-rise');\\n s.packaging = r && r.checked ? 'rise' : 'storyline';\\n var lg = document.getElementById('pub-log'); if (lg) s.logResults = lg.checked;\\n var cc = document.getElementById('pub-code'); if (cc) s.completionCode = cc.value.trim().slice(0, 24);\\n var an = document.getElementById('pub-askname'); if (an) s.askName = an.checked;\\n this.save();\\n if (!s.published) { this.render(); return; }\\n // Already live: persist the packaging change to the same URL right away.\\n this.busy('pub-status', 'Saving your packaging change.');\\n this.api('/api/save', {\\n id: s.simId, editToken: s.editToken,\\n config: this.buildConfig(), answers: this.collectAnswers(), status: 'published'\\n }).then(function() {\\n if (self.needsEpiSim()) {\\n return self.api('/api/save', {\\n id: s.epiSimId || undefined, editToken: s.epiEditToken || undefined,\\n config: self.buildEpilogueConfig(), answers: { note: 'Epilogue companion of sim ' + s.simId }, status: 'published'\\n }).then(function(r2) { s.epiSimId = r2.id; s.epiEditToken = r2.editToken; self.save(); });\\n }\\n }).then(function() { self.render(); })\\n .catch(function(e) { self.fail('pub-status', e.message); });\\n },\\n rPublish: function() {\\n var s = this.state;\\n var url = s.simId ? API + '/s/' + s.simId : '';\\n var epiUrl = s.epiSimId ? API + '/s/' + s.epiSimId : '';\\n var rise = s.packaging === 'rise';\\n var h = '

Publish

';\\n\\n // Packaging + options (editable before AND after publishing)\\n h += '

How will this live in your course?

'\\n + '

'\\n + ' Storyline (web object, live mood characters, variables, course branching)'\\n + ' Export for Rise / embed anywhere (self-contained scene in one iframe: Rise 360, Thinkific, WordPress, your portfolio site)

';\\n if (rise) {\\n var warns = this.riseWarnings();\\n if (warns.length) h += '

Packaging notes.
' + warns.map(this.esc).join('
') + '

';\\n h += '

Ask the learner\\\\'s first name on the intro screen (replaces Storyline\\\\'s LearnerName)

'\\n + '

Completion code shown at the end (blank for none). Rise cannot see inside an embed; a code plus a Rise knowledge check below the embed makes the scene requireable.

';\\n }\\n h += '

Log completed runs to the results dashboard (learners are told on the intro screen)

';\\n\\n if (!s.published) {\\n h += '

Publishing gives your ' + (this.needsEpiSim() ? 'scenario TWO permanent URLs: the sim and its epilogue ending' : (this.isEpilogueOnly() ? 'epilogue a permanent URL' : 'sim a permanent URL')) + '. Editing here later updates the same URL' + (this.needsEpiSim() ? 's' : '') + ', no course changes needed.

'\\n + '

';\\n } else {\\n h += '

Your ' + (this.isEpilogueOnly() ? 'epilogue' : 'sim') + ' is live. Here is everything you need.

';\\n if (rise) {\\n h += 'Your scene URL'\\n + '

' + this.esc(url) + '

'\\n + 'The embed snippet (Rise: Multimedia, then Embed)'\\n + '

' + this.esc(this.embedSnippet(url, s.situation ? s.situation.scenarioTitle : '')) + '

'\\n + '

Embed guide

Where to paste it in Rise, Thinkific, WordPress, and the completion-code recipe.

';\\n } else {\\n h += 'Your sim URL (' + (this.isEpilogueOnly() ? 'this goes on your ENDING slide' : 'this goes in Storyline: Insert, then Web Object') + ')'\\n + '

' + this.esc(url) + '

'\\n + '

';\\n if (this.needsEpiSim() && epiUrl) {\\n h += 'Your epilogue URL (this goes on the ENDING slide as its own web object)'\\n + '

' + this.esc(epiUrl) + '

'\\n + '

';\\n }\\n h += '

Implementation guide

Your exact variables, triggers, and bridge script, prefilled for THIS sim. Print it and follow it top to bottom.

';\\n }\\n if (!this.isEpilogueOnly()) {\\n h += '

Scene Director brief

What to put AROUND the box: setting, character casting, layout, Content Library search terms.

';\\n }\\n h += '

Portfolio design rationale

Turns your Studio answers into a printable case-study page: proof you designed this, not just used a tool.

'\\n + '

'\\n + this.buildPlanHtml()\\n + '

Your edit key

'\\n + '

This browser remembers your sim automatically. Save this key somewhere safe anyway; with the sim URL plus this key you can edit from any computer (support can help you restore it).

'\\n + '

' + this.esc(s.simId) + ' / ' + this.esc(s.editToken) + (this.needsEpiSim() && s.epiSimId ? '
' + this.esc(s.epiSimId) + ' / ' + this.esc(s.epiEditToken) + ' (epilogue)' : '') + '

'\\n + '

Advanced: your config

'\\n + '

The same sim as a hand-editable config block, for the template workflow (adding phases, voice, or logging by hand).

'\\n + '

' + this.esc(JSON.stringify(this.buildConfig(), null, 1)) + '

'\\n + '

';\\n }\\n h += '

';\\n\"],\n [\" }).then(function(r) {\\n self.state.simId = r.id; self.state.editToken = r.editToken; self.state.published = true;\\n self.save(); self.render();\\n }).catch(function(e) { self.fail('pub-status', e.message); });\\n },\\n makeScene: function() {\\n\", \" }).then(function(r) {\\n self.state.simId = r.id; self.state.editToken = r.editToken; self.state.published = true;\\n self.save();\\n if (self.needsEpiSim()) {\\n return self.api('/api/save', {\\n id: self.state.epiSimId || undefined, editToken: self.state.epiEditToken || undefined,\\n config: self.buildEpilogueConfig(), answers: { note: 'Epilogue companion of sim ' + self.state.simId }, status: 'published'\\n }).then(function(r2) {\\n self.state.epiSimId = r2.id; self.state.epiEditToken = r2.editToken;\\n self.save();\\n });\\n }\\n }).then(function() { self.render(); })\\n .catch(function(e) { self.fail('pub-status', e.message); });\\n },\\n makeScene: function() {\\n\"],\n];\n",[],[655,647],"scripts","380d34ef-6a01-4b0d-85fe-990db735dc63","diag-parse-tools.ts","88ff0884-a02a-11f1-b912-1607ee4eb77e",568,["D",1787624141305],"// KEEPER (2026-08-24): parse-checks every inline for the last opened block\n const opens = (html.match(/]*\\bsrc=)[^>]*>/gi) || []).length;\n const closes = (html.match(/<\\/script>/gi) || []).length;\n if (opens !== closes) results.push(`TAG MISMATCH ${name}: ${opens} open vs ${closes} close`);\n\n const re = /]*\\bsrc=)[^>]*>([\\s\\S]*?)<\\/script>/gi;\n let m, idx = 0, any = false;\n while ((m = re.exec(html)) !== null) {\n any = true; idx++;\n const code = m[1];\n try {\n new Function(code);\n } catch (e) {\n const pos = (e.stack || \"\").match(/:(\\d+):(\\d+)/);\n let ctx = \"\";\n if (pos) {\n const ln = parseInt(pos[1], 10) - 1; // new Function adds a wrapper line\n const lines = code.split(\"\\n\");\n const bad = lines[ln - 1] ?? lines[ln] ?? \"\";\n ctx = ` | line~${ln}: ${bad.trim().slice(0, 160)}`;\n }\n results.push(`PARSE FAIL ${name} [script #${idx}]: ${e.message}${ctx}`);\n }\n }\n if (!any && opens === closes) results.push(`NO INLINE SCRIPT ${name}`);\n}\nconsole.log(results.length ? results.join(\"\\n\") : \"ALL CLEAN\");\nconsole.log(`Checked ${FILES.length} files.`);\n",[],[655,657],"09fb9764-0684-4335-aee0-f1c1b6e87f8b",133,["D",1783967292667],[613,614],[655],"5a96ee29-e7db-4baa-a078-f6973a485757","lead-magnet-uptime.ts","acdfa040-9e97-11f1-829a-1607ee4eb77e","158ae3a4-bb8b-49bf-af61-641359d0897e",667,["D",1788540156499],5,"interval","// Lead-magnet uptime monitor (2026-08-22, Jill; item 2.3 of the monitoring backlog,\n// docs/monitoring-backlog.md in jill1/search-hq + the workspace copy).\n//\n// WHY THIS EXISTS. The router serves ~41 slugs. Search HQ's cron watches its 21,\n// AIDA HQ's cron watches its 7 (plus two WordPress-embedded tools). That left the\n// 15 standalone lead magnets below watched by NOTHING: they are top-of-funnel, no\n// member is around to report a break, so a dead one costs leads silently. This is\n// their own small monitor, per the backlog's call, rather than a bolt-on to either\n// HQ's cron.\n//\n// PATTERN. Ported from the HQ monitors (backend/ops.ts in both HQ vals):\n// - TWO STRIKES: a target must fail twice, 5s apart, before it counts as down\n// (one transient blip must not send an email).\n// - ALL-CLEAR: the down set persists in blob storage, so recovery emails.\n// - HARD TIMEOUTS: every fetch capped at 10s.\n// - HOUR-BUCKET DEDUPE, but a CHANGE in what is down alerts immediately.\n// - PAGE PROBES are strict-200 with a referer (the gated slugs, e.g.\n// resume-tailor-gated and scenario-studio, 403 a bare GET; the referer below is\n// on the router's own allowlist, same door a visitor arriving on-site uses).\n// 403/404/5xx are all named failures; strict-200 makes a stale slug in the\n// lists below fail loudly on the first run instead of passing forever.\n// - API PROBES (the 8 slugs with router backends): a HEALTHY backend answers GET\n// with its own 404/405 JSON (\"Use POST /feedback.\"). Down = any 5xx, or the\n// router's literal \"Unknown API slug.\" body (slug fell out of API_BACKENDS —\n// matched on body, not status, because live and unmapped are both 404).\n//\n// KNOWN LIMIT. The 7 page-only slugs are static or call their own direct backend\n// vals from the page (e.g. portfolio-reality-check's AI readout); those direct\n// backends are not probed here. Page coverage + the 8 router backends is what this\n// monitor knows. Verified live 2026-08-22: all 15 pages answer 200, the 8 API slugs\n// answer healthy, the 7 others answer \"Unknown API slug.\" (hence excluded).\n//\n// LEGACY-HOST SCAN (2026-09-02, Jill). Val Town retired the single-dash host form\n// (jill1-.web.val.run; the platform now answers it with a 500). The Roleplay\n// Gym fragment still POSTed to one, so every send failed for members while the page\n// itself answered 200 and passed every page probe. The 8/4 backend audit missed it\n// because it only matched the jill1-- form. This scan reads every fragment named\n// in the router's ROUTES (plus main.ts itself) and flags any https://jill1-\n// host, so a leftover or reintroduced legacy URL fails loudly on the next run.\n// Content, not network, so no two-strike; a read failure is logged and skipped.\n//\n// Email goes to the val owner (Jill) via std/email. One-shot test: run this file\n// directly; when everything is healthy and nothing was down last run, it sends\n// nothing and only writes a console line.\nimport { blob } from \"https://esm.town/v/std/blob/main.ts\";\nimport { email } from \"https://esm.town/v/std/email\";\nimport { readFile } from \"https://esm.town/v/std/utils/index.ts\";\n\nconst LEGACY_HOST = /https?:\\/\\/jill1-(?!-)[a-z0-9-]+\\.web\\.val\\.run/gi;\n\nasync function legacyHostScan(): Promise {\n const found: string[] = [];\n let router: string;\n try {\n router = await readFile(\"main.ts\", import.meta.url);\n } catch (e) {\n console.log(`legacy scan: could not read main.ts (${(e as Error).message}); skipped`);\n return found;\n }\n const files = new Set();\n for (const m of router.matchAll(/file:\\s*\"([^\"]+\\.html)\"/g)) files.add(m[1]);\n const sources: [string, string][] = [[\"main.ts\", router]];\n for (const f of [...files].sort()) {\n try {\n sources.push([`apps/${f}`, await readFile(`apps/${f}`, import.meta.url)]);\n } catch (e) {\n console.log(`legacy scan: could not read apps/${f} (${(e as Error).message}); skipped`);\n }\n }\n for (const [name, text] of sources) {\n const hosts = new Set();\n for (const m of text.matchAll(LEGACY_HOST)) hosts.add(m[0].replace(/^https?:\\/\\//, \"\"));\n if (hosts.size) found.push(`${name} (legacy val.run host still in page: ${[...hosts].join(\", \")})`);\n }\n console.log(`legacy scan: ${sources.length} files checked, ${found.length} with legacy hosts`);\n return found;\n}\n\nconst BASE = \"https://lsd-tools.val.run\";\nconst REFERER = `${BASE}/`;\nconst TIMEOUT_MS = 10_000;\nconst RETRY_DELAY_MS = 5_000;\nconst KEY_DOWN = \"lead-magnet-monitor/down\";\nconst KEY_ALERT_BUCKET = \"lead-magnet-monitor/last-alert-bucket\";\n\n// The 15 standalone lead magnets (from the 2026-08-19 audit; not covered by either\n// HQ monitor). A slug removed from the router shows up as a 404 here on the first\n// run, so this list cannot drift quietly.\nconst PAGE_SLUGS = [\n \"fit-quiz\", \"portfolio-reality-check\", \"role-explorer\",\n \"portfolio-blueprint\", \"is-training-the-answer\", \"week-in-the-life-360\",\n \"followup-email-generator\", \"needs-analysis-simulator\", \"roleplay-gym\",\n \"annual-review-prep\", \"training-measurement-planner\", \"project-post-mortem\",\n \"sme-interview-planner\", \"scenario-studio\", \"resume-tailor-gated\",\n];\n\n// The subset with an API backend in the router's API_BACKENDS map (verified live\n// 2026-08-22, slug by slug). The other 7 return \"Unknown API slug.\" and are\n// excluded on purpose — probing them would be a permanent false alarm.\nconst API_SLUGS = [\n \"fit-quiz\", \"followup-email-generator\", \"needs-analysis-simulator\",\n \"annual-review-prep\", \"training-measurement-planner\", \"project-post-mortem\",\n \"sme-interview-planner\", \"scenario-studio\",\n // roleplay-gym gained an API_BACKENDS entry 2026-09-02 and was still only\n // page-probed here (2026-09-04 code review), which is the exact silent\n // failure the header of this file describes.\n \"roleplay-gym\",\n];\n\ninterface Target { url: string; label: string; kind: \"page\" | \"api\" }\n\nfunction targets(): Target[] {\n const list: Target[] = [];\n for (const s of PAGE_SLUGS) list.push({ url: `${BASE}/${s}`, label: s, kind: \"page\" });\n for (const s of API_SLUGS) list.push({ url: `${BASE}/api/${s}/`, label: `${s} backend`, kind: \"api\" });\n return list;\n}\n\nasync function probe(t: Target): Promise {\n try {\n // Backend probes POST an empty JSON body to /feedback (2026-09-04 code review).\n // The old GET never reached a proxy's origin check or its API-key check, so\n // two live breaks passed every hourly run: a proxy whose allowlist rejected\n // the router's Origin (every call from the page 403) and a proxy with no\n // ANTHROPIC_API_KEY (every call 500). The healthy answer to an empty POST is\n // a 400 \"messages required\" from the proxy's own validation.\n const isApi = t.kind === \"api\";\n const resp = await fetch(isApi ? `${t.url.replace(/\\/+$/, \"\")}/feedback` : t.url, {\n method: isApi ? \"POST\" : \"GET\", redirect: \"manual\",\n signal: AbortSignal.timeout(TIMEOUT_MS),\n headers: isApi ? { referer: REFERER, \"content-type\": \"application/json\" } : { referer: REFERER },\n body: isApi ? \"{}\" : undefined,\n });\n if (t.kind === \"api\") {\n if (resp.status >= 500) return `${t.label} (${resp.status}, backend unreachable or erroring)`;\n if (resp.status === 403) return `${t.label} (403, backend rejects the router's origin, so every call from the page fails)`;\n if (resp.status === 404) {\n try {\n const text = await resp.text();\n if (text.includes(\"Unknown API slug\")) return `${t.label} (router has no backend mapped for this slug)`;\n } catch { /* body unreadable; 404 alone is the healthy shape */ }\n }\n return null;\n }\n // Page: one correct answer. 403 = gate rejecting a legitimate referer,\n // 404 = slug gone/renamed/mistyped, 5xx = router broken. All lead-facing breaks.\n if (resp.status === 200) return null;\n const why = resp.status === 403\n ? \"403, referer gate rejecting valid visits\"\n : resp.status === 404\n ? \"404, slug missing or renamed\"\n : String(resp.status);\n return `${t.label} (${why})`;\n } catch (e) {\n const name = (e as Error).name;\n return `${t.label} (${name === \"TimeoutError\" || name === \"AbortError\" ? \"timed out\" : \"unreachable\"})`;\n }\n}\n\nexport default async function (): Promise<{ checked: number; down: string[] }> {\n const list = targets();\n const down: string[] = [];\n for (const t of list) {\n const first = await probe(t);\n if (!first) continue;\n await new Promise((r) => setTimeout(r, RETRY_DELAY_MS));\n const second = await probe(t);\n if (!second) { console.log(`flap (recovered on retry): ${t.url} — ${first}`); continue; }\n down.push(second);\n }\n // Legacy-host findings join the same down set, so they dedupe per hour and get\n // their own all-clear once the fragment is fixed, exactly like a dead probe.\n down.push(...await legacyHostScan());\n\n const prevDown: string[] = (await blob.getJSON(KEY_DOWN).catch(() => [])) ?? [];\n const labels = down.map((d) => d.replace(/ \$[^)]*\$$/, \"\"));\n\n if (!down.length) {\n if (prevDown.length) {\n await blob.setJSON(KEY_DOWN, []);\n await blob.setJSON(KEY_ALERT_BUCKET, \"\");\n await email({\n subject: \"Lead magnets: back up\",\n text: `Everything the lead-magnet uptime check watches is responding again.\\n\\nWas down:\\n${prevDown.join(\"\\n\")}\\n\\nChecked hourly from the lsd-tools cron (crons/lead-magnet-uptime.ts).`,\n });\n }\n console.log(`all ${list.length} targets healthy`);\n return { checked: list.length, down: [] };\n }\n\n await blob.setJSON(KEY_DOWN, labels);\n const bucket = new Date().toISOString().slice(0, 13);\n const changed = JSON.stringify(prevDown) !== JSON.stringify(labels);\n const lastBucket: string = (await blob.getJSON(KEY_ALERT_BUCKET).catch(() => \"\")) ?? \"\";\n if (!changed && lastBucket === bucket) return { checked: list.length, down };\n await blob.setJSON(KEY_ALERT_BUCKET, bucket);\n await email({\n subject: \"Lead magnets: something is down\",\n text: `These failed the lead-magnet uptime check twice, ${RETRY_DELAY_MS / 1000}s apart:\\n\\n${down.join(\"\\n\")}\\n\\n` +\n `These are top-of-funnel tools with no member around to report a break, so treat this as a real leads leak until confirmed otherwise.\\n\\n` +\n `Checked hourly from the lsd-tools cron (crons/lead-magnet-uptime.ts). You'll get an all-clear email when everything responds again.`,\n });\n return { checked: list.length, down };\n}\n",[],[680,670],"crons","f93cce0c-195c-4683-830d-3ff26ad1a60c",521,["D",1787450970269],[611],[680],"9668c7c4-e78c-4faa-a3cc-0127635a7dac","week-in-the-life-360.html","d3804858-8939-11f1-bbac-1607ee4eb77e","47a6bf47-1d27-4c27-af37-9f16d7745179",259,["D",1785101687956],"\n\n\n\n\nA Week in the Life of a Corporate Instructional Designer — Spend a Week with Nora\n\n\n\n\n\n

A week in the life of a corporate instructional designer

Spend a week with Nora.

A real week. The recital she leaves work for. The difficult subject-matter expert she has to coach. The sick kid on Friday. The hour of deep work that reminds her why she left the classroom. Drop in, feel what the rhythm is like, and see if it looks like the life you're trying to build.

\n \n \n

\n \n

About Nora

Nora Alvarez is 47. She has two kids: Marco (11, obsessed with soccer and Minecraft) and Zoe (8, third year of piano lessons, still occasionally overshooting the black keys). She's a single mom, divorced four years, coparents amicably enough. She spent more than twenty years teaching elementary school before leaving the classroom, spent a year retraining, and landed her first corporate ID role a year ago.

She lives in Willow Creek, a small Midwest town of about 32,000 people. Ninety minutes from the nearest airport. Two decent coffee shops, only one of which she likes. Her house is a 1940s bungalow she bought two years ago.

About the job

She's an Instructional Designer at Ridgewell Health, a regional healthcare network across parts of three states. Twelve outpatient clinics, three hospitals, about 4,000 employees. She designs training for nurses, medical assistants, and administrative staff: new system rollouts, compliance modules, onboarding, workflow changes, clinical education.

The L&D team is five people:

Angela Washington, director. Was an ID herself before moving into leadership. Married with three kids of her own.
Jeremy, junior ID, three months in.
Danielle, mid-level ID, focused on compliance and regulatory training.
Jesse, video and multimedia specialist. Quiet, brilliant editor.
Nora.

Everyone is fully remote. The team flies in three times a year. Otherwise, everything happens on Teams.

About the rhythm

Nora works a full 40-hour week. Her day starts with the 8:30 AM standup after drop-off and ends around 5:30 PM. Lunch is half an hour, give or take. School pickup at 2:55 is another break in the middle of the afternoon, not the end of her workday. Mornings are deep work at the desk in the spare bedroom she turned into an office. Afternoons move to the kitchen table, where the kids do homework across from her. Total: 8 hours worked, most days.

When something personal shifts hours out of the day (a recital, an appointment), she either makes them up on a specific evening later in the week or uses banked flex time. When a kid is sick, that's PTO or sick leave. A company benefit, not something she owes back.

That's the setup. Now spend a week with her.

\n\n\n

Nora's week as an instructional designer

Click on a day, in any order, to walk through it with Nora. Her take is one tap away the whole time.

\n\n\n

\n \n

Nora, end of day

\n\n\n

\n \n

Nora's take

\n\n

What this life changed for me

1. How I structure my day. I stopped pretending the work only counts if it happens in eight straight hours at a desk. My hours run 8:30 to 5:30, with a lunch break and a pickup break in the middle. Most days those run about 30 minutes each, but nobody is timing them. Some days lunch turns into 45 minutes or pickup runs long, and I make it up wherever it fits. The company doesn't care what shape the day takes as long as the deliverables land.

2. How life events land. A sick kid used to mean a scramble, a sub plan, and guilt for taking a day. Now it's a Slack, a laptop on the couch when I can, and PTO for the rest.

3. What my relationships look like. I see my colleagues on a screen. I see my kids after school. I have to work harder for the first, easier for the second. Both changed.

4. What the last year has brought me. The first few months were rebuilding my confidence after leaving the classroom. One year in, I'm already looking at options I never had as a teacher: part-time contract work while Marco is still at home, or a stretch of winter somewhere warmer once the kids are older. I don't have to decide any of it yet.

5. The unlearning. The classroom taught me I had to earn every minute of freedom. This job taught me the opposite. That's the biggest quiet shift, and it's still sinking in. A year in, some weeks it still catches me off guard.

\n\n

The real talk

Corporate ID lets you build a life that fits around you, and that's the real headline. You get treated like an adult, and your work gets recognized in a positive way instead of scrutinized. You own your day, life events don't have to derail your work, and the job scales in ways teaching doesn't. One module you build well can train thousands of people over years.

The learning curve: unlearning the surveillance you got used to as a teacher (the mouse-jiggling PTSD is real), figuring out how to broker feedback and coach reluctant SMEs without wearing yourself out, and getting comfortable saying \"training may not be the fix\" to people who came asking for training. Nora is a year in, and most of it already feels like her normal.

\n\n

This might not be for you if…

You need the classroom energy of being around people all day. Most of your week is heads-down solo work.
You want someone to tell you exactly what to do next. Nobody is checking in. That reads as freedom to some and freefall to others.
You'd struggle to push back on stakeholders. Saying \"training isn't the fix\" or brokering conflicting feedback is unavoidable.
You want to see the impact of your work right away. You build modules and often never watch a single person take them.

\n\n

Want a week that looks more like Nora's?

\n \n \n

The program

AIDA · Applied Instructional Design Academy

Jill's program for becoming a corporate ID. Certification, weekly support, portfolio, job.

\n \n \n

Free · weekly

Jumpstart Your Instructional Design Career

The podcast. Real answers about the transition, every week.

\n \n \n

Free · quiz

The ID Fit Quiz

A few questions about where you are now, and an honest read on what to do first.

\n \n

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n",[],[695,687],"apps","27b38dd9-9a35-4021-acc5-4288d3e05164","training-measurement-planner.html","3b2d52ee-7ed0-11f1-93e7-1607ee4eb77e",461,["D",1785812731225],25,"\n\n\n\n\nTraining Measurement Planner | LS&D\n\n\n\n\n\n\n

\n \n

Training Measurement Planner

\n\n

\n\n\n

\n\n \n \n\n \n

Level 3 Evaluation Planning Coach

Build a plan to measure whether training actually changes on-the-job behavior

\n \n

\n\n \n

\n \n \n

Press Enter to send · Shift+Enter for new line

\n\n

\n\n\n\n",[],[695,697],"3d4f370e-6ab9-4033-984c-46563acccfca","tmay-story-lab.html","c6a86dcc-7a2f-11f1-9343-1607ee4eb77e",848,["D",1789506028243],17,"\n\n\n

\n $\"Learning$ \n

Tell Me About Yourself Lab

The First 90 Seconds of Every ID Interview

\n \n

\n\n

\n\n \n

\n \n\n

Nail the first 90 seconds of your ID interview.

\"Tell me about yourself\" is the first question in almost every interview, and career changers get tripped up here. You either overshare your teaching background and lose them, or you undersell what actually makes you a strong ID candidate.

This lab helps you build a 90-second story that connects your past work, your pivot into ID, and where you're headed, so a hiring manager wants to keep asking questions.

\n\n

How it works

Answer 7 short questions, one at a time, in a conversation.
The coach drafts your 90-second narrative and hands it to a corporate L&D hiring manager.
They go back and forth behind the scenes, up to 3 reads, until it lands. If your answers are thin, you'll get a follow-up question or two.
You see one finished narrative, plus the hiring manager's take in plain English.
Change anything that's off, then copy it, save it as a PDF, or save it to your Search HQ.

\n\n

Your work is saved on this browser as you go, so if you close the tab, you can come back to the same session on the same computer.

\n\n \n

Questions

\n ▶\n

Draft

\n ▶\n

Hiring Manager

\n ▶\n

Polish

\n ▶\n

Done

\n\n

\n \n \n

Press Enter to send. Shift + Enter for a new line.

\n\n \n

\n\n\n\n\n",[],[695,706],"4baaf520-c646-4128-bd30-46163da602f1","storyline-scenario-builder.html","8d532eb6-824c-11f1-9171-1607ee4eb77e",488,["D",1785812880740],2,"\n\n

\n \n $\"AIDA\"$ \n

Storyline Scenario Builder

Plan branching scenarios before you build them

\n\n

\n\n \n

1. Setup

2. Scenario

3. Branches

4. Full Map

\n\n \n

Tell me about your project

This tool helps you plan a branching scenario with two levels of decision points and three choices at each level. You'll get a visual map and a slide-by-slide build plan for Storyline.

\n What topic is this course about?\n \n

\n What should learners be able to do after this scenario?\n \n

\n Do you have a specific situation in mind? (optional)\n \n

\n \n

\n\n \n

Your Scenario

Review and edit the scenario setup. This is the opening scene your learner will see.

\n Scene Title\n \n

\n Setting\n \n

\n Characters\n \n

\n The Challenge\n \n

\n \n \n

\n\n \n

Decision Point 1: First Choices

These are the three choices the learner sees first. Edit any of them, then generate the second level.

\n \n \n

\n\n \n

Your Scenario Map

Click any node to see its details. Edit, then export your build plan.

\n\n \n

Your scenario tree will appear here.

\n\n \n

Node Details

\n \n

\n\n

Want a decision point to be a LIVE conversation?

Instead of three scripted buttons, a decision point can be an open AI conversation: the learner talks with a character, and your course branches on how the conversation ENDS. Build that piece in the AIDA Scenario Studio, publish it, and embed its URL on that slide as a web object. This map plans the course; the Studio builds the conversation. They work together.

\n\n

\n \n \n \n

\n\n

\n\n\n",[],[695,715],"34ffa699-656f-4a25-8d41-e285f82cb929","storyboard-reviewer.html","73abc994-88b1-11f1-9389-1607ee4eb77e",566,["D",1787624092755],"\n\n\n

\n $\"AIDA$ \n

Storyboard Reviewer

Automated rubric review for your AIDA storyboard

\n\n \n

Welcome Back

\n \n \n

\n\n \n

Upload Your Storyboard

Paste your Google Doc link below. Make sure sharing is set to \"Anyone with the link can view.\"

\n Tip: This tool reviews completeness, not content quality. Your content was already approved in the design document stage. We are checking that all required storyboard elements are present and properly formatted.\n

\n Google Doc Link\n \n

\n \n

\n\n \n

Review Results

\n \n \n

\n\n

\n\n \n \n\n \n \n\n \n \n

\n\n

\n\n",[],[695,724],"d8ae20b0-efe1-408d-99a8-8182ea23367f","star-story-builder.html","c6883002-7a2f-11f1-9f47-1607ee4eb77e",["D",1789511797001],36,"\n\n\n

\n $\"Learning$ \n

STAR Story Builder

0 / 5 Stories

\n\n

\n\n \n

\n \n

Build Your Interview Stories

You can build up to 5 STAR stories. Each one gets translated into real instructional design language -- with coaching, analysis, and a cheat sheet you can take into any interview. How do you want to start?

💬

Free Build

Describe an experience from your past and your coach will shape it into a polished STAR story. You'll also see which interview questions your story answers.

\n Start with your experience\n

🎯

Question-Guided

Pick a specific interview question you want to be ready for. Your coach will give you tips on what makes a strong answer, then help you build the story.

\n Start with the question\n

\n\n \n

\n \n

Pick Your Interview Question

Choose the question you most want to nail. Your coach will walk you through exactly what a strong answer looks like for that question, then help you build your story.

\n\n

Instructional Design & Course Development

Tell me about a time you designed a learning program from scratch.→

Tell me about a time you chose a specific instructional strategy and why.→

Tell me about a time you created a blended learning solution.→

\n\n

Needs Analysis & Problem Solving

Tell me about a time you identified that training wasn't actually the solution to a performance problem.→

Tell me about a time you conducted a needs analysis before designing a solution.→

Tell me about a time you had to push back on a request because the data didn't support it.→

\n\n

Stakeholder & SME Collaboration

Tell me about a time you worked with a difficult subject matter expert.→

Tell me about a time you had to manage conflicting feedback from multiple stakeholders.→

Tell me about a time you had to influence a stakeholder who didn't see the value of training.→

\n\n

Project Management

Tell me about a time you managed an ID project with a tight deadline.→

Tell me about a time you juggled multiple projects at the same time.→

Tell me about a time a project scope changed mid-development and how you handled it.→

Tell me about a time you had to deliver with limited resources or budget.→

\n\n

Facilitation & Delivery

Tell me about a time you facilitated a training session that didn't go as planned.→

\n\n

Evaluation & Measurement

Tell me about a time you measured whether your training actually worked.→

\n\n

Collaboration & Communication

Tell me about a time you worked cross-functionally with teams outside of L&D.→

Tell me about a time you had a conflict with a colleague and how you resolved it.→

Tell me about a time you had to communicate a setback or missed deadline to a stakeholder.→

\n\n

Adaptability & Growth

Tell me about a time you received critical feedback on your work and what you did with it.→

Tell me about a time you failed at something and what you learned from it.→

\n\n

AI & Modern Practice

Tell me about a time you used AI to solve a problem or work more efficiently.→

\n\n \n \n\n

\n\n\n\n\n\n\n\n",[],[695,732],"dbae7119-7b64-473a-93b4-3938f52dfdd1","speak-corporate.html","72bf0dfc-7a2e-11f1-a80a-1607ee4eb77e",908,["D",1789508413513],29,"\n\n\n\n\nSpeak Corporate | Learning Strategy & Design\n\n\n\n\n\n\n\n

\n $\"Learning$ \n

Speak Corporate

Your corporate communication training tool

\n\n

Learn the language before you're in the room

Corporate has its own vocabulary and its own way of writing emails. This tool covers both: a searchable glossary of terms you'll hear in meetings and interviews, plus email scenarios that teach you to read between the lines and respond like you belong.

HOW THIS WORKS

Glossary: Search and browse corporate terms with definitions and real usage examples

E-mail Communication: 6 real-world email scenarios where you pick the best response and get scored

Time: Browse at your own pace, or work through all 6 email scenarios in about 10 minutes

\n\n

\n \n \n

\n\n

\n\n\n

Corporate Glossary

Terms and phrases you'll hear in meetings, emails, and interviews. Know what they mean and when to use them.

\n \n

\n\n\n

E-mail Communication

Real email situations you'll hit in the corporate world. Pick the right response. See what separates the corporate mindset from the teacher mindset.

\n\n

\n Your Progress\n 0 / 6 complete\n

Score: 0 correct

\n\n

\n \n

What to do next

You've worked through all 6 email scenarios. Here's how to keep building on this:

Review the Glossary tab to reinforce the terms you saw in context
Try the scenarios again to practice choosing the right tone faster
Use these patterns in your real interview prep and email drafts

\n \n \n

\n\n

\n\n\n\n\n\n",[],[695,740],"6b043768-ca9a-4335-8f3d-d6c715eaddee","sme-interview-planner.html","e14b89ea-7ee2-11f1-a968-1607ee4eb77e",463,["D",1785812737770],"\n\n

\n $\"LS&D$ \n

SME Interview Planner

\n\n

\n ⚠\n Working on a real project? Make sure you have your employer's approval before sharing confidential details here.\n \n

\n\n

SME Interview Prep Coach

Build a tailored question list and meeting agenda for your next SME interview

\n \n

\n\n

LS&D

\n \n \n \n

\n\n

\n \n \n

\n\n",[],[695,749],"c6ff2e3d-46e8-45c5-a4c8-1bdc5a4e2db5","scenario-studio.html","cae2491a-8247-11f1-974b-1607ee4eb77e",491,["D",1785813001223],"\n\n

\n \n $\"AIDA\"$ \n

Scenario Studio

Design an AI conversation sim for your course. You make the decisions; the Studio does the typing.

\n\n

\n\n\n",[],[695,757],"38485a2b-5dd2-4385-b6df-27a34358e130","salary-negotiation-assistant.html","80e08b14-7a2d-11f1-90ec-1607ee4eb77e",917,["D",1789508817077],13,"\n\n\n

\n $\"Learning$ \n

Salary Negotiation Assistant

\n\n

Get the exact words for your salary negotiation

Congrats on your offer! Get the words for your counter offer and come back if you need to further negotiate.

This builds you a personalized negotiation script based on your actual offer details. You'll get word-for-word language for your counter, plus scripts for benefits negotiation if the salary is firm. Come back after each round if you need to negotiate further.

HOW THIS WORKS

What you'll get: A ready-to-send counter offer script, plus benefit negotiation language if needed

What to do first: Enter your offer details (salary, title, company)

Time: About 2 minutes to fill in your details, then instant scripts

Built for W2 corporate offers.

\n\n\n\n",[],[695,765],"dbb97425-b4de-4ed2-b1c8-256cdddf907c","roleplay-gym.html","aca4bf2a-7e62-11f1-97d6-1607ee4eb77e",637,["D",1788381433435],11,"\n\n\n\n\n

\n \n \n\n \n

\n \n\n \n\n

Coaching Feedback

\n \n

What happened

The better move

Now YOU decide

\n \n

\n\n

Scenario Complete!

\n \n

\n\n

SME is thinking...

\n\n\n",[],[695,774],"a6478b73-88a8-4289-a209-039171ec3341","resume-tailor.html","e71a947e-7a2d-11f1-9991-1607ee4eb77e",858,["D",1789506478442],30,"\n\n\n\n

\n $\"Learning$ \n

Resume Tailor

\n\n

Tailor your resume to this job

You've already built a strong ID resume. This tool tailors it to one specific posting. Paste your resume and the job description, and get the keyword gaps plus the top three changes to make before you apply. No full overhaul. Just the targeted tweaks that matter for this role.

\n\n \n

Step 1

Your Resume

Use this once your resume is already ID-ready. It gives you targeted tweaks for one posting, checked against current 2026 ATS guidance. For a full resume overhaul, use the Resume Revamp Assistant instead.

\n \n \n

\n \n

\n 📄\n

Click to upload your resume PDF

or drag and drop here. PDF only, up to 4MB.
Tip: save from Word as PDF for best results. Avoid Canva exports (they save as images that ATS cannot read).

\n 📄\n

resume.pdf

0 KB

\n \n

Step 2

Job Description

\n \n

Please provide your resume and the job description before submitting.

\n \n

\n\n \n

Reading your resume...

Hang tight. This takes about 20-30 seconds.

\n\n \n

\n\n

\n\n\n

\n\n\n\n\n\n\n",[],[695,783],"01a20feb-4ed8-42f9-965b-4c3919409456","resume-tailor-gated.html","2afcb504-7d95-11f1-bdde-1607ee4eb77e",863,["D",1789506557537],23,"\n\n\n\n

\n $\"Learning$ \n

ID Job Posting Resume Translator

\n\n

Tailor your resume to any ID job posting

You've already built a strong ID resume. This tool tailors it to one specific ID job posting. Paste your resume and the posting, and get the keyword gaps plus the top three changes to make before you apply. No full overhaul. Just the targeted tweaks that matter for this role.

\n\n \n

\n What You'll Get\n

The exact keyword gaps between your resume and this posting

Your top 3 highest-impact changes to make before you apply

A follow-up chat to ask questions about your feedback

A printable report you can reference while you edit

\n Get Your Free Resume Analysis\n \n \n

Please enter your name and a valid email address.

\n \n No spam. You'll get instant access and occasional career tips you can unsubscribe from anytime.\n

\n\n \n \n\n \n

Reading your resume...

Hang tight. This takes about 20-30 seconds.

\n\n \n

\n\n

\n\n\n

\n\n\n\n",[],[695,792],"252c3df4-786d-4183-9092-74d97aa902f2","resume-revamp-assistant.html","c53824b0-7a2e-11f1-bf01-1607ee4eb77e",853,["D",1789506326405],34,"\n\n\n\n

\n $\"Learning$ \n

Resume Revamp Assistant

\n\n

Revamp your resume for corporate ID

The one-time foundation review for career changers breaking into Instructional Design. Paste your resume and get a full, ID-focused review measured against what corporate instructional designer roles actually look for. Do this once to get your resume ID-ready, then use the Resume Tailor to tweak it for each job you apply to.

\n\n \n

\n \n

Step 1

Your Resume

This is the big one-time overhaul. Your resume is reviewed against a representative corporate Instructional Designer role and current 2026 ATS guidance. Applying to a specific job? Use the Resume Tailor instead.

\n \n \n

\n \n

\n 📄\n

Click to upload your resume PDF

or drag and drop here. PDF only, up to 4MB.
Tip: save from Word as PDF for best results. Avoid Canva exports (they save as images that ATS cannot read).

\n 📄\n

resume.pdf

0 KB

\n \n

Please provide your resume before submitting.

\n \n

\n\n \n

Reading your resume...

Hang tight. This takes about 20-30 seconds.

\n\n \n

\n\n

\n\n\n\n\n

\n\n\n\n\n\n\n\n",[],[695,801],"af8cfffc-7593-43e0-92e0-40f0af038ae1","project-scope-estimator.html","3aaeed8e-7f19-11f1-a0fd-1607ee4eb77e",156,["D",1783988176054],"\n\n

\n $\"LS&D\"$ \n

E-Learning Project Scope Estimator

Estimate development hours for your e-learning project

\n\n

\n Step 1\n

Course Length

Select the finished runtime of the course, in minutes.

\n Or enter a custom length (minutes):\n \n

\n\n

\n Step 2\n

Interactivity Level

How much of the course is click-through versus built interaction.

\n\n

\n Step 3\n

Content Readiness

How ready is the source content going into design.

\n\n

\n Step 4\n

Multimedia Requirements

What visuals the course needs beyond basic screens.

\n\n

\n Step 5\n

Audio / Narration

How the course will be voiced, if at all.

\n\n

\n Step 6\n

Review Cycles

How many rounds of stakeholder review to plan for.

\n\n

\n Step 7\n

SME Availability

How quickly your subject matter expert responds.

\n\n

\n \n

Takes seconds. You can change your answers and recalculate anytime.

\n\n \n\n

\n\n",[],[695,810],"b1691527-38d8-433d-b708-7f94cb6ca8f9","project-post-mortem.html","f5f3077c-7ed5-11f1-963c-1607ee4eb77e",465,["D",1785812744271],"\n\n\n\n\nProject Post-Mortem | Learning Strategy & Design\n\n\n\n\n

\n\n \n\n

\n\n

How It Works

1. Project OverviewWhat the project was, who it was for, and what problem it needed to solve.
2. What Went WellThe wins, the good calls, and the skills that actually worked.
3. What Didn't Go WellThe friction points, honestly, with no judgment attached.
4. Lessons LearnedThe patterns underneath both lists, and what they mean going forward.
5. Action Items & ReportA short plan for next time, plus a saved report you can keep.

\n\n \n\n \n\n \n\n \n\n

\n\n

\n\n \n\n

\n\n

\n Thinking this through, give it a few seconds (can take up to 30 seconds)...\n

\n\n

\n \n

\n\n

\n \n \n

\n\n

\n\n\n\n\n",[],[695,818],"ab3cefbb-3e44-4b62-9ccc-dfc0e3a4f6b2","professional-summary-coach.html","db22f13e-7a2d-11f1-a4f7-1607ee4eb77e",821,["D",1789505203177],14,"\n\n\n

\n $\"Learning$ \n

Resume Professional Summary Coach

For people moving into corporate instructional design

\n\n

\n\n \n

Build the summary at the top of your resume, the right way

The professional summary is the first thing a hiring manager reads. Most career-change advice tells you to open with \"former teacher transitioning into...\" That's exactly what gets you screened out. This coach helps you position yourself as a capable learning professional whose experience translates, without announcing the pivot in your prime real estate.

\n\n

A coach that keeps the words yours

This tool does not write your summary for you. You'll get building blocks to assemble yourself, or diagnostic feedback on a draft you already have.

Why: a summary that reads like it was generated gets flagged, by both applicant tracking systems and humans. The words have to be yours. The coach makes sure whatever you write positions you as competent and keeps the confessional stuff out.

\n\n

Give your target role, paste your resume, and answer a few quick questions.
No draft yet? Get building blocks for two angles to assemble your own summary from.
Already have a draft? Get diagnostic feedback: what's working, what to cut, what's missing.
Write your summary yourself, in your own words, using what the coach gives you.

\n\n

Heads up. Your answers save to this browser so you can come back and finish later. Same computer, same browser. This tool works on the live site at learningstrategyanddesign.com.

\n\n

\n \n \n

\n\n \n

About you

The more specific you are, the more specific your coaching will be. Paste your real resume text in full. A summary gives the coach less to work with.

\n\n \n

Do you already have a summary written?

This decides whether the coach gives you building blocks or feedback on your draft.

\n No, I'm starting from scratch. Give me building blocks to write my own.\n Yes, I have a draft. Give me feedback on what I wrote.\n

\n\n \n

What job title are you targeting?

The exact title you're applying for. The coach mirrors it where it fits.

\n \n

\n\n \n

Paste your full resume

Work history, education, certifications, skills. The coach only works from what's actually here, it never invents experience you don't have.

\n \n

\n\n \n

Your instructional design certification

If you have one or are working toward one. This is separate from whether you want it in the summary.

\n Completed\n In progress\n None\n

\n Is this the Applied Instructional Design Academy (AIDA)?\n

\n Yes, it's AIDA\n No, another program\n

\n How many months did it take? (optional, adds specificity)\n \n

\n\n \n

Want a certification line in your summary?

Your call. The coach never forces it in, even if you have one.

\n Yes, include it\n No, leave it out\n

\n\n \n

What tone are you going for?

Shape the voice to the industry you're targeting.

\n Direct and confident
Matter-of-fact (default)\n Warm and human
Softer word choice\n Formal and polished
Fuller sentences\n

\n\n \n

Anything you want to lead with? (optional)

One or two lines on what matters most to you here. Skip it if you're not sure.

\n \n

\n\n \n

Paste your current draft summary

The exact summary you've written so far. The coach reacts to this.

\n \n

\n\n \n\n

\n \n \n

\n\n \n

Your coaching Round 1 of 3

This is scaffolding to build from. The finished summary is yours to write, in your own words.

\n\n \n\n

\n\n \n\n \n\n \n

\n\n

\n\n\n\n\n\n\n\n",[],[695,826],"d6759b4f-8a13-4d81-8094-01a9583a8b85","portfolio-writeup-pitch-coach.html","a7a432d2-7a2d-11f1-bd85-1607ee4eb77e",834,["D",1789505535012],16,"\n\n\n

\n $\"Learning$ \n

Portfolio Write-Up and Pitch Coach

\n\n

\n \n \n \n \n

\n\n

\n\n \n

Turn your portfolio sample into a hireable portfolio piece

You finished your sample. Now you need two things that get you interviews: a write-up on your portfolio site and a polished verbal pitch for when an interviewer says \"walk me through this.\"

\n\n

Who's giving you feedback

Throughout this tool, you'll get feedback from the perspective of an experienced hiring manager who hires Instructional Designers. That means they know ID language, they know what good design thinking sounds like, and they know what hiring managers actually look for in portfolio write-ups and interviews. They won't flag ID jargon (that's expected). They will flag teacher-speak, vague answers, missing rationale, and anything that doesn't sound like a working ID.

\n\n

Create your write-up. Nine sections, guided. You'll paste in work you already did (audience, problem, solution) and create fresh content for Highlights, Process, AI Use, and Evaluation with hiring manager feedback.
Practice your pitch. Five common interview questions about your sample. Speak your answer or type it. Get hiring manager critique on each one.
Save your work. Print or save the write-up to PDF. Copy your polished pitches into your interview prep doc.

\n\n

\n \n

\n\n \n

Tools Used

List the tools you used to build your sample. Keep it factual and comma-separated.

\n Your tools\n \n

\n\n \n

Audience

Pull this from your content map. Paste in the audience you defined when you planned your sample.

You already wrote this. No new thinking required. Go to your content map and copy the audience description into the field below.

\n Your audience\n \n

\n\n \n

Problem

The business problem your training solves. Pull this from your content map too.

Copy the problem statement straight from your content map. This is the \"why this training matters\" part. Hiring managers care about this a lot.

\n The problem\n \n

\n\n \n

Solution

The goal or measurable outcome of your training. From your content map.

This is the goal statement, ideally with a measurable target (reduce errors by X percent, increase compliance by Y, etc.). Paste it from your content map.

\n Your solution\n \n

\n\n \n

Highlights

The design moves you made. This is where you show the ID thinking behind the building.

What to include: the strategies you applied (scenario-based, chunking, spaced practice), any standout interactions in your build, and specific moves you made to enhance the learning experience for your learners.

\n \n

Example highlights (retail associate training)

Applied several design strategies to engage learners:

A branching scenario simulating a real customer complaint conversation, with different response paths depending on the choice the learner makes
Chunked the content into five-minute modules with logical sequencing
Knowledge checks with targeted feedback after every section
A downloadable job aid for quick reference during a shift

Interactions used: drag-and-drop sorting, click-to-reveal product details, the branching customer scenario, marker hotspots on a product display image, tabbed FAQ, slider for pricing tiers.

Use this as a structural reference. Create yours about your actual sample.

\n Your highlights (draft)\n \n

\n \n

Hiring manager feedback REVIEW

\n\n \n

Process

Walk through how you approached the project from analysis to delivery. Show the ID thinking behind what you built.

What to include: the analysis you would do (or did) before building, design document and storyboard work, the development tool, and the final deliverable format.

\n \n

Example process (retail associate training)

Before development, a needs analysis would be conducted with store managers and tenured associates to confirm training was the right solution and not a coaching or process issue. A scoping meeting with subject matter experts and operations leadership would define the scope and sequence and set clear, measurable learning objectives. A design document captured the blueprint, and a storyboard mapped out every interaction before development started.

During development, the storyboard was built out in Articulate Storyline with all approved interactions, voiceover, and assessments. The deliverable to the client was a SCORM-compliant package ready to load into their LMS.

Yours will look different depending on your actual sample. Use this for structure.

\n Your process (draft)\n \n

\n \n

Hiring manager feedback REVIEW

\n\n \n

AI Use

Explain if and how you used AI at any point while creating this sample. Being upfront about this is a strength. If you didn't use AI at all, just say so.

What to include: where in the process you used AI (research, drafting, storyboarding, script writing, images, etc.), what you asked it to do, and what you changed or added yourself. If you didn't use AI anywhere in the process, one sentence saying that is enough.

\n \n

Example AI use (retail associate training)

Used ChatGPT to brainstorm realistic customer complaint scenarios for the branching interaction, then rewrote the dialogue myself to match the tone and reading level of the audience. Used Claude to tighten the wording on knowledge-check feedback so it sounded encouraging rather than clinical. Built the storyboard, design document, and all final content myself.

If you didn't use AI, write something like: \"I didn't use AI for this sample. All research, writing, and design decisions were mine.\" Either way, this section gets used.

\n Your AI use (draft)\n \n

\n \n

Hiring manager feedback REVIEW

\n\n \n

Evaluation

How you would measure whether the training actually worked. This is where most career changers stop short and lose hiring managers.

What to include: Kirkpatrick levels if you used them (Level 2 is knowledge checks, Level 3 is on-the-job behavior change), how you'd collect the data, and who'd review it.

\n \n

Example evaluation (retail associate training)

Kirkpatrick Level 2 is measured throughout the course with scenario-based knowledge checks and a final pass-fail assessment that mirrors situations associates face on the floor. Learners must pass the final to complete the course.

Kirkpatrick Level 3 is measured on the job. Floor managers track behavior using a 60-day observation checklist, capturing whether associates apply the trained skills in real customer interactions. Results are reviewed monthly with the L&D team and used to identify whether additional support or refresher content is needed.

If you didn't deploy to real learners, write this as \"would be measured by.\" Hiring managers know it's a portfolio sample.

\n Your evaluation (draft)\n \n

\n \n

Hiring manager feedback REVIEW

\n\n \n

Additional Deliverables

Link the supporting documents from your sample so hiring managers can see the depth of your work.

No writing needed here. On your portfolio page, add a section called Additional Deliverables with links to each of the supporting documents below. Make sure each link is set to \"Anyone with the link can view.\"

Sections to link:

Design Document
Storyboard
Job Aid
Voiceover Script

\n\n

\n \n \n

\n\n

\n\n \n

\n\n

Practice your pitch out loud

Five questions hiring managers actually ask about your portfolio sample. For each one, you'll get a frame, you'll speak (or type) your answer, and you'll get hiring manager feedback. Aim for 60 to 90 seconds per answer.

Voice input uses your browser's built-in speech recognition. Works best in Chrome and Edge. If voice doesn't work for you, just type your answer.

\n\n

\n \n \n

\n\n

\n\n \n

\n\n

Write-Up Preview

\n\n

Save your work

Open a printable version of your write-up. From the print dialog you can choose \"Save as PDF\" to download a copy, or print it directly.

\n \n \n

Your draft is saved in your browser. To pick up where you left off, come back to this same page on the same computer and browser. Clearing your browser data will erase the draft.

\n \n

\n\n

\n\n\n\n\n\n\n\n",[],[695,835],"cdd7a6bf-3ef4-40ce-9500-154fc5f77391","portfolio-topic-generator.html","75d28cd0-7d94-11f1-b7f0-1607ee4eb77e",468,["D",1785812774228],7,"\n\n

\n\n

\n $\"Learning$ \n

Turn Any Idea Into a
Corporate Training Topic

Answer a couple of quick questions and we'll generate real, portfolio-worthy training ideas built around your interests.

\n\n

\n\n \n

\n Get Your Free Portfolio Topic Ideas\n Enter your name and email below to unlock the generator. We'll send you a copy of your results, too.\n\n

\n First Name\n \n

\n\n

\n Email\n \n

\n\n

Please enter your first name and email to continue.

\n \n

\n\n \n

\n Step 1 of 2\n Tell us a little about you\n We'll use your interests and ideas to generate corporate training topics that are actually yours.\n\n

\n What are you into outside of work?\n Or what idea do you have that you would like to expand on?\n \n Separate with commas. The more specific, the better.\n

\n\n

\n What type of portfolio sample are you building?\n

\n \n eLearning Module\n \n Job Aid\n \n Instructor-Led Training\n \n Virtual ILT\n \n Microlearning Video\n

\n Your brief will include format-specific guidance on exactly what to build.\n

\n\n

Please enter at least one interest or idea before continuing.

\n \n

\n\n \n

\n Step 2 of 2\n Here are your corporate training ideas\n Each one connects YOUR interests and ideas to a real business context. Pick the one that excites you most and we'll build a full project brief around it.\n\n

\n Connecting your ideas to real corporate contexts. This can take up to 30 seconds...\n

\n\n

Please pick one idea to continue.

\n\n

\n \n \n \n

\n\n \n

\n Your Portfolio Project Brief\n

\n \n Save this. This is your starting point. Copy it into a doc and build from here.\n\n

\n Building your full project brief. This can take up to 30 seconds...\n

\n\n \n\n

\n \n \n

\n\n \n\n \n

\n\n

\n\n",[],[695,844],"deae3219-5f0a-4b12-962f-2690b13800c1","portfolio-reality-check.html","f0e0a986-7a2c-11f1-92d7-1607ee4eb77e",212,["D",1784418505743],4,"\n\n

\n $\"Learning$ \n

Portfolio Score Card

Find out if your portfolio would survive a hiring manager's first look

\n\n",[],[695,853],"75009fbc-eb47-4340-be84-db3f649e508b","portfolio-interview-simulator.html","d4e3979c-7a2d-11f1-a884-1607ee4eb77e",838,["D",1789505659940],8,"\n\n\n

\n $\"Learning$ \n

Portfolio Interview Simulator

\n\n

Mock Interview

Practice defending one portfolio piece before a real hiring manager does.

Pick one eLearning module from your portfolio. Answer a few questions about it so the interviewer has context. Then get grilled with the questions ID hiring managers actually ask. When you're done, you'll get feedback on how you presented your work and where to tighten up.

\n\n

How this works

Fill out a short intake about one Storyline or Rise sample (about 5 minutes)
Answer 8 interview questions in a chat format (about 15 to 20 minutes)
Get a feedback report with a scorecard and 3 specific improvements
Save your report as a PDF to review later

\n\n

\n Heads up: the interviewer plays fair but pointed, the way real hiring managers do. Expect some pushback. That's the point. The more honest you are in the intake, the more useful the practice.\n

\n\n

\n \n

\n\n

Step 1 of 3

Tell the interviewer about your piece.

Answer honestly. The interviewer will use these answers to ask sharp, specific questions. Vague answers here mean generic questions later.

\n\n

The piece

Quick facts about the sample.

\n\n

\n What's this piece called?\n \n

\n\n

\n Tool used\n \n

\n Length (minutes)\n \n

\n Format\n \n

\n\n

The business context

This is where interviews get real. Weak business context is the fastest way to lose an interview.

\n\n

\n Who's the audience? Role, seniority, industry.\n

e.g., \"New account executives at a B2B SaaS company, 0 to 6 months on the job\"

\n \n

\n\n

\n What business problem was this designed to solve?\n

Not the learning objective, the business problem. Ramp time? Compliance risk? Rework? Missed sales? Errors? What was hurting the business?

\n \n

\n\n

\n Was this a real project or portfolio-only?\n

\n Real work project\n Real client project\n Portfolio-only (made up)\n

\n\n

\n How did (or would) you measure whether this worked?\n

Real measures: reduced ramp time, higher pass rate, fewer support tickets, better test scores, decreased errors. If you're guessing, say what you'd measure and how.

\n \n

\n\n

Design choices

The interviewer will push hardest on the WHY. Be ready.

\n\n

\n Learning objectives (2 to 4)\n

Action verbs. What learners can do by the end.

\n \n

\n\n

\n Why this format? Why eLearning instead of a job aid, video, ILT, or coaching?\n \n

\n\n

\n What are 2 to 3 design choices you're most proud of or most want to talk about?\n

Interactions, scenario branches, layouts, navigation choices, visual design decisions. Be specific.

\n \n

\n\n

Process

Hiring managers care as much about how you work as what you built.

\n\n

\n How did you decide training was the right solution?\n

What did needs analysis look like? If this was portfolio-only, walk through what you'd have done.

\n \n

\n\n

\n How did you work with SMEs (or simulate that for a portfolio piece)?\n \n

\n\n

\n If you rebuilt this today, what's ONE thing you'd change?\n \n

\n\n

\n \n \n

\n\n

Question 1 of 8

\n\n

\n \n

\n Aim for 2 to 4 sentences. Specifics beat sweeping claims.\n \n

\n\n

Your session is saved as you go. Same computer and browser to come back.

\n\n

Your feedback report

Here's how you did.

An honest read on how you presented your work. The interviewer's job is to find the weak spots, so if some of this stings, that's the tool doing its job.

\n\n

Scorecard

\n\n

3 things to sharpen

\n\n

Overall

\n\n

\n \n \n

\n\n

The report opens in a new tab. If it doesn't, allow popups from this page and try again.

\n\n\n\n\n\n\n\n",[],[695,862],"507cb2d3-3ff7-44db-8748-4677f7b45478","portfolio-blueprint.html","b8ba839a-7a2e-11f1-9080-1607ee4eb77e",665,["D",1788540004767],"\n\n

\n\n \n

\n $\"Learning$ \n

The Corporate ID Portfolio Blueprint

\n\n

\n\n \n

1Start Here

Start here.

So, you're building your first ID portfolio and not sure exactly what needs to be in it?

If you want a corporate instructional design job, you need a portfolio. It's the first thing recruiters look at, and if it's missing or has the wrong things in it, you don't get the interview. I will be honest. That's how it works.

Most people building their first portfolio don't know what to include, put in the wrong things, or underestimate how much goes into each piece.

This tool walks you through all of it. What has to be in your portfolio. How to plan the build across 90 days. What each piece needs to look like to land you the job. Plus two downloadable templates you can use as you go.

A few things to know before you start

This is built for corporate ID. Not K-12. Not higher ed. Corporate learning, healthcare training, government and non-profit L&D. That world.
Work through it in order. Each section builds on the last.
You'll build a 90-day plan you can save and come back to.
The templates and checklist are yours to keep.

Ready? Let's start with what good actually looks like.

See what good looks like →

\n\n \n

2Examples

Before you build, see what you're building toward.

The fastest way to figure out what a strong ID portfolio looks like is to see one. Or a bunch of them.

Look at the portfolios of people who've already landed corporate ID jobs. Notice what kinds of samples they have. How they organized the site. What tools they used. What they wrote about themselves. What they left out.

Where to look

We have a website full of portfolios our students built. You'll see actual Rise samples, Storyline projects, design documents, storyboards, and job aids. All from real people who used these to get hired.

Browse student portfolios →

What to notice as you're looking

Variety. A strong portfolio has different types of samples, not four versions of the same thing.
Polish. The pieces look finished. No placeholders, no half-built samples.
Adult, professional topics. Not education-related. Not personal hobbies.
A clear \"about\" or bio that reads like a competent professional wrote it.

Once you've had a look, come back here. Next up: exactly what needs to be in yours.

See what needs to be in your portfolio →

\n\n \n

3Portfolio Sample Overview

What has to be in your portfolio before you start applying.

Here's the minimum you need before you apply for corporate ID jobs. If any of these are missing, you're going to struggle to get an interview. I will be honest. Probably won't get one. These pieces are non-negotiable.

Required (before you apply)

1 Storyline sample
1 Rise sample
1 design document
1 storyboard
1 job aid

Nice to have (add after you're hired, or during the search if you have time)

A second Storyline sample. Shows variety, especially if the second one is an advanced interaction or microlearning.
An AI-related sample that shows you can use AI tools in the ID workflow.
Vyond video (if you take the elective badge)
Camtasia video (if you take the elective badge)
vILT slide deck and facilitator guide (if you take the elective badge)
Graphic design samples, in their own category, kept separate from your ID work
Real work samples from a previous job, scrubbed of the company name and any proprietary info, and only if you have permission

What NOT to include

This is where a lot of first portfolios go sideways. Do not put any of this in your portfolio:

K-12 or higher ed content. Not even PD you built for other teachers.
Personal hobbies or topics that aren't work-relevant.
Anything controversial. Politics, religion, hot-button social issues.
Photography as a separate category.
Placeholders. An empty spot makes the whole portfolio look unfinished.

Now that you know what needs to be in it, here's how to approach the build without trying to do everything at once.

How to approach the build →

\n\n \n

4How To Approach It

How to approach it without doing it all at once.

A full corporate portfolio is more than you can build in one stretch, so don't try. Think of this as your first 90 days. It won't get you all the way to the finish line, but it'll get you a real start, and a real start is what most people never manage.

Pick one of these two starting points, then work top to bottom. Give it 10 to 12 hours a week if you can. Less is okay, it just moves slower. What matters is that you protect the time and keep going.

\n\n

Starting point 1

Build your Storyline sample

The most demanding piece, and demanding enough to be its own project. If Storyline is the thing scaring you, start here and go in this order:

Plan and create your content map. Your planning document. Map out the topic, goal and business problem, audience, objectives, content, and sequence before you build. Grab the content map template from the resources below.
Learn beginning Storyline. Get comfortable with the basics of the tool first. You can't design for software you don't know yet.
Create your first draft. Get a rough version of the course out of your head and built in the tool.
Learn advanced Storyline. Pick up the advanced interactions and features that make a sample stand out.
Iterate, polish, QA, and publish. Refine it, run the checklist, then get it live with a short write-up of your process.

\n\n

Starting point 2

Build the other four pieces

Your Rise sample, design document, storyboard, and job aid. Four lighter pieces you can move through faster, then come back for Storyline. Work in this order:

Rise sample. Plan it with a content map the same way, then build it in the Rise free trial.
Design document. Build it after your sample, based on the same course. It's a pared-down version of your content map, in the format corporate teams actually use. Template below.
Storyboard. Also based on the sample you built, created after you know the tool. A clean, screen-by-screen map a reviewer can follow.
Job aid. A quick, polished win. One strong corporate job aid.

\n\n

Map it to your own calendar. Put these steps against your real weeks. Block out vacations and busy stretches up front so you're planning around real life, not pretending it away.

\n\n \n

Get the full build guide

Enter your name and email to unlock the standards for every piece, plus a printable portfolio checklist and the templates you'll need. Yours to save and come back to.

\n \n \n

\n\n \n

You're in. The full build guide is unlocked below. Grab your printable checklist to keep the whole build in one place, then work through each piece.

\n \n See how to build each piece →\n

\n\n \n

5Build Each Piece

How to build each piece to a professional standard.

Five required pieces, five sets of standards. Tap through each one. This is where you'll see exactly what separates a portfolio that gets interviews from one that gets skipped.

\n\n

Rise

Storyline

Design Doc

Storyboard

Job Aid

\n\n \n

Building your Rise sample.

Rise is where a lot of career changers start with authoring tools because it's the more approachable of the two. Don't take that to mean easy. A strong Rise sample takes real planning and real thought before you ever open the software.

Here are the 9 steps to plan your Rise sample before you build. Work through these in order.

Planning your Rise sample

Choose your topic. Corporate topic, adult audience, work-relevant. Not education-related. Not controversial. Not a personal hobby.
Define your goal and business problem. What problem does this training solve for the business? What's the outcome?
Define your audience. Who is this for? What's their role, their context, their level?
Identify the actions needed to meet the goal. What does the learner have to be able to do by the end?
Write learning objectives. Action verbs, measurable, aligned to the actions.
Brainstorm and analyze source content. What do you already have or know? What do you need to research?
Chunk and sequence your content. Break it into logical groups. Order it so cognitive load stays manageable.
Create the performance-based assessment. How will you check that the learner can do the thing?
Create your content map. The full blueprint of the module before you touch Rise. Use the content map template in the resources below.

Once your plan is solid, then you open Rise.

What a strong Rise sample includes

A clear topic that fits corporate ID
Learning objectives you can actually measure
Interactive elements (not just a text scroll with a quiz at the end)
A knowledge check or performance-based assessment
Clean visual design that uses Rise's built-in style options well
A recognizable corporate use case (not a hobby, not a personal interest)

Where people get tripped up: Most first-time builders skip straight to step 9 (the content map) or worse, skip straight to Rise itself. Then they build something that looks okay on the surface but doesn't teach anyone anything. Recruiters spot that immediately. The planning steps aren't optional. They're how you build something that shows you actually know what you're doing.

If working through those 9 steps on your own is more than you want to figure out solo, the 30-Day Rise Sprint walks you through building your Rise sample with support. Same process, with guidance and feedback so you don't get stuck.

\n \n

See the Rise Sprint →

\n\n \n

Building your Storyline sample.

Storyline is where corporate IDs prove they can build the more complex, custom eLearning that companies actually pay for. It's PowerPoint on steroids, and it takes more skill to build well than Rise does.

The planning process is the same 9 steps as Rise (see the Rise tab). Same discipline: plan the whole thing before you open Storyline. Skipping the planning is the fastest way to build a Storyline sample that looks impressive on the surface and falls apart when a hiring manager clicks through it.

What a strong Storyline sample includes

Custom interactions (not just Rise-style block templates rebuilt in Storyline)
At least one advanced interaction: drag-and-drop, branching scenario, meaningful click-to-reveal, or a simulation
A knowledge check or performance-based assessment
Custom design (not the default template)
Voice-over or captions if audio is used. Accessibility is expected in corporate.

Where people get tripped up

Building something too simple. If your Storyline sample could have been done in Rise, you're missing the point of Storyline.
Building something too complicated. A branching scenario that goes 30 levels deep and never resolves isn't impressive, it's confusing.
Poor design. Clip art, default templates, mismatched fonts. This piece needs to look like something a company would actually deploy.
Not planning your sample out. Your Storyline sample should go through the same nine planning steps you used for Rise before you open Storyline. Skip that and a hiring manager can tell.

\n\n \n

Building your design document.

The design document is the strategic blueprint for a piece of learning: the business problem, the audience, the objectives, the approach. Corporate IDs write these constantly, and producing one proves you can think like an ID, not just build in a tool.

It looks a lot like your content map, so here's the difference. Your content map is the detailed planning document you built your sample from. The design document is a pared-down, higher-level version of it, and it's the format corporate teams actually use to align stakeholders. That's exactly why it makes a strong portfolio sample on its own: it's a real corporate artifact.

One note on timing: on the job the design document comes before the build, but for your portfolio, create it after, based on the Rise or Storyline sample you already built. Same course, no new project to invent, and you'll know it well enough to write the doc quickly.

What a strong design document includes

Project overview and background
The business problem and the goal of the training
Learner audience analysis
Learning objectives
Deliverables (what will be built, in what format, on what timeline)
High-level content outline
Assessment strategy
Success measures

Download the template

We have a design document template you can use. Same structure we teach inside Applied Instructional Design Academy, and it maps to what corporate hiring managers expect.

Download design document template (PDF)

Where people get tripped up

Making it too vague. A design doc that says \"the audience is employees\" and \"the goal is to teach them the process\" tells a hiring manager nothing.
Making it too long. It's a working document, not a novel. Focused beats comprehensive.

\n\n \n

Building your storyboard.

A storyboard maps a learning experience screen by screen: what the learner sees, hears, and does. It's a standalone portfolio sample that shows a hiring manager you can plan at that level of detail and that you understand the ID workflow.

Here's the part that sounds backwards: build your storyboard after you've learned the tool, not before. On the job, the storyboard comes first, because an experienced ID already knows the tool. But you can't design a storyboard for an authoring tool you've never used. You have to learn what it can actually do first, then you can map out a course that uses it well. Building your portfolio, you're learning the tool as you go, so the order flips. And like the design document, your storyboard can be based on the Rise or Storyline sample you already built. Same course, no new project to invent.

What a strong storyboard includes

Screen-by-screen layout (visual sketch or wireframe)
On-screen text
Narration or voice-over script
Interactions and what happens on click
Notes for the developer (or yourself, if you're building it)
References to the learning objectives each screen supports

Format: PowerPoint works. Word works. Some IDs use Miro or Figma. Pick something that reads clearly and looks like a real work artifact.

Where people get tripped up

Confusing the storyboard with the design document. Different levels of detail. The design doc is the strategy, the storyboard is the execution plan.
Skipping the interaction notes. If the storyboard doesn't show what the learner does on each screen, it's just a slide deck.
Making it visually messy. Corporate storyboards are professional artifacts, not sketchbook doodles.

\n\n \n

Building your job aid.

A job aid is a quick-reference document a learner uses at the moment of need. Not a training. Not a course. A single-page or short reference tool that helps someone do their job better right now.

Corporate IDs get asked to build these constantly. Including one in your portfolio shows you can design for real workplace performance, not just seat-time training.

What a strong job aid includes

Clear task or scenario the aid supports
Step-by-step instructions or a decision tree
Clean visual layout the reader can scan
Corporate design (not clip art, not a Google Doc with default fonts)
One page ideally, two at most

Format: PDF is standard. Some IDs build these in InDesign, Canva, or PowerPoint. Whatever tool you use, the output has to look like something a real company would print, hand out, or post on an intranet.

Where people get tripped up

Making it too long. A job aid is not a workbook.
Choosing a topic that's not job-relevant. This is for workplace performance, not personal use.
Skipping the visual design. A wall of text is not a job aid. Layout matters here as much as content.

\n\n

Grab the resources →

\n\n \n

6Resources

Three resources to help as you build.

Everything you need to reference as you work through your portfolio pieces.

Content map template (PDF)

Your planning document. Fill this in first to plan your Storyline or Rise sample before you build. It's the same planning tool we use inside Applied Instructional Design Academy.

Download content map template

Design document template (PDF)

The same structure we teach in Applied Instructional Design Academy. Use it as your starting point for any design doc you build.

Download design document template

Storyline QA checklist (PDF)

Before you call your Storyline sample done, run through this checklist. It's the same one Applied Instructional Design Academy students use to catch the issues hiring managers notice.

Download Storyline QA checklist

One more thing →

\n\n \n

7Take It Further

Would you like to take this further?

You've just seen everything that goes into a portfolio that gets you hired. If the Rise sample is the piece you'd rather not figure out alone, that's exactly what the 30-Day Rise Sprint is for.

It's a short, focused program where I walk you through building one strong Rise sample from start to finish. The kind that looks like a working ID made it, not someone brand new. In 30 days you go from a blank screen to a finished, published sample you can put straight in your portfolio.

Here's what you get

A 5-week guided path: plan and content map, build in Rise, get feedback, revise, then polish and publish
Live coaching calls twice a week for support, accountability, and getting unstuck
Expert feedback on your sample, with back-and-forth until it earns our stamp of approval
The Map Your Sprint planning tool and a day-by-day tracker so you always know your next step
An AI prompt pack for the full ID workflow
A community building their samples right alongside you
No expensive software required. The Rise free trial covers the whole thing.

By the end, the piece you were most worried about building on your own is done, and it's one a hiring manager will actually respect.

\n \n

Enroll in the 30-Day Rise Sprint →

\n\n

\n\n",[],[695,871],"d307849c-42c2-4260-a49d-04313025f531","pitch-your-first-project.html","213e1240-7b0d-11f1-9404-1607ee4eb77e",873,["D",1789506949330],21,"\n\n\n

\n $\"Learning$ \n

Pitch Your First Project

\n\n

Land your first instructional design project, volunteer or paid, without a portfolio full of experience.

Pick where you are, and get customized help for that exact step.

\n\n \n

Where are you right now?

Pick the option that sounds most like you. You can always come back and choose another one.

\n\n

\n \n\n \n\n \n

\n\n \n

\n \n\n

Find your first opportunity

Two ways to identify a target to pitch when you don't have one yet. Direct outreach to an org you've spotted, or someone already in your network.

\n\n

\n Before you scroll\n Pick one nonprofit or organization you'd actually care about. Motivation matters more than the perfect project. A cause you're excited about carries you through the hard part.\n

\n\n

\n Path 1\n

Direct outreach to nonprofits and organizations

Not centralized, but often the best portfolio pieces. Pick a target and pitch them directly.

\n\n

Good direct-outreach targets

Local nonprofits whose cause matters to you (search \"nonprofits + your city\")
Small museums and historical societies (they usually need docent training or tour scripts)
Nonprofits with a volunteer program (they almost always need better onboarding materials)
Open source projects that need training or user documentation
Your current employer, if you're still in a job (tell your supervisor you're transitioning, ask what training projects you could take on)

\n\n

\n Ready to pitch one?\n Once you have a target in mind, click \"Back to options\" and pick \"I have a target and need to pitch.\" The tool will help you write the outreach email.\n

\n\n

\n Path 2\n

Your warm network

Every source says this is the strongest way to find real work. Family, friends, former coworkers.

\n\n

Where to look in your network

Friends or family who own a business (they almost always have a training or onboarding gap)
Former coworkers, especially in HR, L&D, or people-manager roles
Coaches, course creators, or consultants you know (they need help turning content into structured learning and rarely think to hire \"an ID\")
Your kids' school, sports team, or community group if you have an in there

\n\n

How to pick a good target (in any path)

They have a training-shaped hole. Onboarding that doesn't exist, an outdated course, a compliance training everyone complains about.
They can decide fast. One decision-maker is easier than a committee.
You care about what they do. This gets you through the messy middle.
The project fits your bandwidth. Think a 5 to 10 minute module, or a single job aid. A full 60-minute course is too big for a first project.

\n\n

\n \n \n \n

\n\n \n

\n \n\n

Write your pitch

Answer a few short questions about your target and the angle you've spotted. The tool will draft a pitch email tailored to what you've told it, built from your details start to finish.

\n\n

\n Step 1\n

Volunteer or paid?

This changes the framing of the pitch. Volunteer leads with mission fit. Paid leads with the value you deliver.

\n \n \n \n

\n\n

\n Step 2\n

Who are you pitching?

\n Organization or person's name *\n \n

\n What kind of target is this? *\n

\n \n \n \n \n

\n What do they do? (One or two sentences)\n \n

\n\n

\n Step 3\n

The angle

The best pitches name a specific problem you can solve. Offering broad \"instructional design services\" is easy to ignore. What have you spotted?

\n What training-shaped hole did you spot? *\n \n

If you're not sure yet, look at their website, their volunteer page, their FAQs, or a job listing they've posted. The gap is usually there.

\n\n

\n Step 4\n

What can you deliver?

Scope this SMALL. A 5 to 10 minute module, a job aid, or a short guide is enough. Full courses are the wrong ask.

\n What specifically would you build for them? *\n \n

\n How long will it take you?\n \n

\n\n

\n Step 5\n

About you (briefly)

Two sentences on your background. This makes the pitch personal, so it doesn't read like a form letter.

\n Your background *\n \n

\n Your name and how they can reach you\n \n

\n\n \n

\n\n

Writing your pitch email

This can take up to 30 seconds. Hang tight.

\n\n

Your pitch email

Review it, tweak it to sound like you, then send. Short and specific beats long and polished.

\n\n

\n Draft Pitch Email\n

\n\n

\n Before you send\n Read it out loud. If a sentence sounds like a corporate pitch deck, rewrite it in your own words. Send from your regular email. Skip the business address. Follow up once after 5 business days if you don't hear back.\n

\n\n

\n \n \n \n

\n\n

\n \n \n

\n\n \n

\n \n\n

They said yes. Now what?

Two things happen here. First, download the scoping worksheet and walk through it with your client at your kickoff conversation. Once you know what you're building, come back and the tool will draft the agreement email you send now and the closeout email you'll send when the project wraps.

\n\n

\n Step 0 · Before you fill anything out\n

Scoping worksheet

A 12-section worksheet to walk through with your client at kickoff. Covers the deliverables, timeline, review process, payment terms, scope changes, portfolio permissions. Save it, print it, take notes on it, share it back.

\n \n

\n\n

\n Step 1\n

Volunteer or paid?

\n \n \n

\n\n

\n Step 2\n

The client and the project

\n Client name *\n \n

\n Your main point of contact\n \n

\n What was agreed to? *\n \n

Write down what was actually agreed to. Leave out what you hope to build. Specifics only.

\n Timeline *\n \n

\n If paid, what's the fee?\n \n

\n\n

\n Step 3\n

Your name (for the agreement)

\n Your name and email *\n \n

\n\n \n

\n\n

Drafting your emails

Agreement email and closeout email. Up to 30 seconds.

\n\n

Your launch kit

Two emails. Send the agreement now to confirm scope in writing. Save the closeout email for when the project wraps.

\n\n

\n Piece 1\n Agreement email (send this now)\n

Sends the agreed scope back in writing so nobody's guessing. It's a simple paper trail, and it doesn't need to be a legal contract.

\n\n

\n Piece 2\n Closeout email (save for later)\n

Send this when the project wraps. The three asks that most new IDs forget: portfolio permission, a written testimonial, and a referral.

\n\n

\n Two rules for the next four weeks\n Deliver faster than they expect. And say no to anything that shows up outside the agreed scope. Scope creep is what turns a 4-week project into a 6-month one.\n

\n\n

\n \n \n \n

\n\n

\n \n \n

\n\n

\n\n\n\n\n\n\n\n\n",[],[695,879],"3258f075-9a14-4bb0-afee-81a5922e7be6","networking-guide.html","a1f3727e-7a2f-11f1-8c72-1607ee4eb77e",902,["D",1789508252497],31,"\n\n\n\n\nNetworking Message Studio | Learning Strategy & Design\n\n\n\n\n\n\n

\n $\"Learning$ \n

Networking Message Studio

\n\n

\n\n\n

Your networking scripts and confidence tools

Ready-to-use scripts for every networking situation you'll hit during your job search, plus tools to pressure-test your messages before you send them. Pick a scenario, customize a script, and save the ones you like to your Swipe File.

HOW THIS WORKS

Scripts tab: Browse scenarios, pick a tone, copy or personalize any script

Confidence Checker + Reply Helper: AI-powered feedback on your own drafts

Swipe File: Your saved scripts in one place

\n\n

\n \n \n \n \n \n

\n\n

\n \n\n

\n \n

\n\n \n

Scenario 01

LinkedIn Cold Message

You found an ID professional you want to connect with. You've never met. Here's how to reach out without sounding like a bot or a desperate job seeker.

Platform:

Reaching out to an ID at your target company

You want to learn about their experience there

▾

Tone:

Script

Hi [Name], I came across your profile while researching roles at [Company] and was really impressed by your background in instructional design. I'm currently transitioning into ID from [your background] and would love to connect. No ask right now, just building my network with people doing work I admire. Hope that's okay!

✗ Don't

\"Hi [Name], I'm an aspiring instructional designer looking to break into the field. I would love to pick your brain about how you got started and any advice you might have for someone like me who is trying to make a career transition. Please let me know if you'd be open to chatting sometime!\"

Why it fails: Way too long. \"Pick your brain\" is a red flag. \"Someone like me\" sounds self-pitying. Ends with a vague ask that's easy to ignore.

✓ Do

\"Hi [Name], I came across your profile while researching [Company] and loved your ID background. I'm transitioning from teaching and would love to connect. No ask, just building my network with people doing work I admire!\"

Why it works: Specific, short, low pressure. They know exactly who you are and what you want in three seconds.

Pro Tip

Keep it under 4 sentences. Mention something specific about THEM. \"No ask right now\" lowers their guard and ironically makes them more likely to respond.

Connecting after seeing their content

They posted something that resonated with you

▾

Tone:

Script

Hi [Name], your post about [topic] stopped my scroll. That point about [specific thing they said] was exactly what I needed to hear this week. I'm an aspiring ID transitioning from [background] and I've been following your work. Would love to connect!

✗ Don't

\"I loved your post! So inspiring. You really know your stuff. I'm also interested in instructional design and would love to connect and learn from you!\"

Why it fails: Generic flattery with zero specifics. Could have been sent to anyone. They know you didn't actually read it.

✓ Do

\"Your point about ADDIE being a starting point, not a rulebook, stopped my scroll. I'm transitioning from HR into ID and that reframe was exactly what I needed. Would love to connect!\"

Why it works: Quotes something specific. Shows you actually thought about it. Personal without being weird.

Pro Tip

Be specific. \"I loved your post\" means nothing. Referencing the actual idea shows you read it, and that makes all the difference.

Personalize It

Fill in a few details and get a version that actually sounds like you.

Your Name

Your Background

Their Name

What caught your eye about them

\n \n

Writing your message...

Your Personalized Script

\n\n \n

Scenario 02

Info Interview Ask

You want to learn about someone's ID career. Two ways to ask: 1-2 specific questions over message (lower friction, works with almost anyone) or a 30-minute call (higher value when it happens, but not everyone has time for it). Neither one is the \"real\" ask, pick whichever fits how well you know them.

Asking 1-2 questions directly (no call)

Lower friction, a good default for most people

▾

Script

Hi [Name], thanks for connecting! I'm working toward my first ID role and had a specific question: [your specific question]? No need to jump on a call, whenever you get a chance to reply is great.

✗ Don't

\"Hi! I'd love to pick your brain sometime, whenever works for you!\"

Why it fails: No actual question. This is just as much an open-ended time drain as a vague call request, it just doesn't look like one.

✓ Do

\"Had a specific question: how did you make the jump from teaching into your first ID role? No need for a call, whenever you get a chance to answer is great.\"

Why it works: One real question. No calendar coordination required. Easy to answer between meetings.

Pro Tip

Most people who won't get on a call will still answer one good question over message. Try this first with people you don't know well yet, it works at least as well as asking for a call, sometimes better, since there's nothing on their calendar to protect.

Asking via LinkedIn after connecting

You're already connected, now you want a chat

▾

Script

Hi [Name], thanks so much for connecting! I'm actively working toward my first ID role and I'd love to learn from someone already doing the work. Would you be open to a 30-minute virtual coffee chat? I'll come prepared with specific questions. Totally no pressure if the timing isn't right.

✗ Don't

\"Hi! I would love to pick your brain about how you got into ID. Do you have time to chat? It would mean so much to me. I'm really trying to make this transition work.\"

Why it fails: \"Pick your brain\" is exhausting. The emotional appeal puts pressure on them. No time frame. Sounds desperate.

✓ Do

\"Would you be open to a 30-minute virtual chat? I'll come with 3-4 specific questions, no pressure if the timing isn't right!\"

Why it works: Specific time. Specific number of questions. Clear out if they're busy. No guilt trip.

Pro Tip

30 minutes is the standard ask for an informational interview, people are more open to it than you'd think. If you want something lower-friction for a first touch, 15-20 minutes works too. Either way, \"I'll come prepared\" signals you respect their time.

Asking via email cold

You found their contact on their portfolio or site

▾

Script

Subject: Quick question from an aspiring ID\n\nHi [Name], I found your portfolio while researching IDs in [industry] and was genuinely impressed by [specific project or detail]. I'm transitioning into instructional design from [background] and would love to ask you 3-4 questions about your journey. Would a 30-minute call work for you sometime in the next few weeks?

Pro Tip

Say \"3-4 questions\" not \"pick your brain.\" People know that phrase means an open-ended time drain. Specific always beats vague.

Personalize It

Fill in your details and get a version that sounds natural coming from you.

Ask Type

Your Background

Their Industry / Niche

Something specific about their work

Their Name

If asking a question: what's the question?

\n \n

Writing your message...

Your Personalized Script

\n\n \n

Scenario 03

Following Up

You met someone at a virtual event, LinkedIn Live, or a Facebook group. Here's how to turn a brief interaction into an actual connection.

After a virtual event or webinar

You were both in the same session

▾

Script

Hi [Name], I was in [event name] today and saw your comment about [specific thing they said]. That really resonated with me. I'm making a similar transition from [background] into ID. Wanted to connect while it was fresh. Hope to cross paths again in the community!

✗ Don't

\"Hi! I think we were both in that webinar earlier. Anyway, I'm transitioning into ID and thought it would be nice to connect with others in the field!\"

Why it fails: \"I think\" signals you weren't paying attention. \"Anyway\" is dismissive. Nothing about THEM.

✓ Do

\"I was in the ID Insider webinar and your comment about not waiting until your portfolio is perfect really hit home. Transitioning from K-12 into ID. Wanted to connect while it was fresh!\"

Why it works: Names the event. References what they said. Shows you were actually paying attention.

Pro Tip

Send this within 24 hours. The longer you wait, the colder it gets. Reference something specific so they know you weren't mass-connecting.

After someone commented on YOUR post

They engaged with you first, now follow through

▾

Script

Hi [Name], thanks so much for your comment on my post. Your point about [what they said] was spot on and added something I hadn't thought about. I checked out your profile and love what you're doing in [their area]. Would love to stay connected!

Pro Tip

When someone comments on your post, you already have a warm connection. A quick DM turns a comment into a real relationship. Don't let it go cold.

Personalize It

Tell me about the situation and I'll write a follow-up that feels natural.

Their Name

Where you \"met\"

Something they said or did

Your Background

\n \n

Writing your message...

Your Personalized Script

\n\n \n

Scenario 04

Asking for a Referral

This is someone you actually know. Asking for a referral doesn't have to feel transactional. Here's how to do it right.

Asking a former colleague at your target company

You have a real relationship with them

▾

Script

Hey [Name]! Hope you're doing well. I've been thinking about you. I'm actively looking for my first ID role and noticed [Company] is hiring. I know it's a big ask, but if you feel comfortable, would you be willing to refer me or put me in touch with the right person? I have my portfolio ready and I'll make it as easy as possible for you. No pressure at all if it's not a good fit!

✗ Don't

\"Hey, I saw [Company] is hiring. Can you refer me? Here's my resume. Let me know ASAP since I think the deadline is soon.\"

Why it fails: No warm-up. No acknowledgment that this is a big ask. The urgency adds pressure. Purely transactional.

✓ Do

\"I'll make it easy for you. Here's a short blurb you can forward, plus my portfolio link, all ready to paste. If it doesn't feel right, no worries at all!\"

Why it works: Doing the work for them dramatically increases the chance they say yes. Removing friction is the secret.

Pro Tip

\"I'll make it easy for you\" is the magic phrase. Write the blurb they'd forward. Give them your portfolio link ready to paste. Lower their effort and they're far more likely to follow through.

Asking an AIDA cohort member who landed a job

A peer who made it before you did

▾

Script

Hey [Name], I saw you landed at [Company], that's amazing, congrats! I'm still in the job search and wondering if you'd be open to a quick chat about what the process was like there. And if it's a good culture fit, would you feel comfortable passing my name along? I'll send my portfolio link so you have it handy.

Pro Tip

Start with genuine congratulations. Ask about the company first, THEN the referral. That way it feels like a conversation. Jumping straight to the ask feels like a transaction.

Personalize It

Tell me about your situation and I'll write a referral ask that doesn't feel awkward.

Their Name

How you know them

Target Company

Role you're applying for

\n \n

Writing your message...

Your Personalized Script

\n\n \n

Scenario 05

Sharing Your Portfolio

Your portfolio is your superpower. Here's how to put it in front of people without it feeling like you're just blasting a link.

Sharing in a LinkedIn post

Announcing it to your whole network

▾

Script

Six months ago I was a [previous role] with zero instructional design experience. Today I just finished my ID portfolio.\n\nIt has [X projects] including [brief description of 1-2 standout pieces].\n\nI'm actively looking for my first ID role and would love any feedback, connections, or introductions. Link in the comments.\n\n[Tag 2-3 people who supported your journey]

✗ Don't

\"Excited to share that I've been working really hard on my instructional design portfolio! It was a journey but I'm so proud of it. Please check it out at [link] and let me know what you think! #instructionaldesign #elearning\"

Why it fails: Vague. No specifics. Link in the post kills reach. Nothing makes you stop and read.

✓ Do

\"Six months ago I was teaching 8th grade math. Today I have a portfolio with 3 ID projects, including a branching scenario I built in Storyline. Actively looking for ID roles. Link in comments.\"

Why it works: Clear before/after. Specific details. Link in comments for better reach. Direct and confident.

Pro Tip

Put the link in the COMMENTS and keep it out of the post itself. LinkedIn buries posts with external links. You'll get significantly more reach this way.

Sending it directly in a DM

Sharing with someone relevant in your network

▾

Script

I wanted to share my portfolio with you since we've been connecting around the ID job search. Here's the link: [URL]. The project I'm most proud of is [project name] because [one sentence why]. Would love your honest thoughts if you have 5 minutes!

Pro Tip

Always highlight ONE project and save the rest for later. \"Here's my portfolio\" is easy to ignore. \"Here's the project I'm most proud of and why\" makes them curious.

Personalize It

Tell me about your portfolio and I'll write a post or message that gets attention.

Your Previous Role

Standout Project

Why that project stands out

Format

\n \n

Writing your message...

Your Personalized Script

\n\n \n

Scenario 06

When They Ghost You

They said they'd love to chat, then nothing. One more reach-out is completely okay. Here's how to do it gracefully.

Following up on an unanswered message

They never replied to your first outreach

▾

Script

Hi [Name], I know inboxes get busy, just wanted to bump this up in case it got buried. Happy to work around your schedule if you're open to connecting. If the timing isn't right, no worries at all. I appreciate you being part of my network either way!

✗ Don't

\"Hi again, I reached out a while back and haven't heard from you. I was just wondering if you had a chance to see my message? I totally understand if you're busy. No worries if not!\"

Why it fails: Apologetic from the start. Repeating \"no worries\" signals anxiety. The whole message makes you sound like you're shrinking.

✓ Do

\"Just bumping this up in case it got buried, happy to work around your schedule. No pressure either way!\"

Why it works: Short. Assumes the best (a busy inbox, a buried message). Confident but not pushy.

Pro Tip

Wait 5-7 days before following up. One follow-up is professional. Two is pushy. After the second message, move on to the next person.

They agreed to chat but went quiet

They said yes, then disappeared

▾

Script

Hi [Name], I know life gets hectic! I still would love to connect if you have 30 minutes. Here are a couple of times that work for me: [Time 1] or [Time 2]. If those don't work, just let me know what does and I'll make it happen!

Pro Tip

Give two specific time options instead of \"what works for you?\" Open-ended scheduling creates friction. Specific times are easy to say yes or no to.

Personalize It

Tell me what happened and I'll write a follow-up that's confident, with zero desperation in it.

Their Name

What was the original ask

How long since your last message

Did they say yes before going quiet?

\n \n

Writing your message...

Your Personalized Script

\n\n

\n \n

Confidence Checker

Wrote something but not sure if it lands? Paste it here. You'll get honest feedback on tone, length, and specificity, plus an improved version ready to copy.

\n Paste Your Message\n \n

\n \n \n

\n \n

Reviewing your message...

Improved Version

\n \n \n

\n\n \n

Reply Helper

They responded. Now what? This is where most people freeze. Paste what they said and I'll write you a reply that keeps the conversation moving forward.

\n What Did They Say?\n \n What Did You Originally Ask For?\n \n

\n \n \n

\n \n

Writing your reply...

Your Reply

\n \n \n

\n\n \n

💀 The Message Graveyard

These messages didn't make it, and the reasons were rarely outrageous. It's the small, common mistakes that get people every time. Read each one, learn what went wrong, and make sure you never send anything like it.

💀The Novel Nobody Asked ForLinkedIn DM

\"Hi Jennifer! I hope this message finds you well. My name is Ashley and I came across your profile while browsing LinkedIn today. I noticed that you work as an Instructional Designer at Bright Learning Solutions and I thought it would be wonderful to connect with you. I am currently in the process of transitioning my career from K-12 education into the instructional design field and I am really excited about the possibilities. I have always been passionate about how people learn and I think my teaching background gives me a really strong foundation. I would love to hear more about your experience and perhaps get some advice on how to break into the field if you ever have the time. No rush of course! I know you must be very busy. Thank you so much for your time and I hope to hear from you soon!\"

What Killed It

Way too long. LinkedIn DMs should be 3-4 sentences max. This required real effort to read, and most people won't.

Zero specifics about Jennifer. Nothing shows Ashley actually looked at her profile. Could have been sent to literally anyone.

\"Get some advice\" is vague and open-ended. Jennifer doesn't know what she's agreeing to. Vague asks get ignored.

Over-apologizing throughout. \"No rush,\" \"I know you must be very busy,\" \"thank you so much,\" all of it signals low confidence and makes the reader feel guilty before they've done anything.

The Fix

Cut it to 3 sentences. Reference something specific about Jennifer's work. Make one clear, low-pressure ask with a time frame.

\n\n

💀The Job Application Disguised as NetworkingLinkedIn DM

\"Hi Marcus, I saw that your company is hiring for an Instructional Designer role. I am very interested in this position and I think my background in training and curriculum development would be a great fit. I have attached my resume and portfolio for your review. Please let me know if there is anything else you need from me. I look forward to hearing from you!\"

What Killed It

This is not networking. It's a cold job application. Marcus didn't post a job. He's an ID professional. This puts him in an uncomfortable position he didn't sign up for.

No relationship was built first. Skipping the connection step and going straight to \"hire me\" almost never works and often burns the bridge completely.

Nothing about Marcus as a person. No acknowledgment of his work, career, or perspective. Entirely self-focused.

The Fix

Connect first, ask second. Build a genuine relationship before anything job-related. Even one or two exchanges changes the entire dynamic.

\n\n

💀The Guilt Trip Follow-UpFollow-Up Message

\"Hi Priya, I just wanted to follow up on my message from last week since I hadn't heard back. I completely understand if you're busy. I know everyone has a lot going on. I just really wanted to connect because your career is so inspiring to me and it would mean the world to get even 10 minutes of your time. I hope I didn't do anything wrong in my first message! Let me know either way so I know where I stand.\"

What Killed It

\"It would mean the world.\" Emotional pressure in a professional networking message doesn't move the reader. It makes them uncomfortable and shifts the burden onto them.

\"I hope I didn't do anything wrong.\" This signals insecurity and draws attention to the possibility something was off. Never apologize for reaching out.

\"Let me know either way so I know where I stand.\" This forces them to officially reject you. People avoid uncomfortable conversations, so they just ignore this instead.

The Fix

A confident follow-up is short, assumes the best, and gives them an easy out without drama. \"Just bumping this up, no pressure either way!\" is all you need.

\n\n

💀The Copy-Paste BombInfo Interview Ask

\"Hi [Name], I hope you're having a great day! I am an aspiring instructional designer looking to break into the field and I would love to connect with experienced professionals like yourself. Would you be willing to share your career journey with me? I am eager to learn from someone who has already navigated this path. Thank you for your consideration and I look forward to connecting with you!\"

What Killed It

They left [Name] in the message. Immediate sign the message was copy-pasted with zero personalization. Instant delete.

\"Experienced professionals like yourself\" is generic flattery that applies to every person on LinkedIn. Tells them nothing about why you reached out to THEM specifically.

No specific ask. \"Share your career journey\" could mean a 10-minute chat or a 2-hour call. Vague asks create friction and get skipped.

The Fix

Always fill in the name. Always reference something specific about them. Always give a specific time frame. Those three things alone change everything.

\n\n \n

Your Swipe File

Scripts you've bookmarked from the guide. Tap the bookmark icon on any script to save it here. Stays saved in this browser until you clear it.

🔖

Nothing saved yet

Head to the Scripts tab and tap \"Save to Swipe File\" on any script that resonates with you.

\n \n

\n\n

Saved to Swipe File!

\n\n

\n\n\n\n\n\n\n\n\n

${toolName}

Learning Strategy & Design Free Tools

Map your scenario

Skipped for this map

Skipped for this map

Skipped for this map

Skipped for this map

Criteria (edit inline)

Criteria (edit inline)

Play your own sim

Play your own sim

Publish

Your edit key

Advanced: your config

Your build plan

Publish

How will this live in your course?

Your edit key

Advanced: your config

Spend a week with Nora.

About Nora

About the job

About the rhythm

Nora's week as an instructional designer

Nora's take

What this life changed for me

The real talk

You might love this if…

This might not be for you if…

Want a week that looks more like Nora's?

Nail the first 90 seconds of your ID interview.

How it works

Storyline Scenario Builder

Tell me about your project

Your Scenario

Decision Point 1: First Choices

Your Scenario Map

Node Details

Want a decision point to be a LIVE conversation?

Storyboard Reviewer

Welcome Back

Upload Your Storyboard

Review Results

Final Check

Storyboard Review Complete

Learn the language before you're in the room

Corporate Glossary

E-mail Communication

You're thinking corporate.

What to do next

Scenario Studio

Get the exact words for your salary negotiation

SME/Stakeholder Roleplay Gym

Welcome to the Roleplay Gym

Coaching Feedback

What happened

The better move

Now YOU decide

Scenario Complete!

Tailor your resume to this job

Your Resume

Job Description

Tailor your resume to any ID job posting

Your Resume

ID Job Posting

Revamp your resume for corporate ID

Your Resume

🏫 Educator Skills → ID Language Translator

E-Learning Project Scope Estimator

Course Length

Interactivity Level

Content Readiness

Multimedia Requirements

Audio / Narration

Review Cycles

SME Availability

Phase Breakdown

What Adjusted Your Estimate

Build the summary at the top of your resume, the right way

A coach that keeps the words yours

Turn Any Idea Into a
Corporate Training Topic

History · shell.css