Is this project still maintained?

[nobrelli]

Is this project still maintained?

[fullgukbap]

I, too, would like to see a moderator's answer to this issue.

[alnwt]

Hi, @brendensoares.

TLDR: There are a number of things I'm going to work on, would you be willing to have them under the umbrella of @revel project, probably to be released later as a backward incompatible Revel v.2?

I'm about to start working on implementation of a framework that could provide a complete full-stack experience requiring as little boilerplate as possible. While still using the approach of Revel controllers and code generation I expect it to produce not only back-end side but also production-grade web and mobile clients. That is, the ones that could be competitive with existing JS solutions. To be more concrete, some of the ideas I have in mind:

1. Structure the project the way proposed earlier and followed by some Revel offshoots/rewrites: a set of independent tools at the center (revel/revel), user app is a regular standard library compatible program but with Revel style magic controllers invocation; other packages, being easily replaceable in the user's app, could live in their own repositories (revel/*).
2. Use something akin to elm-ui to abstract HTML & CSS away leaving only common building blocks for all platforms.
3. Use either LiveView Paradigm style or htmx like approach, or consider some form of code generation that would produce assets of reasonable size and speed.

Also to be addressed but no specific ideas yet:

1. Decide how Hot Code Reload could keep app's state between restarts.
2. Come up with a solution for models and automatic app deployment.

Is it something that can be done under the umbrella of @revel project? If so, I'll work on its fork so it can be merged back later. If not, I'll start from scratch.