Problem/Motivation

Installing the recipe created a new role 'content editor'

Steps to reproduce

Install recipes using instructions

Proposed resolution

Let site owners handle creation of their own roles

Remaining tasks

Remove the role created in LLM support recipe please, many thanks

Comments

telegraph created an issue. See original summary.

mxr576’s picture

mxr576
Primary language Hungarian
Location Hungary
commented
Version: 1.0.5 » 1.x-dev

My initial reaction would have been “won’t fix.” I understand that some sites may not have a content_editor role, especially when not using the Standard profile. However, that role is now effectively part of Drupal core’s baseline expectations, even if it is profile-provided rather than universally guaranteed.

That said, this issue actually opens up a more interesting direction.

Instead of continuing to depend on the administrator_role and content_editor_role recipes, we could lean into this and simplify the approach. If we treat the content_editor role as an optional but preferred integration point, we can preserve the original goal of having a well-configured llms_txt setup without forcing the creation of additional roles.

In other words, rather than enforcing roles, we could:

  • detect and use content_editor when it exists,
  • fall back gracefully when it does not,
  • and avoid introducing new roles purely for configuration purposes.

This is all possible thanks to https://www.drupal.org/node/3552215

telegraph’s picture

telegraph commented
Title: LLm support creates new role » LLM support creates new role
Component: Code » Documentation

Thanks for your quick response.

We understand the aim to have the recipe creating a fully and well configured llms_txt setup, it makes perfect sense.

The newly created role came as a surprise, hence the ticket, and the solution proposed sounds like it would address this.

Beyond that, it appears that the goal is to add new permissions and functionality for roles and nodes.

As we're deploying this on an existing site with already existing fine grained configuration, it seems we'll need to tune it to properly integrate: we already have several levels of editor roles (different machine names than content_editor_role), and similarly, I now see new taxonomy, node fields and text editor formats.

The recipe is great as it is for new sites, but it would be useful to have some documentation as to the result of deploying on an existing site, to advise what to expect:

The recipe will:
- install and activate the three modules listed
- add a new roles when no existing ones match
- add new text format llms_txt_content, set up with global tokens replacement (for use in llms.txt sections)
- add a new taxonomy vocabulary llms_txt_content_sections
- add new taxonomy reference field field_llms_txt_content_section to every content type
- add a new view llms_txt_content_sections (default only, use the token replacement in llms.txt/sections to output the links for tagged content)
- the view lists linked node title under the taxonomy term (field_llms_txt_content_section) heading that content has been tagged with

Many thanks