You do not need to write the front-end, the server app reads the file at urlServerHomePageSource, fills in some macros and serves it to the user. The client then calls back to the server to get the data it needs using the REST interface.
The client includes JS code and CSS style sheets that form the user interface. That code is not open source in the initial release, it'll need a separate review and cleanup before it's ready for that, but it's perfectly functional.
With this setup you can provide an alternate UI, I plan to do that in converting some of my feed-based products. And I hope others do too. The server has a complete REST interface and additionally, the database can be accessed either through the feedlanddatabase package or through SQL.
This project will be my focus soon
Also I expect to pivot back to this project in the next few days as I (hopefully) finish up on the conversion of Drummer to using email authentication and HTTPS. FeedLand has already been converted.
A frequent question --
You do not need to write the front-end, the server app reads the file at urlServerHomePageSource, fills in some macros and serves it to the user. The client then calls back to the server to get the data it needs using the REST interface.
The client includes JS code and CSS style sheets that form the user interface. That code is not open source in the initial release, it'll need a separate review and cleanup before it's ready for that, but it's perfectly functional.
With this setup you can provide an alternate UI, I plan to do that in converting some of my feed-based products. And I hope others do too. The server has a complete REST interface and additionally, the database can be accessed either through the feedlanddatabase package or through SQL.
This project will be my focus soon
Also I expect to pivot back to this project in the next few days as I (hopefully) finish up on the conversion of Drummer to using email authentication and HTTPS. FeedLand has already been converted.