
Yemi (shutdown)
Blog like you code. Write, commit, push.
Doesn't seem to be much interest in this product. Might be too specific of an audience??
Still have the code, but servers have been removed.
I still love the concept, and hope Hashnode brings this feature out of beta. Being able to source your articles from markdown files in a git repo - without setting up your own hosting, or local dev environment for SSG - is pretty nice.

If you go to a blog, it'll show article previews - starting with the newest. This is based on the order articles are added to the database - oldest to newest (top/down). Then we reverse the array of articles to have the newest ones first.
It's taken a bit of time to get this page working. Previously, I wasn't storing article content in the database - it was in GitHub. Because of this, there didn't seem to be a good way to display articles on the front page of a blog.
Now, when you upload a new article to your repo, we parse the markdown, gather some data/content, and store a copy in our database.
Slightly off-topic:
This also saves API requests to GitHub. As an authenticated GitHub app, we are allowed 5,000 requests per hour per repo.
Since a copy of the content is now in the database, I can begin refactoring code to pull individual article requests from there too. Right now, when you go to an article (not the main blog page), it pulls the data from the cache if it can, then grabs it from GitHub.
Once this refactoring is complete, the only time we should be making a request to GitHub for content is when you add or update an article.

Comment
Deployed both the backend and frontend servers to the cloud.
I've quickly found out methods in a dev environment don't work in production. In my dev environment, everything was running locally on my laptop. In production, I have two servers - both have a public and private IP, but the backend server is only meant to be accessed by the frontend via the private IP. This isn't working for svelte components which make fetches to the backend.
Believe I'll need to setup sapper server routes for certain functions - which in turn, contact the backend.

Comment
There is now an npm package you can install globally, to help create your articles on Yemi.
Since coders and the like are used to the cli, we figured adding this would be a nice convenience method for creating new articles. Especially since we have several options for metadata which must exist at the top of the article's markdown file.
npm i -g @malynium/yemi
yemi article <article-name>
OR
npx @malynium/yemi article <article-name>

Comment
The following options are now available:
-
primary and secondary theme colors. Paid??
-
logo upload
-
several font options. You can choose separate fonts for your blog's title, subtitle, and body
-
define seo title, description and, if needed, a canonical url - for each article
-
support for multiple blogs. You choose a different branch for each one. May be a paid feature.
Things still in the works:
-
thinking about building an npm package, to easily create articles with the metadata shell already in place.
-
custom domains. May be a paid feature.
-
plausible analytics
-
article header pic
-
the home page design for your blog

Comment
Git is a familiar flow for most developers. So why not blog like you code?
Create blog articles with markdown, and they automatically publish once you push the files to a git repo.
It's simple and familiar. And if you don't know Markdown, it's easy to learn.

Comment
About
(rhymes with Jimmy) You know your git workflow, and you wanna start blogging without any website setup. So we're building a platform where you can write with Markdown, from the comfort of your favorite coder editor.
6 Comments
Hi Jason!
I've come up with the idea of building a newsletter tool for developers with managing posts and campaigns in git.
While researching for a potential problem-solution fit, I've come across your idea and I'm really sad that you've shut down Yemi. On the other hand, that is a signal that maybe such tools for developers are either too narrow, or there might be a saturation in the market already.
Have you shut down because of Hashnode gaining significant traction?
I didn't do much research for my idea. I mainly thought it would be a cool way of writing - with markdown, and sourcing from git - without having to stand up your own ssg environment. Plus moving between platforms can be a pain. That's why I thought sourcing articles from your own git repo was a nice solution. You truly own your content.
I'd imagine most who prefer the git route are using static site generators to accomplish it. So why bother using someone else's platform, like Yemi? But the popularity of Hashnode is proof that a lot of devs don't want to spin up their own local ssg environment.
I think Hashnode is also popular because of distribution. Their community of devs who signup for your newsletter.
I may resurrect Yemi at some point, but a lot more work needs to go into planning the strategy of attracting writers.
Not to mention, are there enough people interested in the idea?
I appreciate the insights, Jason.
Answering to your question – I have no idea, to be honest, haven't done any customer development so far.
But I agree – Hashnode's value proposition is distribution and a dev-friendly workflow.
Great idea. Sorry you are shutting down. Always hoped for something similar for Word documents or PowerPoint.
Thanks!