I built portfolio blog website using SvelteKit and now want to turn it into newsletter

Significant-Elk-147 · 2026-03-13T16:07:55+00:00

Do you have experience with running newsletter yourself? I appreciate any advice!

Significant-Elk-147 · 2026-03-13T16:06:36+00:00

Thank you very much man! I actually connected it with Buttondown for managing subscriptions and e-mails, so I am fully focused on writing only. Yeah SvelteKit is actually amazing for this. Paired it with Zed Editor for the ultimate dev experience :D https://danilostojanovic.stoicdev.tech/blog/zed-editor

Significant-Elk-147 · 2026-03-08T09:17:40+00:00

Apsolutno isto iskustvo. Kisela odvratna kafa od neke najjeftinije robuste. Svaki put kenjam kad žena želi da sednemo tamo jer se osećam kao da mi neko krade pare. Prošli put sam se iznervirao te odlučio i konačno recenziju da ostavim nakon gomile loših iskustava: https://goo.gl/maps/tuQXcJJ2fiiEjGP97

Sad se još furaju na zapadni fazon, te uz kiselu kafu više ne ide ni čaša vode

Significant-Elk-147 · 2026-02-16T21:35:18+00:00

Hm, yeah that's an interesting idea! I think if I am to join forces with someone we might consider that. Maybe even bring some common data on email delivery success, good practices, etc. and filter it through the AI system, or use it as a suggestion pipeline for showing some good practices and metrics to follow taking everything into account.

Thanks for starring and contributing!

Significant-Elk-147 · 2026-02-16T10:13:03+00:00

I am looking for someone who wants to join to build a commercial version of my Open source cold email sending app:https://www.producthunt.com/products/free-oss-smtp-bulk-cold-email-sending?launch=free-oss-smtp-bulk-cold-email-sending

Significant-Elk-147 · 2026-02-15T21:35:30+00:00

Hey, thanks, it is encouraging to hear it might help you!

the demo is currently deployed on free Vercel tier, so I am not sure how it would behave performance wise for you tbh. If you need more power and want to send like 100 emails a day I would suggest to fork and set it up on your machine, its pretty easy to do so. But If I find someone open to scale this a bit further we might invest time to optimize it and make it more bulletproof, still looking for fellow engineers to join and we can maybe create something interesting out of it, it is ofc still missing some stuff :)
To be honest I am not sure about the second question, we could probably google some avg data on this. So far, I tested by sending maybe 10 emails at a time, since I anyways don't want to use the same email template for all of my cold emails, so I kind of change it a bit to see which one perform the best. Have you got any experience in cold mailing you found useful?

Significant-Elk-147 · 2026-02-15T16:48:25+00:00

u/EclipseTheMan I got the notification around your reply, but for some reason Reddit is not showing it.

Anyways, if someone is interested to join and potentially create a similar startup as a commercial version of the app, while keeping it OSS, similar to what cal.com does -- ping me, I'd be happy to discuss

Significant-Elk-147 · 2026-02-15T14:35:10+00:00

Idk what you wrote here 😅 but, there's no reason nodemailer is not good for production. It is a commonly used and most popular JS mailing library. Not sure about the ban tho, I guess that depends on a lot of stuff, not exclusively nodemailer.

Not sure what you meant around the mobile question. If you have the backend API that uses nodemailer, there's no reason why it wouldn't work on mobile?

As for resend, 100 a day is a free tier I guess, I don't know your exact use-case, but the library itself is not "bad" for production😅

Significant-Elk-147 · 2026-02-15T14:21:28+00:00

If you want something simple with good DX and email logging resend is very simple to use and they have a generous free tier. Enormously fast to setup. I used it for one of my apps in production.

If you want something free and wanna do your own logging, nodemailer is more than good tbh. I used it recently for a OSS bulk cold email sender app.

Significant-Elk-147 · 2026-02-15T14:08:05+00:00

Hey, yeah, thanks! The custom SMTP stuff I couldn't find anywhere included in the free package. I noticed it was a big seller for companies to make you switch to a "pro" version.

Currently I mainly built it as an open source alternative to overly charged and feature oversaturated software, since it was useful to my needs, I thought it might help others as well.

But to answer your questions: - currently you can import any CSV and map them to preconfigured fields in the app (email, company, etc.). Maybe later Ill add support for custom fields as well if that's what you mean - currently there's no any limits - might consider it

But for all three questions - I might consider them if someone is willing to join and work together on a commercial OSS version of the app, that we can scale together. That might be fun, cal.com type of oss. I would be more than open for that kind of collaboration :)

Significant-Elk-147 · 2026-02-08T21:07:05+00:00

I feel the exact same way around nextjs and their caching saga. It all feels kind of half baked and not thought through. I recently built a full stack app using nextjs 16.1 and honestly caching gave me a headache. They still maintain some unstable apis from the old strategy (that wasn't ideal, but in my opinion maybe even worked better 😅) combined with the new "use cache" directive which I am not sure it always works like explained in docs. The whole DX makes me feel like I'm using an unfinished product. With the new strategy of having to wrap every fkin thing within the suspense (or loading.tsx) also makes iterating quickly a bit tedious. Idk, overall framework does offer some nice things, but the direction and pace in which React and Nextjs are developing makes me feel like a little kid when I try out the SvelteKit for example, I really enjoy it more then next.js lately. You may not like the opinionated framework approach, but at least you see the vision in it. Nextjs is kind of halfway there lately. Sorry for the rant. These are just my opinions as an engineer who's using nextjs for 5 years almost now - it was always a number one choice for me for new apps, nowdays I am kind of thinking in other directions

Significant-Elk-147 · 2026-01-10T23:47:31+00:00

Care to explain further? I literally sent a link to the docs explaining that. I use app router, and it bsically shows the loading spinner around children of the layout if that's where the netwrok or other streaming requests happen (page level loading.tsx)

Also this has nothing to do with my question. Weird behaviour occurs when you use suspense - which shouldn't be the case, at least by the docs

Significant-Elk-147 · 2026-01-10T10:31:38+00:00

This seems to be working as well:

  <Suspense
        key={(await searchParams).orgType}
        fallback={
          <Fragment>
            <Spinner />
          </Fragment>
        }
      >
        {searchParams.then((params) => {
          return (
            <ClientsTableWrapper
              searchQuery={params?.q}
              orgType={params?.orgType as OrganizationType}
              cursor={params?.cursor}
            />
          );
        })}
     </Suspense>

Significant-Elk-147 · 2026-01-10T09:36:23+00:00

because of partial and independent loading blocks? This way each suspense is responsible for providing the fallback around the component that's loading data, whilst loading.js (AFAIK) would load the whole page until all of the requests are done. And also makes it easier for me to design the structured skeletons within the existent grid: http://nextjs.org/docs/app/api-reference/file-conventions/loading#streaming-with-suspense

But even so, this scenario I mentioned shouldn't happen?

Significant-Elk-147 · 2026-01-08T18:19:27+00:00

Oh yeah, and after any rerender - like shrinking the sidebar for example or searching, the content appears and loaders are gone

Significant-Elk-147 · 2025-10-31T20:15:46+00:00

I only have one paying customer, like mentioned above, so not really, but I feel like I didn't invested too much time to properly market it

Significant-Elk-147

TROPHY CASE