This repository holds the documentation for the kabanero-io site. These docs are dynamically pulled in during the Kabanero-website build process.

• Click the fork button to create your fork of the docs repo. Make changes on your fork then open a pull request against kabanero-io/docs:master when you're ready for the changes to be reviewed and merged.

You have 2 options when creating docs: Markdown and AsciiDoc.

• We use Jekyll, which uses the kramdown Markdown renderer, which still supports standard Markdown with some minor modifications.
• We use the Jekyll-asciidoc plugin, which uses Asciidoctor to render AsciiDocs

You need the proper front matter on each doc to get it categorized correctly. The title and the doc-category are the only one you should change for your doc.

• For Markdown, use a YAML front matter

  ---
  layout: general-reference
  doc-category: Configuration
  title: Connecting Kabanero to GitHub with Tekton Webhooks
  ---
  

• For AsciiDoc, use page- AsciiDoc attributes in place.

  :page-layout: general-reference
  :page-doc-category: Configuration
  :page-title: Connecting Kabanero to GitHub with Tekton Webhooks
  :linkattrs:
  :sectanchors:
  

We currently have 3 categories you can use for the doc-category front matter

• Installation
• Reference
• Configuration

If you need a new category feel free to open an issue or discussion in a pull request about the new category.

The doc-categories.adoc file configures the order that the doc categories will show up on our table of contents for the website. Currently the order is

1. Installation
2. Configuration
3. Reference

This file should only be updated if a new category is added.

• If a new category is added you must place your category in the page-categories in order you want it to show up on the site.

Create an a Markdown/AsciiDoc file that contains the documentation in a presentable format. For help on syntax you can view these references.

• Syntax references
  • kramdown syntax
  • AsciiDoc syntax
• Editor options
  • See kramdown live editor
  • See AsciiDoc editor options

If you want to get a doc ready ahead of time, but do not want it published to the site you can still contribute the doc, but be sure to include the published: false front matter. When you are ready to the doc to be published you can remove the published front matter variable.

• For Markdown use published: false
• For AsciiDoc use :page-published: false

To add an image to your AsciiDoc put the image in the img directory. You can reference this image in your AsciiDoc by using the path to the img directory. For example, if you added my_image.png to the img directory you can use that image with the following AsciiDoc syntax: image::/docs/img/my_image.png[My image alt text]. The image will not show for the GitHub preview, but it will be linked on the website when its deployed.

In this repository you shoud place the doc under the folder that best describes the documentation category. These folders located in the ref directory