regards.design

A captured page's sections in order, top to bottom, each with its kind, summary, novelty, screenshot tiles and geometry: the page's structure and rhythm. Use it to see the whole page around a section you found, or to compare how sites build a page. page is a page id (hit.page.id); a section key works too. It returns no image: view_section shows a section. Positions are from our capture of the page (page.shotAt, page.viewport, usually 1440×900), not today's live page: y is CSS px from the top of the captured page. geometry.top/height place the section and geometry.left/right are its horizontal crop. images.tiles are its screenshots top to bottom at page.dsf× pixels, each with top/height in section px (0 = the section's top).

page_sections

One section in full: its kind, summary, novelty and whether it moves (how certain, what kind of motion), its screenshot tiles in every size (images.tiles[].sizes: the same tile at smaller widths, px), the text it visibly shows (headings, labels and paragraphs top to bottom, each with its rect and font size), its page as captured (page, and pageSections: every section on it in brief) and sections of the same site's other captured pages (moreFromSite). Use it when you need a section's words, where it sits on its page, or more from its site. It returns no image: view_section shows the section. Positions are from our capture of the page (page.shotAt, page.viewport, usually 1440×900), not today's live page: y is CSS px from the top of the captured page. geometry.top/height place the section and geometry.left/right are its horizontal crop. images.tiles are its screenshots top to bottom at page.dsf× pixels, each with top/height in section px (0 = the section's top).

get_section

Find sections of real websites to design from, by how they look, what they show and say, and how unusual they are. Use it before you design, build or rethink a website, a landing page, a section, a brand's look on the web or a design system, or commit to an aesthetic direction; and whenever you or the user want inspiration (an aesthetic or mood, a UI element or pattern, a kind of section, something experimental, sites like a named one). Skip it only when the user has fixed the look. It searches regards.design's captures, not the live web, so it can't answer what a site looks like today or anything beyond its design. q is read like a designer's brief, for kinds of section, named sites, the kind of page, things to avoid, motion and novelty; understood and applied show how it was read, and ignore drops a part of that reading. For sections that literally show some text, use contains. An empty q browses the most distinctive sections. Results come in groups: exact (a site you named), match, related (past a filter that left few results, or a contains phrase's words apart), similar (like the named or liked sections) and browse. Each hit has its key, kind of section (role), a one-line summary, novelty from 1 (template) to 5 (experimental), whether it moves, what found it (match.via), screenshot tiles, geometry and links (app: on regards.design; live: the live page). The user sees every hit as a screenshot already; a summary undersells a design, so view_section the two or three you will recommend before judging them, not every hit. Put no images in your reply (the screenshots are shown above it): name the ones you pick and link links.app. Positions are from our capture of the page (page.shotAt, page.viewport, usually 1440×900), not today's live page: y is CSS px from the top of the captured page. geometry.top/height place the section and geometry.left/right are its horizontal crop. images.tiles are its screenshots top to bottom at page.dsf× pixels, each with top/height in section px (0 = the section's top).

search_sections

Sections from any site that look and read like the given ones, by their screenshots and what they show. Use it to widen from hits you liked, or to find alternatives to a section you have. q steers it ("like these but light"); roles, sites, page and contains filter it. It answers like search_sections (same fields and geometry), in one group of kind "similar". Not for a description alone: search_sections takes that, and its like does the same with a query.

similar_sections

See a section: one image of its screenshot tiles stitched top to bottom (every part of a long section), its long edge at most max_px. Use it to judge a section by its pixels before you choose, describe or build from it: the summary is one line. context_px adds that many page px of the sections above and below, from the same capture, with thin magenta lines where the section starts and ends. from_px/to_px show only part of it (section px, 0 = its top), such as a text block's rect from get_section, larger; the image is never scaled past the tiles' own resolution (page.dsf×). The text result maps image px back to page px. Positions are from our capture of the page (page.shotAt, page.viewport, usually 1440×900), not today's live page: y is CSS px from the top of the captured page.

view_section