In the security section, two links gave 404 responses:

https://github.com/basecamp/shipshape/ - shipshape app?

https://github.com/basecamp/shipshape/wiki - list of what is required and why

Global Entry links to https://help.cbp.gov/app/answers/detail/a_id/1035/~/global-entry-program---who-can-apply, which seems to be an invalid page on CBP's website.

The URL you have listed is no longer valid:
https://www.cbp.gov/travel/trusted-traveler-programs/nexus/eligibility

Here's the correct link:
https://www.cbp.gov/travel/trusted-traveler-programs/nexus/nexus-eligibility

37's github repository URL is broken on our-internal-system page. The github repository linked with it is either private now or deleted.

The file/page our-internal-systems.md to a system called The 37 command at https://github.com/basecamp/37, which apparently doesn't exist anymore.

Basecamp has always been an inspiration for me management-wise. So when I decided to finally write down a handbook for our company, yours became one of the first benchmarks.

One thing that I couldn't understand though was why you chose not to include role guidelines for areas like sales, marketing or customer success.

Hi there,

I noticed a couple of 404 on this page: https://github.com/basecamp/handbook/blob/master/our-internal-systems.md

Namely:

• https://github.com/basecamp/37
• https://github.com/basecamp/shipshape

Would have happily made a PR but cannot find the correct links.

Cheers,

Shipshape link is broken 404 in Getting Started https://github.com/basecamp/handbook/blob/master/getting-started.md

In the Product Histories section it says Ta-da closed to new signups in 2014, but DHH's post in SvN says 2012. May be worth checking and correcting.

In https://github.com/basecamp/handbook/blob/master/getting-started.md you're mentioning Shipshape.

Is there any chance to know what's in there? Or make it public just like this handbook?

It's not super clear if you all are open to outside suggestions, so sorry if this is unwanted. Anyhow…

In the International Travel Guide you suggest:

If you're detained or encounter some other serious customs headache, contact our attorney directly: Jennifer Pflanz (get phone number from Andrea). Customs and Border Protection (CBP) is not required to allow you to contact an attorney, but Jennifer is your first call if possible.

Instead, I would suggest (and I'm pretty sure this is an idea I stole from CGP Grey) whenever you travel to a country where you'll have to go through CBP, upon landing — but before going through customs or even deplaning — message some trusted person(s) letting them know you've landed at YYY airport and that you'll be going through customs soon, and to call the lawyer if they don't receive a message from you saying that you've cleared customs in the next X hours (where X is some reasonable number). That way, if things go really poorly, you know at the very least that legal help is on the way.

The last sentence of the Campfire history reads:

Customers can still sign up for an independent Campfire account (they don’t need to be a Basecamp customer), so /play loggins can continue to amuse people indefinitely.

But that doesn't seem to be accurate. Does customer-not-Basecamp-customer mean a Backpack, Highrise, et al customer?

https://www.youtube.com/watch?v=cffU0jSYJd8

Hey

a couple of minor link corrections:

1. repo's website (to the right of Description) should be "https://basecamp.com/handbook"

2. KnowYourCompany is KnowYourTeam now
   https://basecamp.com/handbook/05-product-histories#know-your-company
   https://knowyourcompany.com/story -- > https://knowyourteam.com/m/story

3. A few 🔒 for private links are missing

• https://basecamp.com/handbook/07-where-we-work#from-coffee-shops
  please do mind our basic security rules

• https://basecamp.com/handbook/08-benefits-and-perks#expense-account
  you can find those in Basecamp!

• https://basecamp.com/handbook/11-our-rituals#meetups
  Here are some tips from Basecamp teammates about Meetups

• https://basecamp.com/handbook/11-our-rituals#mini-meetups
  Budget guidelines for mini meet-ups can be found in Basecamp.

• https://basecamp.com/handbook/appendix-07-code-of-conduct#enforcement
  Or you can complete a complaint form.

4. https://basecamp.com/handbook/09-getting-started#your-buddy
   Even when you know who does what should link to https://basecamp.com/handbook/06-orgchart

best,
Maciek

I was just researching for a job application and noticed the monthly coworking space stipend amount differs in this handbook compared to what is currently being listed on the Basecamp Jobs page:

Coworking Space Stipend - Don't feel like working from home? No sweat. Basecamp will pay up to $100/month towards renting co-working space in your city.

https://basecamp.com/about/jobs

From a coworking space

If working from home or from a coffee shop doesn't suit you, then trying a coworking space might just do the trick. Basecamp offers a $200/month stipend towards a desk in such a place.

https://github.com/basecamp/handbook/blob/master/where-we-work.md

Coworking Space Stipend

Basecamp will pay up to $200/month for you to use towards renting coworking space in your city. Please make sure you're using a true coworking space that's meant solely for working, not a club or social space.

https://github.com/basecamp/handbook/blob/master/benefits-and-perks.md

https://www.youtube.com/watch?v=jfTBL94X0hU

In getting-started.md:

We have a very stringent and specific security protocol, which we then monitor using Shipshape. Here's a list of what we require and, just as importantly, why we require it!

Links to "Shipshape" and (as a consequence) "why we require it" are dead (Probably because that's an internal tool and you don't want to disclose your security strategy).

If you can't disclose the content (that's 100% legit, of course !), I would love to hear the general ideas about what to think about when securing a large SaaS app like Basecamp. Maybe that can be a topic for a blog post?

Hey,

the document at https://github.com/basecamp/handbook/blob/master/our-internal-systems.md mentions ShipShape, but the link points to a 404 page. Do you have any plans to make ShipShape available?

Hey all, love what you're doing, thanks for making this resource public to help others get insight into how you run things.

Was just going through it after watching a GettingReal video, and noticed that the highrise section needs to be updated in light of the recent closure to new signups.

Thanks again!

The repos does not exist.

This handbook rocks! 🎸 I'm surely will use this as my company's benefit guideline later in the future😊

But however, I'm noticing that you'll give to your employee $ 1,000 for their home office every 3 years. Is it goes to new comers too? You'll give $ 1,000 right after you hire them?

Is it an internal system?

On https://github.com/basecamp/handbook/blob/master/where-we-work.md we link basic security rules to https://3.basecamp.com/2914079/buckets/34/documents/14419. This page is not accessible to me. Should it? There is the Travel guide and there are quite a few to-dos related to security in the Welcome project template but I'm not confident what the accurate URL should be here. Does someone know?

Hi,

I was reading your handbook (very interesting, thanks for sharing!) and found two dead links at the bottom of this page. I'm not sure you mind, but we never know!

Regards,
Joseph.

https://github.com/basecamp/handbook/blob/master/getting-started.md#your-buddy

At page of Titles for programmers, on line 27, what is example of Deep expertise ?
And please tell us the example of it at Basecamp.

Not sure if you want PRs for that small typo, which appears a few times in this file.

Is Shipshape going to be open-source anytime soon? Also, why does Basecamp only use Apple computers?

Hello,

In https://github.com/basecamp/handbook/blob/master/how-we-work.md#heartbeats

there are links for "daily questions", "weekly questions" and "team updates". Is there any format that you are using? If yes, it would be helpful if that can be clarified.

I think they could have a more clear name.
There is Dev ops, Biz Ops and more being emerging buzzwords.
I see that it makes sense in the context of COO, but I just wanted to give you this feedback that i felt when reading it through.

If the name was to change, what ideas do you have for a better name?

I'm not working in basecamp but i think your handbook gives a view into a great and fascinating work culture.

Best Regards
Simon
A computer science student reading about interesting stuff

First of all, thank you for sharing your handbook to the general public! It is very interesting to learn other companies culture. And it is typically very hard to do..

Reading this handbook I have seen a lot of links that either go to the private GitHub repos or to Basecamp projects. Example01 and Example02.

It would be nice to remove that links and substitute them with description what that system/resource provides if it is appropriate.

Link github.com/basecamp/37 from https://github.com/basecamp/handbook/blob/master/our-internal-systems.md#the-37-command is not found.

Make an encrypted archive of your Basecamp git repos so you can download and restore it after you're through customs.

I assume you are not storing the repo on the said laptop? Can't they require you to decrypt it.

Shiftshape URL is broken on getting-started page of hand book. The github repository linked with it is either private now or deleted.

This sentence under Org Chart > Ops seems to be missing a word or two:

They run rolling tests all web and mobile versions of Basecamp for quality control.

I was reading the basecamp handbook for researching purposes and I noticed a weird and distracting behavior when clicking on links (in the content as opposed to on the sidebar) as the links pointed straight to github.

After some investigation I found that indeed the content is supported inside the handbook domain on it's full glory but the .md address is only converted in the navigation menu and not inside the content of a page (or at least, that's what it seems).

This clearly distracted me enough from my read and I believe it would be more pleasant for the casual reader to stay within the site and be able to get the benefit of the copy and style on the site instead of github.

I wasn't able to find where the actual process of the links resides, I believe it's kept internal, otherwise I will be glad to be pointed to it if you believe that providing a PR will be of any value to the project.

Example:
(note: this is just one of many, all appendix links that appears in a page content shows the same behavior)

Where the link points to in the actual content:

The url in handbook full glory:

Campfire's mentioned, but the history of the product is not included.

Basecamp has always been one of my favorite companies, and I want to show support for everyone that works there. Even though today was a really disappointing display of leadership, I trust that the values that attracted people to company in the first place will be allowed to win out when workers are given a voice.

In making-a-career.md:

Day to day, though, these titles aren't really much of a factor.

Can you expand on that? Aren't the day to day tasks for a Junior going to be significantly different than those of a Principal? How do you define the differences between each level? Do you take scope of work/influence into account?

I'm a fan of Basecamp's employee handbook and would like to use parts of it at Capdesk.
What is the license on the content of this repository?

Thank you!

Without a license, this defaults to All Rights Reserved. Would you consider adding a creative commons license to this content?

Basecamp is amazing! Our team started to use it, both design and dev teams!

We want to share the hill chart with our client so the client could see the progress, is there a way to do that? shared link / API / webhook / whatever works if we can actually get the hill chart somehow.

Thank you guys! Amazing job!

You can use this:

[What We Stand For](what-we-stand-for.md)

instead of:

[What We Stand For](https://github.com/basecamp/handbook/blob/master/what-we-stand-for.md)

and the links would still work.

I'm working on a piece of content that I want to publish on GitHub and I like your approach, but I don't understand the absolute paths. It'd be great if you clarified this for me.

Thanks!