Custom Document support.

[forgo]

Everything in the custom app.tsx currently gets placed into an html <main> tag.

If I want to create a document template with a <nav> component, that contains page <Links>, it is not semantically correct for this to be inside the <main> unless it is a table of contents or tab navigation within the page itself.

I believe this Custom Document feature of Next.js was made for this purpose, but I don't see a way to currently do this in Aleph.

If that's not planned, would it be simple enough to change the following lines to use something like <div id="aleph-app"> instead of <main> to give flexibility to the user to adhere to their own semantic nav and main?

aleph.js/server/project.ts

Line 232 in 659337e

body: `<main>${customLoading?.body || ''}</main>`,

aleph.js/framework/react/bootstrap.ts

Line 60 in 659337e

const mountPoint = document.querySelector('main')

Thank you for the consideration and work on this project.

[ije]

@forgo, thanks for the suggestion, i prefer <div id="__aleph"> instead of <main>.

[shadowtime2000]

I would like to point it that document is meant for stuff like google analytics and third party scripts, not stuff like actual components. I think it would be semantically correct for it to be inside a <div id="__aleph"> which is kind of like what NextJS does.

[shadowtime2000]

Document support would be pretty nice tho it may not be used much because of the built in features of <script> tags and such - so I think this is something we can implement later