Need a Federal landing page on about.GitLab.com

@luke @amara @mitchellwright

Hi Team, I need some help creating these projects. Please let me know what you need from me. Thank you!

**Design mockup:**

Hi Paul, could you be a little more clear in your request? What do you mean by "a Federal about.gitlab.com"? Also, when you say you want a standalone landing page for events and webcasts, can you you explain a bit further what the current webcast and event pages aren't doing to fulfill your needs?

Would love to get some additional insight so we can make sure we're doing the right things!

Mitchell,

Here's an example of a Government landing page- https://www.ansible.com/government

Great example @pauldalmeida. We actually have an issue template for new pages being created. If you click on Edit for this issue, next to the issue title you will see a dropdown. From that dropdown select the New Page template and fill that out. That way @luke will have a much better idea about what needs to be included in such a page.

@pauldalmeida and based on your example, I'd recommend this page to be part of about.gitlab.com and not as a standalone landing page.

@amara can you help with the content on the page?

Thanks for the mention, @pauldalmeida. It seems like my notifications are not set to get an email when you mention me in the body of an issue so I am just seeing this now.

I can certainly help with the content and getting this vertical specific webpage live. What is odd about the Ansible example you shared is that it doesn't seem like you can navigate to this page without knowing the URL. Seems like its basically an SEO landing page.

I'm at a conference most of this week but let's chat about this page on Friday.

@pauldalmeida I meant to get to this copy last week but I ran out of time.

Here is the copy I suggest for the landing page. https://docs.google.com/a/gitlab.com/document/d/1vqm8GwKp-tj4r9GU8djnNcCKykMoU25U0qlA-45Ju4s/edit?usp=sharing

Feel free to edit the doc directly.

@mitchellwright and @luke now that Paul has the copy are you two able to work on creating the landing page?

Do you need anything from me to support the landing page creation?

@amara I can start thinking about concepts for the page based on the copy doc. Paul also shared an example page so I think I have enough to run with. @pauldalmeida what's the ideal launch time for this so I can prioritize accordingly?

changed title from Need a Federal about.GitLab.com and standalone landing page for events and webcasts to Need a Federal landing page on about.GitLab.com

added Design Website Redesign labels

@luke @mitchellwright @pauldalmeida I want to make sure things continue to move forward on this.

@luke I'm not sure what else is on your plate so its hard to prioritize this but since this should help in selling GitLab it feels like it should be high on the list of priorities. To lighten the load of this work is it possible to use any of the templates we have for our current SEO pages. @mitchellwright likely knows what we have currently.

@pauldalmeida any feedback on the copy? Also about logos on the page, it looks like we are only approved to use Nasa's logo.

Thanks @amara, as I mentioned in our team call, this is one of my top priorities this week. I'm working through a couple layout options at the moment.

Is there any imagery, product or otherwise, that comes to mind and might support the copy? Otherwise we can use icons, but the page will be pretty dry...given the audience that might be ok? cc @pauldalmeida

The examples that Paul shared weren't image heavy. My guess is that was intentional since the goal is to get someone to complete the contact form.

@amara that's a valid point, and also seems to be consistent with other examples I've found. Perhaps we should consider placing the contact form on the page (at the bottom) — something like Contact GitLab's Federal Sales team rather than pushing to our generic Contact Sales form?

Yes, I agree that the contact form should be on the page.

Mitchell, can you help us understand how that would work in terms of Marketo forms? I assume we've done this before on SEO landing pages.

Great, I'll add that in. What fields would we like to include?

@luke @amara thanks for all your help. I agree with you Luke about the Federal team getting the contact.

Yes, I agree that the contact form should be on the page.

Mitchell, can you help us understand how that would work in terms of Marketo forms? I assume we've done this before on SEO landing pages.

Yes we would just create a new Marketo form and embed it on the landing page.

@amara @mitchellwright @pauldalmeida here's the initial layout concept, any thoughts? I guessed on the form fields so we can tweak those based on need. We can also change up the page header.

Looks fine from my point of view. I'll view content up to @pauldalmeida and @amara

@pauldalmeida any feedback on the design? You can find the most recent design up top in the issue description. Once I get the I'll find a front-end resource to implement this for us.

@amara any objections to requesting a front-end resource to get started on this?

@luke looking at this again. It feels flat to me. It's likely because in this second iteration the icons were removed but that also drew my eyes to the amount of whitespace on the page. Can we test an alternate layout? Perhaps a two column layout? To accommodate the two column layout and to add useful information can we do the following:

• Change the title of the page to GitLab for Public Sector and perhaps we add a sub head?
• Subhead: Bring the power of Git and CI/CD to your federal, state, and education IT teams.
• Change the body section to be 2 columns with 2 copy blocks each. (Let me know if I need to break the copy up more. I could break it into 6 copy blocks so it's shorter text.)
• @luke where could we add customer logos in the design?
• @pauldalmeida based on the customer reference sheet the only logos we can add seem to be NASA, University of Michigan, UPMC, Federal Reserve Bank of Kansas City
• @luke we'll also need a space for Government schedule. Sorry for the late notice. Maybe before contact form we say "Available on the GSA Schedule and NASA SEWP V" and have a logos for both.

@mitchellwright on our other SEO standalone pages how do we handle EE trials and how do we hand the interaction between the landing page and GitLab's homepage (i.e. should there be a trial CTA or should we like to our homepage?)

@amara I would not add any non US federal agencies- European Space Agency, and Interpol Technical Group.

I like adding GSA schedule, we are also on NASA SEWP contract too.

Can we also mention somewhere about how we can manage STIG and NIST compliance? Those are key words that government folks usually search.

@pauldalmeida I updated my comment to remove the non US agencies and I added SEWP.

I'll update the copy to add STIG and NIST after chatting with Luke about the page layout tomorrow.

@amara so the most recent mockup, in the issue description, includes the icons.

The current copy might be a bit long for a two-column layout, which is why I went full-width with the first version. I can certainly put together a two-column layout pretty quickly, but I do think we will need to break it up, or push it to six blocks instead of four.

I will also go ahead with the other changes and added sections you mentioned.

@amara here's a super quick screenshot with the body text as-is in a two-col layout:

@amara @pauldalmeida here is the latest complete layout with changes and additions based on your comments above. I tweaked the body copy size a bit for the two-col layout, so despite being a bit longer, I don't think they look/read all that bad.

I grouped the logo bar and Available on GSA Schedule... sections together as they looked odd being two separate, short, sections.

Thanks @luke I like the two column layout better.

However, it does make me want to shorten the copy (sorry!) I'll shorten it in the google doc tonight. I'll likely have to break it into 6 copy blocks vs. 4. Hopefully that doesn't affect the design too much.

As for the logos and the GSA schedule, I agree that two boxes for it would be odd. However, right now the two don't feel connected to each other. Should we put something like "Join these public sector organizations and start collaborating on code." Then we can make the second sentence "GitLab is available on..." (and put a period at the end of that sentence as well.)

@amara no worries about the copy, not a ton of work from my end to update it.

I agree about the logo block, I'll add the section heading your recommended, and maybe downplay the Available on GSA Schedule... text so that the section as a whole feels more connected. I'll share a couple different versions.

@amara here are a few variations for the logo section update. The last variation feels the most connected, but not sure how much attention we need to bring to the Available on GSA Schedule... copy.

@luke I like option 2. Can we put a period at the end of the sentence though?

Also I'm working on the updated copy now.

@amara Is it too late to add Dept of State, US Army, USAF, Navy, and DHS logos? I can get those approved.

@pauldalmeida I can add those additional logos pretty easily — let me know when you have them approved. While requesting approval, would it be too much to ask for a black and white logo (.ai, .eps, .svg format)? Otherwise I'll have to spend some time hunting down the correct versions on the web.

@luke I pinged a few of my customers and they said it was okay to use Logo. They are not sure the process of getting approved but since they are a customer it shouldn't be a problem. I can try to find the black and white logos. Do you want me to post here or email them to you?

Awesome @pauldalmeida!!!

on our other SEO standalone pages how do we handle EE trials and how do we hand the interaction between the landing page and GitLab's homepage (i.e. should there be a trial CTA or should we like to our homepage?)

We should have a link to the free trial and/or contact sales page as the main CTA. I think the way @luke has it laid out right now is great.

@luke attached are logos for federal. They are in black and white. I am not sure I got the correct format. Let me know.

@pauldalmeida yeah the logos you posted are a great starting point, I can track down the correct file formats if need be. Thanks!

@luke I updated the copy. I ended up breaking it into 8 sections to keep the copy concise. I think people tend to read headlines more than body copy so its better to have more headlines in my opinion.

The first four copy blocks should be one column (i.e. left column) and then the next four should be the right column.

@pauldalmeida I chatted with Brian quickly on STIG and NIST to make sure it was relevant to us and he noted that STIG doesn't really apply to us. See his quote below. Then on NIST 800-53 compliance, we aren't there yet. That could be something we revisit down the road though if we make some product changes.

It covers OS and network settings and wouldn't really apply to an application.

Updates to the body (need to drop in new icons) and logo sections, I'll have a full page update tomorrow.

Sorry for the delay, here is the complete page update:

Looks great to me. Thanks for all your hard work.

Thank You, Paul Almeida Director of Federal 240-603-4427

Create, Collaborate and Deploy together Sign up for a free trial @ https://about.gitlab.com/free-trial/

@amara can we add this event to the page?

http://fedsummits.com/devops/

@pauldalmeida will there be a recurring list of events? Since it may be odd only to have one event or an empty events section. I'm wondering if the event should be added on the events page: https://about.gitlab.com/events/

@amara maybe we can add it later. We do not have a list of events. It might take a few months to get there. So lets leave it off for now. Thanks

@brent_caldwell Can you add Duns number?

changed the description

@timzallmann can we get a FE resource lined up for this new page? AFAIK the design and layout are complete. You can check out the most recent design mockup in the issue description. Thanks!

removed assignee

Hi @luke and @amara. Paul @pauldalmeida asked me to include some frequently asked data as well to see if we can post this on the federal landing page. See below. In addition - can we/should we link a file as well? We often get asked for a VPAT for 508 compliance. I was thinking we might want to link that file to the page as well. Let us know what you think:

GitLab, Inc. Federal frequently asked info:

Federal Tax ID: 47-1861035 DUNS Number: 087987115 CAGE Code: 7NJT9 NAICS Code: 511210

Export Control Classification (ECCN): 5D002.c.1 (CCATS): G163509

@luke what do you think about putting this next to the contact form? OR we could make the logos their own section and put the GSA section with the below:

• Federal Tax ID: 47-1861035
• DUNS Number: 087987115
• CAGE Code: 7NJT9
• NAICS Code: 511210

Export Control Classification

• (ECCN): 5D002.c.1
• (CCATS): G163509

@bcaldwell-gitlab should we include our GSA schedule # as well?

Hi @amara - yes please on GSA number. @pauldalmeida I assume we should start with the existing GSA number (held by Release Team) as we don't have a GSA for Immix yet?

Yes, I agree. we should add GSA number from Release Team.

@amara @pauldalmeida here's the federal information / numbers next to the contact form. I think it works quite well here, as it holds relevance to those who might be contacting us.

Where would the GSA number be displayed? Under GitLab Inc. Federal Information or in it's own grouping?

@pauldalmeida and @bcaldwell-gitlab do you agree that the GSA number should be in the federal info section?

@luke lets add:

• GSA Schedule Number: GS35F186BA

@amara yes. Thanks.

@amara I think it should be. Thanks.

changed the description

Added the GSA Schedule number, we can reorder those numbers however you like when we get to front-end. You can find the updated design in the issue description.

@timzallmann can you please designate someone from your team to work on this page?

We would like to get it launched next week. If that timing, doesn't work can you please share what the new ETA would be?

@amara + @luke : I didn't forget your request So @jivanvl will be done by tomorrow with his deliverables for 9.3 and then he will do the implementation.

@luke : Can you already prepare the different logos as usable assets, SVG if possible or otherwise PNG.

Thanks @timzallmann - I will share the logos and usable assets with @jivanvl by the end of today.

@jivanvl this should be everything you need to get started on the page:

Icons can be found here.

Org logos can be found here. I cleaned these SVGs as best I could — some are rather complex and did not render correctly once cleaned, I also left the #FFF fill for this reason.

Use this Sketch Measure preivew of the page design for specs on spacing, colors, font sizes, etc. Let me know if you have any questions!

Lastly, the Contact form at the bottom of the page comes from Marketo. We recently implemented a similar version of the form on https://about.gitlab.com/free-trial/. @mitchellwright can help you get the form set up for this page.

assigned to @jivanvl

Spoke with @jivanvl and got him the code for the form to be put on the page and set it up in Marketo.

@jivanvl can you share a rough ETA for this page so we have a date we are all tracking towards?

@amara MR up! https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/6301

Just needs to be checked by @luke, I need also the background for the initial landing section, other than that the design is complete

mentioned in merge request !6301 (merged)

@pauldalmeida If a lead come through this form, who should it be getting distributed to? And who should be getting alerted? cc @jjcordz

@mitchellwright We would like the lead sent to @brent_caldwell, and I would like to be alerted. Thanks for your help.

Lead assignment and alerts have been set up as requested. cc/ @mitchellwright

closed via merge request !6301 (merged)

mentioned in commit 32b0fd9d

Team, Any update on when this landing page will be complete?

@pauldalmeida it's live at https://about.gitlab.com/public-sector/

When I go to about.gitlab.com and I type in federal or public sector in search, it does not come up.

I think out search engine might be still indexing this new site @pauldalmeida, let me see who I can contact that could help us determine if it's indexing at all

Team, last question. Can we add Public Sector to the bottom as a link/tab?

reopened

@pauldalmeida That's easy, the question where should I put it?

cc @amara @luke For input

@pauldalmeida yes, I knew when we launched that discovery was going to be a challenge since the Nav and footer are limiting.

I'm not sure how much traffic the footer sees anyway though. We may want to consider promoting the page until we can find a better home for it in the site flow. It looks like Ansible takes that approach for thier gov page: https://www.ansible.com/government

@mitchellwright any insight into how much traffic the footer sees? Also what are your thoughts on promotion of the page vs. just putting it in the footer.

@amara no hard numbers into footer traffic, but you can be assured that it's going to be a very low number.

I think having the ability for someone to be able to find it on the site in some way is good. I think leaving it as an orphan for now isn't the worst thing, as sales can still use it as an asset to share out with the needed people.

I'm a little bit confused. What's the consensus here? Should we add it or ?

The only places I can think to put this page in our current website flow is in the FAQs for for the contact sales and the /products page.

@pauldalmeida its not ideal but it seems like the best solution for now.

@jivanvl if we take that approach I can submit an MR for this and just have you review it before I merge it.

@amara Sounds good, let me know if you need help with the MR, otherwise I'd be happy to review

Thanks everybody

Sorry for the confusion. My thoughts were as follows:

• Should add a link somewhere (such as a footer) as we do a website redesign, something we are working on at the moment
• For now, would probably be ok to not have a link anywhere and just let the sales people share out that page as appropriate

However, since we have identified a potential location for it, we can go ahead with that.

Sounds great. Thanks everyone!

@amara Do you have the MR for @pauldalmeida request? Can we close this issue?

Thanks!

closed