CZON - AI-Native Markdown Content Engine
Quick Start
👤 Website content creators, especially those who want to write in their native language and automatically generate multilingual versions, and dislike complex configurations.
CZON is an AI-native Markdown content engine designed to help content creators streamline their writing workflow. It emphasizes zero-configuration writing by deeply integrating AI technology to automatically handle tasks such as title generation, summary extraction, tag classification, multilingual translation, and site navigation, minimizing user distractions. CZON includes built-in static site generation but primarily focuses on content creation and management rather than complex theme customization. It is suitable for users who want to write in their native language and automatically generate multilingual versions, especially for website content creators who dislike complex configurations.
- ✨ CZON is an AI-native Markdown content engine focused on content creation
- ✨ Offers zero-configuration writing, reducing user interruptions by hiding configurations in the .czon directory
- ✨ Deeply integrates AI to automatically generate titles, summaries, classifications, and navigation
- ✨ Supports writing in native language with AI automatically performing multilingual translation
- ✨ Includes built-in static site generation to build Markdown folders into HTML sites
868 words · ~4 min read
CZON Custom Style Guide
Customization
👤 Front-end developers or website administrators using CZON to build websites, who wish to customize site styles to match brand or personal preferences.
This article details methods for customizing styles in CZON projects by creating a style.css file in the .czony directory and writing CSS code to override default styles or add personalized appearances. The document explains that CZON detects and copies this file to the output directory during build, adding a style link to each HTML page to ensure custom styles load after built-in styles for effective overrides. It provides a list of available CSS variables, such as background colors, text colors, and link colors, and showcases multiple practical examples, like customizing brand colors, adjusting content area width, customizing code block styles, and hiding specific elements. Finally, it emphasizes precautions, such as the filename must be style.css, rebuilding is required after modifications, using CSS variable overrides is recommended, and !important may be needed when CZON uses Tailwind CSS.
- ✨ CZON supports customizing site styles via the .czony/style.css file
- ✨ Custom styles can override default styles or add personalized appearances
- ✨ During build, CZON detects and copies style.css to the output directory
- ✨ A style link is added to each HTML page, with custom styles loading after built-in styles
- ✨ Provides a list of available CSS variables, including light and dark modes
197 words · ~1 min read
Guide to Deploying CZON Static Sites to GitHub Pages
Deployment
👤 Developers using CZON to generate static sites who wish to deploy to GitHub Pages, particularly those needing multilingual support and automated deployment.
This article details how to deploy CZON-generated multilingual static sites to GitHub Pages via GitHub CLI. First, install and log in to GitHub CLI, ensuring repo permissions. Then run the command npx czon@latest config github, which guides users through a series of steps: checking permissions, initializing a Git repository, configuring the remote repository, enabling GitHub Pages and setting it to workflow type, creating or updating the Workflow file, committing and pushing changes, and finally obtaining the Pages URL. The entire process is automated, simplifying deployment.
- ✨ Install and log in to GitHub CLI, ensuring repo permissions
- ✨ Run the npx czon@latest config github command to automate deployment
- ✨ Check and configure the Git repository and remote repository
- ✨ Enable GitHub Pages and set it to workflow type
- ✨ Create or update the Pages Workflow file
280 words · ~2 min read
CZON Site Configuration Guide
Quick Start
👤 Developers or content managers using CZON to build documentation sites, users who need to configure site options and integrate analytics tools.
This document details the methods and options for CZON site configuration. The configuration is located in the options.site field of the .czon/meta.json file, including site.baseUrl (used to generate sitemap.xml and robots.txt), site.title (site title, default value is 'CZON'), site.gaID (Google Analytics Measurement ID), and site.clarityID (Microsoft Clarity Project ID). All configuration items are optional, and changes require re-running czon build to take effect. If baseUrl is not configured, sitemap.xml generation will be skipped; analytics tools will only load after configuring the corresponding IDs, without affecting page performance. The document provides configuration location, available configuration items, complete examples, and precautions to help users easily set up the site.
- ✨ CZON supports configuring site options through the .czon/meta.json file
- ✨ Configuration is located in the options.site field, including baseUrl, title, gaID, and clarityID
- ✨ site.baseUrl is used to generate sitemap.xml and robots.txt, requiring a full URL format
- ✨ site.title is displayed in the page header, with a default value of 'CZON'
- ✨ site.gaID is the Google Analytics Measurement ID, formatted as G-XXXXXXXXXX
339 words · ~2 min read
Embla Carousel Effect Testing Documentation
Content Writing
👤 Front-end developers, web designers, testers, and technical personnel interested in carousel effects.
This document is an instructional guide for testing Embla carousel effects. It first introduces the basic functionality of Embla carousels, including switching between multiple continuous images by clicking arrows or dragging pictures. Then, it points out that inserting text content into the carousel can interrupt its continuity, forming new carousel groups. The document demonstrates this effect with example images (Images 1-5), emphasizing the impact of text content on carousel layout. The core argument is that Embla carousels support flexible image display and user interaction, but attention must be paid to how text content may disrupt continuity. The conclusion is that developers should consider content structure when using Embla carousels to ensure the desired visual effects.
- ✨ Embla carousels are used to test the display effects of multiple continuous images
- ✨ Users can switch views by clicking arrows or dragging images
- ✨ The document includes example images (Images 1-5) to demonstrate the carousel
- ✨ Inserting text content interrupts the continuity of the carousel
- ✨ After text interruption, new carousel groups are formed
56 words · ~1 min read
KaTeX Formula Display Test Document
Content Writing
👤 Developers, educators, and technical document authors who need to test or use KaTeX for rendering mathematical formulas.
This document is a test document for KaTeX mathematical formula display effects, showcasing the rendering of various mathematical formulas. It includes inline formulas such as E=mc², block-level formulas such as integrals and derivatives, complex formulas such as infinite series summations, and special formulas with cases, matrices, and tables. The document also tests formulas with text descriptions and generalized Kelly formulas. All formulas are designed to verify KaTeX's correct display capabilities, suitable for technical documents or educational materials requiring mathematical formula presentation.
- ✨ Test inline formulas such as E=mc²
- ✨ Test block-level formulas such as integrals and derivatives
- ✨ Showcase complex formulas such as infinite series summations
- ✨ Include formulas with cases, matrices, and tables
- ✨ Test formulas with text descriptions
168 words · ~1 min read
Test Document for Internal Links
Content Writing
👤 Website administrators, document maintainers, technical testers
This document is a test document primarily used to verify the correctness of internal links. It provides two test links, one pointing to a KaTeX test document and another to a Mermaid diagram example, along with footnote testing that demonstrates the correct display of footnote content at the bottom of the page. The core purpose of the document is to help users test and verify the internal link functionality, ensuring that links and footnotes work properly on the page.
- ✨ The document is used to test the correctness of internal links
- ✨ Includes two test links: KaTeX test document and Mermaid diagram example
- ✨ Conducts footnote testing to verify footnote content display
- ✨ Link testing helps validate page navigation functionality
- ✨ Footnote testing ensures auxiliary information is correctly presented
95 words · ~1 min read
Guide to Literary and Emotional Style Analysis Reports
Prompt Engineering
👤 Readers who appreciate literary expression, readers seeking emotional resonance
This document is a guide to literary and emotional style analysis reports, detailing how to extract structured information from documents, including reading focuses such as emotional expression, imagery description, and narrative elements; constructing a knowledge base structure covering file indexing, key quote indexing, imagery indexing, etc.; and providing compression strategies, style positioning, core principles, essential chapter structures, and writing techniques. The guide emphasizes the use of vivid language, metaphors, and narrative techniques to evoke emotional resonance in readers, suitable for readers who appreciate literary expression.
- ✨ Extract emotional expression and imagery description
- ✨ Construct a structured knowledge base index
- ✨ Use poetic language and narrative techniques
- ✨ Target literary enthusiast readers
- ✨ Emphasize authenticity and impact
322 words · ~2 min read
Basic Rules for AI Analysis Report Generation
Prompt Engineering
👤 AI developers, document analysts, users of automated report generation tools, and personnel who need to process large numbers of Markdown files and generate structured reports.
This document outlines the basic rules for AI analysis report generation, with core content covering the document reading process (phased file list acquisition, batch reading and summarization, context management, completeness verification, and report generation), general rules (such as the fact-based principle, citation link specifications, header format, and time weighting), and prohibited behaviors. It emphasizes strict adherence to the process, reading all files one by one, generating reports based on facts, and provides specific operational guidelines and examples to ensure the systematicity, accuracy, and completeness of reports.
- ✨ Must read all Markdown files one by one, without skipping any files
- ✨ Adopt a progressive reading and summarization strategy, processing files in batches and managing context
- ✨ Report generation requires segmented writing, ensuring content is within 2000 words and follows format specifications
- ✨ All viewpoints must be supported by original text, prohibiting fabricated content
- ✨ Citation links must use relative paths and link to specific files, with link text as titles
691 words · ~4 min read
Guide to Objective Critical Style Analysis Reports
Prompt Engineering
👤 Readers who wish to deeply evaluate content value, potential collaborators, content creators themselves
This document is a detailed guide on how to write objective critical style analysis reports. It defines the reading focus points, knowledge base structure, compression strategies, style positioning, core principles, required chapter structure, critical framework templates, and quality checklists for analysis reports. The core value lies in guiding users to conduct constructive criticism based on facts, balance strengths and weaknesses analysis, and promote content improvement. The document emphasizes a professional, well-reasoned tone, targeting readers who wish to deeply evaluate content value, potential collaborators, and content creators themselves.
- ✨ Define the core principles and style positioning of objective critical analysis
- ✨ Provide the required report chapter structure and critical framework templates
- ✨ Emphasize constructive criticism based on facts and balanced analysis of strengths and weaknesses
- ✨ Include knowledge base structure and compression strategies to support information extraction
- ✨ Set quality checklists to ensure the professionalism and effectiveness of reports
314 words · ~2 min read
Guide to Historical Time-Span Style Analysis Reports
Prompt Engineering
👤 Researchers, readers, and document analysts who wish to understand the development context of content
This document is a detailed guide on how to write historical time-span style analysis reports, aiming to help users organize content chronologically, analyze evolutionary trends, identify key turning points, and reasonably predict future directions. It defines essential chapter structures such as overview, phase division, key turning points, thematic evolution, and future trajectory prediction, and emphasizes fact-based objective analysis. Core principles include prioritizing the extraction of precise dates, focusing on event correlations and changes, and retention strategies when compressing knowledge bases. The target audience is researchers and readers who wish to understand development contexts, with a writing tone that should be objective, in-depth, and insightful.
- ✨ Organize content based on chronological order, prioritizing the extraction of precise dates
- ✨ Identify key turning points and analyze evolutionary trends
- ✨ Provide essential chapter structures such as phase division and thematic evolution
- ✨ Emphasize objective analysis and reasonable prediction of future directions
- ✨ Target audience includes researchers and readers who wish to understand development contexts
273 words · ~2 min read
Guide to Objective and Neutral Style Analysis Reports
Prompt Engineering
👤 New readers, potential collaborators, and investors who need to quickly understand the overall picture of the repository.
This document is a guide on how to create objective and neutral style analysis reports. It details the key points to focus on when reading documents (such as file paths, dates, project names, character roles, objective facts, etc.) and provides the structure of the knowledge base (including file index, project index, character index, timeline, and theoretical framework index). The document also introduces compression strategies, style positioning (emphasizing objectivity, professionalism, and neutrality), prohibited practices (such as avoiding subjective evaluations and emotional expressions), and required chapter structures (such as overview, project introduction, key themes, timeline, main characters, and theoretical framework summary). Finally, it provides a quality checklist to ensure the report meets requirements.
- ✨ When reading documents, focus on objective information such as file paths, dates, project names, and character roles.
- ✨ The knowledge base structure includes file index, project index, character index, timeline, and theoretical framework index.
- ✨ The report style must be objective and neutral, avoiding subjective evaluations and emotional expressions.
- ✨ Required chapters include overview, project introduction, key themes, timeline, main characters, and theoretical framework summary.
- ✨ Provides a quality checklist to ensure report quality.
321 words · ~2 min read
Guide to Philosophical Speculative Style Analysis Reports
Prompt Engineering
👤 Readers who enjoy deep thinking and philosophy enthusiasts, seeking to enhance cognitive levels.
This document is a guide for philosophical speculative style analysis reports, aiming to instruct how to extract structured information from documents, such as file paths, core propositions, value judgments, and essential inquiries. It details reading focus points, including discussions on themes like existence, freedom, and meaning; provides the structure of the knowledge base, such as file indexes, proposition indexes, and value judgment indexes; and specifies required section structures, such as introduction, proposition analysis, and spiritual portrait. The document emphasizes logical reasoning, references to philosophical theories, and avoids empty terminology accumulation. The target audience is those who enjoy deep thinking and philosophy enthusiasts, with a writing tone that is profound, speculative, and rigorous.
- ✨ Provides reading focus points and knowledge base structure for philosophical speculative analysis
- ✨ Specifies required sections such as introduction, proposition analysis, and spiritual portrait
- ✨ Emphasizes logical reasoning and references to philosophical theories
- ✨ Target audience is deep thinkers and philosophy enthusiasts
- ✨ Writing tone is profound, speculative, and rigorous
297 words · ~2 min read
Popular Science Style Analysis Report
Prompt Engineering
👤 General readers without a professional background, beginners interested in the field
This document is an analysis report on how to write popular science style content, aiming to help authors introduce complex concepts to general readers in a light and friendly tone. The report details reading focus points, knowledge base structure, compression strategies, style positioning, core principles, essential chapter structures, and quality checklists, emphasizing the use of simple language, everyday analogies, and step-by-step approaches to ensure content is easy to understand and suitable for beginners without a professional background.
- ✨ Use simple language and everyday analogies to explain complex concepts
- ✨ Structured knowledge base includes indexes for files, concepts, projects, and application scenarios
- ✨ Target non-specialist readers, emphasizing a light and friendly writing tone
- ✨ Provide essential chapters such as analogical explanations for core projects and core ideas
- ✨ Include quality checklists to ensure content is understandable and free of jargon
263 words · ~2 min read
Guide to Praise and Encouragement Style Analysis Reports
Prompt Engineering
👤 Potential readers interested in the content and the content creators themselves, aiming to spark interest and enhance recognition.
This document is a guide to praise and encouragement style analysis reports, detailing how to extract structured information from documents, including reading focus points, knowledge base structure, compression strategies, style positioning, core principles, required chapter structures, and quality checklists. It emphasizes fact-based positive evaluations, highlights innovations and achievements, encourages readers and creators with a sincere tone, and is applicable to content analysis and report writing.
- ✨ Fact-based positive evaluation and highlight extraction
- ✨ Structured knowledge base indexing including files, innovations, and achievements
- ✨ Required chapters such as opening highlights, core project highlights, and intellectual contributions
- ✨ Target audience includes potential readers and content creators
- ✨ Emphasizes sincere encouragement rather than exaggeration
299 words · ~2 min read
Psychological Analysis Style Report Guide
Prompt Engineering
👤 Readers interested in psychology, those seeking to gain a deep understanding of the author
This document is a psychological analysis style report guide that details how to extract structured information from documents for in-depth psychological analysis. It defines reading focuses, such as the author's self-description, decision-making processes, emotional expression, etc., and provides a knowledge base structure, including file indexing, MBTI evidence indexing, values evidence indexing, etc. The document also explains compression strategies, emphasizing the need to retain core indexes. The analysis framework covers MBTI personality type analysis (including tendency determination, evidence, and conclusions for four dimensions), Schwartz values analysis (prioritized), psychological defense mechanism analysis (including confidence levels and examples), subconscious motivation analysis, interpersonal relationship patterns, and psychological portrait integration. Finally, the document lists a quality check checklist to ensure analysis completeness. The target audience is readers interested in psychology or those seeking to gain a deep understanding of the author, with a professional, analytical, and evidence-based writing tone.
- ✨ Provides a structured framework for psychological analysis, including MBTI, values, and defense mechanism analysis
- ✨ Defines knowledge base structure to support information extraction and compression strategies
- ✨ Target audience is psychology enthusiasts and those needing a deep understanding of the author
- ✨ Emphasizes professional, analytical writing tone and quality checks
357 words · ~2 min read
TODO Extraction Report
Document Analysis
👤 Developers, project managers, or document analysts who need to automate the extraction and management of TODO items from a large number of Markdown documents.
This document is a detailed guide on how to extract TODO items from a large number of Markdown files. It first outlines the document reading process, including four stages: obtaining file lists, batch reading and extraction, context management, and completeness verification. Next, the document defines TODO extraction rules, including the identification of explicit and implicit TODOs, as well as extraction elements such as description, source file, original text reference, and inferred date. The document also provides status judgment rules (e.g., completed, in progress, not started) and priority marking rules (high, medium, low priority). Finally, the document specifies the output format, including header format, overview, and TODO list presentation, and emphasizes citation link standards, segmented writing rules, and prohibited behaviors. The core value lies in providing a systematic method to help users automate the processing of task information from a large number of documents and generate structured reports.
- ✨ The document defines a complete process for extracting TODOs from Markdown files, including four stages: obtaining file lists, batch reading and extraction, context management, and completeness verification.
- ✨ The document details TODO extraction rules, including the identification of explicit and implicit TODOs, as well as extraction elements such as description, source file, original text reference, and inferred date.
- ✨ The document provides status judgment rules (completed, in progress, not started) and priority marking rules (high, medium, low priority) to help categorize and sort TODO items.
- ✨ The document specifies the output format, including header, overview, and TODO list presentation, and emphasizes citation link standards, segmented writing rules, and prohibited behaviors to ensure report quality.
- ✨ The document's core goal is to achieve automated and structured task management by systematically processing a large number of documents to generate accurate and readable reports.
1,228 words · ~6 min read
CZON Document Date Declaration Techniques
Content Writing
👤 Users of the CZON document system, bloggers, diary keepers, content creators
This article introduces an innovative date declaration method in the CZON document system, allowing users to directly declare dates in free format within the document body (e.g., 'Today is January 8, 2026'), with the system automatically recognizing and processing them as document creation dates. Compared to the traditional Markdown approach relying on fixed fields in YAML Frontmatter, this method is more flexible and intelligent, avoiding issues of forgetting to fill in fields. AI automatically extracts and infers date information, suitable for content types like diaries and blogs, and can generate timeline views for easy browsing and management.
- ✨ CZON allows free-format date declaration in the document body
- ✨ Automatically recognizes and processes dates as document creation dates
- ✨ More flexible and intelligent compared to YAML Frontmatter
- ✨ Avoids issues of forgetting to fill in date fields
- ✨ AI automatically extracts and infers date information
📅 2026-01-08 · 140 words · ~1 min read
Mermaid Diagram Test Document
Content Writing
👤 CZON platform developers, testers, and technical personnel interested in Mermaid diagram integration
This document is a test file designed to verify the rendering support for Mermaid diagrams in the CZON platform. It provides examples of various Mermaid diagram types such as flowcharts, sequence diagrams, Gantt charts, class diagrams, state diagrams, and pie charts, showcasing diagram definitions from basic structures to complex applications. Additionally, the document includes an error syntax test to verify the system's ability to handle incorrect diagrams. Through these examples, the document comprehensively tests the functionality and robustness of the Mermaid integration in the CZON platform, ensuring that diagrams render correctly and handle exceptions properly.
- ✨ The document is used to test the rendering functionality of Mermaid diagrams in the CZON platform
- ✨ Includes examples of various diagram types such as flowcharts, sequence diagrams, Gantt charts, class diagrams, state diagrams, and pie charts
- ✨ Each diagram type has specific code examples and descriptions
- ✨ The document includes an error syntax test to verify error handling
- ✨ The Gantt chart example implies a project timeline, starting from 2024-01-01
📅 2024-01-01 · 58 words · ~1 min read