Patcher

[lubiarz-oliwia]

• patcher landing page (march),
• navbar updates,
• early access form (a new form bucket link for the early access form is needed),
• great news page,
• home updates,
• select plan page updates,
• navbar updates,
• achieve compliance page update,
• reference architecture page updates,
• gruntwork landing zone page updates,
• how it works page updates

[netlify]

✅ Deploy Preview for keen-clarke-470db9 ready!

Name	Link
🔨 Latest commit	f52d95b
🔍 Latest deploy log	https://app.netlify.com/sites/keen-clarke-470db9/deploys/64256c11bdc74100081826fb
😎 Deploy Preview	https://deploy-preview-783--keen-clarke-470db9.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[netlify]

Josh Padnick left a comment:

Is this the latest version of the Patcher UI?

Browser metadata

Path:      /patcher/
Browser:   Chrome 111.0.0.0 on Mac OS 10.15.7
Viewport:  1920 x 944 @2x
Language:  en-US
Cookies:   Enabled

Open in BrowserStack

Open Deploy Preview · Mark as Resolved

[josh-padnick]

I am strongly opposed to including future roadmap commitments. This gains us almost nothing ("Oh cool, they'll eventually do more things") but publicly commits us to a roadmap, or sets us up to fail to deliver what we say we will. Strong recommendation to remove this section entirely.

That being said, we should encourage people interested in joining a paid beta to fill out some kind of conversion form so we can reach out to them about developing Patcher with them.

[josh-padnick]

This page needs a lot more refinement:

Feedback:

• Visually, can we put the form on the right and content on the left? Right now, there's a lot to read before you get to the form.
• The form should be more detailed. We're not looking to drive high-volume leads at this stage, but to understand our customer better. Here are the fields I'd like to see on the form:
  • Name
  • Company email
  • Are you a current Gruntwork customer (Hint: Even if you're not, you can still join the beta!)
  • How many DevOps engineers does your company have?
  • How many total software engineers does your company have?
  • Why do you want to use Patcher?
  • If Patcher didn't exist, what would you do instead?
  • I realize those are a lot of questions, but that's kind of the point. Let's see if users are in pain enough to get through the questions. Plus, we can make only name and company email required.
• The text we use needs to be more professional. We need to remove phrases like "The Magic of Patcher"

[TolaAltalogy]

@josh-padnick Here you can find updated designs of Patcher Landing Page and Patcher Waiting list addressing the feedback above. Figma

[josh-padnick]

Responded in Figma!

[TolaAltalogy]

@josh-padnick the Figma is updated. One thing that is missing is the screen from Patcher interface for paragraph "Automatically discover dependencies in your code". I have tagged Jason in the Figma comment and sent him an email about it.

[TolaAltalogy]

@josh-padnick thank you for your feedback left yesterday in Figma. I have made all the necessary tweaks and updated the mobile accordingly. The only thing we are waiting for is a screenshot of current version of Patcher form Jason.