feat: add llm instruction base. Test llm instructions on two features. (#1315)

Co-authored-by: Sebastian Thulin <sebastian.thulin@helsingborg.se>

Author: sebastianthulin

docs/utils/llm-prompt.md

@@ -0,0 +1,47 @@
+# Promt for Automated LLM Documentation
+This is a "how-to" in order to generate automatic documentation in a LLM. Some features may be to large to input in a all LLM's. Small features will be possible to generate in OpenAI, and larger features has been successfully entered to Gemeni.
+
+---
+
+## How to Retrieve the Feature Code
+To fetch the feature's code, run the following command in the feature directory:  
+```bash
+find . -type f -not -path '*/\.*' | while read -r file; do echo -e "\n=== File: $file ===\n"; cat "$file"; done | pbcopy
+```  
+
+---
+
+# [Feature Name] 
+
+### Description  
+Provide a **brief overview** of the feature and its functionality. Explain what it does and where it is used in the system.  
+
+## How to Utilize  
+
+### For Administrators / Editors 
+- Explain how **administrators** can use the feature, including step-by-step instructions.  
+- Mention any **capabilities/permissions** required (e.g., `edit_posts`, `manage_options`).  
+- Detail where to find the settings (e.g., in the WordPress admin panel).  
+
+### For Users  
+- Describe how users will see or experience the feature on the frontend.  
+
+---
+
+## Purpose  
+
+### Why This Feature Exists  
+- Describe **what problem this feature solves** and why it was implemented.  
+- Explain how it benefits different user groups (administrators, editors, and end users).  
+
+### Key Benefits  
+✅ Centralizes functionality or information.  
+✅ Improves the user experience by [explain benefit].  
+✅ Reduces manual work for [specific user roles].  
+
+---
+
+## Meta  
+
+- **Author:** [Name or Team]  
+- **Initial Release Date:** [Month, Year]

library/GlobalNotices/readme.md

@@ -0,0 +1,64 @@
+# Global Notices Feature  
+
+## Feature Name  
+
+### Description  
+The **Global Notices** feature allows administrators to create and manage **site-wide notifications** that appear in different locations on the website. These notices can be displayed as:  
+
+- **Banners** (full-width messages at the top of the page)  
+- **Toasts** (small pop-up notifications)  
+- **Content Notices** (embedded within page content)  
+
+Each notice can include an **icon**, an **action button/link**, and be **dismissable** for a set period. Notices are managed from the WordPress admin panel and can be configured based on user roles, login status, and page type.  
+
+---
+
+## How to Utilize  
+
+### For Administrators  
+**Accessing the Feature:**  
+- Navigate to **Global Notices** in the WordPress admin menu.  
+- Requires the **edit_posts** capability to manage notices.  
+
+**Creating a Notice:**  
+1. Click **"Add New Notice"** and configure:  
+   - **Message:** The main content of the notice.  
+   - **Type:** Info, warning, error, or success.  
+   - **Icon:** Optional visual indicator.  
+   - **Action:** A button or link (optional).  
+   - **Dismissable:** Set whether users can close the notice and how long it remains hidden.  
+   - **Location:** Choose from **Toast, Banner, or Content**.  
+   - **Constraints:** Restrict visibility based on:  
+     - **User Role & Login Status** (logged-in users vs. guests).  
+     - **Page Type** (frontpage vs. subpages).  
+2. Click **Save & Publish** to make the notice live.  
+
+### For Editors & Users  
+- **Editors** (if they have the required permissions) can also create and manage notices.  
+- **Users** will see notices based on the defined settings.  
+- Dismissable notices remain hidden for the specified duration once closed.  
+- Notices with **actions** (e.g., links/buttons) provide easy access to relevant information.  
+
+---
+
+## Purpose  
+
+### Why This Feature Exists  
+The **Global Notices** feature is designed to:  
+✅ Provide a **centralized** way to display important messages across the website.  
+✅ Allow **targeted messaging** based on user role, login status, and page type.  
+✅ Improve **communication** between administrators and website visitors.  
+
+### Who Benefits?  
+- **Site Administrators**: Easily manage and schedule notices without modifying templates.  
+- **Editors**: Display important updates without relying on developers.  
+- **End Users**: Get relevant information at the right place and time, improving user experience.  
+
+This feature eliminates the need for manually inserting notices on multiple pages and ensures consistency in messaging.  
+
+---
+
+## Meta  
+
+- **Author:** Helsingborg Stad 
+- **Initial Release Date:** February 2025  

library/UserGroup/readme.md

@@ -0,0 +1,50 @@
+# User Group Management and Content Restriction
+
+### Description
+
+This feature enhances user management and content control by introducing user groups and the ability to restrict access to content based on these groups.  It allows administrators to categorize users into groups (e.g., "Subscribers," "Members," "Employees") and then control which groups can view specific posts or attachments. This provides granular control over content visibility, enabling personalized experiences and secure information sharing.  The functionality integrates with Single Sign-On (SSO) for streamlined user login and redirection.
+
+## How to Utilize
+
+### For Administrators / Editors
+
+1. **Access User Groups:** Navigate to "Users" -> "User Groups" in the WordPress admin menu.  This will take you to the taxonomy management screen where you can create, edit, and delete user groups.  *Requires the `manage_options` capability.*
+
+2. **Assign Users to Groups:**  On a user's profile page (Users -> All Users -> Edit User), a new "User Group" field will be present.  Use this field to assign the user to a user group.
+
+3. **Restrict Content Visibility:** When editing a post or attachment, a "User group visibility" meta box will appear in the "Publish" section of the editor (it may be hidden initially, check "Screen Options" at the top right).  Select the user groups that should have access to this content. If no groups are selected, the content will be visible to all logged-in users. *Requires the `edit_posts` capability (or `edit_attachments` for attachments).*
+
+4. **SSO Redirection:** After a user logs in via SSO, they will be automatically redirected to a URL specific to their assigned user group, if configured. T
+
+5. **Automatic mapping of User Groups** Usergroups will automaticly be mapped to the user, based on the "companyname" field in most sso-services.
+
+### For Users
+
+- **Frontend Experience:** Users will only see posts and attachments that are visible to their assigned user group(s). If a user is not logged in, or is logged in but does not belong to a group with access, they will not see the restricted content.
+- **SSO Login:** Users can log in via SSO. If a redirect URL is set for their group, they will be redirected accordingly.
+
+---
+
+## Purpose
+
+### Why This Feature Exists
+
+This feature addresses the need for controlled content access based on user roles or affiliations.  It solves the problem of:
+
+- **Creating internal knowledge bases:**  Sharing information only with specific departments or teams.
+- **Personalizing user experiences:** Showing content relevant to a user's interests.
+- **Simplifying SSO redirection:** Streamlining the post-login experience for users based on their group.
+
+### Key Benefits
+
+✅ **Centralizes functionality:** Manages user groups and content restrictions within WordPress.
+✅ **Improves the user experience:**  Provides personalized content access and a streamlined SSO login flow.
+✅ **Reduces manual work:** Automates content visibility based on user group assignments, eliminating the need for manual checks or workarounds.
+✅ **Enhances security:** Protects sensitive information by restricting access to authorized user groups.
+
+---
+
+## Meta
+
+- **Author:** Helsingborg Stad
+- **Initial Release Date:** October, 2023