How to Submit an AI-Made Web Work to oeeco
A practical guide to preparing a clear, safe, and useful oeeco submission with the right title, summary, tags, demo URL, and creator context.
A good oeeco submission should help a visitor understand what they are about to open before they click. The work can be a game, a tool, a visual experiment, or an interactive page, but the listing needs to be specific, honest, and easy to review.
This guide explains how to prepare a submission so it has a better chance of being accepted and a better chance of being useful once it is public.
Start with a playable or usable URL
The most important part of a submission is the demo URL. It should open in a modern browser, load without special setup, and show the actual work described in the listing. If the page requires a risky download, a private login, or a confusing redirect chain, it is not ready for oeeco.
Before submitting, open the URL in a clean browser session and test the first minute of use. Check desktop and mobile if possible. A work does not need to be huge, but it should not be broken at the first interaction.
Write a title that names the thing
A strong title tells people what kind of work they are seeing. Names like Orbital Salvage, Customer Interview Signal Lab, or Tiny Launch Checklist give visitors a useful mental model. Vague names like New AI Demo or Test Project make the work harder to trust.
If the work is experimental, that is fine. The title can still be concrete. A clear name helps search, review, sharing, and future visitors who are scanning a crowded list.
Use the summary to set expectations
The short summary should answer three questions: what does it do, who might use it, and what happens when someone opens it. A good summary is usually one sentence, not a marketing paragraph.
Avoid claims that the work cannot support. If a tool offers a heuristic score, call it a score. If a game is a prototype, say what the core loop is. Honest summaries help visitors enjoy the work on its real terms.
Choose tags that describe real context
Tags should describe the format, workflow, and audience. For example: codex, browser-game, validation, startup, canvas, product, research, interactive. Do not add unrelated tags just because they are popular.
Good tags help oeeco group works into useful shelves. They also make it easier for visitors to find examples they can learn from.
Add creator notes when the process matters
Creator notes are useful when they explain what was built, why it was built, and what tools or constraints shaped the result. They are not a place for hype. They are a place for context.
A short note about the AI-assisted workflow can make the work more valuable to other builders. Mention what was generated, what was edited by hand, and what you would improve next.