Right now the web-presence for the ui editor is done with a pkgdown site. This is inherently tied to the R package and also is a bit of a mismatch for the scope of the project. The website should be decoupled from the R package so it can treat Python as a first-class citizen and also have a more flexible setup.
One thing to keep in mind is we probably want to use a toolset/chain that the userbase is familiar with so it's not impossible for users to contribute things like articles or typo fixes etc. This means probably not making it something like a full next.js app and instead using Quarto most likely.
nstrayer
commented
1 year ago
Right now the web-presence for the ui editor is done with a pkgdown site. This is inherently tied to the R package and also is a bit of a mismatch for the scope of the project. The website should be decoupled from the R package so it can treat Python as a first-class citizen and also have a more flexible setup.
One thing to keep in mind is we probably want to use a toolset/chain that the userbase is familiar with so it's not impossible for users to contribute things like articles or typo fixes etc. This means probably not making it something like a full
next.jsapp and instead using Quarto most likely.