Skip to content

Update paths for Usage & billing, Protocols, remove duplicate file #328

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 25, 2019
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Update paths for Usage & billing, Protocols, remove duplicate file
  • Loading branch information
sanscontext committed Nov 25, 2019
commit 08d85b51bbc300264f66ee10cfd58f6cb633c308
39 changes: 19 additions & 20 deletions src/_data/sidenav/main.yml
Original file line number Diff line number Diff line change
Expand Up @@ -62,10 +62,10 @@ sections:
title: Account Management
- path: /guides/usage-and-billing/billing
title: Billing and Account FAQs
- path: /guides/usage-and-billing/discounts-for-startups-npos
title: Do you offer discounts or coupons?
- path: /guides/usage-and-billing/mtus-and-throughput
title: 'MTUs, Throughput and Billing'
- path: /guides/usage-and-billing/discounts-for-startups-npos
title: Do you offer discounts or coupons?
- path: /guides/usage-and-billing/startup-program
title: What is the Segment Startup Program?
- section_title: Connections
Expand Down Expand Up @@ -203,30 +203,29 @@ sections:
section:
- path: /protocols
title: Protocols and Schema Controls
- path: /protocols/anomaly_detection
title: 'Protocols: Anomaly Detection'
- path: /protocols/apis-and-extensions
title: 'Protocols: APIs and Extensions'
- path: /protocols/ecommerce-tracking-plan
title: Ecommerce Tracking Plans
- path: /protocols/whats-a-tracking-plan
title: What's a Tracking Plan?
- path: /protocols/what-to-track
title: What Should I track?
- path: /protocols/example-tracking-plan
title: Example Tracking Plans
- path: /protocols/faq
title: Protocols FAQ
- path: /protocols/ecommerce-tracking-plan
title: Ecommerce Tracking Plans
- path: /protocols/schema
title: Schema Controls
- path: /protocols/tracking-plan-events
title: What events should I track?
- path: /protocols/typewriter
title: 'Typewriter'
- path: /protocols/tracking-plan
title: 'Protocols: Tracking Plans'
title: 'Protocols Tracking Plans'
- path: /protocols/anomaly_detection
title: 'Protocols Anomaly Detection'
- path: /protocols/apis-and-extensions
title: 'Protocols APIs and Extensions'
- path: /protocols/faq
title: Protocols FAQ
- path: /protocols/transformations
title: 'Protocols: Transformations'
- path: /protocols/typewriter
title: 'Protocols: Typewriter'
- path: /protocols/what-to-track
title: What Should I track?
- path: /protocols/whats-a-tracking-plan
title: What's a Tracking Plan?
title: 'Protocols Transformations'

- section_title: Segment App
section:
- path: /segment-app
Expand Down
28 changes: 0 additions & 28 deletions src/protocols/tracking-plan-events.md

This file was deleted.

2 changes: 1 addition & 1 deletion src/protocols/what-to-track.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: "What Should I track?"
title: What Should I track?
---

As the central hub for your customer data, we think it's important to give you the benefit of some hard-won best practices from our happiest and most successful customers.
Expand Down