Design systems / Website builder
Aura
Explore and edit a complete page before exporting its implementation.
Understand the resource
What it is.
Aura’s primary template documentation describes editable landing-page designs with HTML, CSS and React export. Treat it as a website-building workflow rather than assuming it only produces a design-system file.
When it is useful
You need a concrete marketing prototype and a path to inspect its code.
A proposed application
Put it to work.
This example illustrates a possible use. The proposed workflow and expected result are separate from the bounded checks recorded below.
Try this
Remix an approved template for a product overview, replace sample claims, and audit the exported form and mobile layout.
Result to aim for
A page draft with code available for engineering review.
Before you start
What you need.
- A browser and builder access; export availability depends on the selected workflow.
The practical boundaries
What to watch for.
- Template export does not verify backend behavior, SEO outcomes or accessibility.
- Review template-specific reuse rights and keep confidential project details out of prompts until data handling is cleared.
Review record
What we could establish.
- Public primary documentation reviewed. See the account-free evaluation for executed checks and remaining workflow limits.
The source-review notes describe documentation and identity. The account-free evaluation below records exactly which public interaction or local fixture was checked, what happened, and what remains untested.
Check current access, terms, licensing and data handling before using a resource with your own material.
Runtime and security evaluation
What the evaluation covers.
The Templates link resolved to Aura’s public template route and displayed HTML, CSS and React template guidance. This confirms navigation to the public catalog, not editing or export.
Methods: Public HTTP response · Public browser sample. A completed check covers the stated sample; it is not a safety certification.
- Target
- https://www.aura.build/
- Version or capture
- Unversioned public page observed on 2026-10-19
- Integrity scope
- sha256:18fc5a884f975e79b4c1315b412b298eab204ba0bae63c3c1ddd13e3ece35ae2 — initial HTTP 200 response body only; not whole-application integrity.
Test conditions
- Chromium 155.0.8059.82, 1365×900 desktop viewport.
- Separate fresh, ephemeral browser contexts for entry and interaction; no owner profile, credentials or stored session.
- Only GET/HEAD network requests allowed; forms, downloads, WebSockets and service workers blocked. Some analytics endpoints also blocked.
- Short bounded waits; no mobile, assistive-technology, cross-browser or performance certification.
Individual checks and observations
Public HTTP response
passPublic HTTP response: Anonymous GET with redirects followed, response-body SHA-256 and selected security-header summaries; no cookies retained.
Observed: The standalone client received 200 at https://www.aura.build/. This establishes response delivery only.
Fresh browser entry
passPublic browser sample: Open the catalog URL in a new anonymous Chromium context with read-only network guards and no inherited profile.
Observed: The document returned 200 and identified itself as “Create Beautiful Landing Pages with AI | Aura”. 2 image elements were present; no account was used.
Observed public sample or navigation
passPublic browser sample: Follow the observed Templates link to https://www.aura.build/browse.
Observed: The destination returned 200; title: “Edit & Export Aura Templates for HTML, CSS & React | Aura”. 2 page image elements had decoded during the bounded wait. This count is not a catalog size or performance benchmark.
Security findings and boundaries
Passive inspection of the initial public document’s response headers and anonymous browser request hostnames, with read-only guards. No source exploitation, account access, dependency audit or private data.
Observed · info
Public response protections
The initial browser page used HTTPS. Its response included HSTS. An enforcing CSP response header declared frame-ancestors, object-src, base-uri. X-Frame-Options was DENY. This records the sampled response only; meta policies, backend authorization and exploit resistance were not assessed.
Observed · info
Request surface in the anonymous visit
Aura attempted requests to 8 additional hosts, including cdn.jsdelivr.net, fonts.googleapis.com, www.googletagmanager.com, cloud.umami.is. Host counts include requests stopped by the test guard; they do not establish what data a service retained.
Practical advice · caution
Before using this reference
Check an actual template’s responsive states and license before relying on its advertised export format.
Practical caveats
- Check an actual template’s responsive states and license before relying on its advertised export format.
- Template export does not verify backend behavior, SEO outcomes or accessibility.
What remains untested
- No prompt was submitted, editor session created, template purchased or code exported. Only two page images had decoded during the bounded visit; catalog completeness was not established.
- Results describe the observed public pages and a bounded action, not the entire product or the referenced designs.
Security limits
- No authentication, authorization, tenant separation, data retention or backend handling was tested.
- Header presence or absence is a sampled configuration observation, not a security certification or an exploit finding.
- 7 blocked-request records were retained across entry and interaction checks. Guards may alter normal page behavior; the logs do not represent unrestricted traffic.
Evaluation sources
Follow the evidence
Sources and further reading.
Keep exploring
More in design systems.
Documentation reviewed
Refero Styles
Turn a visual reference into a starting system an agent can read.
Documentation reviewed
Fudge
Bring references, website feedback and design work into a conversational workspace.
Documentation reviewed
DesignMD
Inspect a website’s visual system before drafting new screens.