> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.komo.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Hub Publishing vs Card Publishing, Visibility & Pages

> Master the complete publishing workflow: hub vs card publishing, page visibility, single card pages, scheduling, and multi-page hub architecture

# Hub Publishing vs Card Publishing, Visibility & Pages

Understanding the complete publishing architecture is crucial for managing your Engagement Hub effectively. This guide covers hub-level publishing, card-level publishing, page visibility, single card pages, and the advanced scheduling system.

## Overview: The Three-Layer Publishing System

Komo uses a **three-layer publishing architecture**:

```
Layer 1: Hub (Site) Publishing
    ↓ Controls entire hub visibility
    
Layer 2: Card Publishing  
    ↓ Controls individual card existence
    
Layer 3: Page Visibility
    ↓ Controls where cards appear within hub
```

### Layer 1: Hub Publishing

**What it controls:** Whether the entire Engagement Hub is accessible to the public.

**States:**

* **Draft** - Hub not visible, only accessible to admins
* **Published** - Hub live and accessible via domain

### Layer 2: Card Publishing

**What it controls:** Whether an individual card exists and can be displayed.

**States:**

* **Draft** - Card exists but isn't visible anywhere
* **Published** - Card is live and can be shown on pages
* **Scheduled** - Will auto-publish/unpublish at set times

### Layer 3: Page Visibility

**What it controls:** Which specific pages within a hub display the card.

**States:**

* **Visible on Page** - Card appears on that page
* **Hidden on Page** - Card exists but doesn't appear there
* **Scheduled** - Will auto-show/hide at set times

## Hub Publishing (Layer 1)

### What Hub Publishing Does

Publishing a hub makes the entire site accessible at your configured domain:

**Before Publishing:**

* Hub only accessible to logged-in admins
* Preview mode available
* Test and refine content
* Configure domain settings

**After Publishing:**

* Hub accessible to public via domain/URL
* All published cards become visible (based on page visibility)
* Analytics tracking begins
* SEO indexing starts

### How to Publish a Hub

1. Navigate to **Hub Settings**
2. Click **"Publish Hub"** button
3. Confirm domain configuration
4. Review publishing checklist
5. Click **"Publish"**

**Publishing Checklist:**

* ✅ Domain configured and pointing correctly
* ✅ At least one page has visible cards
* ✅ Essential cards are published
* ✅ Terms and conditions added (if running competitions)
* ✅ Tested preview mode
* ✅ Branding applied

### Unpublishing a Hub

Unpublishing makes the entire hub inaccessible:

**Use Cases:**

* Ending a campaign
* Major maintenance
* Rebranding
* Seasonal hubs (e.g., Christmas campaign ended)

**What Happens:**

* Public URL shows "Not Found" or custom message
* All cards become inaccessible
* Data and settings preserved
* Can republish anytime

## Card Publishing (Layer 2)

### What Card Publishing Does

Card publishing controls whether a card **exists** in the system:

**Draft Cards:**

* Exist in admin panel
* Editable by team
* Not visible to public
* Can be previewed by admins
* Don't count toward page limits

**Published Cards:**

* Exist and are live
* Can be visible on pages (if page visibility enabled)
* Accessible via single card page
* Count toward page limits (50 cards max per page)

### Publishing a Card

**Method 1: From Card Editor**

1. Edit the card
2. Click **"Publish"** button (top right)
3. Confirm publishing
4. Card status changes to "Published"

**Method 2: From Cards List**

1. Go to **Cards** list view
2. Find the card you want to publish
3. Click the **"Publish"** action in the card's action menu
4. Confirm publishing

**Note:** Cards must be published individually. There is no bulk publish feature.

**What Happens When Published:**

* Card becomes available for page visibility
* Can be added to hub pages
* Accessible via single card URL
* Analytics tracking begins
* Can be shared individually

### Unpublishing a Card

**Use Cases:**

* Remove outdated content
* End a competition
* Fix errors
* Seasonal content (e.g., remove Christmas card after holidays)

**What Happens:**

* Card disappears from all pages immediately
* Single card URL becomes inaccessible
* Data and entries preserved
* Can republish anytime
* Card returns to draft status

**Important:** Unpublishing is **immediate** and affects all pages where the card appears.

### Scheduled Publishing

Set automatic publish/unpublish times:

1. Edit card
2. Click **"Schedule"** button
3. Set **"Publish at"** date/time
4. Set **"Unpublish at"** date/time (optional)
5. Select timezone
6. Save schedule

**Use Cases:**

* Launch campaigns at specific times
* End competitions automatically
* Seasonal content (auto-show Christmas card Dec 1, hide Jan 1)
* Time-limited offers

## Page Visibility (Layer 3)

### Understanding Pages

A hub can have **multiple pages**, each with different cards:

**Home Page:**

* Default landing page
* Usually contains main content
* URL: `your-hub.com` or `your-hub.com/home`

**Additional Pages:**

* Create unlimited pages
* Different content per page
* URL: `your-hub.com/page-name`
* Examples: `/games`, `/competitions`, `/vip`

### Card-Page Relationship

**Key Concept:** Cards exist independently of pages, then are "placed" on pages.

**One Card, Multiple Pages:**

* Same card can appear on multiple pages
* Example: Newsletter signup card on Home, Games, and Contact pages
* Each page shows the same card (shared data/entries)

**Page-Specific Visibility:**

* Card visible on Page A
* Same card hidden on Page B
* Controlled independently per page

### Managing Page Visibility

**Show Card on Page:**

1. Navigate to page editor
2. Click **"Add Card"**
3. Select existing card or create new
4. Card appears on page

**Hide Card from Page:**

1. Find card on page
2. Click **"Hide"** or **"Remove from Page"**
3. Card disappears from that page only
4. Card still exists and can appear on other pages

**Important:** Hiding a card from a page ≠ unpublishing the card. The card remains published and visible elsewhere.

### Visibility Indicators

**In Admin Panel:**

* 🟢 **Green dot** - Visible on page
* 🔴 **Red dot** - Hidden on page
* 🟡 **Yellow dot** - Scheduled visibility
* ⚪ **Gray dot** - Draft (not published)

### Visibility Schedule (Per Page)

Schedule when a card appears/disappears on a specific page:

1. Find card on page
2. Click **"Schedule Visibility"**
3. Set **"Show at"** - When card appears
4. Set **"Hide at"** - When card disappears (optional)
5. Select timezone
6. Save

**Use Cases:**

* Flash sales (show banner 9 AM, hide 5 PM)
* Event countdowns (appear 7 days before, hide after event)
* Daily specials (different card each day)
* Rotating content

## Single Card Pages

### What is a Single Card Page?

A **standalone page** that displays only one card, without the hub navigation, header, or footer.

**URL Structure:**

* Hub page: `hub.com/games` (shows multiple cards + navigation)
* Single card: `hub.com/?card=abc123&singleCard=true` (shows only that card)

### When to Use Single Card Pages

**Use Cases:**

* **Email campaigns** - Link directly to specific competition
* **Social media** - Share direct link to quiz
* **QR codes** - Scan to enter specific promotion
* **Embedded experiences** - Link from external website
* **Focused experiences** - Remove distractions for high-value conversions

### Creating Single Card Links

**Method 1: Share Modal**

1. Edit card
2. Click **"Share"** button
3. Check **"Link to single card page"** checkbox
4. Copy generated URL
5. Optionally add UTM parameters

**Method 2: Manual Construction**

```
https://your-hub.com/?card={card-id}&singleCard=true
```

**With UTM Parameters:**

```
https://your-hub.com/?card={card-id}&singleCard=true&utm_source=email&utm_campaign=summer_sale
```

### Single Card vs Hub Page: User Experience

**Hub Page Experience:**

* User sees hub header/navigation
* Multiple cards visible
* Can browse other content
* Full brand experience
* Context of other offerings

**Single Card Experience:**

* Only the card visible
* No hub navigation
* No distractions
* Focused on one action
* Higher conversion rates for specific goals

### Analytics Differences

**Hub Page Traffic:**

* Tracked as hub page view
* User can navigate to other cards
* Session includes multiple interactions

**Single Card Traffic:**

* Tracked as direct card engagement
* Isolated analytics for that card
* Useful for measuring campaign effectiveness
* Clear attribution

## Multi-Page Hub Architecture

### Creating Multiple Pages

1. Go to **Hub Settings > Pages**
2. Click **"Add Page"**
3. Name the page (e.g., "Games", "VIP Area")
4. Set page slug (URL-friendly name)
5. Configure page settings
6. Add cards to new page

### Page Types

**Standard Pages:**

* Regular content pages
* Show in navigation (optional)
* Can have up to 50 cards

**Hidden Pages:**

* Don't show in navigation
* Accessible via direct URL
* Good for landing pages, special campaigns

**Password-Protected Pages:**

* Require password to access
* Good for exclusive content
* VIP areas, employee-only content

### Navigation Management

**Automatic Navigation:**

* Hub auto-generates navigation menu
* Shows all non-hidden pages
* Order based on page arrangement

**Custom Navigation:**

* Reorder pages in settings
* Hide specific pages from nav
* Add external links
* Customize menu appearance

### Cross-Page Card Strategy

**Shared Cards (Same Card on Multiple Pages):**

* Newsletter signup on every page
* Same competition across multiple entry points
* Consistent branding elements
* Shared data (entries, analytics)

**Page-Specific Cards:**

* Games only on Games page
* VIP content only on VIP page
* Targeted experiences
* Isolated analytics

## Complete Publishing Workflow Examples

### Example 1: New Campaign Launch

**Week 1: Preparation**

* Create hub (draft)
* Add pages: Home, Competition, Terms
* Create competition card (draft)
* Create terms card (draft)
* Test everything in preview

**Week 2: Pre-Launch**

* Publish hub
* Publish terms card
* Set competition card to scheduled (publish Monday 9 AM)
* Hide competition card from navigation until launch

**Week 3: Launch Day**

* Competition card auto-publishes at 9 AM
* Show on Home and Competition pages
* Send email with single card link
* Share on social media

**Week 4: Campaign End**

* Competition card auto-unpublishes (scheduled)
* Add "Campaign Ended" card to page
* Keep terms visible for legal requirements

### Example 2: Multi-Page VIP Experience

**Setup:**

* Main hub: Standard content
* VIP page: Exclusive competitions (password protected)
* Games page: General games
* Rewards page: Loyalty program

**Card Strategy:**

* General signup card: Visible on all pages
* VIP competition: Only on VIP page, requires password
* General games: Only on Games page
* Loyalty dashboard: Home and Rewards pages

**Publishing:**

* Publish hub
* Publish all cards
* Set VIP page to password protected
* Configure page visibility per card

### Example 3: Seasonal Content Rotation

**January:**

* New Year promotion card (scheduled: Jan 1-31)
* Visible on Home page only

**February:**

* Valentine's campaign (scheduled: Feb 1-14)
* Replaces New Year card on Home page
* Also visible on /special-offers page

**March:**

* Easter preview (scheduled: Mar 1-31)
* Different card on Home page
* Valentine's card hidden

**Year-Round:**

* Newsletter signup: Always visible on all pages
* Contact form: Always visible on Contact page

## Best Practices

### Publishing Strategy

**Do:**

* Test thoroughly in draft mode before publishing
* Use scheduled publishing for time-sensitive content
* Keep legal pages (Terms, Privacy) always published
* Create hidden pages for specific campaigns
* Use single card pages for focused conversions

**Don't:**

* Publish unfinished cards
* Forget to unpublish outdated competitions
* Overload pages with too many cards (max 50)
* Publish without testing mobile responsiveness

### Visibility Management

**Do:**

* Use page-specific visibility strategically
* Schedule visibility for time-limited offers
* Hide cards rather than unpublishing (if might reuse)
* Monitor which cards appear on which pages

**Don't:**

* Leave test cards visible on public pages
* Forget to hide seasonal content after holidays
* Make navigation cluttered with too many pages
* Hide essential cards (Terms, Contact)

### Multi-Page Architecture

**Do:**

* Organize content logically by page
* Use clear, descriptive page names
* Limit navigation to 5-7 main pages
* Create focused experiences per page

**Don't:**

* Create too many pages (confusing navigation)
* Put all cards on one page (overwhelming)
* Duplicate same card on every page (redundant)
* Forget mobile navigation experience

## Troubleshooting

### Issue: Card Not Showing on Page

**Check:**

1. Is the card **published**? (not draft)
2. Is the card **visible** on that specific page?
3. Is there a visibility schedule preventing display?
4. Is the hub itself published?
5. Has the card reached its max entries (if competition)?

### Issue: Published Card Not Accessible

**Check:**

1. Hub is published?
2. Card is published (not draft)?
3. Not hidden on that page?
4. No entry limits reached?
5. Eligibility rules met (if configured)?

### Issue: Single Card Link Not Working

**Check:**

1. Card is published?
2. Card ID in URL is correct?
3. `singleCard=true` parameter included?
4. Hub domain is correct?
5. No extra characters in URL?

### Issue: Schedule Not Working

**Check:**

1. Timezone configured correctly?
2. Both publish and unpublish times set (if needed)?
3. Schedule saved successfully?
4. Card status allows scheduling?
5. Check if schedule conflicts with manual publish/unpublish

## FAQ

**Q: What's the difference between unpublishing a card and hiding it from a page?**
A: **Unpublishing** removes the card entirely (invisible everywhere). **Hiding** from a page keeps it published but removes it from that specific page (still visible elsewhere).

**Q: Can I have the same card on multiple pages?**
A: Yes! One card can appear on unlimited pages. All pages show the same card with shared data and entries.

**Q: What happens if I unpublish a hub?**
A: The entire site becomes inaccessible. All cards, pages, and content are hidden from public view. Admin access remains.

**Q: Can I schedule a card to show on different pages at different times?**
A: Yes! Each page has independent visibility scheduling for the same card. Show on Page A Monday, Page B Tuesday.

**Q: What's the maximum number of cards per page?**
A: 50 cards maximum per page. This includes both published and draft cards on that page.

**Q: Can I password-protect individual cards?**
A: No, password protection is at the page level. But you can use entry rules/gating on individual cards.

**Q: Do single card pages count as page views in analytics?**
A: Yes, they're tracked as card-specific engagement. You can see both hub page views and single card views in analytics.

**Q: Can I embed a single card on an external website?**
A: Yes! Use the embed code option to iframe the single card page into external sites.

**Q: What happens to entries when I unpublish a card?**
A: All entry data is preserved. When you republish, entries are still there. Only visibility changes, not data.

**Q: Can I have different versions of the same card on different pages?**
A: No, it's the same card. If you need different versions, create separate cards or use branching logic within the card.

## Related Documentation

* [Card Scheduling](/getting-started/hub-setup/card-scheduling) - Detailed scheduling guide
* [Multi-Page Hubs](/interactive-features/features/multi-page-hubs) - Advanced page architecture
* [Before You Hit Publish](/getting-started/hub-setup/before-you-hit-publish) - Pre-launch checklist
* [Entry Rules](/interactive-features/features/entry-rules) - Gating and access control
* [Analytics](/getting-started/hub-setup/analytics) - Tracking and measurement

***

**Need Help?** Contact [support@komo.tech](mailto:support@komo.tech) for publishing and visibility assistance.