Sustainability improvements
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 12
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Improvements across three key areas for Wagtail sites’ carbon footprints: measurements, awareness, tangible reductions. To see widespread improvements across Wagtail’s ecosystem, for example in how Wagtail sites score on digital carbon ratings:
Intended outcome
Exact improvements to be determined. Current plans:
- 🔍 Measure the carbon footprint of Wagtail
- Create a methodology to measure the carbon footprint of Wagtail websites
- Measure the carbon footprint of building Wagtail: Wagtail events
- Establish a methodology to collect data about how many Wagtail websites there are and their characteristics
- 📣 Spread the word
- Create a sustainability team for Wagtail
- Refine Wagtail’s current sustainability statement, and make it more visible
- Publish case studies on tackling sustainability-related requirements on Wagtail projects
- 📉 Reduce the carbon footprint of Wagtail
- Scale-to-zero CMS database
- Scale-to-zero CMS server
- Light YouTube embeds
- Reporting of performance scores in the CMS
- Starter templates focused on sustainability
- Support for static sites with 90+% of CMS features
More information
- RFC 90: Sustainability roadmap
- Sustainability considerations for Wagtail sites #38
- sustainability roadmap #64
- Introducing our grid-aware websites project
- GSoC 2024: Low-carbon project templates
To deliver this roadmap item, we are looking for a feature sponsorship ❤️.
Contributor guide
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.
Research direction
Start by reading RFC 90: Sustainability roadmap and the linked roadmap issues #38 and #64 to understand the existing plans. The issue names measurements, awareness, and reductions but leaves the exact improvements and completion criteria undecided, so no implementation entry point or concrete definition of done is provided.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100