My bi-annual
@documenso
blog post just dropped!
Dig into the nitty gritty of our new embeds and how we built them as well as the new Documenso Platform? 👇🏻👇🏻
Today at
@documenso
we released embedding for Documents and Direct Templates, this lets you embed our signing experience into your application or website!
You can see it in action here 👇🏻
At
@documenso
we recently integrated Kysely on top of
@prisma
so we can migrate our nasty raw queries to a type-safe alternative.
Can't wait to use this to tackle some of our more complex queries within the app where Prisma's querying language isn't 100% suitable!
The best part about the new
@Documenso
landing was definitely building it with
@shadcn
’s UI.
Such a beautiful and themeable set of primitives for any kind of project 😍
Soon to be open sourced 👀
2023:
- Joined
@documenso
as a co-founder with
@ElTimuro
- Wrote a bunch of bad code
- Landed our angel and pre-seed
- Met a bunch of awesome founders and contributors
- Had my first child (daughter)
My 2024 Goals:
- Launch more frequently
- Share more socially
- Become a better leader
- Hit 20k stars for
@Documenso
- Build a complimentary product with Documenso
- Use Remix
@dan_abramov
The amount of times I've had to refactor another developers code into something simpler because they thought they would be smart...
should be pre-requisite reading for all juniors and mids.
1/ When building Documenso, we've prioritised not bundling required third-party services. This has affected a lot of our decisions but we believe it's helped develop a more robust system and helps us reduce points of failure over time.
Working with
@shadcn
UI library is a breeze, I'm now able to crank out some pretty nice components without needing to think about styling basics.
Instead I can just tie together a few primitives to make elegant comboboxes, dialogs and more.
In the past week I've gained 50 new followers from my review and walkthrough of the
@calcom
codebase, I never knew that people were so interested in understanding open source and hope I can keep you all engaged in the future!
1/ Day 7 of reviewing the
@calcom
codebase.
Today is the last day that I'll be doing these reviews for the moment, but I've had such a fun time doing this so I'll be back once I've finished some other projects.
Anyway, today we're going to look at the main web app.
In following with
@shadcn
's tweet, this week I'm going to read through the
@calcom
source code and note my findings towards the end of the week.
Thanks to
@peer_rich
and the team for their commitment to open source.
I had a whole idea to write a bunch of threads about our company handbook at
@documenso
but I went and forgot to do so didn't I? So instead of trying again you can just view our handbook below 👇🏻
@calcom
is about to get even faster! 😎
We’ve just merged a PR to use
@nextauthjs
’s getServerSession method for SSR and API routes which will speed everything up.
Special thanks to
@zomars
for taking the PR one step further and refactoring even more!
Single player has begun, why waste time signing up to one of the big players and handing over your cash just to sign a simple document.
We'll let you do it fast and for free, try out single player mode and support us on ProductHunt!
We're edging closer and closer to 200 stars! Thanks to all our lovely contributors and followers who want to see document signing be open and transparent 🤗
Want to join in on the fun? Give us a star on Github at
The best part of this is that we had no idea Cat had gone to Barcelona because simply put we don't care!
Work from anywhere and get shit done, that's all that matters 😎
Thanks
@calcom
was reading through the latest post on cold starts since I wanted to see how it all ended and noticed I got a lil shout out 🥰
This is why I love open source!
1/ Recently I embarked on using
@supabase
and
@prisma
together for a side project.
I chose these two as I'm really enjoying using Supabase and I've been meaning to learn Prisma for some time now having previously been a long time TypeORM user.
1/ As we open up our handbook I wanted to chat about parts of it and why it's important to us. For this thread I wanted to chat about our culture at
@documenso
since it's something we consider to be super important to the way we work and how we've made it this far.
I became a parent this week and it’s weird but I’m using ChatGPT more than ever to quell concerns since the only other option is blogspam and outdated books 👨👧
Does anyone have any good recommendations of moderate sized applications built with
@vercel
's Next 13 (app dir)?
I've already read through
@shadcn
's Taxonomy but looking for more to compare best practices and what not.
@Documenso
has a fresh coat of paint 💅🏻
While we're working hard and getting ready for our production release and launch we thought we'd give our landing page an update!
Check us out at and subscribe to be notified of our launch 🫡
Very excited about todays release, adding Zapier and Webhook support will allow others to finally start building their ideal workflows with Documenso!
Kudos to
@catalinmpit
for all his hard work getting this done 💚
Launch. Week. Daaaay. 4 🤘
We all want connection 💚 But not all of us want to go through an API.
Introducing
@Zapier
for Documenso! ⚡️
You can now use the Documenso integration with 5000+ apps to build all kinds of automated workflows. 🚀
Honestly making a simple message queue in Postgres is way too easy.
The below lets me pluck print jobs from the database giving me "exactly once" delivery with retries in the event that the transaction fails somewhere.
@GergelyOrosz
Honestly, I've been on the side that have argued this and then gone and done the rewrite several times. Each time we start cutting fluff that we thought was no longer needed only to come back and reimplement it as it was crucial to certain clients/users.
I'm still thrilled that
@ElTimuro
reached out and asked me to "roast" Documenso 😎
It was such an awesome project to come across and I felt like I had a lot I could bring to take it to the next level 🔥
So naturally when he asked me to join the founding team I had to say yes!
Papermark is nominated for a Golden Kitty Award in the Open Source category on
@ProductHunt
🙀🏆
So incredibly grateful to all open source contributors and my fellow nominated OSS projects 🫶
Let's vote for Open Source! ✨
I've gained like 100 followers in the past couple days, it's nice to meet ya'll!
I'd love to get to know what your up to and what you want to hear about 🤓
After 8 months of building
@middayai
we are finally live on
@ProductHunt
→
Midday is an all-in-one tool for running your business smarter.
Your support would mean the world! 😸
With the
@supabase
launch week around the corner I thought I'd drop a talk I wrote for my local JS meetup early for those who are still debating whether they should adopt Supabase for their company or project.
This week I'll be adding a fallback provider to nodemailer so we can have a safety net for Documenso when an email provider has an outage.
While I have the general implementation pretty well planned I'm not sure on who our secondary provider should be, any recommendations?
Pushing into the final hours of launch day!
Single Player lets you sign and seal documents for free without an account 🔒
Quota agreements, NDA's and even Resumes, you can sign it and show that it hasn't been modified effortlessly 🔥
Support us here:
We're edging closer and closer to 200 stars! Thanks to all our lovely contributors and followers who want to see document signing be open and transparent 🤗
Want to join in on the fun? Give us a star on Github at
@jarek_rozanski
@jdnoc
You're thinking too typical, you can run this at home or colocated in a datacenter and then run a few smaller cloud servers to push jobs onto a queue that this processes.
@supabase
If you liked the video and would like to present it at your local meetup just like me, you can find the slides at the links below!
- Raw Slides:
- Presentation:
If you have feedback, I'd love to hear it so I can update the slides!
@Steve8708
The good: The abundance of libraries and packages for common problems.
The bad: The lack of first party defaults, no two projects are the same.
So I have a nasty habit of naming my
@zodtypes
schemas ZNameSchema with the inferred types being TNameSchema due to some issues I had a while back with type shadowing.
Today I got to force my beliefs onto
@calcom
with the team merging a massive PR that splits up the tRPC router!
Apparently I'm blogging again? I was recently asked about the best way to reach the next level as a developer and see the things that others might miss so I wrote about it 👇🏻
@documenso
just handed out its first bounty (tip) to one of our awesome contributors who added dark mode support to our new design.
We love our community and want to reward them when they do awesome work and we're so glad to have
@algoraio
enabling us to do so! 😍
Shout out to
@NFS__21
for his awesome contribution recently! It only took me forever and half to review but he's been slamming away awesome PR after awesome PR 🎉
Check it out:
A common thread I've seen is people wanting to run headless browsers (Puppeteer, etc) on
@Vercel
for their apps.
They typically end up running a seperate server or spinning up another Vercel project to avoid the function size limits but did you know there's a better way? 👇🏻
It finally happened, definitely happy to pay for
@gitpod
since it honestly saves me so much time and sanity when working with pull requests.
No more tossing my changes and database and putting off reviews!
I did something a bit silly the past few months and built a point of sale and order at table solution for my wife's new restaurant.
While challenging I had a great time working with Next.js appDir,
@shadcn
's UI primitives,
@supbase
and Prisma.
An awesome opportunity for those still in the early days of their COSS journey!
Honestly something I wish I had years ago when I was working on an OSS project with no idea how to push it further.
4/ Another example of this is our file uploads we wanted to use S3 and CloudFront but don't want to burden self-hosters and developers with that choice; so we also support database storage with room to add more providers in the future.
Server actions were causing some bundling weirdness that would cause a top-level await in the final chunk, ripping it out and switching the actions back to tRPC resolves the issue and brings bundling back to normal 🥲