Description of the need I have adopted a practice of moving config files from the files directory to a special config directory 1 level below Backdrop CMS root. However, this is not consistent across all my sites. I think it would be great if the status report page showed where Backdrop CMS is actually looking for the config files (as set in the settings.php file)
Proposed solution Add "config directory" path to the status report.
Alternatives that have been considered None
Additional information This seems pretty obvious to me so I expect that there is another ticket somewhere discussing this that I was unable to find.
I am also considering that this MIGHT not be a good idea for security reasons. Maybe there are good reasons to not include the path to these files in the UI. I'm not sure if this would be a problem and look forward to hearing from others.
Recent comments
I’ve been diving into adding schema for profile pages too! It can be tricky getting the right metatags. What challenges have you run into while configuring yours? slope run
Add ProfilePage to schema metatag module
I think this is the best gift you can give designers—just design, create a new distribution, and get creative with Backdrop.
Add 'recipe' project type to Backdrop
@yorkshirepudding thank you for the additional info on improving discoverability and a handy way to keep a list of projects for reuse.
Why not add a Github star?