markojs.com valid

Marko

Marko is a superset of well-formed HTML that makes building web applications fun and productive. It combines HTML with JavaScript syntax features and introduces reactivity for building high-performance web applications with rich client interactions.

For agents: Marko is a JavaScript framework using HTML-superset syntax with reactivity for web apps; the llms.txt links to getting-started, tutorials and full reference doc

marko frameworkjavascripthtml reactivityweb componentsfrontend framework

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T02:44:52.527Z. Cached copy · Source on markojs.com

# Marko

> Marko is a superset of well-formed HTML that makes building web applications fun and productive. It combines HTML with JavaScript syntax features and introduces reactivity for building high-performance web applications with rich client interactions.

Marko's key features include:
- Streaming and high throughput rendering
- Built-in progressive rendering and resumability
- Fine-grained reactivity system
- HTML-based syntax with granular JavaScript integration
- TypeScript support with full type checking
- Zero-JS-by-default with sub-component partial hydration

> **IMPORTANT FOR AI ASSISTANTS**: This documentation is for Marko 6. 
> DO NOT use Marko 5 syntax such as:
> - ❌ `$ let x = 0;` (scriptlets)
> - ❌ `style { ... }` (style blocks)
> - ❌ `class { ... }` (class blocks)
> - ❌ `onClick("handleClick")` (old event handler syntax)
> 
> Instead, use Marko 6 syntax:
> - ✅ `<let/x=0>` or `<const/y=x*2> (tag variables)
> - ✅ `<style>` with standard CSS (style tags)
> - ✅ `onClick() { /* function content */ }` or `onClick=handleClick` (function shorthand / passing)
> 
> `<script>` tags have special meaning, and are similar to effects in React. Use them sparingly, and do NOT declare template-wide state or functions in a `<script>`. Prefer tag variables when possible.

## Full Documentation
- [Reference Documentation](/docs/reference-full.md): Complete reference documentation

## Introduction

- [Getting Started](/docs/introduction/getting-started.md): Quick start guide for new projects
- [Welcome to Marko](/docs/introduction/welcome-to-marko.md): Introduction to the framework
- [Installation](/docs/introduction/installation.md): Installation and setup
- [Why Marko](/docs/introduction/why-marko.md): Performance benefits and core principles
- [Integrations](/docs/introduction/integrations.md): Integration with other tools

## Tutorials

- [Fundamentals](/docs/tutorial/fundamentals.md): Core concepts and syntax
- [Components and Reactivity](/docs/tutorial/components-and-reactivity.md): Building interactive components

## Guides

- [Styling](/docs/guide/styling.md): Styling in Marko applications
- [Library Integration](/docs/guide/library-integration.md): Using third-party libraries
- [Publishing Components](/docs/guide/publishing-components.md): Publishing reusable components
- [Low-level APIs](/docs/guide/low-level-apis.md): Advanced low-level APIs
- [Duplicate Form Submissions](/docs/guide/duplicate-form-submissions.md): Preventing duplicate submissions
- [Using Multiple Marko Versions](/docs/guide/marko-5-interop.md): Interoperability with Marko 5

## Explanation

- [Why is Marko Fast?](/docs/explanation/why-is-marko-fast.md): Architectural performance characteristics
- [Streaming](/docs/explanation/streaming.md): Streaming server-side rendering
- [Targeted Compilation](/docs/explanation/targeted-compilation.md): Compilation strategy
- [Fine-grained Bundling](/docs/explanation/fine-grained-bundling.md): Automatic code splitting
- [Separation o
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=markojs.com · GET /v1/domain/markojs.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for markojs.com:
1. POST https://agentwebmap.com/v1/sites/markojs.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://markojs.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/markojs.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/markojs.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.