Editor.js VS Twenty

I am supporting a project where lawyers, advisors can publish articles or news, to get more attention and clients. Initially it was made through TinyMCE, but they wanted not just HTML, but also a way of showing many pictures with interactions. I was seeking UI editor like Medium, and I guess best what I found was EditorJS and during checking its Awesome List there were several carousel plugins and I stopped on this.

We call it EmailBuilder.js – a powerful block-based email builder that takes the best parts of other open source libraries like Editor.js and email component libraries and puts them into an easy to use no-code builder.

I tried the "Doc", "Sheet" and "Slide" feature and each of them are incomplete and lacks most of the popular features. It would be better if the author uses existing solutions instead of implement them from ground up.

editor.js [0] for documents and Grist [1] for spreadsheet are some good examples.

[0]: https://editorjs.io/

Editorjs [https://editorjs.io/]

Use Gutenberg or a block editor like this (https://github.com/codex-team/editor.js) for a CMS. The WYSIWYG days are over.

Has anyone had any luck adding editor.js to your app? I've got a plain rails/stimulus/turbo/activeStorage app which needs a dynamic page builder and editor.js looks like it has promise. However it's a pretty specialized workflow and Im not sure if it jives well with the plain Rails ecosystem.

try this: https://editorjs.io/ might come handy, it's a very nice library and it's well maintained.

I had the opportunity to work on a github issue in an open source project to add a Github workflow that runs if some files where modified in the path packages/twenty-website and checks that the website is still building.

You should check out Twenty! https://twenty.com/ (YC S23) -- they're an OSS CRM.

I totally agree the object management UI is too clunky right now. I want to redo that set of pages, they were the first ones we shipped. Not gonna lie, idk if anyone except me and Ned are really pining to learn hotkeys for managing object schemas, since in practice we're the only ones doing that on a regular basis -- we do initial setup on behalf of our customers.

Yeah, I consider latency part of UX. We're doing some somewhat fancy stuff to reliably replicate every record into a couple of stores, each of which is optimized for different access patterns (search, get latest by ID, etc.). The big central Postgres(TM) is mostly there to be authoritative and to transactionally maintain invariants in the system.

Open Source software will never be able to monetize as well as closed-source. We might only capture 10% of the value we create. But being open source inherently creates strong network effects that tends to push towards a limited number of winners, and the addressable market in CRM is so big that it's still possible to build multi-billion dollar company while massively driving the costs down for everyone.

It's kind of like the Prisoner's Dilemma: If every company keep their software proprietary, they can all make on moderate growth/profit. But if one goes open-source, they could attract a large community, drive innovation, and potentially reap long-term profits while reducing the overall market size.

[1] https://github.com/twentyhq/twenty

Twenty- A modern CRM offering the flexibility of open-source, advanced features and sleek design.

Twenty: https://github.com/twentyhq/twenty/pulls?q=is%3Apr+author%3A...

Our main technical challenge has been securing code sharing. One solution was building GitSlice, which enables creating sub-repos that sync with the upstream repo. When GitStart devs create PRs on the platform, GitSlice syncs them upstream while pulling back CI/CD checks and review comments. This enables our devs to contribute with limited codebase access.

To prevent slices from breaking, we verify they run within a docker container, which also enables us to build review environments. Fun fact: we managed to support native iOS and Android codebases by building and running them on appetize.io instead of docker.

There have been countless attempts at this space so we would love to hear your feedback on how we approached this problem or your past experiences working with junior devs in this way. We look forward to a good conversation!

Interesting, the UI looks the same as Twenty ( https://twenty.com/ ), that was shared on HN this week.

Sorry about that, it's not an intentional dark pattern, just the result of a very short timeline to build this. I've just created an issue to prioritize this soon: https://github.com/twentyhq/twenty/issues/774

We are trying to be conscious about data privacy too (e.g. no tracker or third-party cookie on our website)