Finished is not the same as findable
Many good open resources are never used because nobody can find them, or nobody is sure what they are allowed to do with them. A resource sitting on a personal drive with no license statement is, in practice, not open. This guide covers the second half of the process: the choices that happen once the content exists. It assumes the content is already drafted and checked.
Four decisions matter most: where to host the work, which license to apply, how to describe it, and how to keep it alive.
Choosing a home
There are several kinds of places to host an open resource, each with trade-offs.
- Subject or institutional repositories and libraries. These are collections run by universities, networks or non-profits. They often provide search, standard descriptions, and some quality review, and their audience is educators who are already looking. Different repositories have different rules, review processes and license requirements, so read their submission policies before you start.
- General-purpose archives. Some research and data archives accept educational materials too, give them permanent identifiers, and promise long-term preservation. That stability matters if you want the link to work in ten years.
- Your own website. This gives you full control over layout and wording, but you are responsible for keeping it online, and discoverability depends on your own effort.
- Code-hosting sites. These suit materials that are written like software, with source files, version history and contributions from others. They are less friendly to non-technical visitors.
Consider placing the work in more than one location, with one master copy that you update and others that point to it. When you compare options, ask: Will it still exist in five years? Can others download an editable version? Are the license terms displayed clearly? Can I remove or update the resource later? For a wider look at where to find and place materials, repositories and libraries are the main starting point.
Choosing a license
The license tells people what they may do. Creative Commons licenses are the most widely used general option for educational content, and they work through combinations of a few conditions:
- Attribution means users must credit you.
- Share-alike means adaptations must carry the same license.
- Non-commercial limits commercial use, though what counts as commercial can be unclear in practice.
- No-derivatives forbids changes, which makes translation and adaptation difficult and so sits awkwardly with the aim of open education.
There is also a public domain dedication for creators who wish to give up rights as far as the law allows. Licenses cannot be mixed freely. If you built your resource using material under share-alike or non-commercial terms, your own choice is limited by theirs. Settle copyright and licensing questions before you publish, because it is difficult to withdraw a license once copies are out. Once a license is granted for a specific version, others may keep using that version under those terms. This is general information, not legal advice, and rules differ by country.
Describing the work with metadata
Metadata is the information that travels with the resource and lets search systems find and sort it. Even a short, consistent description helps. A sensible minimum is:
- Title that says what the resource is.
- Author or authors, and any contributors.
- A short description of what it covers and who it is for.
- Subject area and education level.
- Language.
- License, with a link to its full text.
- Date created and last updated, and version number.
- Format and approximate length or time to complete.
- Requirements, such as prerequisites or software.
- Credits for any reused material.
Write the description in plain words that a teacher would type into a search box. Avoid vague promotional claims like “the best guide ever”, and avoid claims of learning gains that you cannot support. Where a repository offers fixed fields, fill them all in; those fields are what its search uses. Some systems identify authors with persistent identifiers, which helps credit follow the work.
Preparing the files
Package the resource tidily. Include the editable source as well as the ready-to-read version, use clear file names, and put the license statement inside the resource itself rather than only on the hosting page, so it stays attached to any copy. Think about file formats and hosting too: open, widely supported formats last longer and are easier for others to edit. If the resource has many parts, add a short readme that lists them and explains the order.
Getting the work found
Publishing is a start, not an end. Some realistic steps:
- Tell colleagues and professional groups that the resource exists, with a short and accurate description.
- Ask a few users to try it and leave comments.
- Give each resource its own stable web address and avoid moving it.
- Consider adding the work to more than one directory.
- Use the vocabulary your audience uses in the title and description, so ordinary searches match.
Uptake is uncertain, and many resources are used quietly without any message reaching the author. Do not judge success by a single number such as downloads.
Maintenance
Add a date and a version number, and keep a short change note. Decide who will answer corrections, and say how to contact them. If you can no longer maintain the work, say so, and note that others may take it on under its license. Marking an old resource as retired is better than leaving it to silently go out of date.