There is the CSL Visual Editor,. While it's old, it seems like it's improved a lot over time.
But it's pretty complex, as it tries to represent the full CSL 1.0 model.
I'm imagining instead something simpler and higher-level, that both relies on this code and uses some of the ideas I laid out in the link above to ask users a series of questions and spit out a style file.
The anystyle idea would allow users to paste formatted output into a field, and the UI would present a few options to select from.
As I've said before, I'm pretty sure every sort of style variant has already been written, and is somewhere in the style repo. If we can find a way to programmatically extract all those macros into standalone template files that can be shared across styles, the UI becomes much simpler.
So though I doubt it would be needed, for more complex template adjustment, I think there are likely solutions in the JS world, if we can constrain them to simply calling other templates.
Now this is a Rust-first project, am thinking this should be implemented using these libraries, both for CLI and web. But not worth wasting considerable time on it until things stabilize.
Another transfer from the typescript repo. Ideally, I want to include this in the CLI initially.
A core idea in this experiment is that a simpler model enables easy-to-use GUIs; both CLI and web.
https://github.com/citation-style-language/schema/issues/244
There is the CSL Visual Editor,. While it's old, it seems like it's improved a lot over time.
But it's pretty complex, as it tries to represent the full CSL 1.0 model.
I'm imagining instead something simpler and higher-level, that both relies on this code and uses some of the ideas I laid out in the link above to ask users a series of questions and spit out a style file.
The
anystyle
idea would allow users to paste formatted output into a field, and the UI would present a few options to select from.As I've said before, I'm pretty sure every sort of style variant has already been written, and is somewhere in the style repo. If we can find a way to programmatically extract all those macros into standalone template files that can be shared across styles, the UI becomes much simpler.
For CLI apps, see:
https://betterprogramming.pub/how-to-create-beautiful-command-line-interactions-with-node-js-2fcdfbbac62c
So though I doubt it would be needed, for more complex template adjustment, I think there are likely solutions in the JS world, if we can constrain them to simply calling other templates.