Resources
Where to get code templates and boilerplate
Don't want to build the project structure from scratch? We've gathered proven boilerplate sets for frontend, backend and quick prototypes.
The internet is packed with free resources — icons, fonts, templates, photos. But "free to download" and "allowed to use in your project" are two different things. An image from search results, a font from a pirate site or code without a license can turn into a claim from the rights holder, especially in a commercial project.
The good news: there are as many legal sources as questionable ones — you just need to know where to look and how to read a license. This page is a map of trusted resources across six categories plus a short breakdown of the MIT, CC0, Apache and other licenses.

The main risk with free resources is not quality, but the right to use them. A file may be posted for free, yet with the caveat "for personal projects only". Put such a font in a client's logo and you formally breach the license.
Rule number one: license first, download second. If the terms aren't stated anywhere, assume you can't use it: by default any work is protected by copyright.
If a file's terms of use aren't stated anywhere, by default it's protected by copyright — assume you can't use it.
| License | Commercial use | Credit the author | In plain words |
|---|---|---|---|
| CC0 / Public Domain | Yes | Not required | "Do whatever you want." As free as it gets. |
| CC BY | Yes | Yes | Anything goes, but credit the author. |
| CC BY-SA | Yes | Yes | Derivative works — under the same license. |
| CC BY-NC | No | Yes | Non-commercial use only. |
| MIT | Yes | License text | The freest one for code. |
| Apache 2.0 | Yes | License text | Like MIT + patent protection. |
| GPL | Yes | Yes | Derivative code must also be open. |
Three practical takeaways:
Everyone needs icons — for websites, apps, presentations. The key sources provide sets under open licenses (often MIT or CC0).
What to look for: SVG is preferable to PNG (scales losslessly, colored via CSS); a consistent style from a single set; an open license.
The font has the strongest effect on perception, and this is also where licenses get breached most often. Safe: libraries of open-source fonts under the SIL Open Font License (OFL) — it can be used in commercial projects.
What to check: OFL — green light; the range of styles; Cyrillic support.
A UI kit is a ready set of interface components in a single style. It saves designers and developers weeks of work.
What to check: the format (source file or code components); the license; how current the guidelines are.
A dataset is a structured collection of data for analytics, training models, testing and study. Open datasets are published under free licenses.
What to check: the license (even data has one); freshness and completeness; the format (CSV and JSON are more convenient).
Boilerplate is a ready-made project scaffold. Instead of setting things up from scratch, a developer clones a proven starter. The license is almost always MIT.
What to check: a match with your stack; freshness; the license (MIT/Apache — go for it).
Detailed review: Where to get code templates and boilerplate →
Photos, videos, illustrations, music. The main risk is grabbing "a nice picture from Google": it's almost guaranteed to be someone else's intellectual property. Safe: stock platforms with a CC0 license.
What to check: CC0 is the safest label; releases for photos with people; resolution.
The file may be used only in non-commercial projects. Any commercial use requires a paid license.
Yes. CC0 is the freest license: you can use it however you like, even without crediting the author.
Both allow commercial use and only require you to keep the license text. Apache 2.0 additionally includes explicit patent protection.
It depends on the license. CC0 — not required. CC BY and OFL — recommended or required.
There are enough legal file sources for any task — icons, fonts, UI kits, datasets, boilerplate and stock media. The one skill that separates safe use from risk is the ability to read a license. Remember three labels: CC0 for media, MIT/Apache for code, OFL for fonts.
We've covered licenses — now to practice. Where to get proven starters and boilerplate for your stack.