Handling of references and definitions with asciidoctor

Centralized configuration management, linting, and development workflows for DocOps Lab repositories

jcn processor for asciidoctor

Geolexica sites generator based on Jekyll

giblish generates indexed and searchable documents from a tree of asciidoc files.

asciidoctor guard

Ingo converts AsciiDoc files in a directory and converts them using Asciidoctor. It is built for collecting notes in AciiDoc format and presenting them.

This plugin is a group of Asciidoctor extensions that perform directory walking, resolving the location of titles and anchors in all adoc files so that inter-document cross-references in a Jekyll project are resolved automatically. Also included are some custom macros and blocks that are useful for techinical writing.

Turn your LinkedIn Profile into a professional resume in many formats (PDF / HTML5 / LaTeX / Asciidoc)

LiquiDoc conveniently harnesses the power of Liquid templates, flat-file data formats such as YAML, JSON, XML, and CSV, as well as AsciiDoc markup and powerful Asciidoctor output capabilities -- all in a single command-line tool.

HTML-formats text documents such as Markdown, textile, and source code

Core library for Metanorma processor registration and plugin dependencies

metanorma-mpfd lets you write MPF documents in AsciiDoc syntax. This gem is in active development.

Metanorma plugin for yaml2text and json2text

Metanorma plugin for glossarist

Metanorma plugin for PlantUML

metanorma-utils provides utilities for the Metanorma stack

natour provides an application and a library to document nature activities.

Asciidoctor extensions by Neo4j.

# Otto AsciiDoc-powered static site generator with Jekyll-style conventions: layouts, includes, data files, posts, drafts, permalinks, and custom collections. ## Install ```sh gem install ottogen ``` Requires Ruby 3.0 or newer. ## Quickstart ```sh mkdir mysite && cd mysite otto init otto build otto serve open http://127.0.0.1:8778/ ``` For a longer walkthrough including AsciiDoc syntax, see [GUIDE.md](GUIDE.md). ## Commands | Command | Description | |---|---| | `otto init [DIR]` | Scaffold a new site (current dir if omitted) | | `otto build` | Render the site to `_build/` | | `otto build --drafts` | Include posts from `_drafts/` | | `otto watch` | Rebuild on file change | | `otto serve` | Serve `_build/` on port 8778 | | `otto generate PAGE` | Create a new page in `pages/` | | `otto post "Title"` | Create a new dated post in `_posts/` | | `otto clean` | Delete `_build/` | | `otto doctor` | Sanity-check project layout | ## Project layout ``` my-site/ ├── .otto # marker ├── config.yml # site config ├── assets/ # copied verbatim into _build/ ├── pages/ # AsciiDoc pages, output mirrors path ├── _layouts/ # ERB layouts (.html.erb) ├── _includes/ # ERB partials ├── _data/ # YAML/JSON files exposed as site.data.* ├── _posts/ # YYYY-MM-DD-slug.adoc └── _drafts/ # undated drafts (excluded by default) ``` ## Configuration (`config.yml`) ```yaml title: My Otto Site description: Things I write url: https://example.com baseurl: "" permalink: /:year/:month/:day/:slug/ collections: recipes: output: true ``` `permalink` accepts these tokens: `:year`, `:month`, `:day`, `:slug`, `:title`. Templates ending in `/` produce pretty URLs (`<path>/index.html`). ## Pages and posts Both support YAML front matter: ```adoc --- layout: default title: Hello tags: [ruby, cli] --- = Hello Welcome to {site_title}. This page is at {page_url}. ``` Pages live under `pages/`; posts under `_posts/` with `YYYY-MM-DD-slug.adoc` names. Layouts wrap rendered AsciiDoc; partials in `_includes/` are pulled in via `<%= partial 'header.html' %>`. ## License MIT