creativecommons / creativecommons/vocabulary

[Bug] Raw > Should Be Encoded as > in Vocabulary Documentation

Open
#285 4 comments 0 reactions 0 assignees View on GitHub
🏁 status: ready for work 💻 aspect: code 🛠 goal: fix 🟩 priority: low
Dominant language
HTML
Stars
23
Forks
84
Avg merge
1d 9h
Merged PRs (30d)
3

Description

## Description

The vocabulary/docs folder contains validation errors in HTML files, specifically related to improper character encoding and trailing whitespace. These issues may affect the rendering and validation of the documentation.

## Reproduction

1. Navigate to the vocabulary/docs folder in the project.
2. Run an HTML validation check using the html-validate tool on the docs/index.html file.
3. Review the error messages generated during validations.

## Expectation

HTML Errors:

- Error 1: Raw > must be encoded as ">";
File: docs/index.html
Line: 415

## Screenshots

## Environment

- Device: (_eg._ iPhone Xs; laptop)
- OS: (_eg._ iOS 13.5; Fedora 32)
- Browser: (_eg._ Safari; Firefox)
- Version: (_eg._ 13; 73)
- Other info: (_eg._ display resolution, ease-of-access settings)

## Additional context

These validation errors appear in multiple HTML files throughout the vocabulary/docs folder. Addressing these issues will improve the documentation's compliance with HTML standards.
## Resolution

- [x] I would be interested in resolving this bug.

Contributor guide

Open the contributing guide

Research direction

Start with vocabulary/docs/index.html at line 415 and run html-validate as described in the issue. Inspect the other HTML files in vocabulary/docs for the reported character-encoding and trailing-whitespace errors; done means the validation errors are resolved across the affected documentation files.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
documentation
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.