docToolchain / docToolchain/docToolchain

generateDeck: not ported to v4 — evaluate modern slide tooling before porting

Open
#1,645 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Groovy
Stars
864
Forks
240
Avg merge
2m
Merged PRs (30d)
2

Description

`generateDeck` is still a v3 `scripts/generateDeck.gradle` and was **not ported** to a v4 `.groovy` task.

Before investing in a v4 port, note that **slide-from-Markdown/AsciiDoc tooling has matured a lot**: asciidoctor-revealjs, [Marp](https://marp.app/), [Slidev](https://sli.dev/), reveal.js directly. A hand-maintained jBake/Gradle deck task may no longer be the best answer.

**Decision needed:**
- [ ] Port `generateDeck` to v4 as-is, **or**
- [ ] Recommend/integrate a modern tool and document the migration path, **or**
- [ ] Drop it.

For now: leave `generateDeck` unported; this issue tracks the decision. Related: v4 task rollout, DtcException.

Contributor guide

Open the contributing guide

Research direction

Start by reading scripts/generateDeck.gradle and the related v4 task rollout mentioned in the issue. Compare the listed slide-from-Markdown/AsciiDoc tools and determine whether to port, replace, or drop the task; done means the decision and, if applicable, the migration path are documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
groovy, markdown
Domain
build-system, documentation, tooling
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.