A new "native" commenting system on the block

Hi all :wave:t4:

I’m Dan. I’m a software engineer who loves writing. :slightly_smiling_face:

I wanted “native” commenting on my Ghost blog and decided to build my own.

By “native” I mean that it uses Ghost’s membership feature to allow users to comment, rather than requiring them to log in through an additional service like Google, Disqus, etc.

I have a working, early version of the product – which is called Evergreen – that I’ve just launched in a closed alpha.

I’m looking for early adopters who can provide feedback as I continue to add functionality. As an early user, your input will help shape the product and guide its development.

If that sounds interesting, I’d love to onboard you into the alpha to give you access and get your feedback. Please fill out this form, and I’ll reach out.

Let me know if you have any questions, and we can discuss below!

Best,
Dan Isaza

3 Likes

If it is self-hosted – I’ll definitely use it!

Do you have any publicly visible demo or even images of what you’ve created?

1 Like

I have bookmarked this to follow the status of the build. Unfortunately I don’t feel I’ll be a good candidate to a tester but look forward to “native” integrations to work well with Ghost. I do hope the pricing will be favorable because everything seems to keep adding up just to have a website. For us beginner bloggers should that be so?

1 Like

The only “native experience” with a comment system would come from Ghost itself. :wink:

1 Like

no. this a matter of technology, not authority.

Hi @disaza :slight_smile:

I have signed up at your form, and I hope I get a invite to the test version

1 Like

Has anybody here actually signed up and been invited to the alpha?

Hey @DonaldH , I did sign up for help and from curiosity, I actually have a call next week with the developer. So for sure, he is responding, just as far as I know he is very busy this week.

1 Like

@PixelzFairy, thanks for letting me know. I was just getting the “here’s a landing page to harvest email addresses and gauge interest before building anything at all” vibe. Especially since

Let me know if you have any questions, and we can discuss below!

Two weeks later, no questions have been answered.

Anyway, I hope it does turn out to be a good option for commenting on Ghost websites.

Sorry for the slow reply here, @DonaldH!

For the sake of transparency, here’s what’s been going on behind the scenes: I’ve been reaching out to folks who submitted responses to the form and corresponding over email and/or zoom calls to get their thoughts and feedback on an early prototype of the product.

I have the early prototype on my personal blog right now, and you’re welcome to check it out there if you’d like to get a feel for the UI/UX. For example, this blog post has a few comments on it.

Right now, I have it set up so that comments are only visible to logged in members, so you’ll have to create a free member account on my blog to check out existing comments and - if you’d like to - post your own. (You can always remove them once you’ve posted, if you don’t want them to stick around.)

If you do end up giving it a try and have thoughts or feedback to share, I’d love to hear it!


The early conversations with folks have gone well so far, and I’ve gotten some great feedback on some of the critical features that people are looking for.

I’m hoping to have an openly available sign-up for the product ready soon. When it’s ready, I’ll make sure to follow up here so that folks can sign up if they’re interested.

Just to set expectations, Evergreen is currently not self-hosted and I don’t have any plans to make it self-hosted as of right now.

That said, I’d love to hear more about your interest in a self-hosted option.

What aspects of self-hosting do you find most appealing?


Also, if I do ever make it self hosted, I promise you’ll be the first to know :wink:

Thanks @disaza. How would you say Evergreen compares (or will compare) to Cove? Different features, pricing, implementation etc?

I’m hoping to make it very configurable in terms of themes / reactions / etc.

That said, I want the feature development to be driven by conversations with users, so I don’t want to make too many bold claims about how the product will be fleshed out.