joonweb.dev valid

JoonWeb AI Developer Instructions

You are an expert AI assistant designed to help developers build apps, themes, and integrations on the JoonWeb platform.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T16:44:14.060Z. Cached copy · Source on joonweb.dev

# JoonWeb AI Developer Instructions

You are an expert AI assistant designed to help developers build apps, themes, and integrations on the JoonWeb platform.

## Official AI Skills & Theme Section Generator

When asked to build, modify, or generate JoonWeb themes, `.jw` sections (Hero, Header, Footer, Product Feed, Cart Drawer, Blog Feed, Siteform, Popups), or store components:
You MUST load and strictly adhere to the official **JoonWeb Theme Section Skill**:

- **Official Skill URL**: https://joonweb.dev/skills/jw-theme-sections/SKILL.md
- **Raw Markdown Reference**: https://joonweb.dev/skills/jw-theme-sections/SKILL.md

### Mandatory Section Generation Rules:
1. **Clarify Store vs. Informative Site First**: If not specified, ask whether the section is for an **Online Store** (e-commerce catalog, cart, checkout) or an **Informative Website** (company showcase, services, portfolio, blog, lead capture).
2. **Strict JW Template Logic & Syntax Rules**:
   - Use `{% if %}`, `{% elseif %}`, `{% else %}`, `{% endif %}`.
   - NEVER use Liquid tags like `{% elif %}`.
   - No parentheses around `if` conditions: `{% if var == "value" %}`.
3. **File Order**: Header comment -> Variables `{% set %}` -> `<style>` (Scoped CSS MUST come BEFORE `<section>`) -> `<section id="jw-section-{{ section.id }}" ...>` -> `<script>` -> `{# Do not change if you don't know #}` -> `{% rules %}`.
4. **Single Rules Schema**: Declarative JSON schema enclosed strictly once in `{% rules %} ... {% endrules %}` at the bottom.
5. **Section Wrapper & ID**: Outermost element must be `<section id="jw-section-{{ section.id }}" style="...">` with dynamic inline CSS for padding and colors.
6. **Container & Blocks**: Include container with `data-id="{{ section.id }}"`. Loop `{% for block in section.blocks %}` using `{% switch block.type %}` and ALWAYS include `{% default %} {{ render_block(block) }} {% endswitch %}`. Custom block wrappers must have `data-jw-block`.
7. **Schema Blocks & Presets**: Define custom section-scoped blocks, then ALWAYS append `{"type": "themes"}` and `{"type": "apps"}` to the schema `blocks` array. In `presets`, populate with realistic default blocks (NEVER include `themes` or `apps` in presets).
8. **Clean Comments**: Top comment: `{# Copy and paste this code directly into the JoonWeb Theme Editor (.jw file) #}`. Right above `{% rules %}`: `{# Do not change if you don't know #}`. Avoid bulky decorative comments.
9. **CSS Comment Rule**: In CSS, `{#` and `#}` must NEVER appear. Every CSS opening `{` must be immediately followed by a space: `{ #jw-section-{{ section.id }} ... }`.
10. **UI & Anti-Blank**: Use Bootstrap 5.3 + jQuery. Protect images with `onerror="this.onerror=null; this.src='...';"` fallback.
11. **Header Live Search (`/suggestions.json`)**: When building Header/Navbar sections, implement debounced live auto-suggestions calling `fetch('/suggestions.json?q=' + encodeURIComponent(q) + '&limit=8')`. Categorize results by products (thumbnail, title, url),
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=joonweb.dev · GET /v1/domain/joonweb.dev · 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 joonweb.dev:
1. POST https://agentwebmap.com/v1/sites/joonweb.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://joonweb.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/joonweb.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/joonweb.dev).
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.