#include-binary directive is not documented in preprocessor section
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- css
- Domain
- documentation
Research direction
Start in the documentation's preprocessor section and look for coverage of the #include-binary directive. Check nearby directive entries for the expected format and details, then document this directive consistently with them. Done means the preprocessor section explains #include-binary.
Written by the indexing model from the issue text.
Description
The title says it all.
- Dominant language
- CSS
- Stars
- 68
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from red/docs
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
What's `#INF`? Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
Similar issues
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
-
Перевод устарел
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
-
affects/8.7 affects/8.8 affects/8.9
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
camunda/camunda-docs#9997 ·
-
Website Doc Typo Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100