The Project Management Committee for Backdrop CMS is considering 'initiative' proposals. Post your initiative ideas here and comment on others, one topic per initiative idea.
| Topics | Comments |
Last comment |
|---|---|---|
| Official Initiative: "Ready To Wear" -- Theme development should not be necessary to use Backdrop CMS Accepted answer | 11 | 1 month 2 days ago |
| Initiative Proposal: Documentation | 2 | 1 month 3 days ago |
| Initiative proposal: Drupal-Compatibility Helpers | 6 | 5 months 2 weeks ago |
| Official Core Initiative: Telemetry | 12 | 5 months 2 weeks ago |
| Initiative Proposal: Usability Testing | 1 | 5 months 3 weeks ago |
| Initiative Proposal: Better support for contrib project maintainers | 1 | 5 months 3 weeks ago |
| Initiative proposal: built-in data import and export | 2 | 5 months 3 weeks ago |
| Initiative Proposal: Better caching and Mobile approach | 3 | 5 months 3 weeks ago |
| Initiative Proposal: Better editorial capabilities - SEO | 5 | 5 months 3 weeks ago |
Recent comments
Wow, the PR works perfectly when updating a module on my site hosted by Strato. Will post details in the issue thread.
Error update modules 1and1
Hello @Venky and welcome to Backdrop 👋 I do not see anything changed in hook_menu in Backdrop: https://api.backdropcms.org/api/backdrop/1/search/hook_menu Since the modules are custom, we won't be...
Drupal 7 Custom Module Menu not showing after upgrade to Backdrop CMS
But it doesn't, though. Or it didn't when I created it. I tried amending the commit to remove the hashtag but that doesn't seem to have made any difference. I am very confused by the whole thing.
creating pull requests