New features

Also, I just had an idea. For the "new features" thing. What about creating a markdown file, that we update and keep into the single_app folder, that is updated whenever we want to update it, and you write a parser to take the markdown language and parse it into HTML from the backend markdown file. This way, we can avoid the whole pipeline thing, but also keep it for AGC. If you build it right (for example, have a header with the release version, make that an accordian, all the features for that release), you could have several releases "in the rears" for the feature updates and what not.

Then we have a new features for users and admin for controls.

Review the single_app folder and the existing pipeline and AGC references first. Define how the markdown release data should become backend HTML, including release accordions and the separate user and admin feature controls. Done requires an agreed scope and working behavior for these areas, but the issue does not name files or tests.

Written by the indexing model from the issue text.