Skip to content

Commit c8f7586

Browse files
committed
Pipeline update
Editor manual update
1 parent bd7df44 commit c8f7586

2 files changed

Lines changed: 2 additions & 7 deletions

File tree

.github/workflows/deploy-docs.yml

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -54,13 +54,6 @@ jobs:
5454
git push origin HEAD
5555
fi
5656
57-
- name: Generate intros and keywords
58-
uses: addnab/docker-run-action@v3
59-
with:
60-
image: mckeea/llm-doc-annotator:latest
61-
options: -e GEMINI_API_KEY=${{ secrets.GEMINI_API_KEY }} -v ${{ github.workspace }}:/app
62-
run: python .github/scripts/generate_intros_and_keywords.py
63-
6457
- name: Build Docs
6558
run: .github/scripts/build-docs.sh
6659

DOCS/guidelines/editor-manual.qmd

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,8 @@ format:
1919

2020
This manual guides users through creating technical documentation for the Copernicus Land Monitoring Service using [**Quarto**](https://quarto.org/). Quarto simplifies the process of writing professional documents in [**Markdown**](https://www.markdownguide.org/), and converting them into **HTML** and **PDF** for nice publishing. The manual covers basic Markdown writing, document rendering, as well a the review, and publication process of technical CLMS documents. It also describes the project folder structure, template usage, and common mistakes to avoid.
2121

22+
If you're responsible for setting up the documentation repository, follow the steps in [Adding Documentation to Your Project](#adding-documentation-to-your-project). Editors can skip this part and continue reading the manual to learn about editing and Markdown syntax.
23+
2224
::: callout-note
2325
You don't need to be a programmer nor an expert to use Quarto. If you've ever written a document in Microsoft Word, you'll be able to use Quarto with a bit of practice.
2426
:::

0 commit comments

Comments
 (0)