cms-best-practices

Name: cms-best-practices
Author: webflow

106stars16forks

How to install cms-best-practices?

webflow/webflow-skills/cms-best-practices

$npx -y skills add webflow/webflow-skills --skill cms-best-practices

Installs into the current project.

Summary

Expert guidance on Webflow CMS architecture and best practices. Use when planning collections, setting up relationships, optimizing content structure, or troubleshooting CMS issues.

Files · 1

View on GitHub

SKILL.md

1	# CMS Best Practices
2
3	Provide expert guidance on Webflow CMS architecture, relationships, optimization, and troubleshooting.
4
5	## Important Note
6
7	ALWAYS use Webflow MCP tools for all operations:
8	- Use Webflow MCP's `webflow_guide_tool` to get best practices before starting
9	- Use Webflow MCP's `data_sites_tool` with action `list_sites` to identify available sites
10	- Use Webflow MCP's `data_sites_tool` with action `get_site` to retrieve site details and plan limits
11	- Use Webflow MCP's `data_cms_tool` with action `get_collection_list` to analyze existing collections
12	- Use Webflow MCP's `data_cms_tool` with action `get_collection_details` to examine collection schemas
13	- Use Webflow MCP's `data_cms_tool` with action `list_collection_items` to assess content volume
14	- Use Webflow MCP's `data_pages_tool` with action `list_pages` to understand page structure
15	- Use Webflow MCP's `ask_webflow_ai` for specific API questions
16	- DO NOT use any other tools or methods for Webflow operations
17	- All tool calls must include the required `context` parameter (15-25 words, third-person perspective)
18
19	## Instructions
20
21	### Phase 1: Discovery & Analysis
22	1. Identify the request: Determine if user is:
23	- Planning new CMS structure
24	- Optimizing existing collections
25	- Troubleshooting performance issues
26	- Setting up relationships
27	- Seeking architecture guidance
28	2. Get site information: Use Webflow MCP's `data_sites_tool` with actions `list_sites` and `get_site` to understand plan limits
29	3. Analyze existing structure: Use Webflow MCP's `data_cms_tool` with actions `get_collection_list` and `get_collection_details` to examine current setup
30	4. Assess content volume: Use Webflow MCP's `data_cms_tool` with action `list_collection_items` to understand scale
31	5. Review pages: Use Webflow MCP's `data_pages_tool` with action `list_pages` to see how content is displayed
32
33	### Phase 2: Requirements Gathering
34	6. Understand use case: Ask clarifying questions:
35	- What content needs to be managed?
36	- Who will update the content?
37	- How will content be displayed?
38	- What relationships are needed?
39	- Expected content volume?
40	7. Identify constraints: Consider plan limits, technical constraints, team skills
41	8. Define success criteria: Performance goals, editorial workflow, scalability needs
42
43	### Phase 3: Architecture Planning
44	9. Design collection structure: Plan collections, fields, and relationships
45	10. Select field types: Choose appropriate field types for each content element
46	11. Plan relationships: Design one-to-many and many-to-many connections
47	12. Consider taxonomy: Determine categories, tags, and organizational structure
48	13. Plan for scale: Design for growth (pagination, performance, limits)
49	14. Document decisions: Explain tradeoffs and reasoning
50
51	### Phase 4: Recommendations & Validation
52	15. Generate recommendations: Provide specific, actionable guidance
53	16. Prioritize changes: Organize by impact (quick wins vs. long-term)
54	17. Explain tradeoffs: Help users understand limitations and workarounds
55	18. Validate against best practices: Check against Webflow limitations and patterns
56	19. Provide alternatives: Offer multiple approaches when applicable
57	20. Create implementation roadmap: Break down into phases
58
59	### Phase 5: Implementation Guidance
60	21. Provide step-by-step instructions: Clear guidance for implementation
61	22. Offer to assist: Suggest using other skills (cms-collection-setup, bulk-cms-update)
62	23. Document structure: Recommend documentation for team reference
63	24. Suggest testing approach: Guide on how to validate changes
64	25. Plan for migration: If refactoring, provide migration strategy
65
66	## Collection Architecture
67
68	### When to Use CMS vs Static
69
70	Use CMS when:
71	- Content updates frequently (weekly or more)
72	- Multiple similar items (blog posts, products, team members, projects)
73	- Non-technical users need to edit content
74	- Content needs filtering/sorting on the frontend
75	- Same content appears on multiple pages (author bios, product features)
76	- Content follows a consistent structure across items
77	- You need to dynamically generate pages
78
79	Use Static when:
80	- Content rarely changes (annual updates or less)
81	- Unique one-off sections (about page hero, homepage special features)
82	- Complex custom layouts per item that don't follow patterns
83	- No need for dynamic filtering or search
84	- Content is highly customized and doesn't share structure
85	- Performance is critical and content doesn't change
86	- You need complete design flexibility per section
87
88	Hybrid Approach:
89	- Static pages with CMS-driven sections (e.g., static homepage with CMS testimonials)
90	- CMS for recent content, static archives for old

People who liked this also viewed

6 picks

Type

cms-best-practices

106stars16forks

View on GitHub

How to install cms-best-practices?

webflow/webflow-skills/cms-best-practices

$npx -y skills add webflow/webflow-skills --skill cms-best-practices

Installs into the current project.

Summary

Expert guidance on Webflow CMS architecture and best practices. Use when planning collections, setting up relationships, optimizing content structure, or troubleshooting CMS issues.

Files · 1

View on GitHub

SKILL.md

1	# CMS Best Practices
2
3	Provide expert guidance on Webflow CMS architecture, relationships, optimization, and troubleshooting.
4
5	## Important Note
6
7	ALWAYS use Webflow MCP tools for all operations:
8	- Use Webflow MCP's `webflow_guide_tool` to get best practices before starting
9	- Use Webflow MCP's `data_sites_tool` with action `list_sites` to identify available sites
10	- Use Webflow MCP's `data_sites_tool` with action `get_site` to retrieve site details and plan limits
11	- Use Webflow MCP's `data_cms_tool` with action `get_collection_list` to analyze existing collections
12	- Use Webflow MCP's `data_cms_tool` with action `get_collection_details` to examine collection schemas
13	- Use Webflow MCP's `data_cms_tool` with action `list_collection_items` to assess content volume
14	- Use Webflow MCP's `data_pages_tool` with action `list_pages` to understand page structure
15	- Use Webflow MCP's `ask_webflow_ai` for specific API questions
16	- DO NOT use any other tools or methods for Webflow operations
17	- All tool calls must include the required `context` parameter (15-25 words, third-person perspective)
18
19	## Instructions
20
21	### Phase 1: Discovery & Analysis
22	1. Identify the request: Determine if user is:
23	- Planning new CMS structure
24	- Optimizing existing collections
25	- Troubleshooting performance issues
26	- Setting up relationships
27	- Seeking architecture guidance
28	2. Get site information: Use Webflow MCP's `data_sites_tool` with actions `list_sites` and `get_site` to understand plan limits
29	3. Analyze existing structure: Use Webflow MCP's `data_cms_tool` with actions `get_collection_list` and `get_collection_details` to examine current setup
30	4. Assess content volume: Use Webflow MCP's `data_cms_tool` with action `list_collection_items` to understand scale
31	5. Review pages: Use Webflow MCP's `data_pages_tool` with action `list_pages` to see how content is displayed
32
33	### Phase 2: Requirements Gathering
34	6. Understand use case: Ask clarifying questions:
35	- What content needs to be managed?
36	- Who will update the content?
37	- How will content be displayed?
38	- What relationships are needed?
39	- Expected content volume?
40	7. Identify constraints: Consider plan limits, technical constraints, team skills
41	8. Define success criteria: Performance goals, editorial workflow, scalability needs
42
43	### Phase 3: Architecture Planning
44	9. Design collection structure: Plan collections, fields, and relationships
45	10. Select field types: Choose appropriate field types for each content element
46	11. Plan relationships: Design one-to-many and many-to-many connections
47	12. Consider taxonomy: Determine categories, tags, and organizational structure
48	13. Plan for scale: Design for growth (pagination, performance, limits)
49	14. Document decisions: Explain tradeoffs and reasoning
50
51	### Phase 4: Recommendations & Validation
52	15. Generate recommendations: Provide specific, actionable guidance
53	16. Prioritize changes: Organize by impact (quick wins vs. long-term)
54	17. Explain tradeoffs: Help users understand limitations and workarounds
55	18. Validate against best practices: Check against Webflow limitations and patterns
56	19. Provide alternatives: Offer multiple approaches when applicable
57	20. Create implementation roadmap: Break down into phases
58
59	### Phase 5: Implementation Guidance
60	21. Provide step-by-step instructions: Clear guidance for implementation
61	22. Offer to assist: Suggest using other skills (cms-collection-setup, bulk-cms-update)
62	23. Document structure: Recommend documentation for team reference
63	24. Suggest testing approach: Guide on how to validate changes
64	25. Plan for migration: If refactoring, provide migration strategy
65
66	## Collection Architecture
67
68	### When to Use CMS vs Static
69
70	Use CMS when:
71	- Content updates frequently (weekly or more)
72	- Multiple similar items (blog posts, products, team members, projects)
73	- Non-technical users need to edit content
74	- Content needs filtering/sorting on the frontend
75	- Same content appears on multiple pages (author bios, product features)
76	- Content follows a consistent structure across items
77	- You need to dynamically generate pages
78
79	Use Static when:
80	- Content rarely changes (annual updates or less)
81	- Unique one-off sections (about page hero, homepage special features)
82	- Complex custom layouts per item that don't follow patterns
83	- No need for dynamic filtering or search
84	- Content is highly customized and doesn't share structure
85	- Performance is critical and content doesn't change
86	- You need complete design flexibility per section
87
88	Hybrid Approach:
89	- Static pages with CMS-driven sections (e.g., static homepage with CMS testimonials)
90	- CMS for recent content, static archives for old

People who liked this also viewed

6 picks

Type