[META] Make Drupal CMS modules ready to Experience Builder

Add tagify.

Marked some of the items that do not apply. Also added 📌 Confirm Semi-coupled form elements can work with State API visibility Active for pathauto which I've been told has the potential to make the pathauto widget work.

Added more of the pathauto related issue :)

Added XB issues discussing search indexing and metatags.

Identified more modules that do not apply inside XB.

@catch: for metatag there is also the question I think of what should be expose din XB of the metatag fields. XB seems to have a hardcoded meta image and description field that is not provided by metatag currently.

gábor hojtsy → credited berdir → .

Added webform issue that I just opened :) Also result of discussion about token with @berdir.

XB seems to have a hardcoded meta image and description field that is not provided by metatag currently.

That doesn't seem like a viable approach at all? A lot of sites will just want to pull that information from structured fields on the entity, not add a whole extra set of data entry for metatags.

Updated the IS to group the modules based on whether they are relevant to XB and made a few other updates.

Updated the note on event type to be clearer about being removed not meaning that the feature will entirely go away (dependent on site templates, eg. it could be an addon still).

Re sitemap, that was moved to not applying inside XB, while that is true, is it confirmed that XB pages show up fine in sitemaps? I think if that is not the case, we should keep it and solve it. :)

@catch: re the metatag, I did not mean to imply that the current solution is the final one. The XB page type is not for demos, it is the main thing that XB is built against and can manage the list of XB pages (titles, paths, etc) inside XB in the top bar. XB is being adapted to nodes too with field matching to props for sure. I meant that the metatag field on entities could get very unwieldy so there needs to be some kind of UX definition of what should be exposed in XB of metatags.

Opened 📌 Make coffee module work in Experience Builder Active for coffee.

Sitemap module just allows you to enable various menus or taxonomy vocabs to display on the sitemap page. So it shouldn't be affected by XB I think? If there are XB pages in the menu, they would appear in the sitemap.

Reformatted the table as various lists for easier scanning and so we can list more issues and notes without breaking everything :) I think I kept all the info and now represent it better hopefully.

Minor cleanup.

Added task for trash, the module works, just need to work out how to modify the confirmation message to reflect that.

Updating to reflect that simple sitemap (XML sitemap generator) already works.