go-mail VS Hugo

Using it for my private blog, a website of a NPO and the documentation site forgo-mail. Wouldn't choose anything else anymore if I don't have to.

You might want to check out the go-mail package, which takes care of all this for you.

The used [gopkg.in/mail.v2](gopkg.in/mail.v2) package hasn't seen an update in 4 years and seems unmaintained. I suggest to use go-mail instead.

The gomail package you are referring to has not seen an update for 6 years and seems to be unmaintained. I suggest to use go-mail instead, which is actively maintained and implements some additional features that are not found in the unmaintained one.

$ go run main.go Date: Sat, 08 Oct 2022 12:47:50 +0200 MIME-Version: 1.0 Message-ID: <[email protected]> Subject: Why are you not using go-mail yet? User-Agent: go-mail v0.2.9 // https://github.com/wneessen/go-mail X-Mailer: go-mail v0.2.9 // https://github.com/wneessen/go-mail From: To: Content-Type: multipart/alternative; boundary=9c5a427bc18e45ff56e0b8f7053cddceaca54a5c985a425213544ab7977f --9c5a427bc18e45ff56e0b8f7053cddceaca54a5c985a425213544ab7977f Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 You won't need a sales pitch. It's FOSS and HTML! --9c5a427bc18e45ff56e0b8f7053cddceaca54a5c985a425213544ab7977f Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 You won't need a sales pitch. It's FOSS and plain text! --9c5a427bc18e45ff56e0b8f7053cddceaca54a5c985a425213544ab7977f--

Due to the above mentioned reasons and the lack of proper alternatives decided to write my own Go mail library. On a long weekend I started working on wneessen/go-mail and in the night of Sunday I had a kind of working prototype and I implemented it with js-mailer.

This blog is running on Hugo. It had previously been running on Jekyll. Both these SSGs ship with the ability to create excerpts from your markdown content in 1 line or thereabouts.

Hugo

Hugo is a popular static site generator specifically designed to create websites and documentation lightning-fast. Its minimalist approach, emphasis on speed, and ease of use have made it popular among developers, technical writers, and anybody looking to construct high-quality websites without the complexity of typical CMS platforms.

As per many other comments, it sounds like a static site generator like Hugo (https://gohugo.io/) or Jekyll (https://jekyllrb.com/), hosted on GitHub Pages (https://pages.github.com/) or GitLab Pages (https://about.gitlab.com/stages-devops-lifecycle/pages/), would be a good match. If you set up GitHub Actions or GitLab CI/CD to do the build and deploy (see e.g. https://gohugo.io/hosting-and-deployment/hosting-on-github/), your normal workflow will simply be to edit markdown and do a git push to make your changes live. There are a number of pre-built themes (e.g. https://themes.gohugo.io/) you can use, and these are realtively straightforward to tweak to your requirements.

Create the technical documentation of your project You can use any of the following options: * A wiki, like the ArchWiki that uses MediaWiki * Read the Docs, used by projects like Setuptools. Check Awesome Read the Docs for more examples. * Create a website * Create a blog, like the documentation of Blowfish, a theme for Hugo.

Doing this made me appreciate existing SSGs like Hugo and Next.js even more👏👏

I suggest hugo: https://gohugo.io/

Generates a completely static website from MD (and other formats) files; also handles themes (including a lot of them rendering well on mobile), and different types of content - posts, articles, etc. - depending on the theme.

It's open source and, being completely static, cheap as fuck to self host.

I would suggest looking into static site generators. Some popular examples, which are used myself are: - Hugo: https://gohugo.io/ - Jekyll: https://jekyllrb.com