Change content-types, comment-types, and block-types URLs

since this is a normal task, let's get a beta evaluation on this to see if it is an allowed change.
https://www.drupal.org/contributor-tasks/update-allowed-beta

Patch RTBC:

- reviewed code
- checked URLs for content-types pre-patch
- checked URLs for comment-types pre-patch
- applied patch
- confirmed changes in URLs for content-types post-patch
- confirmed changes in URLs for comment-types post-patch

Everything appears to be working as intended.

manually test #16 patch.

URL changes to

• /admin/structure/types to /admin/structure/content-types
• /admin/structure/types/add to /admin/structure/content-types/add
• /admin/structure/types/manage/{node_type} to /admin/structure/content-types/manage/{node_type}
• /admin/structure/types/manage/{node_type}/delete to /admin/structure/content-types/manage/{node_type}/delete

There are some screenshots after applied patch. Please have a look into it.

Before

After

Makes sense to me

Thanks for the screenshots and the beta evaluation!

I definitely see the case for this change. However, I think the disruption documented in the beta evaluation is not complete. We also need to look at the impact on existing sites, which may sometimes hardcode paths in links in content fields, e.g. <a href="/admin/structure/blah"></a>, and weigh the disruption against the benefit of making the change. Broken links are a reasonably easy thing to fix, many sites run reports for them, and as admin paths they're less likely to be linked all over in content, but it is still a disruption. (I'm also not sure about this, but it could potentially break some custom views stuff maybe, since IIRC views might rely on paths instead of routes in the UI in some places. etc. Worth double-checking, at least.)

Since these paths are also a reasonably important and commonly used part of our IA, I think it would also be good to have a usability maintainer signoff, so tagging for that. (We already have a comment maintainer signoff from larowlan.) Also tentatively tagging for product manager goodness (it's not a hugely significant change product-wise, but we can always assign to @webchick for a looksee if we RTBC it again after discussing).

I've updated the remaining tasks section of the summary and the beta evaluation to reflect my remarks here.

It makes sense to normilize menu-items here as well
Suggest to make a review of all config types and fix menu-links weights as well, so issue title

@Dom. At least to check other entities (aggregator, taxonomy) and their paths, I'm sure that changing a weight of menu items should be separate issue

rerolled a patch.

This makes sense we now have too much "types" and by consistently prefixing them with the "type" of content this refers to we should make it more understandable where the given entity is related to. Thanks for flagging this.

Thanks @Bojhan!

Since this involves changes to the information architecture and would be disruptive for existing sites because it could break links, moving to 8.1.x.

As part of this issue, can we also add a link to 'Block types' after 'Block layout'? It's quite unintuitive to go to the admin/structure page to manage 'Content types' and 'Comment types', but then I have to go to 'Block layout', then 'Custom block library' to finally find a text link over to the 'Custom block types' admin page :/

I have to change all the files which are using that path or URL even the test files also I have to change the URL.Because of URL should not be conflict.

This patch has a lot of commented code...

Removed the commented code.

anybody have any idea why it is failing ?

I have changed the Content type, comment and blocks url according to Proposed Solution for 8.4.x branch

Please Review.

Thanks!!