One of the bigger milestones at the moment is getting the frontend working again.
The "rust compiled template engine" (ructe) templates, which are in /aardwolf-templates, are no longer functional due to being stuck on old crates which are incompatible with the code-as-written.
It should also be said that ructe always felt geared toward rust developers, and may not have been as easy for frontend-dev's to pick up. One of the primary goals of this project is to try and keep it accessible to any level of developer, which is one of the main reasons we started looking at (Yew Framework)[https://yew.rs/].
What I would like to see is either:
Fix the existing ructe templates, and write them in a way that is friendly and familiar to frontend devs.
or
Replace them with the Yew versions which have been started in /aardwolf-yew-app
Either solution would also need to be compatible with the future API plans. #315
One of the bigger milestones at the moment is getting the frontend working again.
The "rust compiled template engine" (
ructe) templates, which are in/aardwolf-templates, are no longer functional due to being stuck on old crates which are incompatible with the code-as-written.Link to (ructe docs)[https://docs.rs/ructe/latest/ructe/]
It should also be said that
ructealways felt geared toward rust developers, and may not have been as easy for frontend-dev's to pick up. One of the primary goals of this project is to try and keep it accessible to any level of developer, which is one of the main reasons we started looking at (Yew Framework)[https://yew.rs/].What I would like to see is either:
ructetemplates, and write them in a way that is friendly and familiar to frontend devs. or/aardwolf-yew-appEither solution would also need to be compatible with the future API plans. #315