Data

Tools

Indexes

Applications

Experiments

Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / w3c/sustyweb issues and pull requests

#127 - 3. Web Development (wording update suggestions)

Issue - State: closed - Opened by andreadavanzo 6 months ago

#126 - Update index.html

Pull Request - State: closed - Opened by augier 8 months ago - 2 comments
Labels: technical

#125 - rework 3.14 and Additional Content

Pull Request - State: closed - Opened by andreadavanzo 9 months ago - 8 comments
Labels: technical

#124 - Incorporate new updates to business/product strategy guidelines

Issue - State: closed - Opened by timfrick 9 months ago - 2 comments
Labels: enhancement

#123 - restore (2 years) to end date

Pull Request - State: closed - Opened by tantek 10 months ago - 1 comment
Labels: technical

#122 - update note on charter and add current Interest Group chartering efforts

Pull Request - State: closed - Opened by tantek 10 months ago - 1 comment
Labels: technical

#121 - [charter] SustyWeb IG charter should coordinate with IETF environmental efforts

Issue - State: closed - Opened by tantek 10 months ago - 1 comment
Labels: technical

#120 - [charter] SustyWeb IG charter should state intended audience of guidance

Issue - State: closed - Opened by tantek 10 months ago - 1 comment
Labels: technical

#119 - editorial: fix link to "on GitHub" to use /ig

Pull Request - State: closed - Opened by tantek 10 months ago - 2 comments
Labels: technical

#118 - Suggested adjustments to IG charter

Pull Request - State: closed - Opened by ianbjacobs 11 months ago
Labels: technical

#117 - Drop "Normative"

Pull Request - State: closed - Opened by ianbjacobs 11 months ago - 1 comment
Labels: technical

#116 - Suggested changes to draft IG charter

Pull Request - State: closed - Opened by ianbjacobs 11 months ago - 1 comment
Labels: technical

#115 - which policies should we add?

Issue - State: closed - Opened by fullo 11 months ago - 3 comments
Labels: enhancement

#114 - Plain English

Issue - State: closed - Opened by AlexDawsonUK 12 months ago - 1 comment
Labels: enhancement

#113 - Educational Materials

Issue - State: closed - Opened by AlexDawsonUK about 1 year ago - 1 comment
Labels: roadmap

#112 - Implementation Report

Issue - State: closed - Opened by AlexDawsonUK about 1 year ago - 2 comments
Labels: roadmap

#111 - Onboarding Improvements

Issue - State: closed - Opened by AlexDawsonUK about 1 year ago - 2 comments
Labels: roadmap

#110 - Greenwashing

Issue - State: closed - Opened by AlexDawsonUK about 1 year ago - 1 comment
Labels: enhancement

#109 - Continuous Emissions

Issue - State: closed - Opened by AlexDawsonUK about 1 year ago - 1 comment
Labels: enhancement

#108 - ESG Term Usage

Issue - State: closed - Opened by AlexDawsonUK about 1 year ago - 4 comments
Labels: technical

#107 - Living Document (Cross-Pollination)

Issue - State: closed - Opened by AlexDawsonUK about 1 year ago - 7 comments
Labels: roadmap

#106 - [charter] Custom Success Criteria for SustyWeb Interest Group and WSG Statement

Issue - State: closed - Opened by tantek about 1 year ago - 1 comment
Labels: roadmap

#105 - [charter] A SustyWeb IG would work better to publish a WSG Statement sooner

Issue - State: closed - Opened by tantek about 1 year ago - 2 comments
Labels: roadmap

#104 - Resort Guidelines based on Impact

Issue - State: closed - Opened by AlexDawsonUK about 1 year ago - 1 comment
Labels: roadmap

#103 - [charter] Focus on environmental issues, over social or governmental ones

Issue - State: closed - Opened by jyasskin about 1 year ago - 2 comments
Labels: question

#102 - [charter] Coordinate with ISO

Issue - State: closed - Opened by jyasskin about 1 year ago - 4 comments
Labels: enhancement

#101 - Define the system boundaries

Issue - State: closed - Opened by chrisn about 1 year ago - 5 comments
Labels: roadmap

#100 - Combine overlapping guidelines

Issue - State: closed - Opened by jyasskin about 1 year ago - 3 comments
Labels: roadmap

#99 - Defend the impact and effort claims

Issue - State: closed - Opened by jyasskin about 1 year ago - 2 comments
Labels: roadmap

#98 - Provide guidance on tradeoffs

Issue - State: closed - Opened by jyasskin about 1 year ago - 3 comments
Labels: roadmap

#97 - Make sure all success criteria are yes/no questions

Issue - State: closed - Opened by jyasskin about 1 year ago - 2 comments
Labels: technical

#96 - Normative references need reviewing

Issue - State: closed - Opened by chrisn about 1 year ago - 4 comments
Labels: technical

#95 - Open Source Tools and GRI Reporting

Issue - State: closed - Opened by chrisn about 1 year ago - 8 comments
Labels: technical

#94 - SDG Targets

Issue - State: closed - Opened by AlexDawsonUK about 1 year ago - 3 comments
Labels: enhancement

#93 - Sustainability Scheme

Issue - State: closed - Opened by AlexDawsonUK about 1 year ago - 6 comments
Labels: roadmap

#92 - Improve Specification Readability

Issue - State: closed - Opened by AlexDawsonUK over 1 year ago - 1 comment
Labels: technical

#91 - New guideline for Business Strategy and Product Management

Issue - State: closed - Opened by iceraluk over 1 year ago - 1 comment
Labels: enhancement

#90 - Why Carbon aware in Mobile first?

Issue - State: closed - Opened by jeanmonod over 1 year ago - 2 comments
Labels: technical

#88 - STAR 1.0 Draft Suggestion -- WD08-1: Validate Source Code for Semantic Accuracy minor rewording suggestion

Issue - State: closed - Opened by airbr over 1 year ago - 1 comment
Labels: technical

#85 - STAR 1.0 Draft suggestion - Remove "The objective of this technique is to" text from most techniques

Issue - State: closed - Opened by airbr over 1 year ago - 1 comment
Labels: technical

#84 - Suggested changes to policies doc

Issue - State: closed - Opened by ianbjacobs over 1 year ago - 1 comment
Labels: enhancement

#83 - Escaping issue in 5.22 Promote and Implement Responsible Emerging Technology Practices

Issue - State: closed - Opened by acme over 1 year ago - 1 comment
Labels: technical

#82 - Update intro.html

Pull Request - State: closed - Opened by gaelduez over 1 year ago - 1 comment
Labels: technical

#81 - Web Sustainability Laws & Policies

Issue - State: closed - Opened by AlexDawsonUK over 1 year ago - 4 comments
Labels: enhancement

#80 - Specification Hotfix Applied - Charter Readiness

Issue - State: closed - Opened by AlexDawsonUK over 1 year ago - 1 comment
Labels: technical

#79 - SC "Performance By Default" meaning is unclear

Issue - State: closed - Opened by thibaudcolas over 1 year ago - 3 comments
Labels: technical

#78 - New SC for 4.9: Event-Driven Architecture

Issue - State: closed - Opened by AlexDawsonUK over 1 year ago - 1 comment
Labels: enhancement

#77 - New SC for 5.27 KPI Budget

Issue - State: closed - Opened by AlexDawsonUK over 1 year ago - 1 comment
Labels: enhancement

#76 - New SC for 5.5 Tooling Impact

Issue - State: closed - Opened by AlexDawsonUK over 1 year ago - 1 comment
Labels: enhancement

#75 - New SC for 5.26 Right-to-Repair

Issue - State: closed - Opened by AlexDawsonUK over 1 year ago - 1 comment
Labels: enhancement

#74 - Proposed guideline: Choose tooling and / or programming language appropriate to the task.

Issue - State: closed - Opened by BezPowell over 1 year ago - 9 comments
Labels: enhancement

#73 - Proposed guideline: Process data close to the source.

Issue - State: closed - Opened by BezPowell over 1 year ago - 5 comments
Labels: enhancement

#72 - New Guideline for Hosting, Infrastructure and Systems: Caching?

Issue - State: closed - Opened by BezPowell over 1 year ago - 5 comments
Labels: technical

#71 - New SC for 3.7: Third-party Preferences

Issue - State: closed - Opened by AlexDawsonUK over 1 year ago - 5 comments
Labels: enhancement

#70 - STAR: Section 2.4 Hosting, Infrastructure and Systems

Issue - State: closed - Opened by mgifford over 1 year ago - 2 comments
Labels: enhancement

#69 - Charter: Do we want to primarily use a mailing list for discussions?

Issue - State: closed - Opened by mgifford over 1 year ago - 4 comments
Labels: technical

#68 - Comment on 2.14 Write With Purpose, in an Accessible, Easy To Understand Format

Issue - State: closed - Opened by airbr over 1 year ago - 4 comments
Labels: enhancement

#67 - New SC for 2.26: Performance Testing

Issue - State: closed - Opened by AlexDawsonUK over 1 year ago - 3 comments
Labels: enhancement

#66 - New SC for 5.22: Environmental Impact

Issue - State: closed - Opened by AlexDawsonUK over 1 year ago - 2 comments
Labels: enhancement

#65 - Terminology: visitors vs. users

Issue - State: closed - Opened by thibaudcolas over 1 year ago - 5 comments
Labels: question

#64 - Terminology: abandonment

Issue - State: closed - Opened by thibaudcolas over 1 year ago - 7 comments
Labels: invalid

#63 - Terminology and understanding of web accessibility

Issue - State: closed - Opened by thibaudcolas over 1 year ago - 4 comments
Labels: technical

#62 - View Source Affordance as a sustainable engineering principle

Issue - State: closed - Opened by airbr over 1 year ago - 4 comments
Labels: enhancement

#61 - Marketing and communication view ?

Issue - State: closed - Opened by www-diogo-in over 1 year ago - 7 comments
Labels: technical

#60 - Checklist visibility

Issue - State: closed - Opened by www-diogo-in over 1 year ago - 3 comments
Labels: technical

#59 - Additionnal resource for 3.9 Resolve Render Blocking Content

Issue - State: closed - Opened by ldevernay over 1 year ago - 2 comments
Labels: enhancement

#58 - Relevance of a criterion for 3.5 Ensure Your Solutions Are Accessible

Issue - State: closed - Opened by ldevernay over 1 year ago - 2 comments
Labels: technical

#57 - Spacing needs to be fixed for resources in 2.18 Take a More Sustainable Approach to Typefaces

Issue - State: closed - Opened by ldevernay over 1 year ago - 1 comment
Labels: technical

#56 - Example for 2.7 Avoid Unnecessary or an Overabundance of Assets

Issue - State: closed - Opened by ldevernay over 1 year ago - 2 comments
Labels: technical

#55 - Example for 2.4 Consider Sustainability in Early Ideation

Issue - State: closed - Opened by ldevernay over 1 year ago - 2 comments
Labels: technical

#54 - Google Lighthouse Plugin

Issue - State: closed - Opened by AlexDawsonUK over 1 year ago - 18 comments
Labels: roadmap

#53 - "Web Workers" may cause confusion

Issue - State: closed - Opened by chrisn over 1 year ago - 1 comment
Labels: technical

#52 - Pull Requests

Issue - State: closed - Opened by AlexDawsonUK over 1 year ago - 1 comment
Labels: roadmap

#51 - Document and Share Project Outputs benefits

Issue - State: closed - Opened by chrisn over 1 year ago - 13 comments
Labels: technical

#50 - Examples with code could have a broader relevance

Issue - State: closed - Opened by thibaudcolas over 1 year ago - 7 comments
Labels: enhancement

#49 - Grammar errors for plural words and abbreviations

Issue - State: closed - Opened by YummyBacon5 almost 2 years ago - 2 comments
Labels: technical

#48 - New content about the `Use Beneficial JavaScript and Its API's` [3.15]

Issue - State: closed - Opened by DocRoms almost 2 years ago - 1 comment
Labels: question

#47 - New content to reduce the Impact of Downloadable or Physical Documents [2.23]

Issue - State: closed - Opened by DocRoms almost 2 years ago - 2 comments
Labels: enhancement

#46 - New content about the non-graphic ways to Interact with content [2.21]

Issue - State: closed - Opened by DocRoms almost 2 years ago - 2 comments
Labels: question

#45 - New content about a sustainable practice to improve loading medias [2.16]

Issue - State: closed - Opened by DocRoms almost 2 years ago - 2 comments
Labels: enhancement

#44 - New Content: 5.22 - Emerging Technologies

Issue - State: closed - Opened by AlexDawsonUK almost 2 years ago - 1 comment
Labels: enhancement

#43 - Sustainable Web Design Relaunch

Issue - State: closed - Opened by AlexDawsonUK almost 2 years ago - 2 comments
Labels: roadmap

#42 - Add metadata to JSON API

Issue - State: closed - Opened by screenspan almost 2 years ago - 2 comments
Labels: technical

#41 - Tree Shaking Is Not Great

Issue - State: closed - Opened by srsgores almost 2 years ago - 1 comment
Labels: invalid

#40 - Avoid optional HTML?

Issue - State: closed - Opened by j9t almost 2 years ago - 5 comments
Labels: enhancement

#39 - Headings case

Issue - State: closed - Opened by j9t almost 2 years ago - 1 comment
Labels: technical

#38 - Impact & applicability of 3.13 Use CSS Preference And Media Queries

Issue - State: closed - Opened by thibaudcolas almost 2 years ago - 3 comments
Labels: technical

#37 - Opportunity to begin to decolonize perspective on user research

Issue - State: closed - Opened by joshkimux almost 2 years ago - 2 comments
Labels: enhancement

#36 - JavaScript is rarely dynamic

Issue - State: closed - Opened by grugnog almost 2 years ago - 4 comments
Labels: technical

#35 - 4.2 / 4.3 (proposal) : add NGINX exemples

Issue - State: closed - Opened by JulienWilhelm almost 2 years ago - 2 comments
Labels: technical

#34 - 3.14 (proposal) : mobile-first should only be applied if relevant

Issue - State: closed - Opened by JulienWilhelm almost 2 years ago - 4 comments
Labels: question

#33 - Update example for 3.14

Pull Request - State: closed - Opened by JulienWilhelm almost 2 years ago - 1 comment
Labels: technical

#32 - Permanent URI – Cool URIs don't change

Issue - State: closed - Opened by signalwerk almost 2 years ago - 2 comments
Labels: question

#31 - Typo in 5.17

Issue - State: closed - Opened by jimmccool almost 2 years ago - 2 comments
Labels: invalid

#30 - Suggestion: add some nuance in 3.6 avoid code duplication

Issue - State: closed - Opened by marie-ototoi almost 2 years ago - 4 comments
Labels: enhancement

#29 - Manual VS Automated Testing

Issue - State: closed - Opened by AlexDawsonUK almost 2 years ago - 9 comments
Labels: enhancement

#28 - Website Audit

Issue - State: closed - Opened by AlexDawsonUK almost 2 years ago - 15 comments
Labels: roadmap