What earns a place in the directory.
Tessli lists design references, tools, libraries, assets and learning sources that are useful to designers and frontend builders. A listing needs a working destination, a clear use case, and enough checked information to describe it without exaggeration. The directory stays small on purpose: a source is listed when a curator would defend it next to its peers.
- A practical reason to use or study the source.
- A concise description visitors can understand before opening it.
- A category and access label that fit the available source information.
Metadata describes, not ranks.
Names, descriptions, categories, access labels and best-for and limitation notes help visitors decide whether to open a source; they are not ratings, popularity scores, or promises of quality.
Free, freemium, paid, open-source, and free-trial labels describe the recorded access model. Pricing, licensing, availability, and product scope can change, so the original destination remains the source to verify.
Suggestions and corrections go through GitHub.
Anyone can suggest a source, or report a broken link, changed access, a wrong category, a misleading description, a trademark concern or a removal request, with a GitHub issue form. A maintainer opens the source and decides; nothing is accepted automatically, and a correction never invents a replacement fact.
Sources are never deleted silently. A source that should go is archived with a recorded reason, and its page stays up with that reason and any replacement, so old links keep working.
Previews remain secondary to the original source.
Cards may use an approved preview, an Open Graph image, a favicon, or a generated letter mark. Tessli does not inject remote SVG markup or use destination images as permission to redistribute a site's work.