Next.js + Apollo + Server Side Rendering (SSR)

There are a variety of approaches, but Shaw has set his sights on a very developer-ergonomic version here where you can leave queries on individual components and mark them as SSR-or-not.

[@PiotrNalepa]

Apollo is nice, but I suggest to start from urql first. Thanks to that, you have a very lightweight version of Apollo (the same API) and if you need more sophisticated solutions then there's no problem with switching to Apollo in most cases. Using urql helps developers to keep app bundle sizes much smaller than when using Apollo library.

[@mrcaf2824]

Great gentlemen, keep up the good work.

[@sinamashini6708]

The only thing that I didn’t get is when we have this approach and we navigate to other page the page should be refreshed or no need to refreshing the page for having n SSR

[@ZealousSwede]

Great stuff.

[@andreadiotallevi5780]

Very interesting! I have been searching for a solution to this exact problem. Only reservation is that getInitialProps used in the setup will be deprecated so I am not sure how maintainable this solution can be.

[@user-hv4m4441]

У

[@Образовательный-э6г]

Здравствуйте
Мы занимаемся в сфере образовательных онлайн уроков. Мы ищем решение редактора блочной доски для создания этих уроков которую можно интегрировать на наш сайт.
Доска должна быть функциональной и гибкой, создавать уроки из картинок, видео и текста. Лучший вариант это блочный редактор, где будет возможность вставлять блоки и каждый блок наполнять картинкой, текстом или видео, и чтобы это было просто для наших преподавателей. У вас есть подобное решение?

[@isaac4386]

This so cool cause you dont need to have getServerSideProps anymore to sever side render the page

[@onrjs]

Why