Closed he3als closed 8 months ago
So this would be one page with a bunch of headings and subheadings? It seems like there's a lot to cover.
I might do it with tabs, but probably headings.
I might do it with tabs, but probably headings.
You should do it. 🥺
@he3als https://prebook.asterisk.lol/faq/features/ something like this?
It could be automatically generated to a degree due to all of the YAML files in the Playbook having descriptions and titles, but I'm not sure.
It could be automatically generated to a degree due to all of the YAML files in the Playbook having descriptions and titles, but I'm not sure.
Yeah but in terms of layout, and yes it should be autogenerated that's so much easier, we do that for the bot already.
I'm sure the almighty 🦆 can handle such a task.
The 'Removed Features' page was rewritten. It's not a complete changes list, but I think it's good enough, so I'll close this.
9hAhZ6iik
Test
Currently the Removed Features page is not very descriptive, and a formatted page of changes should be completed to be more transparent with users. By formatting, I mean making the page have different headings for different categories of tweaks, like removals, QoL changes, etc...
Each YAML file inside of the Atlas playbook has a description and title, which can be used to aid in this.