Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Puts Debuggerer
Ruby library for improved puts debugging, automatically displaying bonus useful information such as source line number and source code.
Vercel: User dashboard hosting.
Tailwind CSS: A CSS framework I've recently started using. I don't love most CSS frameworks, but this one meets most of my needs and has a lot of existing components you can just copy/paste into your project.
Stripe: Payment processing, required by Outseta. I don't use Stripe directly since it would require a lot more custom code to set up things like teams, and have the data linked to a CRM. Using Outseta for that stuff saves a lot of time.
Sendgrid: Email API for whenever I need transactional emails for more complex use cases beyond what Outseta sends.
React: UI framework, used by both Next.js and Sanity. Since React is the most popular UI framework at the moment, you'll have a pretty easy time finding open source projects you can leverage, which will save you a ton of time.
Next.js: I build the user dashboard, and APIs in Next.js. I integrate Outseta to gate the dashboard content, and query data from Sanity for things like API keys, user data, or whatever else your app might need
GitHub: Used for source code management, and also scheduling tasks and long-running workflows with GitHub Actions.
GitHub: Used for source code management, and also scheduling tasks and long-running workflows with GitHub Actions.
Docusaurus: If the product is technical, I write the documentation in markdown, and generate a docs site with Docusaurus. If the product is not technical, and I don't need things like syntax highlighting, I just put the docs in the Webflow site.