Fetching Content

Launchpad's content fetching process is designed to be flexible and robust, allowing you to fetch, transform, and manage content from various sources. This guide provides an overview of how content flows through Launchpad, from configuration to storage.

Basic Configuration

Content fetching requires a ContentConfig object in your Launchpad configuration:

// launchpad.config.js
import { defineConfig } from '@bluecadet/launchpad/cli';
import { content } from '@bluecadet/launchpad/content';
import { jsonSource } from '@bluecadet/launchpad/content/sources/json';

export default defineConfig({
  plugins: [
    content({
      sources: [
        jsonSource({
          id: "example-source",
          files: {
            "example.json": "https://example.com/api/data",
          },
        }),
      ],
      transforms: [], // Add transforms here
      downloadPath: './content',
      backupAndRestore: true,
    }),
  ],
});

See the Content Configuration Reference for all options.

Running Content Updates

You can update content in two ways:

# As part of the full Launchpad startup
npx launchpad start

# Content updates only
npx launchpad content

See the CLI Commands Reference for more details.

Content Sources

Sources define where your content comes from. Launchpad includes several built-in sources:

• JSON/REST APIs
• CMS platforms (Contentful, Sanity, etc.)

Check the Content Sources Reference to learn more about available sources and how to create custom ones.

Fetch Lifecycle

Each content.fetch run now uses a staged run directory under tempPath.

1. Launchpad prepares a fresh staged output tree for the run.
2. Matching files from the currently published downloadPath that satisfy keep are copied into staging.
3. Sources and transforms write only into the staged tree for that run.
4. If every source and transform succeeds, the staged output is promoted into the published downloadPath, including any files written at the root of the staged download tree.
5. If the run fails, the staged output is discarded and the previously published downloadPath remains unchanged.
6. Promotion is fail-safe: Launchpad moves the current published path aside and restores it automatically if replacement cannot complete.

This makes the normal fetch path atomic at the source-directory level without requiring rollback from backups.

Transforms

Transforms process your content after it's downloaded. Common use cases include:

• Converting Markdown to HTML
• Resizing images
• Validating data
• Custom transformations

Learn more in the Transforms Reference.

Best Practices

• Rely on staged promotion for normal safety: Fetches now keep the published tree unchanged until promotion succeeds.
• Use backupAndRestore as compatibility protection: Backups are still available, but they are no longer the primary rollback mechanism for ordinary fetch failures.
• Treat content:document:write paths as staged paths: Event listeners should not assume the emitted path is already published.
• Implement Error Handling: Use the error handling system to gracefully handle failures.
• Monitor Progress: Use the logging system to track content updates.
• Organize Sources: Group related content into separate sources for better management.
• Cache Effectively: Configure appropriate cache settings for your content type.

Next Steps

• Read about Content Configuration
• Learn about Content Sources
• Explore Transforms
• Understanding Error Handling

For complete API documentation, visit the Content Reference Documentation.