charlesTwenty

17 ms·

1.
by charlesTwenty 3y ago
Hi, I'm Charles and leading the engineering work on Twenty! We've made the bet to invest on a tailored design for our components. Using an existing UI library is a strength to use robust components and move faster, but I've a
2.
by charlesTwenty 3y ago
Very nice Readme! What have you used to generate the illustrations? Also, congratulation guys. It looks very interesting and as an engineer I'm always happy to see more open-source solutions!
3.
by charlesTwenty 3y ago
Hi, I'm one of the main maintainer of Twenty and we have onboarded Gitstart on our codebase a few weeks ago. I can give a feedback on our collaboration so far: 1) Code quality is good, I would compare it to a very good junior engineer
4.
Show HN: Open-Source Favicon Provider(github.com)
14 points by charlesTwenty 3y ago|0 comments
5.
by charlesTwenty 3y ago
Interesting feedback! The recommended install is already local (through yarn). The only piece mentioning docker is to provision a Postgres database, which you need to have to run a CRM anyway. We have planned to replace it by a section expl
6.
by charlesTwenty 3y ago
We are unsure about the right license to use, so this is a great feedback. We had a MIT license one week ago that we know that we cannot hold on long term and we felt we were lying to the community by keeping an MIT license and changing it
7.
by charlesTwenty 3y ago
The pricing is for the cloud version: you can use it for free if you stay under 100 contacts. Self-hosting is completely free!
8.
by charlesTwenty 3y ago
Thank you!
9.
by charlesTwenty 3y ago
Yes, as an engineer I am rooting for opensource and to build something that last beyond the company. I also think it will force us to install a good company culture centered around transparency and give back. They are many example of succes
10.
by charlesTwenty 3y ago
Yes! https://app.twenty.com . It's still very early but we are happy to share it and to get feedbacks. We already have a few users that are using it on a daily basis and we are trying to get as much feedback as possible to
11.
by charlesTwenty 3y ago
Thank you, we put a lot of effort into providing a good user experience and a good developer experience. Feel free to jump in on Github issues!
12.
by charlesTwenty 3y ago
+1, thanks for the link
13.
by charlesTwenty 3y ago
Very interesting, this makes sense, it is definitely a direction we could go into. We are using Postgres and were also considering using 1 schema per tenant.
14.
by charlesTwenty 3y ago
Thank you, happy to see you on the codebase!
15.
by charlesTwenty 3y ago
Thank you for the feedback. What you said resonates with me a lot. Standardized APIs: While we are designing Twenty, we have in mind to provide three APIs: a GraphQL API (headless), a Front-end React API and a NodeJS API that engineers coul
16.
by charlesTwenty 3y ago
We have mainly chosen to use JS on the frontend and on the backend to lower the learning curve for people that would want to contribute / extend it to their own needs. Then typescript (with its limitations!) it our best shot on top of
17.
by charlesTwenty 3y ago
A middle ground I've encountered in an ERP system (prophet21 if you're interested) was each table had multiple "CUSTOM_XX" columns that were initially blank. Customers could edit their UI and would drag/drop the cus
18.
by charlesTwenty 3y ago
Haha! Yes, fixing it, thank you!
19.
by charlesTwenty 3y ago
I'm rather worried about having a large table being able to accommodate for any custom object than the fact it is multi-tenant, we could shard by tenant_id quite easily. I might be missing your point and I'm far from being a datab
20.
by charlesTwenty 3y ago
Yes, agree! We try to re-use as much opensource software as possible. One difficulty is that we are also trying to make it as easy as possible to self host the CRM. If we start including all these tools by default, it will be hard for peopl
21.
by charlesTwenty 3y ago
Thanks for the feedback! We have been discussing this a lot. Here is one of the option we have in mind for the upcoming months and we would love to know if this could work in your opinion. Data ownership: a) Twenty makes the distinction bet
22.
by charlesTwenty 3y ago
That's a very good point. In the early stage, we were thinking about a single tenant architecture which would make this questions way easier. However, I am a strong believer in multi-tenant architectures as they allow to scale while mu
23.
by charlesTwenty 3y ago
We also plan to support CSV import and export
24.
by charlesTwenty 3y ago
Yes, we are providing a graphql API that you can find "documented" here: https://docs.twenty.com/graphql/ Right now, you need to provide a JWT token that you can get at login or refresh against a refresh_toke
25.
by charlesTwenty 3y ago
Sure! We want to build something flexible where users can define their own custom objects and fields. We were thinking about leveraging Hasura that's already providing a flexible graphql API based on metadata which is exactly what we n
26.
by charlesTwenty 3y ago
Thanks! Yes :D We are publishing the repo as it is, and we know we have a ton of things to improve, including documentation! I had actually forgotten about this readme, will make sure to remove it https://github.com/twentyhq