TLDR; Mead is a special case static site generator that automates the process of compiling and uploading to your S3 account.
Mead is a desktop application that combines the flexibility of static site generators (Jekyll, Hugo, etc) with Medium's ease of publishing. I created Mead because I wanted to write more and the present options put up too many obstacles.
Like many others, I don't like the experience Medium offers to readers. Modals and banners distract the user from engaging with the content and in some cases, prevents them entirely.
Static site generators are great in terms of their flexibility. They're the only way we can fully control what trackers and advertisements readers are exposed to. However, the writing process is a bit cumbersome. I often forget the commands I need to run, and I'd like to not have to run 3 git commands every time I notice a typo.
Mead, at its core, prioritizes simplicity. It was made so I could easily open up an app on my computer, write some text, add an image (automatically uploading to S3), paste in a code snippet, click a button, and have the whole thing public without any other effort.
Mead is also an experiment in creating a product that does not need advertisements or trackers to continue existing. My goal here is to fully respect the privacy of others. If I'm failing in some way, please gently point it out and I will make the necessary corrections.
If you have any comments, feedback, or feature requests, please feel free to reach out. My email is [my username] at gmail
(Yes, wrote that like that on purpose)
Cool that you launched and want to build a business 100% but reconsider your features vs cost design and the value you want to deliver. You'll have a lot better chance at building a solid platform to push back on the monetary building tactics Medium has been pushing the hard the past couple years.
Limit on things like custom domains, customization, or tack on features that aid in growth or marketing if you want to wrap cost up in gained features/value by paying.
Thanks for your honest feedback and letting me know which features you find value in.
1. Why S3 rather than an entirely free service like netlify, github pages, or surge?
2. Isn't one of the main advantages of medium the discovery element? As a reader of medium, I get connected to articles from new authors based on my interests. As an author, readers are connected to me who may not have otherwise heard of me.
> Why S3 rather than an entirely free service like netlify, github pages, or surge?
I wanted to start with something that was simple and scalable. At one point I tried using github for hosting, but managing commits got a bit complicated. There are also some limitations on repository size. Although it wouldn't become an issue for a long time if images were uploaded to S3 and the content to github, I would have had to integrate with multiple platforms.
I am open to adding additional hosting solutions, but I wanted to launch to get a pulse on what folks would like those options to be.
> Isn't one of the main advantages of medium the discovery element?
This is definitely one of the main values that Medium has to offer. It's also not the only reason people want to share their thoughts. I wanted to offer the flexibility to own your content and not be locked in to a platform (All HTML files for your site remain in your control). There are a lot of ways to promote your content, if Medium happens to work best for some folks, It could be a good idea to cross post on Medium.
As Mead evolves, I'm open to making promotion of your content on other services easier and in as many cases as possible, automated.
I hope I don't sound too harsh, seems like a good idea overall.
That said, I’d consider opening up the free tier to be almost the same features as pro except you need to include the a “get Mead” banner on the site.
Can I reach out to you for future feedback when I'm reconsidering plans?