Make report type configurable

I too think this is how the module should have been setup, All the reports be editable and installed from config when first installing the module, and maybe a library of "Pre-made" prompts people can choose from so those default ones can be improved over time.

I will be working on this feature possibly this week in scope of our project. So hopefully next week we have something.

Great I can help if you get a branch going, I was going to maybe take a stab at it as well.

I am not going to start at least today, so if you you like you can start.
The only think I want to push - I made some fixed in form it self, because it was bugy. Hovewer, it is not part of that issue, so I think we will just merge conflicts once we have one or another issue merged.

While the team and I and worked on the task https://www.drupal.org/project/ai_seo/issues/3536408 ✨ Make report type configurable Active , we decided to move it into an own module because the same code can cover many more use cases than just SEO.

I prompt everyone to switch to https://www.drupal.org/project/ai_content_advisor → since it is more flexible in creating new prompts types, and we have some ideas for future features that will be useful for others.

Some fixes and new features in a new module:

1. In a new module I also fixed the issue when for Anonymous users some HTML from Admin theme and logged-in users can show up.
2. Also, fix a lot of small bugs in the code, specifically related to AJAX on the Analyze form.
3. Added a block to show the Analyze form on the node page.
4. Add a field to the report to show the used HTML, this can be useful for prompt results analysis.

Thanks to both! I've updated the module to support configurable report types along with the fix to frontend HTML rendering for reports.

I'll keep this module still active. Will develop it as well for personal needs that only relate to SEO but having a content advisor work with the same principle is definitely a worthwhile module to develop as well.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

I don’t see the reasons keeping that module active. Our module can handle SEO and other cases with content.

By default it provides SEO reports, but can be configured for other type of reports.

We can have broader solutions which covers more cases with the same codebase. I added you as an maintainer to that new module, so you can implement your ideas there.