here is a correct one: https://rdmueller.github.io/maven_asciidoc_build/
I am already fixing this

currently, only posts are in the search index

open question: how to setup the certificate the right way...

[] why docs-as-code
[] (dis)advantages of other approaches (docx, UML, wiki)

On the "Getting Started" page, the name of the gradle build file should be build.gradle, not gradle.build.

see https://github.com/docToolchain/docs-as-co.de/network/dependencies

[] quickstart: use gradle (siehe Kolumne Folge 1)
[] I cannot use gradle: use Docker (to be done)
[] I like it, I want the full package: use docToolchain
[] Additional options: PlantUML, EnterpriseArchitect(tm), Confluence(tm), ... (to be done)

The examples page https://docs-as-co.de/examples shows a broken link to
http://aim42.github.io/htmlSanityCheck/hsc_arc42.html.

and convert them from md to adoc

on docs-page, there should be additional links to arc42

• docs.arc42...
• faq.arc42

Do we need the Google-Analytics imprint? Or do we just drop Google Analytics?

https://github.com/docToolchain/docs-as-co.de/blob/master/docs/_pages/imprint-privacy.md

Ralf, I assume you want the email to point to your gmail address?

You could configure a mail forward with the docs-as-co.de domain...
but our personal addresses would be ok for me too

"unbelivable wisdom"... does that have any deeper meaning? I don't get it...

Now that this repository contains some cool features, we should extract a template from it

don't know if it is just a missing stylesheet or more...

See Quickstart page: https://docs-as-co.de/getstarted/quickstart

Your doc on https://docs-as-co.de/getstarted/tutorial2 starts with

Unresolved directive in tutorial2.adoc - include::feedback.adoc[]

You might want to fix it :)

This issue was generated by todo based on a TODO comment in fb0999d. It's been assigned to @rdmueller because they committed the code.

I host approx 6 websites with different jekyll versions... and don't want to modify my local setup
by calling "bundle install"... as that would surely cause some (negative) side effects...

Maybe "testcontainers" would also be a good idea...

The tutorial under
https://github.com/docToolchain/docs-as-co.de/blob/master/docs/_pages/getstarted/
contains some minor issues.
E.g.

• typo

mkdir tutorial1 
cd tutorial

the last command is missing a '1'

• file overwrite
  gradle initproduces a nice settings.gradle file (in folder tutorial1). The next command echo "include 'docToolchain'" > settings.gradle overwrites it's content with the one-liner.
  append the 'include' statement with >>

• runtime errors due to uncommented line numbers

white on light-gray image is not readable...

Either use a dark image, or a more compact "slug" (my suggestion).

As the existing "summary" is nice, we could move it to a "quotation" on the page itself"

This issue was generated by todo based on a TODO comment in 722a99f when #41 was merged. cc @docToolchain.

... is now included in the build :-)

... but we get lots of errors and warnings

... and when rc2 of HSC is out, the build has to be modified in order to check all files

The font size of the pre-formatted sections on https://docs-as-co.de/getstarted/tutorial2 are too small.
The whole page would benefit from larger fontsizes.

The "You May Also Enjoy" section refers to recommended articles. It seems that the preview images are missing (in Firefox Quantum 66.0.5 (64-Bit) and Internet Explorer 11 on Windows 10, not in Chrome or Edge):

Firefox:

Internet Explorer:

You can find an example on https://docs-as-co.de/news/jax2019/ at the bottom.

need to upgrade to jekyll ~> 3.7.4

will branch and create PR for it!

Hi there,

i would like to ask for assistance. It was very easy (and a nice experience, too ❤️ ) to follow the simple Tutorial on https://docs-as-co.de/getstarted --> The Build-Tool Approach --> Gradle.

calling the asciidoctor task (see below) created the test.html file

After having created the test.html file i wanted to publish that to confluence.

I researched the gradle plugin https://plugins.gradle.org/plugin/de.docs-as-co.publishToConfluence ... but i was not able to find out how to configure it. ... I also looked at http://doctoolchain.org/docToolchain/v2.0.x/015_tasks/03_task_publishToConfluence.html#_configuration ... and tried that ... but i am not doing it the right way 😢

Could you/someone maybe answer with a (configured the right way way 🤷 ⁉️ ) gradle task config for my build.gradle file for the following setup: (the part in the task asciidocToConfluence seems to be improvable 😅 )

Thank you in advance, if you maybe be able to help me!

As an alternative: do you know any github repos that show a working setup for "publishing to confluence"? I then could look at that, and maybe repair it myself ✊

asciidoctor {
  //  sourceDir  file('docs/asciidoc')
  //  sources {
  //	include 'toplevel.adoc', 'another.adoc', 'third.adoc'
  //  }
  //  outputDir  file('build/docs/asciidoc')
}

asciidocToConfluence {
	
	input = [
		[ file: "build/docs/asciidoc/test.html" ],
	]
	
	// endpoint of the confluenceAPI (REST) to be used
	api = 'https://confluence.host.url/rest/api/'
	
	// the key of the confluence space to write to
	spaceKey = '$CONF_SPACE_KEY'
	
	// variable to determine whether ".sect2" sections shall be split from the current page into subpages
	createSubpages = false
	
	// the pagePrefix will be a prefix for each page title
	// use this if you only have access to one confluence space but need to store several
	// pages with the same title - a different pagePrefix will make them unique
	pagePrefix = 'Testtest - '
	
	// username:password of an account which has the right permissions to create and edit
	// confluence pages in the given space.
	// if you want to store it securely, fetch it from some external storage.
	// you might even want to prompt the user for the password like in this example
	
	credentials = "$user:$password".bytes.encodeBase64().toString()
}

https://docs-as-code.netlify.com/publications