GPN19:Documentation with any editor: Unterschied zwischen den Versionen
aus dem Wiki des Entropia e.V., CCC Karlsruhe
(Die Seite wurde neu angelegt: „ Ein Vortrag von Christoph Stoettner auf der GPN19. Creating professional documentation with asciidoctor and some other opensource tools, using the editor…“) |
Keine Bearbeitungszusammenfassung |
||
| Zeile 1: | Zeile 1: | ||
Ein Vortrag von Christoph Stoettner auf der [[GPN19]]. | Ein Vortrag von Christoph Stoettner auf der [[GPN19]]. | ||
Creating professional documentation with asciidoctor and some other opensource tools, using the editor of your choice. I create a pipeline (Jenkins or Gitlab CI/CD) to convert a simple ascii text to any documentation format. So when your project needs | Creating professional documentation with asciidoctor and some other opensource tools, using the editor of your choice. I create a pipeline (Jenkins or Gitlab CI/CD) to convert a simple ascii text to any documentation format. So when your project needs html that’s fine, when your customer needs some PDF and you want to use your company logo that’s nearly the same. You can create multiple outputs from one source, update screenshots automatically and still edit it on any of your devices or editors. Using a pipeline and containers after commiting to a version control system can be used on any operating system, or directly in the cloud. So there is nothing between you and your documentation. | ||
{{Navigationsleiste GPN19:Vorträge}} | {{Navigationsleiste GPN19:Vorträge}} | ||
Version vom 29. Mai 2019, 12:29 Uhr
Ein Vortrag von Christoph Stoettner auf der GPN19.
Creating professional documentation with asciidoctor and some other opensource tools, using the editor of your choice. I create a pipeline (Jenkins or Gitlab CI/CD) to convert a simple ascii text to any documentation format. So when your project needs html that’s fine, when your customer needs some PDF and you want to use your company logo that’s nearly the same. You can create multiple outputs from one source, update screenshots automatically and still edit it on any of your devices or editors. Using a pipeline and containers after commiting to a version control system can be used on any operating system, or directly in the cloud. So there is nothing between you and your documentation.