Producers are required to develop sites and databases that are compliant with Progressive Web Application (PWA) standards and best practices. A checklist of these standards can be found at https://developers.google.com/web/progressive-web-apps/checklist. Specifications for sites and databases to be hosted by PBS can be found below
CMS content should be managed via Git plugin where possible, e.g., https://wppusher.com/
Otherwise, utilize a migration plugin, e.g., https://straightupcraft.com/craft-plugins/migration-manager or https://wordpress.org/plugins/all-in-one-wp-migration/
Export files must be delivered via AWS S3
XML Sitemap + Robots.txt
Estimated lifespan of site/app before first refresh
Estimated change/deployment frequency
Third party development or support agreement
Source code repository – GitHub preferred. PBS can provide Bitbucket access.
In an effort to provide PBS producers greater flexibility with innovation, as well as greater freedom to tackle emerging issues, PBS is providing select producers with dedicated compute and storage resources. These resources provide content producers greater technological freedom to innovate and experiment with new technologies, while introducing isolation between producer sites, dramatically reducing the impact of adverse events.
With these dedicated resources, producers now have nearly complete control over their environment and the means to address most issues autonomously. Provided resources are for the exclusive use of the producer to which access is granted.
Technical support is provided by PBS but is limited to the following:
PBS does not provide technical support for issues regarding the use, development, application, tuning, or customization of development and scripting languages, application frameworks, or applications developed by third parties and/or the open source community. PBS requires third party developers to be self-sufficient in these areas.
PBS views web application security as a joint responsibility. In order to ensure the highest level of Confidentiality, Integrity and Availability (CIA), the following measures will be enforced wherever possible:
All Content Management System plans must be reviewed and approved by your program manager at the start of your project. File a support ticket with any questions.
Due to repeated security and performance issues with high-traffic sites, Drupal is not supported.
Sites may not assume that their IP addresses will not change. In other words, your site must still function properly even if the IP address changes.
Sites should not assume that their domain names are fixed; if the domain name changes, the site should still function.
Site should be immutable on Amazon. For legacy sites on server infrastructure, PBS should be able to back up the producers application directory and database, create a new machine, and the site should come up without any human intervention. All customizations must be automated using the boot.sh file which is run once upon server provisioning. Apart from container images, sites should be immutable via IAC (Terraform of CloudFormation) and auto-scale without user disruption.
All third-party developers and producers are expected to utilize the PBS Content Delivery Network, which is currently hosted by AWS CloudFront.
Full use of the CDN is a launch requirement for the following media types:
All database-intensive sites must implement object-based and/or page level server side caching as necessary in order to maintain high performance.
In order to maintain the highest level of user experience, PBS requires that all applications and sites developed by third party developers for hosting on PBS's AWS hosting service undergo (and pass) performance and load testing.
Performing this testing is the sole responsibility of the third party producer or developer. The purpose of this load testing is to demonstrate that the application has been engineered to handle the high levels of traffic that the site may experience at launch.
In order to reach the most users, sites should be developed using HTML specification 4.0 and cascading style sheet specification CSS1. Other HTML specifications may be used as long as the principals of Progressive Enhancement/Graceful Degradation are applied so that there is always a compelling and usable experience available for the site user. Compliance with The World Wide Web Consortium (W3C) guidelines and recommendations is required. HTML standards must be compliant for the doc-type being declared. If not, PBS reserves the right to not publish or to limit the site audience.
Sites must be developed to support PBS-approved web browsers across platforms. Although it is not assumed that all users will have the identical experiences when using different browsers, it is vital that every user be able to experience the same content and as much visual richness and interactivity as possible.
|Supported desktop browsers||Supported mobile devices|
** Latest, or most widely used version http://gs.statcounter.com/
Any national producer website on the pbs,org domain should have Google Tag Manager (GTM) across all webpages. Please view all information about implementation and further details about custom event tracking here: https://docs.pbs.org/display/AN/Implementation+of+Google+Tag+Manager+for+PBS.org+Sites
Any project wishing to provide registration or authentication services to its viewers must utilize PBS Account.
When a plug-in is required to view site content, the teaser must be accompanied by introduction text that:
Use of any cookies is subject to the oversight of the PBS technical staff and cookies that extend beyond a user session must be developed in partnership with PBS technical staff.
To request airdates code for a national program website, please contact your program manager or submit a ticket via the digital support portal.