Help Center

It gathers what you commonly need for front-end and design work in one place: small online tools, motion and page inspiration, technical articles, interview question sets and structured handbooks. No sign-up required — open it and use it.

No. There is no account system at all: tools, articles and question sets can be read and used directly, and sending a message needs no login either.

On a wide screen, use "More" at the bottom of the left rail; on a narrow screen, tap "More" in the bottom bar. Your choice is remembered, the next visit uses the same language, and page URLs carry the matching language prefix.

Yes. On narrow screens the navigation drops to the bottom of the viewport, and tool and article pages collapse into a single column. The image tools work on phones too, though with many or large files a computer is better — more memory and more speed.

Everything is free, with no usage limits. The tools run inside your browser and use no server resources, so there is no need to trade limits for cost.

No. Compression, format conversion, slicing, stitching and mockups all run in the browser with Canvas — files are never uploaded and are cleared on refresh; these tools even work offline.

Image compression, format conversion (including HEIC), 3×3 grid slicing, image stitching, mockup generator, app icon asset pack and image-to-ico all live under "Toolbox → Image".

Redis commands are compiled one by one from the official documentation, with complexity, return values and examples noted; regex and Cron are validated live by parsers running in your browser. If you spot a mistake, tell us with the form below.

Yes. The tools only process material you provide, and the output is yours. Copyright in the material itself stays with its author, so check your rights before commercial use — commercial fonts, other people's screenshots and so on.

Page inspiration (full pages and footers), UI/UX micro-interactions, component prompts, CSS text animations, MotionSites prompts, free commercial fonts, plus a set of recommended sites. On wide screens the category tree stays pinned beside the rail, so switching categories needs no scrolling.

Open a card for a live preview; in the dialog you can swap in your own text, preview again, then copy the CSS or the prompt. Paste the CSS into your stylesheet and it works; hand the prompt to an AI to reproduce the same effect.

They are taken from each site's public pages and are shown for reference only. Copyright stays with the original sites: don't deliver them as your own design and don't republish them.

To save power, cards pause when scrolled off screen and resume when they come back; they also stop if your system has "reduce motion" enabled. Some effects rely on WebGL, so with hardware acceleration turned off only a static frame remains.

Yes, as long as you credit the author and link the original — don't edit them and pass them off as your own. Please contact us first for commercial use.

Questions come from public interview material and my own notes, and answers include sources and examples wherever possible. If an answer is wrong or you know a better solution, send us the question number with the form below.

Each handbook has the chapter tree on the left and the text on the right; reading in order works best, and any single chapter can be shared by link. For exercise chapters, try them yourself first, then expand the reference answer.

Not yet. New content is recorded in the changelog, which you can bookmark to keep up; you can also bookmark the blog list page.

Their respective authors and rights holders. This site only displays and indexes them and claims no rights. Whether a font may be used commercially depends on the licence stated on its font page.

No. What you send through the help centre form or "Recommend a site" only reaches the admin side; there is no public message list. The IP address and browser identifier are recorded to rate-limit and block spam. No other personal information is collected.

Inspiration, fonts and recommended sites are hand-picked, with sources noted on each item; question sets and handbooks are written and organised here; the Redis command reference follows the official documentation. Feedback on anything wrong is welcome.

Use the form below, pick "Site issues", and say which page, what you clicked and what you expected. If you have a screenshot, paste an image link.

Two ways in: open “More → Recommend to Us” in the rail to get the recommendation form directly, or use the message form at the bottom of the Help Center page (reachable from “More → Help Center” in the rail, or the Help Center link in the homepage footer). Either way, fill in the site name, URL and a one-line description; submissions are reviewed by hand and appear in the list once approved.

Usually within one business day, sent to the email address you left. Without an address there is no way to reply, so remember to fill it in.