Next.js

I've been using Django for quite a long time and in my opinion I would never switch from it. My company is currently using Django with REST framework and a part in GraphQL using Graphene. On the frontend we use Next.js and so far everything has been running quite good. I've found limitations but manage to solve it.

As someone mentioned before, if you are comfortable with Django, don't switch. There's no need since with django you can basically achieve anything. Of course this will depend on the project you want to build, but the scalability and flexibility django can offer it's just out of this world. (Don't want to sound like a fan boy haha but it really is).

At IT Minds we create customized internal or #B2B web and mobile apps. I have a go to stack that I pitch to our customers consisting of 3 core areas. 1) A data core #backend . 2) A micro #serverless #backend. 3) A user client #frontend.

For the Data Core I create a backend using TypeScript Node.js and with TypeORM connecting to a PostgreSQL Exposing an action based api with Apollo GraphQL

For the micro serverless backend, which purpose is verification for authentication, autorization, logins and the likes. It is created with Next.js api pages. Using MongoDB to store essential information, caching etc.

Finally the frontend is built with React using Next.js , TypeScript and @Apollo. We create the frontend as a PWA and have a AMP landing page by default.

Next.js We use next.js to serve SSR, in order to score best at SEO.

We are in the process of adopting Next.js as our React framework and using Storybook to help build our React components in isolation. This new part of our frontend is written in TypeScript, and we use Emotion for CSS/styling. For delivering data, we use GraphQL and Apollo. Jest, Percy, and Cypress are used for testing.

React Next.js Evergreen

Our #Frontend at FeaturePeek uses the Evergreen UI framework as a starting point for our basic UI primitives like buttons, modals, and inputs. I chose this library not only because it's beautiful and frequently updated, but also because the CSS-in-JS model inherited from ui-box is such a joy to work with.

Any CSS property can be passed to any UI component as a prop. Evergreen then compiles atomic classes from the rules used, and injects the styles in the head for every page. The easiest way I've encountered to achieve critical CSS. It even hydrates into the Next.js SSR scripts, so styles aren't lost when JavaScript is disabled.

#Frontenddevelopment #FrontEndFrameworks

Having a single Next.js that handles several websites at the same time, with a lot of custom-unique components can be a pain in the a**, with TypeScript our team can see what props are needed and what kind of data needs to be passed to it in order to work correctly.

We use Next.js because it's the best framework for server side rendering on react right now. Our platform handle websites for clients, which means on all of those websites we need to worry about the SEO, and that google can find them on the search results. Next made it extremely easy in combination with express to be able to render dynamic routes based on the user configuration for their website. We were able to build a small "Wix" in our own platform. 😊

When we started thinking about technology options for our own Design System, we wanted to focus on two primary goals

1. Build a design system site using design system components - a living prototype
2. Explore new ways of working to position our technical capabilities for the future

We have a small team of developers responsible for the initial build so we knew that we couldn’t spend too much time maintaining infrastructure on the Backend. We also wanted freedom to make decisions on the Frontend with the ability to adapt over time.

For this first iteration we decided to use Node.js, React, and Next.js. Content will be managed via headless CMS in prismic.io.

1. Next.js so that we can run React serverside without worrying about server code.
2. prismic.io so that our content is accessible via API and our frontend is fully independent.

I just finished a web app meant for a business that offers training programs for certain professional courses. I chose this stack to test out my skills in graphql and react. I used Node.js , GraphQL , MySQL for the #Backend utilizing Prisma as a database interface for MySQL to provide CRUD APIs and graphql-yoga as a server. For the #frontend I chose React, styled-components for styling, Next.js for routing and SSR and Apollo for data management. I really liked the outcome and I will definitely use this stack in future projects.

We needed a frontend framework for to make it easier to work with JavaScript. We chose Next.js since it maintains the flexibility of something like Create React App but gives some structure on how to organize the app similar to Ember.js.

Webpack and Babel are configured out of the box for #ServerSideRendering, #TreeShaking, and other nice #JS features.