Not use if it’s a good idea to put rescript files directly in pages/ rather than re rexporting them from a different place like pages_res since there’s a big chance of duplicated file names between pages and other modules.
I am not aware of any naming collision than index.js (which you can also circumvent for subdirectory index.js with a folder.js next to folder). Maybe some [slug].js files might collide, but I haven’t run into this issue yet.
I started the pages_res idea because I didn’t have a choice back then. Now I’d probably just use pages if possible.
The only reason why I had to touch the _document.js file so far was to be able to add a simpleanalytics script to rescript-lang.org. The Next docs state that you shouldn’t touch that file too much, so I kept it in JS format. Also I am not sure if we can efficiently express a class A extends B relationship in ReScript.
Can you create an issue on the template repo and add a minimal reproducible example? I will have a look! For now, you can also have a look at an example within the rescript lang website using getStaticProps / getStaticPaths.