Find files, editable templates and browser test targets by what you need to make or test. Explore complete business kits for connected records, templates and expected results.
Page 101 of 221; 24 results per page.
A page that names itself canonical while telling robots not to index it, and then contradicts that again with an agent-specific googlebot meta that permits indexing. For testing directive precedence when a page argues with itself.
A deliberately invalid annotation block: `en-UK` is not a region code, `de_DE` uses an underscore, `zz` is not a language, one alternate has no hreflang attribute at all, one drops to http, there is no x-default, and the canonical points outside the cluster. For testing that every defect is reported, not just the first.
A deliberately invalid page carrying two canonical tags in the head and a third in the body. Search engines ignore body-level canonicals entirely and treat multiple head-level ones as a conflict. For testing that an extractor reports position as well as value.
A minimal, valid HTML5 document (doctype, head, and a single heading) for testing HTML parsers, highlighters, and validators against the simplest well-formed page.
A realistic semantic HTML page with landmark elements (header, nav, main, article, footer), a figure with alt text and caption, and lists, for testing HTML parsers, accessibility tooling, and highlighters.
A flat table of the HTML5 constraint attributes: what each applies to, whether the browser enforces it, whether it blocks submission, and one valid and one invalid example. The spreadsheet-shaped twin of the JSON constraint rules.
A machine-readable reference for every HTML5 constraint attribute: which control types accept it, an example that validates, an example that does not, and the behaviour that surprises people. Paired with the constraint-matrix forms in this wave.
SAMPLE htpasswd using Apache APR1 MD5-style hash for legacy Basic-auth tests.
SAMPLE htpasswd with a bcrypt hash line for Basic-auth file parsers.
An Apache/nginx .htpasswd file with two users hashed using the {SHA} scheme (Base64 SHA-1): the sample passwords are documented in the file, for testing Basic-Auth credential parsers and hash identification.
Multi-user SAMPLE htpasswd mixing bcrypt, APR1, and {SHA} lines for algorithm-detection tests.
A humans.txt crediting the people and stack behind a site, in the conventional TEAM/SITE block format, for testing plain-text metadata parsers.
humans.txt: Wave G SAMPLE for crawler and .well-known tooling.
A right-to-left Arabic i18next catalog: real Arabic UI strings for testing bidirectional text handling, RTL layout, Unicode, and font fallback.
A Chinese (CJK) i18next catalog: real Chinese UI strings for testing CJK Unicode handling, wide-character layout, and font fallback.
An i18next translation JSON (English) with {{name}} interpolation and an object-form plural (one/other): the common React/Node i18n catalog shape.
A right-to-left Hebrew i18next catalog: real Hebrew UI strings for testing bidirectional text handling, RTL layout, Unicode, and font fallback.
A Japanese (CJK) i18next catalog: real Japanese UI strings for testing CJK Unicode handling, wide-character layout, and font fallback.
The Spanish i18next catalog twin, for testing i18next loaders, interpolation, and plural resolution against the same keys.
Minimal i18next SAMPLE catalog for locale ar (greeting/save/cancel).
We use Google Analytics and show ads via Adsterra. Non-essential cookies and ad scripts run only after you allow the matching categories. See our cookie policy.
