agilesix / agilesix.com Goto Github PK

STR:

1. browse to https://agile6.com/contact
2. fill out contact us form
3. be sure to fill out the "message" field
4. send the message
5. go to https://app.netlify.com/sites/agile6/forms/5d287d547662aa00096839ba
6. open up the message you just sent

ER:
Message written in the message field shows up somewhere in here

AR:
Message written in the message field does not show up anywhere. Ever.

As a site visitor I want to understand Agile Six core values so that I understand more about the values underlying the company.

AC:

• There is a place on the site that identifies our core values.
  • Integrity
  • Initiative
  • Commitment
  • Resilience
  • Fun
• Values should be incorporated into the website per the updated site design (done in #22):

As an Agile Six strategy stakeholder, I want our website to showcase important news about the company so that our team's accomplishments are highlighted.

AC:

• Information about newsworthy events can be quickly and easily added to and removed from our website.
• Visitors can quickly determine how old a news item is.
• Design should follow design created in #22

Right now netlify does not format quotes with any distinguishing factors.
I would like to update the Quotation Block formatting to be more similar to how it appears in places like Notion so that a reader can distinguish between quotes if they are added consecutively.

@DanielMiller-agile6 / @amponce Is this a relatively easy change to make?

Setup a Netlify action for https://agile6.com/contact/ form to send to our Slack channel https://agilesix.slack.com/messages/CN2KERNHE (#a6-website-contact-us)

As a potential hiring candidate for Agile Six I would like to know what positions are available and how to apply for open positions.

AC: Repo is renamed to "AgileSix.com"

• Rename Repo
• Configure Netflify to use new repo name (it may auto detect that)
• Check ZenHub to see if it auto detects new repo name, if not reconfigure ZenHub too
• Make repo public

As an Agile Six strategy stakeholder, I want a place where I can direct people to find white papers, case studies, slide decks, and other digital assets so that they are easy to find.

The website may be a good place for these, but we don't want to presume the solution here.

AC:

• Digital content is easy to upload, publish, and manage.
• Digital content can be found easily by people who want to learn more about A6.
• As a digital content author, I can easily link to this content from a variety of places (Slack, email, etc)
• Design should be done per guidance from #22

AC: Matt, Lauren, and Morgan are removed from #initiative-website-refresh channel

I'd like to add Agile Six's main phone number and mailing address to the main website.
Main phone: (619) 350-6292
Mailing Address: Agile Six Applications, Inc.
501 West Broadway, Suite 800
San Diego, CA 92101

Getting cert error on https://www.agilesix.com when it tries to redirect

dig www.agilesix.com

www.agilesix.com. 3504 IN CNAME agilesix.com.
agilesix.com. 504 IN A 184.168.131.241

ip2location.com > 184.168.131.241 > godaddy.com

As a stakeholder, I want the ability to easily and quickly preview site changes based on enablers/constraints built into a system of reusable components.

AC:

• A component documentation site can be viewed to see what most common components look like.
• Developers can leverage components to quickly build new features.
• Developers and/or designers can assemble "previews" quickly.

Note: Storybook may be a good tool to use to create this.

We need a website for our new JV CivitasDX. I'm hoping that we can reuse parts of our AgileSix website as a starting point.

What we need is an analysis of what we can leverage and any notes around overall approach to reuse, risks, etc. This can be written up as notes in this user story, or linked to a separate spreadsheet if that conveys the information better.

Ex: Do we want to leverage the same theme, or start with a Gatsby starter theme?

AC:

• A spreadsheet representing the analysis similar to what is described above has been added to this story.

-- Let's table this until we get a revamped site design. We've incorporated looking at careers in that story. (#22)

Saw this tweet by @gatsbyjs about their /careers page and thought it would be nice to add something like this to our site.

https://twitter.com/gatsbyjs/status/1215398218944610310

cc @JQuaggles @bderfer68 @robrasmussen1970

As a strategy stakeholder, I want to understand how our site resonates with people who have recently been hired to A6 so that we can incorporate their feedback and improve the site.

AC:

• We get feedback from all new hires, including new hires who didn't visit our website.
• We understand why people did not visit our website to learn about us (if that applies to anyone).
• We gain an understanding of where our site was not clear or where someone had a question about our company which was not answered by the site.

As a developer I want to see and test my code changes before they get merged so that I can get feedback on them as rapidly as possible and avoid breaking the site.

https://www.netlify.com/blog/2016/07/20/introducing-deploy-previews-in-netlify/

AC:

• Stakeholders can see and approve changes in context before they are deployed to production.
• Technically: Full-site preview is posted as a link on the PR after pushing changes to my PR.

As a strategy stakeholder I want an overall site design that incorporates the new features we intend to add to the site, including an area to display our core values, an area to display digital assets like white papers, a separate "Careers" page, and a news area so that our site remains intuitive and easy to navigate while displaying the new features.

Note: we believe our audience, in priority order, is

1. Potential customers -- CORs and COs, Product Owners, Government Management, etc.
2. Potential future employees
   ---- big gap ------
3. Potential Partners

Prerequisite:

• Some idea of the content copy that will go into each section.
• Some minimal (at least) design system has been created based on the existing site

AC:

• General mockup is created for the site incorporating each of the changes that can be viewed for a variety of view sizes.
• Digital content and news are easy to upload, publish, and manage.
• Digital content and news can be found easily by people who want to learn more about A6 (but not necessarily pushed at them -- i.e. we want to see careers and jobs first).
• Possibly break "Careers" out into a separate page.
• As a digital content author, I can easily link to news or digital asset content from a variety of places (Slack, email, etc).
• The site still "hangs together" as a unified experience (i.e. we don't want new features to feel "tacked on.")

Current deploys and builds are taking 10+ minutes. I wonder if it something to do with shared workers on Netlify's side and if we can throw some $$ at the problem. This may not be the issue, but I do know that a fresh site should build/deploy in under 3 minutes.

Here is a sample log where we see 9 minutes in between boostrap and build steps with no information as to why the wait, which leads me to believe it is a Netlify worker. Maybe we can have our own dedicated worker?

2:58:49 PM: info bootstrap finished - 353.318 s
2:58:52 PM: warning Browserslist: caniuse-lite is outdated. Please run next command yarn upgrade
3:00:10 PM: success Building production JavaScript and CSS bundles — 80.929 s
3:00:12 PM: { title: 'Get in touch',

I ran some quick accessibility tests over the agile6.com site (using Axe Chrome plugin) and found a few issues. There aren't many serious or critical failures, but most of these should be quick fixes. We're also missing skip nav links, which are helpful for screen readers and keyboard navigation. As a government contracting company, it might be good to show that we practice what we preach regarding 508 compliance :).

First steps would be to resolve issues found from these tests, but we could delve deeper in the future with a more robust accessibility audit and automated axe-core tests as part of our build and deploy process.

Here are a few screenshots of errors I found:

Stub epic for work around creating an open source employee handbook.

Two existing, opensource handbooks to look at for ideas:

1. https://about.gitlab.com/handbook/
2. https://handbook.civicactions.com/

@JQuaggles:

On the capabilities page, I changed Design to Human-Centered Design and now the content block disappeared off the production page.

This is the commit e16f169

Description
We are currently using an Application Tracking System (ATS) called Workable. We currently have it set up where the Team page is pulling the job openings through their API.

We have switched our ATS to Greenhouse.io. So we need to switch the API to the Greenhouse API within the Team page (until later when we push it to a new page).

Story
As the Hiring Manager I need Agile6.com/Team to pull jobs from Greenhouse so that our website is pulling from the correct system and potential candidates can apply for roles at Agile Six.

Acceptance Criteria

• The Greenhouse API is set up live and is able to pull open and published positions from Greenhouse.
• When a role is clicked on it will take you to the Greenhouse ATS page for Agile Six roles.

Add @DanielMiller-agile6 and @ElijahLynn to Netlify account so they can see and debug build/deploys and configure the account as needed.

• Purchase upgrade
• Add them