Welcome to freeCodeCamp's Developer News codebase — A JAMStack app built with Hashnode, 11ty, and lots of love from the community. We use this project to build and deploy multiple instances of our publications in several world languages. All of the services are then distributed globally by our CDN.
We limit contributions to this specific repository because of the complexities of our deployment and QA processes. We welcome you to work on any of our other open-source projects. You can find our contributing guidelines here.
If you have found an issue or a bug in this repository, please connect with us in the contributor's chat room first.
Happy Contributing!
You can click on the badges below to go to the dashboards detailing the status of the latest deployments. If you see something is not right, wait for a few hours. Our team is usually on top of these with automated alerts.
| Language | Status (Click to see details) |
|---|---|
| English |  👈 Yes – you can click these things! |
| Others(i18n) |  |
New builds to the /news sites are triggered according to the schedule below:
| Language | Schedule (UTC) |
|---|---|
| English | Every 3 Hours - except between UTC 00:00 - UTC 06:00 on Wed & Sat for maintenance |
| Others(i18n) | Every 6 Hours - except between UTC 00:00 - UTC 06:00 on Wed & Sat for maintenance |
Important
Once a build is triggered, it can take up to an hour to complete and cascade to all regions in the world.
You can check the status of the latest builds by clicking the Deployment Status badge in the previous section.
Your published article and changes may take longer than usual to appear. We have multiple layers of caching, which helps us serve content faster to our users.
When you publish a change in CMS (such as updating scripts, adding a new article, updating old articles, or adding/updating pages), it will eventually appear on the public-facing site.
Sometimes, it can take up to an hour after the build is completed for the changes to appear on the site.
We recommend waiting at least a day before reaching out to someone to investigate. We have recovery workflows in place to fix most issues automatically.
Additionally, the team receives alerts for all build failures. There's no need for you to alert them again - unless it's been more than a day since the build failed.
Copyright (c) 2021 freeCodeCamp.org - Released under the BSD 3 license.