Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Role guide
Web and Multimedia Developer Source-Aware Guide
Defines source-aware web and multimedia design, implementation, testing,
Read the fileOverview
Web and Multimedia Developer overview
Use this bundle to prepare source-aware web and multimedia design, implementation, testing, and release planning and a review-ready web and multimedia implementation brief.
Read the fileWorkflow
Web and Multimedia Developer source-aware triage
1. State the requested decision or artifact. 2. Inventory evidence: requirements, users, platforms, assets, and rights; code, dependencies, build and runtime versions; media specifications.
Read the fileTemplate
web and multimedia implementation brief
Review-ready artifact for web and multimedia design, implementation,
Read the fileIs this bundle right for your task?
Who it is for
- People performing or supporting Web and Multimedia Developer work, plus teams reviewing its decisions and outputs
- Teams working in Software engineering, Digital products
When to use it
- A Web and Multimedia Developer task needs a structured plan, evidence checklist, or review-ready output.
- A recommendation needs its assumptions, owners, risks, dependencies, and success measures made explicit.
What you need to provide
- The task objective, intended audience, working context, constraints, source material, and decision owner.
- Relevant reports, exports, examples, policies, prior decisions, and success measures available for the task.
Tasks and expected outputs
Questions it helps answer
- Prepare a web and multimedia implementation brief without fabricating local facts.
- Separate verified, provided, assumed, and missing evidence.
- Produce a review-ready recommendation with explicit verification and approval boundaries.
What it helps produce
- web and multimedia implementation brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the task objective, intended audience, working context, constraints, source material, and decision owner. Ask the agent to approach Web and Multimedia Developer work by producing web and multimedia implementation brief with a prioritized plan, evidence checks, owners, risks, and unresolved questions. Begin with ilo.org — Docs / D2513, then confirm that the reference is current and applicable. Inspect Web and Multimedia Developer Source-Aware Guide before drafting.
Context path: bundles/roles/web-and-multimedia-developer
What the bundle includes
Frameworks
- source-evidence matrix
- web and multimedia design, implementation, testing, and release planning review matrix
- qualified-review gate
Evaluations
- Web and Multimedia Developer source-awareness check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Treating the bundle as a substitute for organization-specific authority, firsthand evidence, or accountable review.
Known limitations
- Use the cited authoritative sources for general role, standards, or regulatory context; local facts, records, values, states, and permissions require inspected evidence.
- Task-specific work requires current evidence for requirements, users, platforms, assets, and rights; code, dependencies, build and runtime versions; media specifications, APIs, security and privacy constraints; responsive, browser, device, accessibility, performance, test, deployment, and rollback evidence.
- Do not infer asset rights, compatibility, accessibility, security, performance, test result, or production state.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, health, and other sensitive data.
- Require explicit confirmation before actions that publish or deploy, use credentials, change production data, or claim compatibility, security, or conformance.
- Route legal, privacy, security, compliance, financial, employment, clinical, safety, and other qualified judgments to an evidenced accountable reviewer.