cloud-gov / cg-landing

[DEPRECATED] Landing page for cloud.gov. New repo: https://github.com/18F/cg-site

DEPRECATED

We've migrated this information to 18F/cg-site, and that repository is now the source for the live version of https://cloud.gov/. Please go to that repository to file issues and pull requests for the site. Thanks!

cloud.gov landing page

The informational website for the cloud.gov PaaS service. Provides information about the platform and links to technical documentation and the live console.

Uses the U.S. Web Design Standards

Installation

This site is made with Jekyll. Once you've got Ruby on your computer, you can install the necessary dependencies using the following commands:

cd cg-landing
gem install bundler
bundle install

(Note: depending on how Ruby was installed, you may need to prefix the last two commands with sudo.)

To start up the local server, run:

bundle exec jekyll serve --baseurl='' -w

Then visit http://localhost:4000 to view it. The -w (or --watch) flag tells Jekyll to rebuild the relevant pages when you edit the source files.

Style development

This site uses a shared cloud.gov style, cg-style. This means any styling code has to be developed in cg-style.

0. Download or clone the cg-style repository, git clone [email protected]:18F/cg-style.git
1. Follow the instructions on the cg-style readme to install and build the library.
2. Run the watching build task in the cg-style repository: npm run watch
3. Replace the gem 'cloudgov-style' line in the Gemfile with 'cloudgov-style', :path => 'path/to/local/cg-style/gem'.
4. Run bundle install again.
5. Edit code in the cg-style directory and they will propagate down to cg-landing
6. Run bundle exec jekyll serve --watch.

cg-landing's Issues

Local installation error: Failed at the [email protected] watch script 'watch 'npm run build' ./src'.

Hi there. I'm trying to get this site running locally so that I can contribute to it. I followed the installation instructions, but I'm running into an error.

1. I cloned this repository as well as the cg-style repository.
2. I ran gem install github-pages. That showed messages of: Successfully installed github-pages-69 and Done installing documentation for jekyll-github-metadata, github-pages after 1 seconds 2 gems installed.
3. I ran jekyll serve --baseurl='' -w. That allowed me to view the site locally, but without any styling applied to it.
4. In my local directory for cg-style, I ran npm run watch and got the following error:

Failed at the [email protected] watch script 'watch 'npm run build' ./src'.
npm ERR! This is most likely a problem with the cloudgov-style package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! watch 'npm run build' ./src

Here's the entire output from npm-debug.log.

I'm on Mac OS 10.6, node v4.4.3, npm v2.15.1

Thanks for any assitance.

Clicking in the "The Government Innovation Platform" section of the page (right below header) causes gray box artifact to show on page

Am running Chrome Version 50.0.2661.102 (64-bit)

Status page has accessibility issues

Ref https://github.com/18F/Accessibility_Reviews/issues/18

Add link on homepage to this Github repo

Use a progressive jpg for the big background image

When I don't have the large background image (/img/clouds.jpg) in my cache, it loads in fat chunks moving down the page. A progressive jpg would improve this by loading it as less and less blurry and more data is received.

Layout of content part on /updates should match homepage and other pages

The width of the content section of the /updates page where the story previews are should be smaller so it matches with the rest of the site layout.

list pricing

We get this question internally and externally all the time...would be good to have somewhere to point people to.

No Atom/RSS feed for subscribing to updates

I'd like to get updates from https://cloud.gov/updates/ via Atom/RSS. It seems like the _feed.xml is disabled.

set up automatic deployment of landing page to staging

...in GovCloud, at least. Follow-up to #74.

Acceptance criteria

• Site is automatically deployed to staging when a change lands in master

TODOs

• Get staging credentials
• Create deployer user in staging
• Tweak pipeline to deploy to staging
• Successfully deploy to staging

picking nits :)

Howdy, all. The migration to the SBST template looks lovely! Nice job. Here are a few of the things I was mentioning in Slack that I think could clean it up even more:

• re ^^ make sure the background is dark enough for a 4.5:1 contrast ratio
• remove the icons from the About section -- will make it cleaner, and they don't really relate
• after ^^ you could bump up the font size of those headings 5-10%
• need to modify the hero area for the mobile breakpoints (title text goes outside background box)
• need to modify the header/nav for mobile breakpoints (fails between 600px-840px)
• lowercase "g" on government in 2nd blurb title
• "focus on" instead of "focus in" in 3rd blurb

Totally personal preference stuff:

• vertically center the hero text on the cloud image (looks better w/ this design; also looks ok at the top)
• "Your team, unleashed." instead of all caps
• ^^ remove the sans serif font and just let it default to the serif
• "Sign up to receive updates..." at font-size: 400; instead of 700

$0.02

Feature icons are mismatched

As reported on Hacker News, the feature icons are mismatched. For example, the lock is above "Scalability" when it should be above "Security".

Screenshot:

Form on #about needs a legend

Form at the bottom, Fieldset requires a legend

Documentation link in the header doesn't go to docs site

"Deck" in nav bar is confusing

The "Deck" link in the nav bar goes to an application called "Cf-Deck" but is hosted at the URL "console.cloud.gov". The repository that powers that application is 18f/cg-deck.

I think the application name, the menu link text and the URL should all match or be similar enough (docs.cloud.gov for "Documentation"), though I think the repo can be called anything as long as there is a description, which there is.

Just a note that this will also require changes be made in the following repositories to make all global navs look similar:

1. 18f/cg-deck
2. 18f/cg-docs

Fix navigation to different pages.

I think to fix the issue where you can't get back from a different page, we should make the links in the headers not anchor links. This will break the functionality where it smooth scrolls back to the top, but ensures you can navigate correctly.

<a class="navbar-brand page-scroll" href="#page-top">

to

<a class="navbar-brand page-scroll" href="/">

clean up CI files

It's a bit confusing to follow what all of the continuous integration logic—having better names for the files (and seeing where they can be consolidated) would be a huge help.

/cc @jmcarp

508 Issues from pa11y-rails

Results can be recreated using HTML_CodeSniffer

Results for https://cloud.gov/:

• Error: Heading tag found with no content. Text that is not intended as a heading should not be marked up with heading tags.
  • WCAG2AA.Principle1.Guideline1_3.1_3_1.H42.2
  • html > body > header > div > h2
  • <h2 class="header-title"> <a href="/" class="logo"...</h2>
• Error: This fieldset element does not have a name available to an accessibility API. Valid names are: legend element.
  • WCAG2AA.Principle4.Guideline4_1.4_1_2.H91.Fieldset.Name
  • #contact > fieldset
  • <fieldset> <h4>Sign up for update...</fieldset>
• Error: Fieldset does not contain a legend element. All fieldsets should contain a legend element that describes a description of the field group.
  • WCAG2AA.Principle1.Guideline1_3.1_3_1.H71.NoLegend
  • #contact > fieldset
  • <fieldset> <h4>Sign up for update...</fieldset>

Summary:

• 3 Errors

set up continuous deployment

Can copy from:

• https://github.com/18F/cg-docs/blob/master/wercker.yml
• https://app.wercker.com/#applications/55036dfb210ef9cf6a005391/settings/targets/56173bc74010ec244a4f32c3

Make it clear who cloud.gov is for

The site doesn't seem to state who the target audience of the service is. This came up in a Hacker News comment on the launch:

https://news.ycombinator.com/item?id=10362544

The site should probably clarify somewhere that it's for federal agencies only.

Consolidate our contact/sign-up vectors

At the moment, the "Contact" link at the top of the homepage goes down to the form to "Sign up for updates", but I imagine what a lot of people want is actual contact info, which is available from the "cloud.gov help" link in the footer. Not sure of the ideal way to reconcile this, since I don't think we want people emailing us to say "can I get access?".

link to repository from homepage

Hard to find the source behind the landing page!

switch to using Concourse for deploying in us-east

Follow-up to #74.

Currently the us-east deployment is using Wercker, whereas the govcloud deploy is using Concourse. Let's turn off the Wercker deploy so that it's consistent.

Migrate old updates from docs.cloud.gov to cloud.gov/updates

We should either make them visible again, or delete the _posts/ directory.

Ensure cloud.gov logo links to cloud.gov

set up continuous integration

We want to ensure that new pull requests don't break the site.