basecamp

For and against frameworks: React, Vue, Angular, Ember, JQuery, Bootstrap, Tailwind, Pure, Ruby-on-Rails…

To require javascript to display "Hello world", a brochure website or even a basic weblog adds complexity for complexity's sake. Go native.

Intelligent defaults are at the core of brilliant software. You shouldn't have to micromanage your projects or your software.

A developer's paradise, here's two years of experience dealing with the TeamworkPM API.

We didn't want our customers to feel that they were in a help desk. Support should be as easy as email. Hands on test of the leading solutions.

37signals don't do client work anymore and live in a bubble. If you face clients and billing, TeamworkPM is a much stronger solution.

I often have to introduce our team to Textile formatting and our clients. I've linked to the other great Textile documentation out there.

So for non-programmers, here's how to get Textile editing working on BBEdit. Review of other OS X textile solutions.

With up to 20 people on a single project, spanning design, programming, SEO and content, notifying everyone is a nightmare.

Keeping out of date and inaccurate information in your help documents is just wrong. Case in point: 37signals Highrise export.

Is it worth upgrading to the 37signals suite from Basecamp? Really, it depends how much sync you need and how much integration you want.

37signals abandons white label Basecamp betraying original subscribers: open source self-hosted Basecamp replacement on the way.