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

Decide what the editor style guide covers

Open Beginner friendly
  • Is something wrong?
#194 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
documentation

Research direction

Start with docs-llms/core-editor-ui-style-guide.md and check how the guide defines its scope and covers composite controls. Decide whether to document SplitButton alongside them or state that the guide covers tokens and classes only. Done when the guide’s scope is clear.

Written by the indexing model from the issue text.

Description

question

Should the editor style guide also cover components?

Either document SplitButton alongside composite controls or state that the guide covers tokens/classes only.

Done when: The guide scope is clear.

Start: core-editor-ui-style-guide.md. Source: Original §57.

Dominant language
JavaScript
Stars
162
Forks
6
Avg merge
12h 55m
Merged PRs (30d)
2

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

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 tsiger/widgetizer

All issues in tsiger/widgetizer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.