Possible roadmap for future releases

[arecvlohe]

Thanks again for this library. I use it for a public facing project I have. For this reason I am invested in the project at least for the reasonml side of things.

Considering my investment in this project and wanting to see it improve over time, do you have a roadmap or ideas for how the project can improve so that I can spend my off time working on them?

I don't have a great deal experience in this area in terms of what the project needs or where the project can be improved. But if I am given some direction and I can certainly pick things up and take them forward.

One thing I was thinking of improving was upgrading bucklescript to v7. Monadic binding may be landing soon as well too and I thought it would be cool to allow users to have that natively in bs as opposed to having to install a ppx. I can make this in to a separate issue and then you can let me know what the upgrade path would look like if that works.

Anyhow, just some thoughts. I would also be interested in improving docs as well. Anywhere help is needed really.

[MoOx]

Hi,

Sorry for not being involved in Phenomic this days...

There is so many things to do right now that I don't think it's still interesting to spend time on this project. I would recommend you to switch to Next.js since static export is more & more officially supported (See vercel/next.js#9524).

I have currently just a few site I maintain using phenomic & I plan to try nextjs soon.

For reasonml, I guess bindings for next should be available somewhere.

If you really think it's a shame that phenomic is being left appart, we can discuss this more but I have lost hope for this project & nextjs seems a very good replacement.
I won't recommend Gatsby as there is IMO too much "proprietary" APIs & stuff to learn to start using it. Nextjs API surface is very small compared & can be used for fully static/hybrid/dynamic sites so I think it's better to learn & use this.

[arecvlohe]

@MoOx Thanks for the honest response. I was thinking of moving to next.js as well but wanted to see what might be the next steps for this library. I actually was more interested in maintaining the reason-react static site generator than having to maintain the others. But I understand the burden of OSS and how it's better to join a bustling community that has a lot of support than to build such a community yourself. But I agree, I think next.js is a great alternative so I will start to explore that now.

I would probably suggest putting in the README that this project is not going to be maintained in the near future or if you are really sure of its fate then to make the repository read-only.

Thanks for all the work you did on this project and for all your contributions to the reason community, it's certainly appreciated!

[Timer]

Just dropping in here as I saw this issue referenced on vercel/next.js#9524.

I think it'd be cool to collaborate on adding ReasonML support directly to Next.js!

Though, we could start with a plugin first to work out the implementation.

[arecvlohe]

@Timer That would be awesome! I would like to help but would need some guidance as I am no expert on next.js internals. Let me know how/if I can help.

[Timer]

You can view a sample plugin here: https://github.com/zeit/next-plugins/blob/master/packages/next-source-maps/index.js!

This would need adjusted to add the appropriate loaders for Reason, etc.

[Timer]

This example of using ReasonML with Next.js may also be of value:
https://github.com/zeit/next.js/tree/canary/examples/with-reasonml

And a TODO app:
https://github.com/zeit/next.js/tree/canary/examples/with-reasonml-todo

[arecvlohe]

@Timer I will take a look soon. Thanks!