Closed apaleslimghost closed 5 years ago
for now, i'm going to use the parts of the shell that Shell includes within the Next.js custom Document
When we've tried Next.js with Page Kit before this is exactly what we did. The shell component provides a set of opinions about how to structure and bootstrap a web page but my assumption is that apps using Next.js would prefer to utilise that frameworks opinions instead.
It would be interesting to know more about this as we didn't look much beyond the shared UI components which are hopefully quite straightforward to implement within Next.js. We did not consider meta data or ads for example which the graphics page must need 🤔
Something worth considering... because the graphics app is only one of the twenty apps we need to migrate any changes required to the shell or other packages in order to accommodate it will need to be balanced against the needs of the other 95%.
maybe a good middle ground would be exporting Shell
's subcomponents from the package? right now i'm having to dip into dist/node/components
which feels like a hack
next-graphics-page
usesNext.js
, and i'm pretty sure the only way to useShell
with that would be via Next'sHead
tag. currentlyShell
uses<head>
, if it were possible to replace that inShell
this integration would be simplerfor now, i'm going to use the parts of the shell that
Shell
includes within the Next.js customDocument