Update docs

Author: cklei-carly

app/(home)/page.tsx

@@ -1,4 +1,5 @@
 import { OtherProducts, PluginCards } from '@/components/partials/plugin-cards';
+import { Metadata } from 'next';
 
 export default function HomePage() {
   return (
@@ -16,4 +17,8 @@ export default function HomePage() {
       </section>
     </div>
   );
+}
+ 
+export const metadata: Metadata = {
+  title: 'Solution Forest Plugins',
 }

app/docs/components/helpers.ts

@@ -5,7 +5,7 @@ export function generateMetadataForPlugin(plugin: string) {
   const pluginConfig = config.plugins.find(p => p.id === plugin);
   if (!pluginConfig) return null;
   return {
-    title: pluginConfig.name,
+    title: `${pluginConfig.title} | Solution Forest Plugins` ,
     description: pluginConfig.description,
     // openGraph: {
     //   images: [

backup/filaletter/4.x/features/workspace.mdx

@@ -0,0 +1,58 @@
+---
+title: Workspace | 4.x
+description: Modern self-hosted email marketing platform built specifically for Filament Admin Panel with subscriber management, email campaigns, and automation features.
+lastUpdated: 2026-03-03T05:10:19.253Z
+---
+
+# Workspace
+Workspaces enable you to manage distinct subscriber lists and campaigns for various projects. For example, you might have one workspace for your personal website's mailing list and another for your podcast.
+
+## Default Workspace
+
+Upon installation, a default workspace is automatically created and set. The workspace ID resolver will attempt to retrieve the current workspace ID from the session, using the default workspace ID as a fallback. You can change the default workspace ID by updating the `workspace_id_fallback` value in the configuration.
+
+## Register the workspace switcher to topbar
+
+A Livewire component for switching workspaces is available for your convenience. By default, this component is registered to the topbar. You can enable or disable this feature or change its position by modifying the configuration.
+
+Alternatively, you can manually register the workspace switcher through your application's service provider:
+
+```php
+public function boot(): void
+{
+    FilamentView::registerRenderHook(
+        PanelsRenderHook::GLOBAL_SEARCH_AFTER,
+        fn() => \Illuminate\Support\Facades\Blade::render("@livewire('switch-workspace')"),
+    );
+}
+```
+
+## API Tokens
+
+You can create and delete API tokens for each workspace. These API tokens can be used in private API routes. See [API Authentication]([[app_url]]/documentation/3-api/2-authentication) to learn more.
+
+
+## Extending the Current Workspace ID Resolver
+
+The workspace ID resolver determines which workspace is currently active for a user or API request. By default, the resolver checks for an API token in the request, then the session, and finally falls back to a default value from the configuration.
+
+If you need to customize how the current workspace ID is resolved, you can override the resolver logic. For example, you might want to resolve the workspace ID based on a custom request parameter or user attribute.
+
+To set a custom resolver, use the following approach in your service provider:
+
+```php
+Sendportal::setCurrentWorkspaceIdResolver(function () {
+    // Your custom logic to determine the workspace ID
+    // Example: return request()->get('custom_workspace_id') ?? config('filament-newsletter.workspace_id_fallback');
+});
+```
+
+The default resolver logic is as follows:
+
+1. Checks for an API token in the request's bearer token or `api_token` parameter, and resolves the workspace ID using the token if present.
+2. Checks the session for a configured workspace ID session key and returns its value if found.
+3. Falls back to a default workspace ID from the configuration if neither of the above are present.
+
+You can refer to the `setCurrentWorkspaceIdResolver` method in the `FilamentNewsletterServiceProvider` for the default implementation.
+
+This flexibility allows you to adapt workspace resolution to your application's specific requirements.

backup/filaletter/4.x/getting-started/getting-a-license.mdx

@@ -0,0 +1,65 @@
+---
+title: Getting a License | 4.x
+description: Modern self-hosted email marketing platform built specifically for Filament Admin Panel with subscriber management, email campaigns, and automation features.
+lastUpdated: 2026-03-03T05:10:19.253Z
+---
+
+# Getting a license
+To use this package, you must purchase a license.
+
+# Requirements
+
+In order to distribute your PHP package you must make sure a valid composer.json is located in the root of your repository. If you attempt to import or publish a release without a valid composer.json you will receive an notification.
+
+# Installation via Composer
+
+To get started with the Filaletter Plugin, follow these steps:
+
+1. Add the package to your `composer.json` file in the repositories key:
+
+    ```json
+    {
+        "repositories": [
+            {
+            "type": "composer",
+            "url": "https://filasend.composer.sh"
+            }
+        ],
+    }
+    ```
+
+2. Once the repository has been added to the `composer.json` file, install the Filaletter Plugin like any other composer package using the `composer require` command:
+
+    ```sh
+    composer require solution-forest/filament-newsletter
+    ```
+
+3. Once the repository has been added to the composer.json file, they can install Filaletter like any other composer package using the composer require command:
+
+    ```
+    Loading composer repositories with package information
+    Authentication required (filasend.composer.sh):
+    Username: [licensee-email]
+    Password: [license-key]
+    ```
+
+    You will be prompted to provide their username and password. The username will be their email address and the password will be equal to their license key. Our license policy requires a fingerprint that you will need to append his/her fingerprint to their license key. 
+    
+    For example, let's say we have the following licensee and license activation:
+
+    Contact email: philo@anystack.sh
+    License key: 8c21df8f-6273-4932-b4ba-8bcc723ef500
+    Activation fingerprint: anystack.sh
+
+    This will require your licensee to enter the following information when prompted for their credentials:
+
+    ```
+    Loading composer repositories with package information
+    Authentication required (filasend.composer.sh):
+    Username: philo@anystack.sh
+    Password: 8c21df8f-6273-4932-b4ba-8bcc723ef500:anystack.sh
+    ```
+
+    To clarify, the license key and fingerprint should be separated by a colon (`:`).
+
+

backup/filaletter/4.x/getting-started/installation.mdx

@@ -0,0 +1,120 @@
+---
+title: Installation | 4.x
+description: Modern self-hosted email marketing platform built specifically for Filament Admin Panel with subscriber management, email campaigns, and automation features.
+lastUpdated: 2026-03-03T05:10:19.253Z
+---
+
+# Installation
+
+
+### Version Compatibility
+
+| Filament Version | Filament Newsletter Version |
+|------------------|---------------------------|
+| v3.x             | v1.x – v3.x               |
+| v4.x             | v4.x                      |
+
+
+
+You can install the package via composer:
+
+```bash
+composer require solution-forest/filament-newsletter
+```
+
+
+You can register this plugin and its widgets through your panel provider:
+
+```php
+public function panel(Panel $panel): Panel
+{
+    return $panel
+        ->widgets([
+            \SolutionForest\FilamentNewsletter\Filament\Widgets\Dashboard\TotalSubscribers::class,
+            \SolutionForest\FilamentNewsletter\Filament\Widgets\Dashboard\CompletedCampaigns::class,
+            \SolutionForest\FilamentNewsletter\Filament\Widgets\Dashboard\RecentSubscribers::class,
+        ])
+        ->plugins([
+            \SolutionForest\FilamentNewsletter\FilamentNewsletterPlugin::make()
+        ]);
+}
+```
+
+You can publish and run the migrations with:
+
+```bash
+php artisan vendor:publish --tag="filament-newsletter-migrations"
+php artisan migrate
+```
+
+You can publish the config file with:
+
+```bash
+php artisan vendor:publish --tag="filament-newsletter-config"
+```
+
+Optionally, you can publish the views using
+
+```bash
+php artisan vendor:publish --tag="filament-newsletter-views"
+```
+
+## Running the queue without Laravel Horizon
+If you don't want to use Horizon to manage you redis queue or you're using the database driver you will have to run a queue worker for each queue that Filaletter uses.
+
+default: processes default queues
+sendportal-message-dispatch: dispatches messages to the email service
+sendportal-webhook-process: processes incoming webhooks
+```php
+php artisan queue:work
+php artisan queue:work --queue=sendportal-message-dispatch
+php artisan queue:work --queue=sendportal-webhook-process
+```
+
+You may also run a single worker with processing priority:
+
+```php
+php artisan queue:work --queue=default,sendportal-message-dispatch,sendportal-webhook-process
+```
+
+## Running Redis Queues With Laravel Horizon
+SendPortal bundles Laravel Horizon as an easy way to run and manage redis queues.
+
+Configuration for the queues necessary to run SendPortal is already included. In order to use Horizon as your queue manager, you should first publish the Horizon assets:
+
+```php
+php artisan horizon:publish
+```
+To start processing your queue items with Horizon, you simply need to run the following command:
+
+```php
+php artisan horizon
+```
+
+## Running the Scheduler Locally
+
+```php
+php artisan schedule:work
+```
+
+## Support for SQLite
+
+To use this package with SQLite, the following code could be added to AppServiceProvider:
+
+```php
+if (DB::connection() instanceof SQLiteConnection) {
+    DB::connection()->getPdo()->sqliteCreateFunction('date_format', function ($date, $format) {
+        return date($format, strtotime($date));
+    }, 2);
+
+    DB::connection()->getPdo()->sqliteCreateFunction('FROM_UNIXTIME', function ($unixtime) {
+        return date('Y-m-d H:i:s', $unixtime);
+    }, 1);
+
+    DB::connection()->getPdo()->sqliteCreateFunction('UNIX_TIMESTAMP', function ($date) {
+        return strtotime($date);
+    }, 1)
+}
+```
+
+

backup/filaletter/4.x/getting-started/introduction.mdx

@@ -0,0 +1,40 @@
+---
+title: Introduction | 4.x
+description: Modern self-hosted email marketing platform built specifically for Filament Admin Panel with subscriber management, email campaigns, and automation features.
+lastUpdated: 2026-03-03T05:10:19.253Z
+---
+
+# Filaletter - Streamline Email Marketing within FilamentPHP
+
+The Filament Newsletter plugin empowers you to manage your email marketing campaigns directly within your FilamentPHP admin panel.  Leveraging the flexibility and user-friendliness of Filament, this plugin simplifies the process of creating, sending, and tracking newsletters, all without leaving your familiar admin environment.
+
+Built upon the open-source Sendportal core project ([Sendportal core](https://github.com/sendportal/sendportal)), Filament Newsletter offers:
+
+* **Seamless Filament Integration:** Manage all aspects of your email marketing without ever leaving your Filament admin panel.
+* **Complete Control and Personalization:** Craft highly targeted emails with customizable templates.
+* **Broad Email Service Provider Support:** Integrate with popular providers like Amazon SES, Mailgun, SendGrid, Mailjet, Postmark, and SMTP. (Verify Mandrill support and update list accordingly).
+* **Scalable Solution:** Manage unlimited* campaigns, subscribers, and mailing lists within your server's capacity. (*See footnote for details).
+
+## Documentation:
+
+For detailed information on using the Sendportal core features within Filament Newsletter, refer to the Sendportal documentation: ([Sendportal Documentation](https://sendportal.io/docs)). This documentation covers core concepts such as template language and API usage.  Filament-specific integration details are provided below. [Filamentphp Documentation](https://filamentphp.com/)
+
+## Package Requirements:
+
+* Laravel 11 or higher
+* Filament Admin Panel 3.2 or higher
+
+### Version Compatibility
+
+| Filament Version | Filament Newsletter Version |
+|------------------|---------------------------|
+| v3.x             | v1.x – v3.x               |
+| v4.x             | v4.x                      |
+
+
+---
+
+<span style=\{\{fontSize: "smaller"\}\}>**Footnote:**  The term "unlimited" refers to the plugin's design. Practical limits may be imposed by your server resources, database capacity, and email sending provider limits.</span>
+
+
+

backup/filaletter/4.x/getting-started/quick-start.mdx

@@ -0,0 +1,62 @@
+---
+title: Quick Start | 4.x
+description: Modern self-hosted email marketing platform built specifically for Filament Admin Panel with subscriber management, email campaigns, and automation features.
+lastUpdated: 2026-03-03T05:10:19.253Z
+---
+
+# Quick Start: Sending Your First Campaign with Filament Newsletter
+
+This guide walks you through the steps to send your first email campaign using Filament Newsletter within your FilamentPHP admin panel.
+
+## 1. Create an Email Service:
+
+Filament Newsletter integrates with various email providers: Mailgun, Mailjet, Amazon SES, SendGrid, Postmark, and SMTP.
+
+* Navigate to the "Email Services" section in your Filament admin panel.
+* Click "Create Email Service."
+* Select your desired provider and fill in the required credentials.  These vary by provider for detailed setup instructions for each provider.
+* Test your connection using the "Test Email" feature, providing a "To" and "From" address.
+
+## 2. Add or Import Subscribers:
+
+You need subscribers to send your campaigns.  Here are three ways to add them:
+
+* **Manually:**  Go to "Subscribers" in the sidebar, click "New Subscriber," enter their email address, ensure "Subscribed" is checked, and click "Save."
+* **API:** Use the Filament Newsletter API to add subscribers programmatically.
+* **CSV Import:** Import subscribers in bulk from a CSV file. 
+
+For more details, see the [Subscriber Documentation](../../documentation/2-features/1-subscribers).
+
+## 3. Create a Segment (Optional):
+
+Segments allow you to group subscribers for targeted campaigns.
+
+* Go to "Segments," click "Create Segment," and give your segment a name.
+* On the segment edit page, use the relation manager to add subscribers to the segment.
+
+## 4. Create a Template:
+
+Templates ensure consistent branding across your campaigns.
+
+* Navigate to "Templates" and click "Add Template."
+* Your template should be valid HTML and *must* include the `\{\{content\}\}` tag, where your campaign content will be inserted.
+* See the [Template Documentation](add link to template documentation) for more details.
+
+You can also create campaigns *without* a template if you prefer.
+
+## 5. Create a Campaign:
+
+* Go to "Campaigns" and click "New Campaign."
+* Select your template (if you created one).  The campaign content you enter will be placed within the `\{\{content\}\}` tag of the template.
+* Refer to the [Campaign Documentation](add link to campaign documentation) for further information.
+
+## 6. Send Your Campaign:
+
+Review your campaign before sending:
+
+* **Recipients:** Choose "All Subscribers" or select specific segments.
+* **Schedule:** Send immediately or schedule for a specific date and time.
+* **Sending Behavior:**
+    * **Save as Draft:**  Save individual emails as drafts for manual review and sending.  Access these in the "Draft Messages" section.
+    * **Send Immediately:**  Send emails as soon as the system is ready.
+