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

Add textlint

Open
#249 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
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale

Research direction

The issue names API reference content but no files, tests, or entry points. Start by locating that content and the project’s content-checking entry point, then use the listed textlint rules and options as the acceptance checklist, including deciding whether stop-words is too aggressive.

Written by the indexing model from the issue text.

Description

We should have some linting on the API reference content to help fix common errors:

textlint rules:
  • alex
  • max-comma (max 3)
  • terminology
    terms: SMTP, Transmissions API etc., SparkPost, MTA, Message Systems, Momentum, Port25, TPS and other protocols, JSON, PHP and other library languages,
  • write-good
    options: weasel, adverbs, so, illusion, cliches
  • spellchecker
  • stop-words (This might be too aggressive for us)
Dominant language
API Blueprint
Stars
18
Forks
9
Avg merge
8d 7h
Merged PRs (30d)
4

Getting set up

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 SparkPost/developers.sparkpost.com

All issues in SparkPost/developers.sparkpost.com

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.