15 docs tagged with "Pages Basics"

The 21st Century Integrated Digital Experience Act (IDEA) aims to improve the digital experience for government customers and reinforces existing requirements for federal public websites. Specifically, the Act requires all executive branch agencies to:

Working with markdown

We've worked to make publishing a government site on Pages as simple as possible. Please note that while the entire process usually takes a couple days, it may take up to a week, so plan accordingly.

Site previews

When you are ready to share your site with the public you can add your own custom domain. Please make sure you have completed all of the requirements in before you launch before continuing.

Customizing your site

An outline of external tools and resources customer could leverage outside of the Cloud.gov Pages platform to improve site accessibility, user experience, and security posture.

After we execute an Inter-Agency Agreement (IAA), and you are a live customer, we will onboard you into our support process. Our goal is to provide you with support responses within one business day though we aspire to be faster in our responses. As a reminder, Pages agreements do not include labor hours, but we always want to make sure the platform is working and responsive to your needs as we consider new features.

Pages recently integrated support for Decap CMS, an open source content management system for your Github-based content that provides editors with a friendly UI and workflow.

Pages is a continuous deployment-like build environment for sites. It works by setting a webhook on your site's GitHub repository and generates your site on each push event to that repository, then uploads your site files to S3. Changes made to the site's content and files in its repository through the GitHub web editor or otherwise launch rebuild tasks of the site in a build environment container.

- An automatic deployment mechanism for static site assets and supported site engines.

There are a few guidelines and restrictions to be aware of when dealing with large files, or a large number of files.

As mentioned elsewhere, Pages is built on top of the Cloud.gov platform-as-a-service (PaaS). Cloud.gov takes care of the vast majority of the systems functionality that enables Pages, especially by maintaining a FedRAMP authorization. Cloud.gov also provides security, logging, authentication, cryptographic protection, monitoring, and provisioning services that Pages consumes. Pages' compliance memo and extension letter explain the technical relationship in detail.

Getting started

Current Support