9 Digital Production and Publishing
Learn how to plan, create, manage, review, and publish digital media while addressing accessibility, rights, quality, and future maintenance.
Plan the
A is a planned sequence of tasks, decisions, and reviews. It turns a project's goals and source materials into finished media that people can find, use, and access. A reliable process also manages assets, checks rights and , prepares suitable versions for distribution, and preserves materials needed for future updates.
Define the brief. Identify the purpose, audience, deliverables, channels, schedule, budget, and success criteria. Decide early which and technical requirements apply.
Plan and gather materials. Create a production schedule, assign responsibilities, and collect or make images, audio, video, text, and other assets. Record where each item came from and how it may be used.
Create and revise. Edit working copies of the materials. Keep an editable project file as well as suitable output files, and track significant revisions so collaborators know which version is current.
Review and approve. Check accuracy, presentation, , rights, and technical quality. Fix issues and obtain required approvals before release. Include checks throughout production rather than leaving them until the end.
Package and publish. Export versions appropriate to each destination, add descriptions and other required information, and upload or distribute the files. Confirm that the published item works as intended.
Maintain or archive. Keep the files, documentation, and permissions needed for updates or future use. Plan how content will be corrected, replaced, or withdrawn when necessary.
For example, a short instructional video might move from a brief and script to filming, editing, captioning, review, export, and upload. A reviewer checks captions and image descriptions, confirms that music and footage are cleared for the intended use, and tests the uploaded video before it is announced.
Manage digital assets
is the organized handling of materials from creation or acquisition through use, storage, and eventual replacement or preservation. Good practices make materials easier to identify, find, verify, and reuse.
Use consistent file names, folder structures, and version labels. For example,
garden-interview-2026-10-08_v02.wavis more informative thanfinal-new2.wav.Keep an unchanged source or primary file when practical, and make separate working copies and delivery versions. A compressed export may be convenient to publish but unsuitable for later editing.
Record such as an asset's title, creator, date, format, description, source, rights, and permitted uses. can help teams route assets for review or prevent use when distribution rights are unclear.
Back up important files and periodically confirm that copies can be restored. For long-term access, consider whether a format is documented, widely supported, and manageable with available tools. Format choice alone does not guarantee preservation.
A useful asset record might say: “Photo of the north entrance; creator: Jordan Lee; created: 8 October 2026; source: project photographer; credit required; approved for the project website and social posts.” The record should describe the actual permission; an asset is not necessarily reusable simply because it is stored in a shared folder.
Build in
means providing different ways for people to perceive and operate content. Plan for it when choosing a format and designing the experience, then test the result with both tools and human review. Automated tools can help, but no single tool can determine whether a site is accessible.
Useful practices include:
Add alternative text that communicates an image's relevant information or function. A decorative image can be marked so assistive technology can ignore it, while a complex chart may need a fuller text explanation.
Provide captions for video with meaningful speech or sounds. When visual information is not conveyed by the soundtrack, provide an appropriate text alternative or audio description. requirements include text alternatives and alternatives for time-based media.
Use meaningful headings, readable text, sufficient contrast, and clear instructions. Do not rely on color alone to convey important information.
Make interactive controls understandable and operable with a keyboard, and give controls labels that communicate their purpose.
Test the published experience, not just the source files. Check captions for accuracy, try keyboard navigation, and ask people with varied access needs for feedback when possible.
is a production responsibility, not merely a final formatting step. Scripts, storyboards, design choices, and asset selection all affect what alternatives can be provided later.
Check rights and permissions
Before an asset, establish who owns it and what uses are allowed. In the United States, generally protects original works once they are fixed in a tangible form, and owners hold specified exclusive rights subject to legal limitations. Buying a copy of a work does not, by itself, mean that every reuse is permitted.
For each third-party image, recording, clip, font, or other material, record its source and check the relevant license or permission. Confirm that permission covers the intended use, such as editing, commercial distribution, online publication, or use in a particular territory or period. Follow license conditions, including attribution when required.
Public-domain status, an applicable license, or a legal exception may allow some uses, but the facts matter. When uncertain, seek permission or qualified advice. Keep written evidence, such as a license, permission email, or signed release, with the project records.
Also check whether people, locations, trademarks, or private information featured in the content raise separate permission or privacy concerns. Requirements depend on the context and jurisdiction; this is general production guidance, not legal advice.
Publish and maintain content
makes a completed item available through a channel such as a website, social platform, streaming service, app, or downloadable file. Each channel may have different requirements for file type, size, dimensions, captions, , and playback. Preserve an editable working version when needed, then export a delivery version suited to the destination.
Before release, use checks to confirm that:
The item opens and plays correctly on the intended channel and devices.
The correct, approved version is being published, and links, titles, descriptions, and credits are accurate.
Captions, text alternatives, and interactive controls are usable.
Permissions and required attributions are documented.
The published file and supporting records are stored where the team can retrieve them.
After publication, verify the live result and monitor for broken links, display problems, or needed corrections. is not always the end of a project: digital content may need maintenance as platforms, formats, rights, or audience needs change.