search

0xVentures / 0xV-website

0xVentures Website
https://0xventures.org
3 stars 1 forks source link

Dev decisions #11

Closed Framsynt closed 3 years ago

Framsynt commented 3 years ago

I guess someone needs to start with this question: how are we going to build this site? Which backend, which frontend, which DB? I know people have really strong opinions about those things, so it would be great to be on the same page from the start.

If it was discussed before in Discord, please copy here.

fullmetalengineer commented 3 years ago

I personally am not super opinionated.

I prefer front-end work in React or a react-based framework like Next.js. I like Angular too. I have no experience with Vue.

For backend tech, I primarily build with a Rails API layer, but I've worked with Node in the past too and enjoyed it. So, I'm open. I can learn just about anything, I'm not really worried about it. If someone has a preference, I'm fine with going with that.

IShotTheSheriff commented 3 years ago

My point of view:

As mentioned on Discord I also believe website is not the same as webapp. Therefore we might think of doing this repo a monorepo. For starters I guess there might be 3 packages - backend, website and webapp. Food for thoughts.

As for the backend solutions I do like idea of firebase although I don't have too much experience. Graphql API seem to be cool and we can defintiely try to build with Apollo, but then again I'm not too opinionated here and REST + Node.js backend is also a viable choice for me.

Any other backends like Rails or Python based I just wouldn't be able to help much, but if we got experts on board I wouldn't mind either.

Framsynt commented 3 years ago

My skillset is in SCSS, UI, UX, typography. I made some webapps and mobileapps, but I am far from expert. I see two votes for Next.js, I have not worked with it but agree that it is a way to go.

What I am opinionated about is styling. Tailwindcss is IMHO a nightmare to keep the style consistent. I am more https://maintainablecss.com/ fan. But we will se what others think. I can adjust. I will be working on a style guide to keep everyone on the same page.

I used firebase before while coding dart/flutter apps. I feel its super user friendly, but I am not sure if we want to be tied too much to google. I guess it is up to @bullishtrader.

I am not sure what scope the webapp will have. Graphql API seems to be an overkill. Again, Bull said he has everything in his mind and need to dump it here first. We will see.

I guess we also need to start discussion about architecture. I am not sure how would the website and app differ. Should the website be just a showcase? It could be static then.

fullmetalengineer commented 3 years ago

I am sort of a Rails API expert. Not opposed to Node.js either. Next.js is fine with me, I have some experience with it. I've never tried GraphQL but it feels excessive for a small project not touching a bunch of services, or do I have the wrong read on it?

bgbahoue commented 3 years ago

I'll be able to help on the backend if we go the Node.js + REST route. I don't know Graphql but do know that a lot of similar overlay exists. I think it overall depends on (1) the complexity and (2) the maintainability of what we want to do.

We can also do both BTW

  1. start with Graphql to deliver something fast and
  2. refactor on Node.js or any other language in //

Finally we don't have to choose only 1 language if we have a REST approach. We can break down the backend API in different micro services, each running in its own language. Will be more painful in term of maintenance but could work as well and might be a better use of our collective resources and won't put the workload on only 1 person

Just my 2p :)

Andyproject1 commented 3 years ago

Hi guys,

My skillset is JavaScript, HTML, CSS. My strong points are working with frontend, design included. I have worked on a previous website in the past for work experience. However i am currently working on the Privacy Policy and Terms and Conditions as discussed with The Bull. Happy to help with the small stuff if you guys decide it's best you work on the website i can try help with designing it too, currently working on a mockup as we speak.

Framsynt commented 3 years ago

This can be closed now.

As @IShotTheSheriff PRed, we are going nextjs + firebase + microservices. Styled components for styling and most probably three.js with webGL for graphics.