releasehx 0.1.1 → 0.2.0

data/build/docs/index.adoc

@@ -1,27 +1,60 @@
 :page-layout: default
-:page-permalink: /docs
+:page-permalink: /docs/
+:page-title: ReleaseHx Docs
+:page-permalink: /docs/
+:page-title: ReleaseHx Docs
 :page-nav_order: 1
-[[releasehx]]
 = ReleaseHx
 // tag::ai-prompt[]
 // Collects AsciiDoc content for presenting to a generative AI prompt
 // Other AI-only prompt matter could go here
-// tag::globals[]
-:docopslab_git_www: https://github.com/DocOps
-:this_prod_slug: releasehx
-:releasehx_prod_repo: {docopslab_git_www}/{this_prod_slug}
-:releasehx_demo_repo: {docopslab_git_www}/releasehx-demo
-:this_prod_repo: {releasehx_prod_repo}
+// tag::global-settings[]
+:this_proj_slug: releasehx
+:this_proj_name: ReleaseHx
+// tag::universal-settings[]
+:docopslab_src_www_url: https://github.com/DocOps
+:docopslab_domain: docopslab.org
+:docopslab_www_url: https://{docopslab_domain}
+:docopslab_io_www_url: https://docopslab.github.io
+:docopslab_ruby_version: 3.2.7
+:docopslab_src_www_url: https://raw.githubusercontent.com/DocOps
+:docopslab_git_src_uri: git@github.com:DocOps
+:this_proj_src_www_url: {docopslab_src_www_url}/{this_proj_slug}
+:this_proj_src_raw_url: https://raw.githubusercontent.com/DocOps/{this_proj_slug}/main
+:this_proj_src_main_files_url: {this_proj_src_www_url}/blob/main
+:this_proj_src_main_edit_url: {this_proj_src_www_url}/edit/main
+:this_proj_src_git_uri: {docopslab_git_src_uri}/{this_proj_slug}.git
+:this_proj_ruby_version: {docopslab_ruby_version}
+// tag::env-settings[]
+:extn:
+ifdef::env-github[]
+:extn: .adoc
+:icons: font
+:caution-caption: :fire:
+:important-caption: :exclamation:
+:note-caption: :paperclip:
+:tip-caption: :bulb:
+:warning-caption: :warning:
+endif::[]
+// end::env-settings[]
+// end::universal-settings[]
+:releasehx_demo_repo: {docopslab_src_www_url}/releasehx-demo
+// tag::product-settings[]
+:this_prod_slug: {this_proj_slug}
+// tag::version-settings[]
 :this_prod_vrsn_major: 0
-:this_prod_vrsn_minor: 1
-:this_prod_vrsn_major-minor: {this_prod_vrsn_major}.{this_prod_vrsn_minor}
+:this_prod_vrsn_minor: 2
+:this_prod_vrsn_majmin: {this_prod_vrsn_major}.{this_prod_vrsn_minor}
 :this_prod_vrsn_patch: 0
-:this_prod_vrsn: {this_prod_vrsn_major-minor}.{this_prod_vrsn_patch}
-:next_prod_vrsn: 0.2.0
+:this_prod_vrsn: {this_prod_vrsn_majmin}.{this_prod_vrsn_patch}
+:next_prod_vrsn: 0.3.0
+:next_prod_vrsn_majmin: 0.3
+// end::version-settings[]
 :tagline: Generate formatted release histories from Jira, GitHub, GitLab, YAML, or JSON sources.
 :description: pass:q[CLI utility and Ruby API for generating structured release notes and changelog documents from various issue-tracking platforms or YAML definitions into plaintext drafts (*AsciiDoc*, *Markdown*, *YAML*) and rich-text output (*HTML* and *PDF*).]
 :gem_config_definition_path: ./specs/data/config-def.yml
 :app_default_config_path: ./.releasehx.yml
+:docker_run_command: docker run -it --rm --user $(id -u):$(id -g) -v $(pwd):/workdir docopslab/{this_prod_slug} rhx
 // Default configuration values - single source of truth for config-def.yml
 :default_markup: markdown
 :default_slug_type: kebab
@@ -45,19 +78,8 @@
 :draft_source_extensions: {markdown_extensions}, {asciidoc_extensions}, {yaml_extensions}
 :enrich_file_types: HTML, PDF
 :enrich_extensions: .html, .pdf
-:docker_base_command: docker run -it --rm --user $(id -u):$(id -g) -v $(pwd):/workdir docopslab/releasehx rhx
-:this_prod_repo_branch: {this_prod_repo}/tree/release/{this_prod_vrsn_major-minor}
-ifdef::env-github[]
-:docs_extn: .adoc
-:releasehx_www: https://releasehx.docopslab.org
-:releasehx_docs_www: {releasehx_www}/docs
-:default-config_www: {releasehx_docs_www}/sample-config.html
-:this_prod_docs_www: {releasehx_docs_www}
-endif::[]
-ifndef::env-github[]
-:docs_extn: 
-endif::[]
-// end::globals[]
+// end::product-settings[]
+// end::global-settings[]
 :toc: macro
 :toclevels: 3
 
@@ -209,7 +231,7 @@ With Docker installed and running...
 . Run the `rhx` command.
 +
 [.prompt,subs=+attributes]
- {docker_base_command}
+ {docker_run_command}
 +
 This mounts your local directory to be writeable by the Docker container.
 Everything after `rhx` accepts the standard <<rhx,arguments and options>> of the ReleaseHx utility.
@@ -219,7 +241,7 @@ Everything after `rhx` accepts the standard <<rhx,arguments and options>> of the
 Optionally alias the base Docker command.
 
 [.prompt,subs=+attributes]
- alias rhx='{docker_base_command}'
+ alias rhx='{docker_run_command}'
 ====
 
 Try the <<demo-setup,demo configs and data>> to get a feel for how ReleaseHx works.
@@ -265,6 +287,7 @@ It does not provide assistance for command-line actions or other configurations
 For your LLM client (such as Copilot, Claude Code, Codex, Cursor, etc) to interact with this service, it must be configured using a general MCP syntax.
 This data is usually added to a `mcp.json` file or another object.
 
+// 1. This block is totally fine
 Generic MCP config (global gem install)::
 [source,json]
 ----
@@ -277,12 +300,12 @@ Generic MCP config (global gem install)::
 }
 ----
 
+// 2. This block looks totally fine
 Generic MCP config (Docker)::
 +
---
 Use the Docker image for maximum compatibility across environments.
-This is the **recommended approach** for most users.
-
+This is the *recommended approach* for most users.
++
 [source,json]
 ----
 {
@@ -294,13 +317,11 @@ This is the **recommended approach** for most users.
   }
 }
 ----
---
 
+// 3. The first line on this block is white instead of blue like a DL term designator should be
 VS Code MCP configuration (Docker)::
-+
---
 Create or update `~/.config/Code/User/mcp.json` (Linux/Mac) or `%APPDATA%\Code\User\mcp.json` (Windows).
-
++
 [source,json]
 ----
 {
@@ -312,13 +333,11 @@ Create or update `~/.config/Code/User/mcp.json` (Linux/Mac) or `%APPDATA%\Code\U
   }
 }
 ----
---
 
+// 4.This and all the following blocks are improperly highlighted
 VS Code MCP configuration (global gem install)::
-+
---
 If you have ReleaseHx installed globally (`gem install releasehx`), you can use this simpler configuration:
-
++
 [source,json]
 ----
 {
@@ -329,7 +348,6 @@ If you have ReleaseHx installed globally (`gem install releasehx`), you can use
   }
 }
 ----
---
 
 Local repo MCP config (Bundler + cwd)::
 [source,json]
@@ -410,9 +428,11 @@ Global gem::
 
 If your MCP server isn't working in VS Code or Copilot:
 
-. **Verify Docker image exists**: Run `docker images | grep releasehx` to confirm the image is available.
+. *Verify Docker image exists.*
+Run `docker images | grep releasehx` to confirm the image is available.
 
-. **Test MCP server manually**: Run the following to verify the server responds:
+. *Test MCP server manually.*
+Run the following to verify the server responds:
 +
 [.prompt]
 ----
@@ -421,11 +441,14 @@ echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":
 +
 You should see a JSON response with `"serverInfo":{"name":"releasehx-mcp"}`
 
-. **Check VS Code MCP config**: Ensure `~/.config/Code/User/mcp.json` exists and uses the correct command format (see examples above).
+. *Check VS Code MCP config.*
+Ensure `~/.config/Code/User/mcp.json` exists and uses the correct command format (see examples above).
 
-. **Restart VS Code**: After changing `mcp.json`, restart VS Code completely for changes to take effect.
+. *Restart VS Code.*
+After changing `mcp.json`, restart VS Code completely for changes to take effect.
 
-. **Check VS Code logs**: Open Output panel (Ctrl+Shift+U) and look for errors related to MCP or the releasehx server.
+*Check VS Code logs.*
+Open Output panel (kbd:[Ctrl+Shift+U]) and look for errors related to MCP or the releasehx server.
 
 [TIP]
 ====
@@ -1140,6 +1163,203 @@ Templates replace their namesakes built into the ReleaseHx application or API.
 By default, ReleaseHx expects templates to be formatted in link:https://shopify.github.io[Liquid], but it uses the Jekyll-enhanced Liquid 4.
 See <<templating>> for details.
 
+[[styling-customization]]
+==== HTML Styling and CSS Integration
+
+ReleaseHx provides multiple approaches for customizing the appearance of HTML output through the `history.styling` configuration section.
+
+[[styling-modes]]
+===== Styling Modes
+
+The `history.styling.mode` property controls how CSS is applied to HTML output:
+
+`framework` (default)::
+Uses only the configured CSS framework (Bootstrap, etc.) via CDN links.
+No additional custom CSS is included.
+Best for standard, professional appearance with minimal configuration.
+
+`embedded`::
+Includes comprehensive CSS directly in the HTML `<style>` block.
+Generates standalone HTML files that display correctly without external dependencies.
+Automatically includes framework CSS plus custom theming.
+Best for distribution and email-friendly HTML.
+
+`external`::
+References an external stylesheet via `<link>` tag.
+Requires `history.styling.css_url` to specify the stylesheet location.
+Framework CSS is disabled when using external stylesheets.
+Best for custom branding and when CSS needs to be shared across multiple pages.
+
+`minimal`::
+Provides basic semantic styling with minimal inline CSS.
+No framework dependencies or complex styling.
+Best for simple, lightweight output or when CSS will be applied by a static site generator.
+
+[[theme-variants]]
+===== Theme Variants
+
+When using `embedded` or `framework` modes, the `history.styling.theme` property controls spacing and typography:
+
+`default`::
+Balanced spacing and typography for general use.
+
+`compact`::
+Reduced spacing and condensed layout for information-dense displays.
+Ideal for internal documentation or when screen space is limited.
+
+`detailed`::
+Expanded spacing and enhanced typography for presentation contexts.
+Includes larger headings and more prominent metadata display.
+
+[[configuration-examples]]
+===== Configuration Examples
+
+.Framework Mode with Default Theme
+[source,yaml]
+----
+history:
+  html_framework: bootstrap5
+  styling:
+    mode: framework
+    theme: default
+----
+
+.Embedded CSS with Compact Theme
+[source,yaml]
+----
+history:
+  html_framework: bootstrap5
+  styling:
+    mode: embedded
+    theme: compact
+    embed_css: true
+----
+
+.External Stylesheet
+[source,yaml]
+----
+history:
+  styling:
+    mode: external
+    css_url: "assets/custom-releasehx.css"
+----
+
+.Minimal Styling
+[source,yaml]
+----
+history:
+  styling:
+    mode: minimal
+----
+
+[[custom-css-development]]
+===== Custom CSS Development
+
+When using `external` mode, create a CSS file that targets ReleaseHx's semantic HTML structure:
+
+.Key CSS Classes and Elements
+[source,css]
+----
+/* Main containers */
+.release-history { /* Overall wrapper */ }
+.release-section { /* Individual release container */ }
+
+/* Content sections */
+.changelog-section { /* Changelog entries container */ }
+.notes-section { /* Release notes container */ }
+
+/* Individual items */
+.release-note { /* Individual release note */ }
+.change-entry { /* Individual changelog entry */ }
+
+/* Components */
+.card-header, .card-body, .card-footer { /* Note structure */ }
+.change-metadata { /* Metadata display container */ }
+.badge { /* Type/status badges */ }
+----
+
+For a complete example, see the `releasehx-custom.css` file in the https://github.com/DocOps/releasehx-demo[releasehx-demo repository].
+
+[[css-variables]]
+===== CSS Variables for Easy Customization
+
+ReleaseHx's embedded CSS uses CSS custom properties for easy theming:
+
+[source,css]
+----
+:root {
+  --release-spacing: 3rem;    /* Space between releases */
+  --section-spacing: 2.5rem;  /* Space between sections */
+  --item-spacing: 1rem;       /* Space between items */
+  --primary-color: #0d6efd;   /* Brand primary color */
+  --success-color: #198754;   /* Success/changelog color */
+  --info-color: #0dcaf0;      /* Info/notes color */
+}
+----
+
+Override these variables in your external CSS to customize the appearance without rewriting the entire stylesheet.
+
+[[dark-theme]]
+===== Dark Theme Support
+
+ReleaseHx's embedded CSS includes comprehensive dark theme support that automatically adapts to user preferences:
+
+Automatic detection::
+When using `framework: bootstrap5` mode, ReleaseHx includes a detection script that automatically applies dark theme based on system preferences.
+The script listens for system theme changes and updates the display in real-time.
+
+CSS custom properties::
+Dark theme colors are defined using CSS custom properties within a `@media (prefers-color-scheme: dark)` query.
+All color values automatically invert for dark mode while maintaining proper contrast ratios.
+
+Manual override::
+Users can manually toggle dark mode using the `.dark-theme` class on the `<html>` element.
+This overrides system preferences for explicit theme control.
+
+.Dark Theme Configuration Example
+[source,yaml]
+----
+history:
+  html_framework: bootstrap5
+  styling:
+    mode: embedded
+    theme: default
+----
+
+When rendered, the HTML will include:
+
+* Bootstrap 5 with `data-bs-theme` attribute management
+* CSS custom properties for both light and dark color schemes
+* JavaScript to detect and respond to system preference changes
+* Manual theme toggle capability (if you add UI controls)
+
+.Dark Theme CSS Variables
+[source,css]
+----
+@media (prefers-color-scheme: dark) {
+  :root {
+    --bg-color: #1a1a1a;
+    --text-color: #e0e0e0;
+    --border-color: #444;
+    --card-bg: #2d2d2d;
+    --note-bg: #252525;
+    /* Additional dark theme variables */
+  }
+}
+----
+
+For examples of dark theme in action, see the demo configurations in the {releasehx_demo_repo}[releasehx-demo repository], particularly `github-dark-mode.yml` and `github-bootstrap-dark.yml`.
+
+[[html-wrapper-control]]
+===== HTML Wrapper Control
+
+To enable HTML wrapper with CSS, use either:
+
+* Configuration: `modes.html_wrap: true`
+* CLI flag: `--wrap`
+
+The wrapper includes proper HTML document structure, meta tags, and CSS framework loading.
+
 [[sourcing-strategy]]
 === Sourcing Strategy
 
@@ -1581,7 +1801,7 @@ Writes to `<output_path>/<file_template>` or `<PATH>`.
 *--wrap, --no-wrap*::
 {cli_option_message_wrap}.
 When enriching to HTML, _include_ (`--wrap`) or _exclude_ (`--no-wrap`) the `<head>` and `<body>` tags and their content.
-For use when the opposite value is set in the config file ([.ppty]*<<conf_ppty_modes_wrapped>>*).
+For use when the opposite value is set in the config file ([.ppty]*<<conf_ppty_modes_html_wrap>>*).
 
 *--quiet*::
 {cli_option_message_quiet}.
@@ -1723,7 +1943,7 @@ Each item must have a `user` property that matches a username in the Issues syst
 These pertain the to the main configuration file, which is defined specifically for your _application_ of ReleaseHx.
 By default, the application config is found at `{app_default_config_path}.`
 
-The full configuration reference is published at link:{releasehx_docs_www}/config-reference{docs_extn}[].
+The full configuration reference is published at link:{releasehx_docs_www}/config-reference{extn}[].
 
 [[sample-config]]
 === Sample Application Configurations
@@ -1762,7 +1982,7 @@ If you add a non-standard API, please consider <<contributing,contributing it>>
 
 ReleaseHx connects to all upstream REST APIs via YAML-based client configurations.
 
-For reference, the official configs for the three supported REST APIs are at link:{this_prod_repo}/blob/lib/releasehx/rest/clients/jira.yml[jira.yml], link:{this_prod_repo}/blob/lib/releasehx/rest/clients/github.yml[github.yml], and link:{this_prod_repo}/blob/lib/releasehx/rest/clients/gitlab.yml[gitlab.yml].
+For reference, the official configs for the three supported REST APIs are at link:{this_proj_src_www_url}/blob/lib/releasehx/rest/clients/jira.yml[jira.yml], link:{this_proj_src_www_url}/blob/lib/releasehx/rest/clients/github.yml[github.yml], and link:{this_proj_src_www_url}/blob/lib/releasehx/rest/clients/gitlab.yml[gitlab.yml].
 
 To override any of these or to add your own, place a file at `.releasehx/rest/clients/<hostslug>.yml`.
 Make sure it conforms to the schema defined in `specs/data/api-client-schema.yaml`.
@@ -1851,9 +2071,9 @@ Most configuration of output (for drafting or enriching), is handled in the main
 
 For reference, the official mapping configs for the three supported REST APIs are at: 
 
-* link:{this_prod_repo}/blob/lib/releasehx/rest/mappings/jira.yaml[jira.yaml]
-* link:{this_prod_repo}/blob/lib/releasehx/rest/mappings/github.yaml[github.yaml]
-* link:{this_prod_repo}/blob/lib/releasehx/rest/mappings/gitlab.yaml[gitlab.yaml]
+* link:{this_proj_src_www_url_files_path}/lib/releasehx/rest/mappings/jira.yaml[jira.yaml]
+* link:{this_proj_src_www_url_files_path}/lib/releasehx/rest/mappings/github.yaml[github.yaml]
+* link:{this_proj_src_www_url_files_path}/lib/releasehx/rest/mappings/gitlab.yaml[gitlab.yaml]
 
 To override any of these or to add your own, place a file at `.releasehx/rest/mappings/<hostslug>.yml`.
 
@@ -1966,8 +2186,7 @@ For example, if your GitHub issues use labels like:
 Your ReleaseHx application will need an alternate mapping because the default GitHub mapping expects native `issue_type.name` fields.
 
 An example alternate mapping for label-based GitHub type extraction can be found at:
-
-`link:{releasehx_demo_repo}/blob/main/_mappings_/legacy-labels/github.yaml[releasehx-demo/_mappings_/legacy-labels/github.yaml]`
+link:{releasehx_demo_repo}/blob/main/_mappings_/legacy-labels/github.yaml[`releasehx-demo/_mappings_/legacy-labels/github.yaml`]
 
 This mapping includes Ruby logic to:
 
@@ -2060,7 +2279,30 @@ The various sample configurations found in the link:{releasehx_demo_repo}/blob/m
 
 A complete link:{default-config_www}[sample config] displays default values and commented descriptions of all available properties.
 
-[[liquid-extensions]]
+[[template-support]]
+==== Template and Theme Support Policy
+
+The RHYML templates in link:{this_proj_src_www_url_files_path}/lib/releasehx/rhyml/templates/[`lib/releasehx/rhyml/templates/`] are the default templates used for drafting and enriching content.
+
+Templates filenames formatted like `*.{html,yaml,md,adoc}.liquid` all contain expressive markup intended for output.
+We will call these files, such as `changelog.adoc.liquid` and `changelog.html.liquid` _expressive templates_.
+
+All files that are just `<string>.liquid`, such as `changes-sorter.liquid` and `parts-listing.liquid` merely generate data objects and produce express no output to the rendered output.
+We'll call these _parsing templates_.
+
+During pre-1.0 releases, changes made to _parsing templates_ will maintain backward compatibility.
+Deprecations will be announced as early as possible, but we will not change the output of these files except by addition or in the case of a bug, in which case we will change the output to match the documented/expected processing.
+
+When it comes to _expressive templates_, DocOps Lab intends to make incremental improvements and fine tuning.
+
+You will always be able to use the templates from a prior version by dropping them into your local custom-templates directory (`_templates/`) by default, but set using {ppty_conf_paths_templates_dir}.
+
+_After the 1.0 release_, all templates will be kept backward compatible between major releases; so no breaking changes until 2.0, 3.0, etc.
+
+[NOTE]
+This is true of the RHYML domain-specific language, as well.
+We may modify it during pre-1.0 development, but it will be kept backward compatible thereafter.
+
 [[custom-liquid-tags]]
 ==== Custom Liquid Tags
 
@@ -2160,6 +2402,20 @@ Returns a YAML representation of the input for debugging purposes.
 example:::
 `{{ changes | inspect_yaml }}`
 
+[[jekyll-asciidoc-liquid-filters]]
+==== Jekyll/AsciiDoc Liquid Filters
+
+ReleaseHx supports all link:https://jekyllrb.com/docs/liquid/filters/[filters provided by Jekyll 4.4].
+
+It also includes all filters provided by the jekyll-asciidoc plugin.
+
+asciidocify::
+Uses Asciidoctor API to convert a string of AsciiDoc content to HTML.
+
+tocify_asciidoc::
+Generates a table of contents in HTML from the parsed AsciiDoc document of the current page.
+For use outside the context of a full AsciiDoc document, such as in a sidebar or drop-down ToC.
+
 
 [[troubleshooting]]
 == Troubleshooting
@@ -2304,7 +2560,7 @@ To work with ReleaseHx source, clone both repositories side by side for the most
 . Clone both repositories.
 +
 [.prompt]
- git clone {releasehx_prod_repo}
+ git clone {this_proj_src_www_url}
  git clone {releasehx_demo_repo}
 +
 This will give you `<source_dir>/releasehx` and `<source_dir>/releasehx-demo`, side by side.
@@ -2319,9 +2575,9 @@ From the `releasehx` repository:
 [.prompt]
  cd releasehx
  bundle install
- bundle exec rake build
+ bundle exec rake build:gem
 +
-This creates the gem file in the `pkg/` directory.
+This operation generates untracked dependencies during a _pre-build_ stage and compiles the gem file in the `pkg/` directory.
 
 . Install the locally built gem for testing.
 +
@@ -2336,7 +2592,7 @@ Alternatively, for development testing without installing:
 . Run the test suite to verify functionality.
 +
 [.prompt]
- bundle exec rake spec
+ bundle exec rake rspec
 
 [[working-with-the-demo-repository]]
 ==== Working with the Demo Repository
@@ -2456,7 +2712,7 @@ To maintain DRY sourcing, make your changes in the following files:
 To build the documentation locally, run the following command from the project root:
 
 [.prompt]
- bundle exec rake docs
+ bundle exec rake build:docs
 
 This will generate the documentation in the `build/docs` directory.
 
@@ -2475,6 +2731,7 @@ Use `PORT=NNNN` environment argument to specify a different port.
 [.prompt]
  PORT=4000 bundle exec rake serve
 
+[[docopslab-devtool]]
 ==== DocOps Lab Devtool (`docopslab-dev`)
 
 Special dev Rake tasks and libraries are available via the `docopslab-dev` gem.
@@ -2483,7 +2740,7 @@ Special dev Rake tasks and libraries are available via the `docopslab-dev` gem.
 [.prompt]
  bundle exec rake --tasks | grep labdev:
 
-The link:{docopslab_git_www}/lab/tree/main/gems/docopslab-dev/README.adoc[DocOps Lab Devtool] or see `.agent/docs/topics/docpslab-devtool`.
+The link:{docopslab_src_www_url}/lab/tree/main/gems/docopslab-dev/README.adoc[DocOps Lab Devtool] or see `.agent/docs/topics/docpslab-devtool`.
 
 // tag::releasehx-api[]
 [[issue-data-mapping]]

data/build/docs/landing.adoc

@@ -1,6 +1,7 @@
 :page-permalink: /
 :page-layout: minimal
 :page-liquid: true
+:page-nav_exclude: true
 = ReleaseHx
 
 ++++
@@ -10,12 +11,18 @@
       <h1 class="title">
         ReleaseHx
       </h1>
-      <h2 class="subtitle">
-        {{ site.tagline }}
-      </h2>
+      <nav class="top-nav">
+        <a href="/docs/" class="button is-primary is-medium">
+          Documentation
+        </a>
+        &nbsp;|&nbsp;
+        <a href="/docs/releases/" class="button is-link is-medium">
+          Releases
+        </a>
+      </nav>
     </div>
   </div>
 </div>
 ++++
 
-include::index.adoc[tags="globals,intro,features-list"]
+include::index.adoc[tags="global-settings,intro,features-list"]

data/build/docs/manpage.adoc

@@ -4,7 +4,7 @@
 :manpage:
 :man-linkstyle: pass:[blue R < >]
 :toc: macro
-include::../README.adoc[tags="globals,helpscreen_attrs"]
+include::../README.adoc[tags="global-settings,helpscreen_attrs"]
 
 
 [[name]]
@@ -12,7 +12,7 @@ include::../README.adoc[tags="globals,helpscreen_attrs"]
 
 releasehx - {tagline}
 
-*Tip:* Type `q` to exit this page.
+TIP: Type `q` to exit this page.
 
 
 [[aliases]]