{
"faq": {
"hero": {
"badge": "FAQ",
"title": "Frequently Asked Questions",
"subtitle": "Everything you need to know about No.JS."
},
"search": {
"placeholder": "Search the FAQ"
},
"sidebar": {
"questions": "Questions",
"gettingStarted": "Getting Started",
"coreConcepts": "Core Concepts",
"comparisons": "Comparisons",
"security": "Security & Production",
"resources": "Resources",
"documentation": "Documentation",
"examples": "Examples",
"discord": "Discord Community"
},
"gettingStarted": {
"title": "Getting Started",
"q1": {
"question": "What is No.JS?",
"answer": "An HTML-first reactive framework. State, data fetching, routing, i18n, animations: all declared through HTML attributes. Validation and drag-and-drop are now available via NoJS Elements. Zero dependencies, no build step."
},
"q2": {
"question": "How do I get started?",
"answer": "Add one script tag:
<script src=\"https://cdn.no-js.dev/\"></script>
No build step, no package manager. Start writing attributes."
},
"q3": {
"question": "Do I need to know JavaScript?",
"answer": "Basic knowledge helps for writing expressions in attributes, but you won't write JavaScript files. Everything is declarative: state, bind, on:click, each.
For advanced use cases like custom filters or directives, you'll write some JS. The goal is to reduce, not eliminate."
},
"q4": {
"question": "Can I use it with existing projects?",
"answer": "Yes. Add the script tag to any HTML page. No.JS only processes elements with its attributes, so it won't interfere with existing code or other libraries. Progressive adoption by design."
}
},
"coreConcepts": {
"title": "Core Concepts",
"q5": {
"question": "How does reactivity work?",
"answer": "JavaScript Proxy objects. When you declare state, the framework wraps your data in a Proxy. On every property change, the set trap notifies registered watchers, which update the DOM directly. No virtual DOM, no diffing."
},
"q6": {
"question": "What about computed state and async data?",
"answer": "Computed: computed + expr recalculates automatically when dependencies change.
Async: get, post, put, patch, delete fetch data into the reactive context. Use into to pipe results to a global store.
Batching: multiple changes in the same cycle are deduped. Watchers fire once."
},
"q7": {
"question": "What features are included?",
"answer": "Everything ships in one file:
• Reactive state and computed properties
• SPA routing with lazy loading
• Declarative HTTP (GET, POST, PUT, PATCH, DELETE)
• i18n with external locale files
• Form validation (Now in NoJS Elements)
• Animations and transitions
• Drag and drop (Now in NoJS Elements)
• 32 built-in filters"
},
"q8": {
"question": "What's the right use case?",
"answer": "Landing pages, dashboards, internal tools, prototypes, anything where you need reactivity without the ceremony of a full framework.
If business logic stays in the backend where it belongs, the frontend never needs to be complex enough to justify a heavy framework."
}
},
"comparisons": {
"title": "Comparisons",
"q9": {
"question": "No.JS vs Alpine.js?",
"answer": "Alpine is reactive and lightweight, but lacks declarative HTTP, SPA routing, i18n, and built-in filters.
No.JS covers the full lifecycle: fetch, bind, loop, route, animate, all through HTML attributes. Form validation and drag-and-drop are available via NoJS Elements."
},
"q10": {
"question": "No.JS vs HTMX?",
"answer": "HTMX excels at server-driven HTML. It assumes a backend that returns HTML fragments.
No.JS works with any API (JSON endpoints, REST, public APIs) without requiring a server to template responses. Different philosophy: HTMX extends the server, No.JS extends the browser."
},
"q11": {
"question": "No.JS vs React or Vue?",
"answer": "React and Vue require a build step, a virtual DOM, and JavaScript files. No.JS requires none of that.
HTML files vs compiled bundles. Deployment means uploading HTML, not configuring a pipeline."
},
"q12": {
"question": "This reminds me of AngularJS. Is it similar?",
"answer": "Same intuition: bring web development back to HTML. Different execution: zero dependencies, no complexity spiral.
No.JS stays intentionally small and focused on the use cases where a full framework is overkill."
}
},
"security": {
"title": "Security & Production",
"q13": {
"question": "How does No.JS handle security?",
"answer": "Three layers of protection:
• HTML sanitization: strips <script> tags, event handlers, and javascript: protocols
• Scope isolation: each component's context is isolated via Proxy
• CSP-safe by default: expressions are evaluated by a custom parser — no eval() or Function() constructor is used"
},
"q14": {
"question": "How big is the bundle?",
"answer": "It includes reactivity, routing, data fetching, i18n, animations, and 32 filters. Drag-and-drop and form validation are now in NoJS Elements. Zero dependencies."
},
"q15": {
"question": "Do I need a build step?",
"answer": "No. One script tag, zero configuration. No compilation, no transpilation, no bundling. Deployment is uploading HTML files."
},
"q16": {
"question": "Is it production-ready?",
"answer": "Yes. 1,350+ unit tests, tested across modern browsers. This documentation site is built entirely with No.JS."
}
},
"cta": {
"title": "Still Have Questions?",
"subtitle": "Check the documentation or join the community.",
"docs": "View Documentation",
"discord": "Discord Community"
}
}
}