microsite VS Papercups

None are ready for the public yet, but all in the hopper or under serious consideration:

- Personal site/blog with a bunch of algorithmically generated art and other fun stuff, built on Node/Preact but progressively enhanced/almost completely JS-free at runtime. Motivation for the build approach is that I’m on the low/no client JS static site bandwagon but I quite like the DX of JSX components and CSS-in-JS.

- I’m using a few excellent existing tools[1][2] for said site which unfortunately aren’t designed to work well together, so I have a variety of wrapper tooling that makes them live peacefully together. I’m also developing a bunch of other build-stage tools for my use cases. I plan to open source (or hopefully contribute back) all of that as soon as I’m satisfied with their quality.

- A set libraries for building declarative, type safe, automatically validated/documented service API boundaries (HTTP/REST to start, but I also plan to support other transport protocols) — think io-ts[3] type interfaces but you get swagger docs for free in a transport-agnostic interface. I’ve built this kind of thing before, it was wildly successful in real world use, but it’s proprietary to a previous employer and I’m starting over with all the stuff I learned in hindsight.

- A “nag me” app that’s basically “reading list” plus “reminders” with minimal config, eg “nag me soon” or “nag me after a while”. My personal use case is I frequently screenshot/text myself/etc stuff I want to look at later (usually on phone but need a computer to dive in), then it just goes down the memory hole. I’ve tried setting reminders but it’s often too much fuss, and I’m far too ADHD to use a passive list.

- Exploring building yet another FE build tool/bundler that’s explicitly multi-stage/sequential with static input/output validation, per-step/time travel debugging. Motivation is that existing tools are just a big ball of config magic and totally inscrutable. I’d likely wrap existing build tools because their set of responsibilities isn’t my motivation and I don’t want to introduce that much more new API surface area to weary FE devs.

[1]: https://github.com/natemoo-re/microsite

Microsite es un generador de sitios estáticos (SSG) construido sobre Snowpack y que utiliza Preact como framework.

The best language for the task at hand, when presented with time constraints, is the one that you already know well. OP said in the article that they authored Papercups [1]. Adopting Elixir for a websocket-push service makes a lot of sense, then. However, why don't you learn Elixir, some OTP, and then reconsider that question? You could be missing out.

[1] https://github.com/papercups-io/papercups

https://github.com/papercups-io/papercups - 5.2k stars, uses Phoenix 1.6

Papercups

Phoneix - Elixir

We're a live message tool and it is basically what Elixir is built for https://github.com/papercups-io/papercups.

The Elixir community has been great and incredibly friendly. I originally was worried about the size of the community but that hasn't been an issue the community has been super helpful. I also think the annual stackoverflow usage surveys are very misleading because most of the community's questions get asked in ElixirForum and not on Stackoverflow.

Phoneix is the web framework of Elixir which is very similar to Rails but minus a lot of the magic has been very helpful for our productivity as well.

If I had to built another service that is websocket heavy I would definitely use Elixir. Even if it was a standard crud app I would still most likely choose Elixir.

Interestingly, the features page goes straight to github. With a list of features... followed by screenshots. So I found it!

https://github.com/papercups-io/papercups/wiki/Features

Yeah I agree, we're planning on updating the landing page to include a lot more screenshots/videos/demos :)

In the meantime, here are some screenshots from our GitHub wiki: https://github.com/papercups-io/papercups/wiki/Features

And our demo page: https://app.papercups.io/demo

I maintain the Papercups project, which is an open source customer messaging tool: https://github.com/papercups-io/papercups

Thanks for building this! Love this version I think this would work great for making and fixing bugs. I think automated tests and chores as a category would actually be great to add to this.

For our open source project (https://github.com/papercups-io/papercups). We participated in hacktoberfest recently and one problem we ran into is people submitting low quality PRs. Which ends up taking up way more time to review than to merge.

I would love to be able to filter by users who have merged multiple issues or some sort of quality bar for our bounties. Obviously since you are just starting out your users won't have too many issues merged. You might be able to work around this by finding the number of Github issues an author have merged previously to any projects that is greater than x number of stars. This way you might be able to bootstrap some credibility of the authors. Then maybe a contributor can gate on only allowing some reputable contributors.

One inspiration I would recommend is taking a look at how 99designs has different tiers of designers you can have a bounty for your design. If you could build 99design for open project that would be amazing. Best of Luck!

An open source live chat tool for customer support https://github.com/papercups-io/papercups

We launched on August and have been steadily getting some traction and building a little community in our Slack channel