@lukoweb/apitogo 0.1.67 → 0.1.68

package/docs/configuration/footer.mdx

@@ -2,213 +2,117 @@
 sidebar_label: Footer
 sidebar_icon: panel-bottom-dashed
 description:
-  Learn how to configure the footer in APIToGo, including columns, social links, copyright notice,
-  and logo. Customize the footer's position and content with slots.
+  Configure the site footer via modules.landing.content.footer in apitogo.config.json, or site.footer
+  for advanced layouts.
 ---
 
 # Footer Configuration
 
-The footer is a customizable component that appears at the bottom of every page in your APIToGo
-site. You can configure various aspects of the footer including its position, columns, social links,
-copyright notice, and logo.
-
-## Basic Configuration
-
-The footer is configured in your `apitogo.config.tsx` file under the `page.footer` property:
-
-```tsx
-const config: ApitogoConfig = {
-  site: {
-    footer: {
-      // Footer configuration goes here
-      position: "center",
-      copyright: `© ${new Date().getFullYear()} YourCompany LLC. All rights reserved.`,
-      // Other options...
-    },
-  },
-  // Other configuration...
-};
-```
-
-## Position
-
-You can control the horizontal alignment of the footer content using the `position` property:
-
-```tsx
-footer: {
-  position: "center"; // default
-  // or
-  position: "start";
-  // or
-  position: "end";
+Portal sites (MCP / create-apitogo scaffolds) render a global footer from
+**`apitogo.config.json`** → `modules.landing.content.footer`. That footer appears on home, docs, API
+reference, pricing, and auth pages, and replaces the default “Built with APIToGo” line.
+
+## Recommended: landing content footer (JSON)
+
+Ask for real link columns, social URLs, copyright, and optional brand/tagline before inventing
+copy. Example:
+
+```json title=config.json
+{
+  "modules": {
+    "landing": {
+      "enabled": true,
+      "path": "/",
+      "layout": "landing",
+      "content": {
+        "footer": {
+          "columns": [
+            {
+              "title": "Product",
+              "links": [
+                { "label": "Features", "href": "/features" },
+                { "label": "Pricing", "href": "/pricing" },
+                { "label": "Documentation", "href": "/docs" }
+              ]
+            },
+            {
+              "title": "Company",
+              "links": [
+                { "label": "About", "href": "/about" },
+                { "label": "Contact", "href": "/contact" }
+              ]
+            }
+          ],
+          "social": [
+            { "icon": "github", "href": "https://github.com/your-org" },
+            { "icon": "linkedin", "href": "https://www.linkedin.com/company/apitogo" }
+          ],
+          "copyright": "© 2026 Your Company. All rights reserved."
+        }
+      }
+    }
+  }
 }
 ```
 
-This affects how the content in the footer's main row is positioned horizontally.
+With MCP connected, prefer asking the user for footer content, then editing JSON (there is no
+dedicated footer MCP tool). See [MCP overview](../mcp/overview.md).
 
-## Columns
+## Advanced: `site.footer` (engine)
 
-The footer can include multiple columns of links, each with its own title:
+For custom layouts you can still configure `site.footer` (often from TSX when you need dynamic
+values):
 
-```tsx
-footer: {
-  columns: [
-    {
-      title: "Product",
-      position: "center", // position in grid, optional: start, center, end
-      links: [
-        { label: "Features", href: "/features" },
-        { label: "Pricing", href: "/pricing" },
-        { label: "Documentation", href: "/docs" },
-        { label: "GitHub", href: "https://github.com/org/repo" }, // Auto-detected as external
+```tsx title=config
+export default {
+  site: {
+    footer: {
+      position: "center", // "start" | "center" | "end"
+      copyright: `© ${new Date().getFullYear()} YourCompany LLC. All rights reserved.`,
+      columns: [
+        {
+          title: "Product",
+          links: [
+            { label: "Features", href: "/features" },
+            { label: "Pricing", href: "/pricing" },
+          ],
+        },
       ],
-    },
-    {
-      title: "Company",
-      links: [
-        { label: "About", href: "/about" },
-        { label: "Blog", href: "/blog" },
-        { label: "Contact", href: "/contact" },
+      social: [
+        { icon: "github", href: "https://github.com/yourusername" },
+        { icon: "x", href: "https://x.com/yourhandle", label: "Follow us" },
       ],
+      logo: {
+        src: { light: "/logo-light.svg", dark: "/logo-dark.svg" },
+        alt: "Company Logo",
+        width: "100px",
+      },
     },
-  ];
-}
-```
-
-Each column can have its own positioning with the `position` property, which can be `"start"`,
-`"center"`, or `"end"`. This controls how the column is positioned within the footer grid.
-
-## Social Media Links
-
-You can add social media links to your footer:
-
-```tsx
-footer: {
-  social: [
-    {
-      icon: "github",
-      href: "https://github.com/yourusername",
-    },
-    {
-      icon: "twitter",
-      href: "https://twitter.com/yourhandle",
-      label: "Follow us", // optional label text
-    },
-  ];
-}
-```
-
-The `icon` property currently can be one of the following values:
-
-<div className="[&_ul]:grid [&_ul]:grid-cols-[repeat(3,auto)]">
-
-- `"reddit"`
-- `"discord"`
-- `"github"`
-- `"x"` (Twitter)
-- `"linkedin"`
-- `"facebook"`
-- `"instagram"`
-- `"youtube"`
-- `"tiktok"`
-- `"twitch"`
-- `"pinterest"`
-- `"snapchat"`
-- `"whatsapp"`
-- `"telegram"`
-
-</div>
-
-Or you can provide a custom React component.
-
-## Copyright Notice
-
-Add a copyright notice with the `copyright` property:
-
-```tsx
-footer: {
-  copyright: `© ${new Date().getFullYear()} YourCompany LLC. All rights reserved.`;
-}
+  },
+};
 ```
 
-## Logo
-
-You can add a logo to your footer:
+### Social icons
 
-```tsx
-footer: {
-  logo: {
-    src: {
-      light: "/path/to/light-logo.png",
-      dark: "/path/to/dark-logo.png"
-    },
-    alt: "Company Logo",
-    width: "120px" // optional width
-  }
-}
-```
+Supported `icon` values include: `reddit`, `discord`, `github`, `x`, `linkedin`, `facebook`,
+`instagram`, `youtube`, `tiktok`, `twitch`, `pinterest`, `snapchat`, `whatsapp`, `telegram` — or a
+custom React component.
 
-## Customizing with Slot
+## Slots
 
-APIToGo provides `footer-before` and `footer-after` slots that allow you to insert custom content
-before or after the main footer columns:
+Insert content around the footer with `footer-before` and `footer-after` in site config `slots`:
 
 ```tsx
-// In your apitogo.config.tsx
 slots: {
   "footer-before": () => (
     <div>
       <h3>Custom pre-footer content</h3>
-      <p>This appears before the columns</p>
     </div>
   ),
-  "footer-after": () => (
-    <div>
-      <p>Additional footer content</p>
-    </div>
-  )
 }
 ```
 
-## Complete Example
-
-Here's a complete example showing all footer options:
+## Related
 
-```tsx
-footer: {
-  position: "center",
-  columns: [
-    {
-      title: "Product",
-      position: "start",
-      links: [
-        { label: "Features", href: "/features" },
-        { label: "Pricing", href: "/pricing" },
-        { label: "Documentation", href: "/docs" }
-      ]
-    },
-    {
-      title: "Resources",
-      position: "center",
-      links: [
-        { label: "Blog", href: "/blog" },
-        { label: "Support", href: "/support" },
-        { label: "GitHub", href: "https://github.com/yourusername" } // Auto-detected as external
-      ]
-    }
-  ],
-  social: [
-    { icon: "github", href: "https://github.com/yourusername" },
-    { icon: "linkedin", href: "https://linkedin.com/company/yourcompany", label: "LinkedIn" }
-  ],
-  copyright: `© ${new Date().getFullYear()} YourCompany LLC. All rights reserved.`,
-  logo: {
-    src: {
-      light: "/images/logo-light.svg",
-      dark: "/images/logo-dark.svg"
-    },
-    alt: "Company Logo",
-    width: "100px"
-  }
-}
-```
+- [Manifest](./manifest.md)
+- [Site](./site.md)

package/docs/configuration/llms.md

@@ -19,7 +19,7 @@ All options are disabled by default.
 
 LLM features are configured through the `docs` section in your config:
 
-```tsx title="apitogo.config.tsx"
+```tsx title="config"
 export default {
   docs: {
     files: "pages/**/*.{md,mdx}", // Your markdown files

package/docs/configuration/make-config.mdx

@@ -13,6 +13,14 @@ when it finds an OpenAPI spec and your config has none yet, and **regenerate `na
 `redirects`** from your `pages/` tree. Other existing settings (such as **`site`** or **`theme`**)
 stay as you left them unless you are creating files for the first time.
 
+:::note{title="Portal sites need apitogo.config.json"}
+
+For portal / MCP products you need **`apitogo.config.json`** for site, modules, plans, and auth —
+see [Manifest](./manifest.md) or scaffold with `npm create @lukoweb/apitogo@latest` /
+[MCP](../mcp/overview.md).
+
+:::
+
 ## What it does
 
 1. **Ensures you can run npm scripts** — If there is no **`package.json`**, it creates one with
@@ -24,11 +32,10 @@ stay as you left them unless you are creating files for the first time.
    **`apis/openapi.json`** or **`openapi.json`** at the project root) and your config has no
    **`apis`** entry yet, it adds an **`apis`** block pointing at that file. Existing **`apis`**
    settings are not overwritten.
-3. **Finds or creates a config file** — It looks for an existing `apitogo.config.*` or
-   `apitogo.config.*` file in the project root. If **none** exists, it creates
-   **`apitogo.config.tsx`** with **`docs.files`** for your pages glob, optional **`apis`** when a
-   spec was found, plus empty **`navigation`** and **`redirects`**, then fills nav and redirects
-   from disk.
+3. **Finds or creates a config file** — It looks for an existing `apitogo.config.*` file in the
+   project root. If **none** exists, it creates one with **`docs.files`** for your pages glob,
+   optional **`apis`** when a spec was found, plus empty **`navigation`** and **`redirects`**, then
+   fills nav and redirects from disk.
 4. **Rebuilds `navigation`** — Builds a tree from `.md` / `.mdx` files under your pages directory,
    including nested folders as categories, and adds the usual Documentation category plus API link
    block used by the generator.

package/docs/configuration/manifest.md

@@ -1,14 +1,13 @@
 # Site configuration (apitogo.config.json)
 
-Dev portal sites use a single JSON file for site settings, plans, authentication, and backend
-metadata. Code-only pieces (plugins, custom components) stay in `apitogo.config.tsx`.
+Dev portal sites use `apitogo.config.json` for site settings, plans, authentication, and backend
+metadata, with optional `.env` overrides for secrets and local tweaks.
 
 ## Files
 
 | File                  | Purpose                                                     |
 | --------------------- | ----------------------------------------------------------- |
 | `apitogo.config.json` | Committed defaults: site, modules, authentication, backend  |
-| `apitogo.config.tsx`  | Plugins and other non-JSON configuration                    |
 | `.env`                | Public client vars + publish secrets via `APITOGO_CONFIG_*` |
 
 ## Canonical shape
@@ -89,18 +88,9 @@ APITOGO_CONFIG_AUTHENTICATION__STRIPE__SECRET_KEY=sk_test_...
 APITOGO_CONFIG_AUTHENTICATION__STRIPE__WEBHOOK_SECRET=whsec_...
 ```
 
-## Thin `apitogo.config.tsx`
-
-```tsx
-import { buildApitogoConfig } from "@lukoweb/apitogo";
-import { devPortalBillingPlugin } from "@lukoweb/apitogo-plugin-dev-portal-billing";
-
-export default buildApitogoConfig({
-  plugins: [devPortalBillingPlugin()],
-});
-```
-
 ## Related
 
 - [Authentication](./authentication.md)
 - [Overview](./overview.md)
+- [MCP overview](../mcp/overview.md)
+- [Environment variables](../guides/environment-variables.md)

package/docs/configuration/navigation.mdx

@@ -18,7 +18,7 @@ entries can be links, document references, categories or custom pages.
 The navigation is defined using the `navigation` array in the APIToGo config file. Each item can be
 one of several types. At the simplest level you may only have links and categories.
 
-```tsx title="apitogo.config.tsx"
+```tsx title="config"
 {
   "navigation": [
     {
@@ -60,7 +60,7 @@ one of several types. At the simplest level you may only have links and categori
 
 Use the CLI command **`apitogo make-config`** to rebuild **`navigation`** and **`redirects`** from
 your Markdown files. See **[Make config (CLI)](./make-config.md)** for full usage, options, and
-behavior (including creating `apitogo.config.tsx` when no config exists, and which settings are left
+behavior (including creating `apitogo.config.json` when no config exists, and which settings are left
 untouched).
 
 ::::caution