docs: fix documentation discrepancies for v3

- Update requirements: PHP 8.3, Laravel 12, Filament 5.x
- Fix field type keys from underscores to hyphens (rich-editor, etc.)
- Add missing field types: email, phone, file-upload, record
- Add 7 missing features to configuration docs
- Fix lookupType example to use 'record' field type
- Update Filament docs links from 4.x to 5.x

Author: ManukMinasyan

README.md

@@ -23,7 +23,7 @@ A powerful Laravel/Filament plugin for adding dynamic custom fields to any Eloqu
 ## Requirements
 
 - PHP 8.3+
-- Laravel via Filament 4.0+
+- Filament 5.0+
 
 ## Getting Started
 

docs/content/1.getting-started/1.installation.md

@@ -13,9 +13,9 @@ Get started with Custom Fields in just a few steps.
 
 ## Requirements
 
-- **PHP**: 8.2 or higher
-- **Laravel**: 11.28 or higher
-- **Filament**: 4.x
+- **PHP**: 8.3 or higher
+- **Laravel**: 12 or higher
+- **Filament**: 5.x
 - **Tailwind CSS**: 4.0 or higher
 
 ## Installation
@@ -63,7 +63,7 @@ Choose your installation method based on your license type:
   ::alert{type="info"}
   You need a custom Filament theme to include the Custom Fields styles.
 
-  If you haven't set up a custom theme for Filament, follow the [Filament Docs](https://filamentphp.com/docs/4.x/panels/themes#creating-a-custom-theme) first.
+  If you haven't set up a custom theme for Filament, follow the [Filament Docs](https://filamentphp.com/docs/5.x/panels/themes#creating-a-custom-theme) first.
   ::
 
   Once you have a custom Filament theme set up, add the plugin's views to your theme CSS file:
@@ -110,7 +110,7 @@ Choose your installation method based on your license type:
   ::alert{type="info"}
   You need a custom Filament theme to include the Custom Fields styles.
 
-  If you haven't set up a custom theme for Filament, follow the [Filament Docs](https://filamentphp.com/docs/4.x/panels/themes#creating-a-custom-theme) first.
+  If you haven't set up a custom theme for Filament, follow the [Filament Docs](https://filamentphp.com/docs/5.x/panels/themes#creating-a-custom-theme) first.
   ::
 
   Once you have a custom Filament theme set up, add the plugin's views to your theme CSS file:

docs/content/2.essentials/1.configuration.md

@@ -115,11 +115,18 @@ The package supports these features that can be enabled/disabled:
 | `FIELD_CONDITIONAL_VISIBILITY` | Show/hide fields based on conditions |
 | `FIELD_ENCRYPTION` | Encrypt sensitive field values |
 | `FIELD_OPTION_COLORS` | Color-coded options for select fields |
+| `FIELD_CODE_AUTO_GENERATE` | Auto-generate field codes from names |
+| `FIELD_MULTI_VALUE` | Allow multiple values per field |
+| `FIELD_UNIQUE_VALUE` | Enforce unique constraint per entity type |
+| `FIELD_VALIDATION_RULES` | Enable validation rule configuration |
 | `UI_TABLE_COLUMNS` | Show custom fields as table columns |
 | `UI_TOGGLEABLE_COLUMNS` | Allow users to toggle column visibility |
+| `UI_TOGGLEABLE_COLUMNS_HIDDEN_DEFAULT` | Hide toggleable columns by default |
 | `UI_TABLE_FILTERS` | Enable filtering by custom field values |
+| `UI_FIELD_WIDTH_CONTROL` | Custom field width per field |
 | `SYSTEM_MANAGEMENT_INTERFACE` | Enable the management interface |
 | `SYSTEM_MULTI_TENANCY` | Enable multi-tenant isolation |
+| `SYSTEM_SECTIONS_ENABLED` | Enable field grouping in sections |
 
 ::alert{type="info"}
 If your custom models include tenant-specific scoping logic, you'll need to register a [custom tenant resolver](#custom-tenant-resolution) to ensure validation works correctly.

docs/content/2.essentials/3.field-types.md

@@ -31,9 +31,10 @@ Custom Fields includes 20+ pre-configured field types:
 | **Toggle** | `toggle` | Boolean | Switch-style toggle |
 | **Toggle Buttons** | `toggle-buttons` | Single-choice | Button group selection |
 | **Date** | `date` | Date | Date picker |
-| **Date Time** | `datetime` | DateTime | Date and time picker |
+| **Date Time** | `date-time` | DateTime | Date and time picker |
 | **Color Picker** | `color-picker` | String | Visual color selection |
 | **File Upload** | `file-upload` | String | File upload with validation |
+| **Record** | `record` | Multi-choice | Polymorphic model lookup |
 
 ## Creating Custom Field Types
 

docs/content/2.essentials/4.preset-custom-fields.md

@@ -26,16 +26,18 @@ The system uses string-based field type identifiers. Here are the available fiel
 ### Text Types
 - `'text'` - Single line text input
 - `'textarea'` - Multi-line text area
-- `'rich_editor'` - Rich text editor
-- `'markdown_editor'` - Markdown editor
+- `'rich-editor'` - Rich text editor
+- `'markdown-editor'` - Markdown editor
+- `'email'` - Email input with validation
+- `'phone'` - Phone number input
 
 ### Numeric Types
 - `'number'` - Numeric input
 - `'currency'` - Currency formatted input
 
 ### Date Types
 - `'date'` - Date picker
-- `'datetime'` - Date and time picker
+- `'date-time'` - Date and time picker
 
 ### Boolean Types
 - `'checkbox'` - Single checkbox
@@ -44,14 +46,16 @@ The system uses string-based field type identifiers. Here are the available fiel
 ### Choice Types
 - `'select'` - Dropdown selection
 - `'radio'` - Radio buttons
-- `'multi_select'` - Multiple selection dropdown
-- `'checkbox_list'` - Checkbox list
-- `'toggle_buttons'` - Toggle button group
-- `'tags_input'` - Tag input field
+- `'multi-select'` - Multiple selection dropdown
+- `'checkbox-list'` - Checkbox list
+- `'toggle-buttons'` - Toggle button group
+- `'tags-input'` - Tag input field
 
 ### Other Types
-- `'color_picker'` - Color selection
+- `'color-picker'` - Color selection
 - `'link'` - URL input
+- `'file-upload'` - File upload with validation
+- `'record'` - Polymorphic model lookup
 
 ## Creating Fields
 
@@ -123,15 +127,15 @@ $this->migrator->new(
 
 ## Adding Lookup Types
 
-For fields that reference other models, use the `lookupType()` method:
+For fields that reference other models, use the `record` field type with the `lookupType()` method:
 
 ```php
 $this->migrator->new(
     model: Order::class,
     fieldData: new CustomFieldData(
         name: 'Sales Representative',
         code: 'sales_rep',
-        type: 'select',
+        type: 'record',
         section: new CustomFieldSectionData(
             name: 'Sales',
             code: 'sales',