# Regor's Documentation Site Rebuilt With PureStack, Its Own Successor Framework The maintainer of the build-less TypeScript UI library says the redesigned Regor site is generated entirely with PureStack, which uses Regor as its reactive engine — a two-way dependency he presents as his pre-AI and AI-assisted projects powering each other. Canonical URL: https://freelancenews.online/news/regor-s-documentation-site-rebuilt-with-purestack-its-own-successor-f231dbf2 Published: 2026-10-08T06:17:50.705Z Updated: 2026-10-08T06:17:50.705Z Source published: 2026-10-08T06:00:30.000Z Event date: Not established Review status: source-reviewed Review method: Automated comparison against retrieved source text; not independent fact-checking. ## Report The developer behind Regor, an open-source TypeScript reactive UI library, has published a redesigned website and documentation site for the project and states that the site is built entirely with PureStack, a separate open-source frontend framework he also maintains. The announcement appeared as a community post on dev.to. The Regor GitHub repository separately states that its documentation sources live in a docs-site directory built with PureStack. Both statements come from the same author, so the arrangement is an author claim rather than an independently verified fact. The relationship between the two projects is the substance of the announcement. According to the post, PureStack uses Regor as its reactive UI engine, and the new Regor site now runs on PureStack — meaning each project depends on the other in some capacity. The author frames this as two generations of his own engineering work complementing each other, and says both are independent, MIT-licensed open-source projects. The post draws a generational line between the two codebases. The author says he began developing Regor in August 2023, before AI coding agents became a significant part of his workflow, and that its reactive engine was designed and implemented by hand. PureStack, by contrast, is described as a newer framework produced with an AI-accelerated workflow. No dates are given for PureStack's creation, and the post does not quantify how much of either project was AI-assisted. The new site is said to consist of documentation, API references, directive guides and interactive examples. PureStack's static site generation and component capabilities are showcased here, according to the author, in what is described as a further real-world example. The repository's own link list names website and documentation, getting started, an API reference and an online playground, and identifies docs-site as the location of the documentation sources. Regarding the site's launch date, neither source provides one beyond the publication of the post itself. Regor's technical pitch is a deliberate departure from Virtual DOM frameworks. The repository states that reactive changes update the actual DOM directly, that components and application logic use standard TypeScript rather than framework-specific file formats, and that no build step is required — templates can be written as tagged string templates and evaluated at runtime via npm, CDN ESM or a global build. The author's post repeats the no-Virtual-DOM and TypeScript-first points and adds progressive enhancement: reactivity can be added to existing HTML without replacing the DOM. The template syntax will look familiar to Vue users. Regor ships directives prefixed with r-, including r-if, r-for, r-model, r-bind, r-text, r-html, r-on, r-show, r-else, r-else-if and r-pre, plus shorthands for binding and events. The repository documents that the prefix itself is configurable — RegorConfig.getDefault().setDirectives('v-') is given as an example of aligning with Vue's naming convention. The repository also states that Regor is openly inspired by Vue's concepts while diverging in implementation. Reactivity control is where the repository makes its most specific claims. It lists ref for deep in-place reactivity, cref for copy-first deep reactivity and sref for shallow reactivity without nested observation, alongside batch, startBatch, endBatch, pause, resume, trigger, entangle and unref. The stated intent is explicit state orchestration rather than automatic proxy-based tracking. The repository also documents computed, computeMany, watchEffect, collectRefs, observe, observeMany and observerCount, plus persist for reactive local-storage persistence. Two features stand out for teams working inside existing applications. The repository describes static-first plus islands — binding to existing DOM without removing server-rendered HTML — and 'reentrance', the ability to mount multiple times over already-mounted regions with the same or different app contexts. It also claims compatibility with other libraries that manipulate the DOM. These are the claims most relevant to incremental adoption, and they are the ones a prospective adopter would need to test directly. On security, the repository states that Regor includes a secure JavaScript VM for runtime compilation that can operate under a strict Content Security Policy, and shows a meta tag example using require-trusted-types-for 'script'. The stated benefit is that runtime compilation need not be removed to satisfy a security policy — a common friction point for frameworks that compile templates in the browser. This is a vendor claim about the project's own implementation, not an independent audit. The repository also documents runtime prop validation through head.validateProps(...) with a pval helper set, including isString, isNumber, isBoolean, isClass, optional, nullable, or, oneOf, arrayOf, shape, refOf, describe and fail. Validation is opt-in and local to the component author, validates only listed keys, does not coerce values and does not mutate head.props. Behavior is governed by RegorConfig.propValidationMode, with 'throw' as the default, 'warn' to report through warningHandler and continue, and 'off' to skip validation. Table templates get special handling. The repository says Regor preprocesses table-related markup so components remain valid inside table structures, normalizing component tags under row containers to valid hosts and under tr to td hosts, with exceptions for native td, th and col elements. Supported containers listed are table, caption, colgroup, thead, tbody and tfoot. The repository gives a TableRow and TableCell example using r-for over rows. The repository's comparison with Vue is the maintainer's own characterization of a competing framework, not a measured benchmark. It argues Vue's Virtual DOM suits highly dynamic single-page applications but usually requires a compilation step and can be strict about hydrating server-rendered HTML, while Regor binds directly to the real DOM and supports mounting over existing server-rendered markup. It also argues Vue's proxy-based reactivity is easier for beginners while Regor's manual controls give engineers finer orchestration. No performance figures accompany any of these statements. For freelancers and developers evaluating a UI library for client work, the practical question is whether Regor's build-less, runtime-compiled model fits projects where a bundler is unwanted or where markup is already server-rendered. The documented CSP support and configurable directive prefix are the kind of details that matter in enterprise or legacy contexts. The tradeoff the repository itself implies is that manual reactivity control demands more discipline than automatic proxy tracking, and that a smaller ecosystem means fewer third-party components and less community troubleshooting than Vue offers. The two-way dependency between the projects is worth flagging as an editorial observation rather than a criticism. A documentation site generated by a framework that itself depends on the library being documented is a genuine integration test, but it is also a closed loop: it demonstrates the two projects working together, not either one working in an unrelated production environment. The author invites technical feedback specifically on Regor's direct-DOM reactive architecture, which suggests the architecture is the part he considers least settled. Several things remain unknown from the supplied evidence. There is no stated release version for the new site, no pricing or commercial offering, no independent performance measurement, and no third-party adoption data. The post gives no date for PureStack's initial release and does not quantify AI involvement in either codebase. The repository's Vue comparison contains no benchmarks, and the security claims about the JavaScript VM are not backed by an external review in the material provided. The announcement is best read as a maintainer's progress note with a concrete artifact attached: a documentation site that now exercises PureStack's static generation and component model. For developers curious about build-less TypeScript reactivity, the repository's directive list, reactivity primitives and prop-validation API are documented in enough detail to assess fit before installing anything. The claims about CSP compliance, reentrance and DOM compatibility are the ones that would need hands-on verification in a real project. ## Key points - The author states the new Regor website and documentation site is built entirely with PureStack, which in turn uses Regor as its reactive UI engine — a two-way dependency between his two MIT-licensed projects. - Regor is documented as a build-less, TypeScript-native UI library that binds directly to the real DOM instead of using a Virtual DOM, with Vue-style r- directives and a configurable prefix. - The repository claims a secure JavaScript VM allows runtime template compilation under a strict Content Security Policy, plus static-first islands and 'reentrance' mounting over existing server-rendered markup. - Runtime prop validation is opt-in via head.validateProps with pval helpers, governed by a propValidationMode setting defaulting to 'throw', with 'warn' and 'off' alternatives. - The repository's comparison with Vue is the maintainer's own characterization and includes no benchmarks or independent measurements. ## Practical implications — editorial interpretation For freelancers and developers who want reactivity without a bundler or who need to add interactivity to existing server-rendered HTML, Regor's documented no-build workflow, configurable directive prefix and claimed CSP-compatible runtime compilation are the details worth evaluating first. The tradeoff is a smaller ecosystem and a manual reactivity model that requires more deliberate state orchestration than Vue's automatic proxy tracking. ## Limitations and unknowns All evidence comes from the project author's own post and repository, so the PureStack-built site, the CSP security claim and the Vue comparison are unverified vendor statements with no independent testing or benchmarks. No release version, launch date for the site, pricing or third-party adoption data is provided, and PureStack's own release timeline is not stated. ## Sources - [1] dev.to: Regor's New Website Is Live and Built with PureStack https://dev.to/purestack/regors-new-website-is-live-and-built-with-purestack-15le Retrieved: 2026-10-08T06:17:01.755Z - [2] github.com: Regor https://github.com/PureStackStudio/Regor Retrieved: 2026-10-08T06:17:02.684Z ## Claim references - The author says the new Regor website is built entirely with PureStack, which uses Regor as its reactive UI engine. [source 1] - The Regor repository states its documentation sources are in docs-site and built with PureStack. [source 2] - Regor is described as binding directly to the real DOM rather than using a Virtual DOM layer. [source 2] - The repository claims a secure JavaScript VM enables runtime compilation under a strict Content Security Policy. [source 2] - Prop validation behavior is controlled by RegorConfig.propValidationMode, with 'throw' as the default and 'warn' and 'off' as alternatives. [source 2] - The author states he started developing Regor in August 2023, before AI coding agents became a major part of software development. [source 1]