From 4b584cc9dff93904aedb025434510a5fd838b1f3 Mon Sep 17 00:00:00 2001 From: David Holdeman Date: Sat, 1 Jan 2022 13:54:06 -0600 Subject: [PATCH] Newlines --- Draft-of-new-Documentation-Workflow.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Draft-of-new-Documentation-Workflow.md b/Draft-of-new-Documentation-Workflow.md index a09f1bd5..1ee520b3 100644 --- a/Draft-of-new-Documentation-Workflow.md +++ b/Draft-of-new-Documentation-Workflow.md @@ -6,6 +6,7 @@ When a change is made to the repo, a Github Action automatically builds the wiki For example, in order for user abelom to edit this page: + 1. abelom would start editing at https://github.com/rusefi/rusefi_documentation/blob/master/Documentation_Workflow.md which would automatically create a branch in https://github.com/abelom/rusefi_documentation fork 2. Once changed are made, abelom would create a Pull Request 3. Once that PR is merged into primary rusEFI modified content would appear as https://github.com/rusefi/rusefi_documentation/blob/master/Documentation_Workflow.md @@ -28,11 +29,14 @@ For example https://github.com/rusefi/rusefi_documentation/blob/master/FAQ/image Links to page names use only the name of the page; relative path does not matter. Example: + `[The Documentation Workflow](Documentation-Workflow)` Links to images are relative to the .md file they are in. Example: + `![TunerStudio New Project View](FAQ/images/TunerStudio_new_project.png)` **Q:** What sort of fancy options do we have? + **A:** We can do collapsible sections & hints sections! See [cranking](Cranking) for an example.