slim-rebranding

Rebrand SLIM marketplace artifacts across hero, registry, and documentation assets.

35|14|Updated Feb 16, 2022

Search Tags:#automation #branding #registry #marketplace #Docusaurus #docs-generation #SLIM

Ready to run

npx skills add https://github.com/NASA-AMMOS/slim --skill slim-rebranding

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: slim-rebranding
Source: https://github.com/NASA-AMMOS/slim/tree/main/static/marketplace/skills/slim-rebranding
Command: npx skills add https://github.com/NASA-AMMOS/slim --skill slim-rebranding

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Rebranding SLIM marketplace artifacts for a new project identity while preserving core attribution and structure.

Core Features & Use Cases

Hero and branding adjustments: Update logos, taglines, and project metadata across the website without losing SLIM's proven architecture.
Registry and marketplace handling: Import external registries when needed and clear local marketplace content to align with the new branding.
Documentation generation: Create updated documentation pages and ensure references remain consistent with the new brand.

Quick Start

Use the slim-rebranding skill to initiate branding changes, provide the new project name and URL, and optionally supply external registry sources. The workflow will update docusaurus.config.js, brandingConfig, and registry files, then generate updated docs and commit the changes.

Frequently Asked Questions about slim-rebranding

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I rebrand a Docusaurus marketplace site for a new project?▼

You can clear local marketplace content to align with the new branding by removing existing local artifacts and optionally importing external registry sources to populate the marketplace with the correct project identity.

Does SLIM rebranding preserve the original project attribution and structure?▼

Yes, the rebranding process preserves core attribution and structure by updating logos, taglines, and project metadata across the website while maintaining the proven SLIM architecture underneath.

What do I need to set up before applying automated branding to a registry marketplace?▼

Before applying branding, you need access to a target Git repository containing Docusaurus configuration files, standard Node.js tooling installed, and optionally external registry sources to import into your marketplace.

How do I update documentation generation when changing a project's brand identity?▼

Documentation generation updates automatically during the branding workflow by creating updated documentation pages and ensuring all references remain consistent with the new project brand across the Docusaurus site.

Can I import external registries while clearing local marketplace content during rebranding?▼

Yes, you can import external registries when needed and clear local marketplace content simultaneously, allowing you to align the marketplace with new branding while pulling in external sources to populate the registry.