Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Decide and execute: Spark-first theme getting-started

Open
#35 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Domain
documentation

Research direction

Start with content/docs/index.mdx and inspect the shared _view-intro-theme snippet used by themes/index.mdx and urls-and-template-paths.mdx. Compare how the current Intro Bootstrap guidance differs from Spark and record the starter decision. Done means the decision is documented and, if Spark is selected, the getting-started and structure pages lead with Spark while retaining Intro Bootstrap as legacy documentation.

Written by the indexing model from the issue text.

Description

Problem: The theme docs still present Intro Bootstrap as the starter: getting-started clones it, the structure diagram shows sass/ and omits directories Spark uses, and Spark appears only in the AI-skills catalog. The public guides now lead with Spark, so the two doc surfaces recommend different starting points.

Evidence: content/docs/index.mdx getting-started step 2; the shared _view-intro-theme snippet injected into themes/index.mdx and urls-and-template-paths.mdx; Spark absent from theme-doc prose.

Done when (decision, then execution):

  • A decision is recorded that Spark is the documented default starter (or explicitly not yet).
  • If yes: getting-started and the structure pages lead with Spark, and Intro Bootstrap is marked as the legacy starter with its docs retained.
Dominant language
MDX
Stars
2
Forks
0
Avg merge
6h 4m
Merged PRs (30d)
13

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NextCommerceCo/developer-docs

All issues in NextCommerceCo/developer-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.