CPQDEVELOPERS Brand Consistency Guide
This document defines the standard naming conventions, phrases, and taglines to use consistently across the site and all communications.
Brand Names
Primary Brand
| Usage | Format | Notes | |——-|——–|——-| | Site name | cpqdevelopers | Lowercase, one word, no spaces | | Legal entity | CPQDEV LLC | All caps for LLC | | Domain | cpqdevelopers.com | Lowercase |
Incorrect usages to avoid:
- CPQDevelopers (camel case)
- CPQ Developers (two words)
- cpq-developers (hyphenated)
- CpqDevelopers (mixed case)
Logo Text
- Display as:
cpq(colored) +developers(plain) - Never abbreviate to just “CPQ” when referring to the site
Taglines & Headlines
Primary Tagline
Learn Salesforce Revenue Cloud with Confidence
Use for: Homepage hero, primary marketing materials
Value Proposition
Get expert guidance, set up your trial, and gain CPQ-to-Revenue Cloud migration insights.
Use for: Hero descriptions, about sections, email signatures
Site Description (Meta/SEO)
Get specialized, Salesforce Revenue Cloud CPQ expertise for your projects.
Use for: Meta descriptions, social sharing
Blog Section
Articles - “Read our industry case studies and how-to guides”
Product & Technology Names
Always use official Salesforce naming:
| Correct | Incorrect |
|---|---|
| Salesforce Revenue Cloud | Revenue cloud, revenue-cloud, RC |
| Salesforce CPQ | CPQ (standalone is OK), Salesforce Configure Price Quote |
| Revenue Lifecycle Management (RLM) | revenue lifecycle management, Rlm |
| Quote Line Editor (QLE) | quote line editor, Qle |
| Revenue Cloud Advanced (RCA) | revenue cloud advanced, Rca |
First Mention Rule
- First mention: Full name with abbreviation, e.g., “Revenue Lifecycle Management (RLM)”
- Subsequent mentions: Abbreviation is acceptable, e.g., “RLM”
Author Attribution
Formal
Skylar Rhodes, Salesforce Revenue Cloud CPQ Architect
Informal
Skylar Rhodes, founder of cpqdevelopers
Bio (Standard)
Hey, I’m Skylar Rhodes, a Salesforce Revenue Cloud CPQ Architect. I created cpqdevelopers to fill the void of information that developers, admins, and product owners face while navigating the complicated world of Salesforce Revenue.
Content Categories (Tags)
Use lowercase, hyphenated tags consistently:
| Tag | When to Use |
|---|---|
revenue-cloud |
Revenue Cloud specific content |
cpq |
CPQ specific content |
api |
API tutorials, integrations |
code |
Code samples, Apex, development |
migration |
CPQ to Revenue Cloud migration |
rlm |
Revenue Lifecycle Management |
Call-to-Action Phrases
Consultation Booking
- Primary: Free Assesment
- Alternative: Let’s Work Together!
- Link text: Schedule a 15-minute consultation
Content Engagement
- Articles: Read our industry case studies and how-to guides
- Resources: Explore our developer tools
URL Conventions
- Use lowercase
- Use hyphens for word separation
- Be descriptive but concise
Examples:
/salesforce-revenue-cloud-setup-guide//cpq-price-waterfall-calculator//revenue-cloud-vs-cpq-business-decision-guide/
Social Media Handles
| Platform | Handle | URL |
|---|---|---|
| skylarrhodes | linkedin.com/in/skylarrhodes/ | |
| YouTube | @cpqdeveloperss | youtube.com/@cpqdeveloperss |
| GitHub | sr7d | github.com/sr7d |
Associated Products
| Product | Domain | Description |
|---|---|---|
| SilkQuote | silkquote.com | AppExchange product |
Tone & Voice
Characteristics
- Expert but approachable: Demonstrate deep knowledge without being condescending
- Practical: Focus on real-world applications and solutions
- Direct: Get to the point, respect reader’s time
- Educational: Fill the “void of information” that exists in this space
Avoid
- Overly promotional language
- Jargon without explanation
- Vague claims without substance
- Unnecessary complexity
LLM & AI References
When referring to AI/LLM capabilities on the site:
- LLMs.txt file:
/llms.txt - LLM documentation page:
/for-llms/ - Description: “LLM-readable documentation” or “AI-friendly documentation”
Quick Reference Checklist
Before publishing content, verify:
- Site name is “cpqdevelopers” (lowercase, one word)
- Salesforce product names use official capitalization
- Tags are lowercase and hyphenated
- URLs follow the convention (lowercase, hyphens)
- Author bio matches standard version
- CTAs use approved phrases
- First mention of abbreviations includes full name
Last updated: 2025-01-27