Why the technical side matters
Open licenses decide what you are legally allowed to do with a resource. Technical choices decide whether you can actually do it. A resource released under a permissive license but locked in a format nobody can edit, or hosted on a site that no longer exists, is open in name only. This review covers the practical requirements for both using and publishing, in plain terms, for people who are not technical specialists.
File formats
The key question is whether a format is editable, widely supported and able to carry accessibility information.
| Type of content | Commonly used formats | Points to note |
|---|---|---|
| Text documents | Word-processor files, open document formats, HTML, Markdown | Editable and convertible; best for adaptation |
| Fixed documents | Good for printing; hard to edit; accessible only if tagged | |
| E-books | EPUB | Reflowable text; support for images and math varies |
| Slides | Presentation files, HTML slides | Editable files are far more reusable than exported images |
| Images | PNG, JPEG, SVG | SVG is scalable and editable; JPEG suits photographs |
| Audio | MP3, other compressed formats | Provide transcripts |
| Video | MP4 and similar | Provide captions; files can be large |
| Data | CSV, plain-text formats | Simple, widely readable |
Two principles help. First, publish an editable source alongside any fixed version, since a PDF alone makes adaptation hard. Second, prefer open or widely documented formats over those that need one particular program, because they are more likely to still open in ten years. The openness of the format itself is related to the idea of open standards, which are publicly documented specifications that anyone can implement.
Hosting and storage
Where you put a resource decides who can find it and whether it survives. Common options include:
- an institutional repository, usually stable and managed by staff
- a subject or national collection that accepts contributions
- a learning management system, convenient but sometimes behind a login, which limits who can reuse the material
- a public file-hosting or code-hosting service
- your own website
For a resource to be reusable, it should be reachable without a paid account or login where possible, have a stable web address that does not change, and show its license on the page. Link rot is a real problem; avoid moving files around, and if you must, keep a redirect or notice in place. Keep your own backups, ideally in different places, because a hosting service can close or lose data. Treat cloud storage as convenient but not as your only copy.
Metadata
Metadata is the descriptive information attached to a resource: title, creator, date, language, subject, level, license and format. Complete metadata lets search tools and repositories index your work, and lets others judge it quickly. Some repositories ask for it in a specific structure; filling in the basic fields is worth the few minutes it takes.
Devices and software for users
Think about what your audience actually has. Some learners use shared computers, older phones or tablets with small screens; others have modern laptops. Some points to check:
- Does the resource work in a standard web browser without extra plug-ins?
- Does it display well on a small screen and reflow when resized?
- Does it need specific software, and is that software free and available on the platforms learners use?
- Are there any account requirements, and do they raise privacy concerns?
- Can it be printed legibly, in black and white if needed?
Plain web pages and simple documents work on the widest range of devices. Heavy interactive items and special viewers work on fewer.
Bandwidth and offline use
File size matters. A high-resolution video that plays smoothly on a fast connection can be unusable on a limited mobile data plan. Practical steps include compressing images sensibly, offering lower-resolution video options, separating large files from the main text, and describing file sizes before download. Learners with unreliable connections benefit from downloadable packages that work offline, such as a single bundle of web pages, an EPUB or a printable PDF.
This ties into questions of home internet access and device and data access, which affect who can use online materials at all. If your audience may be affected, plan an offline or print route from the start, instead of treating it as an afterthought.
Accessibility and standards
Technical choices underpin accessibility. Structured headings, text descriptions, captions and reflowable layouts all depend on the format and tools used. Many projects follow recognized web guidelines to guide this. Test with a keyboard and, if you can, a screen reader before release.
What you need to publish
For most educators, the requirements are modest:
- A way to create editable content, such as a word processor or simple web editor.
- Basic checks for accessibility and broken links.
- A place to host the files that is stable and publicly reachable.
- A license statement and credits visible on the work.
- Backups of your sources.
- A method for receiving corrections, such as an email address.
Larger projects may add version control, automated builds or a dedicated site, but these are not needed for a first resource.
What you need to reuse
Reusing is even simpler: a browser, a tool that can open the format, somewhere to store copies and a record of source and license. If you plan to edit, make sure you can open and save the format without damaging layout or accessibility features.
Keeping expectations realistic
Technology is rarely the main barrier. Time, confidence and clear licensing usually matter more. Start with common, simple formats, test on the devices your learners have, and improve from there.