-
-
Notifications
You must be signed in to change notification settings - Fork 707
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edit documentation: DR: img tag
#4363
Comments
This comment was marked as outdated.
This comment was marked as outdated.
DR: img tag
This comment was marked as resolved.
This comment was marked as resolved.
DR: img tag
DR: img tag
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
|
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
IssueNone Problem StatementIn our codebase, we are not consistent with whether we apply an ending slash for img HTML tags. Example of code with <img src="/assets/images/404.svg" alt="404"> Example of code with <img class="donate-banner-icon" src="/assets/images/donate/solidarity-pana.svg" alt="" /> Potential SolutionUse the img HTML tag without an ending slash meaning <img...> (Source 1). Feasibility DeterminationThis is feasible because we only use HTML. An ending slash in an img tag is needed for XHTML and XML (Source 2), which we don't use. Sources |
|
Dependency
Overview
We need to edit a decision record
DR: img tag
so that it has content that is helpful in understanding our standards forimg
HTML tags.Action Items
DR: img tag
in the website-wiki with the content in Edit documentation:DR: img tag
#4363 (comment)Resources/Instructions
DR: img tag
#4363 (comment)DR: img tag
in the website-wiki repo: https://github.com/hackforla/website-wiki/blob/main/docs/decision-records/adopted/standardize-html-img-tag.md?plain=1The text was updated successfully, but these errors were encountered: