Andre Wanlin

All the above plugins now have PRs created to deprecate their support for the legacy backend. 👍

FYI - Work has started upstream to remove `@backstage/backend-common` - https://github.com/backstage/backstage/pull/28182 - https://github.com/backstage/backstage/pull/28189 I'm sure there will be more. Also, this section about deadline should be helpful: https://github.com/backstage/backstage/issues/24493#deadline

Can we add a lint rule to the repo to forbid the use of `@backstage/backend-common` so that way we don't get new usages added?

Best I can tell this is the last PR for this work, once merged all direct references to backend-common will be gone! https://github.com/backstage/community-plugins/pull/3433

Historical note: when this plugin was developed we didn't take screen size into account, though some of the work was done on a laptop but it may have been high-resolution...

Hi @rahulpalivela18, thanks for logging this, can you share the screen sizes you used? Resolution would help as well. Just so that who ever picks this up makes sure to...

Hi @christoph-jerolimov or @ciiay, any chance you can look into why Topology is unhappy with this change, please?

Hi @veenarm, thanks for logging this. Though TechDocs doesn't support the results from running MkDocs directly it should fail fast for cases like this and not get stuck in a...

Yes, totally agree, there's a lost opportunity to help those looking to use plugins in the various workspaces. I wonder if we could generate some of this? Given say this...

We should also look at updating this - https://github.com/backstage/community-plugins/blob/main/workspaces/repo-tools/packages/cli/src/lib/workspaces/templates/workspace/README.md - with some suggested text so that way it stays up to date.