initial commit after project creation

This commit is contained in:
Gerhard Scheikl
2026-04-01 09:38:50 +02:00
commit b02af637d4
292 changed files with 61408 additions and 0 deletions

View File

@@ -0,0 +1,128 @@
---
seo:
title: Q1 Campaign Launch - Marketing Team
description: Internal guide for launching our new product features in Q1
title: Internal Document Example
last_edited: '2025-07-15T07:37:45.447Z'
---
<Callout
body={<>
🤖 This example is AI generated, any references to real places or people are incidental.
</>}
variant="warning"
/>
**Marketing Team Internal Documentation**
This guide outlines the complete campaign strategy, timeline, and deliverables for our Q1 feature launch.
<Callout
body={<>
**Campaign Deadline**: All assets must be finalized by **March 15th** for the March 20th launch.
</>}
variant="warning"
/>
## Campaign Overview
**Product**: Enhanced Analytics Dashboard\
**Target Audience**: Enterprise customers, data analysts, product managers\
**Launch Date**: March 20, 2025\
**Campaign Duration**: 8 weeks (Pre-launch + 6 weeks active)
## Key Messaging & Positioning
### Primary Message
"Transform raw data into actionable insights with our most powerful analytics dashboard yet."
### Supporting Points
* 3x faster query performance
* Real-time collaboration features
* Advanced visualization tools
* Enterprise-grade security
<Callout
body={<>
All messaging must align with our established brand voice: **Professional, innovative, and customer-focused**. Reference the brand guidelines doc for tone specifics.
</>}
variant="info"
/>
## Campaign Timeline & Deliverables
| Week | Phase | Key Deliverables | Owner | Status |
| -------- | ------------- | ----------------------------------------- | ------------ | -------------- |
| Week 1-2 | Pre-Launch | Blog posts, case studies, email sequences | Content Team | ✅ Complete |
| Week 3 | Soft Launch | Partner announcements, beta user outreach | Partnerships | 🟡 In Progress |
| Week 4 | Launch Week | Press release, social campaign, webinar | PR & Social | ⏳ Pending |
| Week 5-6 | Amplification | Customer stories, retargeting ads | Growth Team | ⏳ Pending |
| Week 7-8 | Optimization | A/B testing, performance analysis | Analytics | ⏳ Pending |
## Content Calendar
### Blog Content
* **March 5**: "The Future of Data Analytics" (Thought Leadership)
* **March 12**: "Customer Success Story: TechCorp's 200% ROI" (Case Study)
* **March 20**: "Introducing Enhanced Analytics Dashboard" (Product Launch)
* **March 27**: "5 Ways to Maximize Your Analytics ROI" (How-To Guide)
### Social Media
* **LinkedIn**: B2B focused, 3 posts/week
* **Twitter**: Industry news & quick tips, daily posts
* **YouTube**: Product demo video, launch day
<Callout
body={<>
Remember to use campaign hashtag **#DataDrivenDecisions** consistently across all channels. Pre-schedule posts using Hootsuite.
</>}
variant="success"
/>
## Budget Allocation
| Channel | Budget | Expected ROI | Notes |
| ----------------- | ----------- | ------------ | --------------------------- |
| Paid Social | $15,000 | 4:1 | Focus on LinkedIn & Twitter |
| Google Ads | $25,000 | 3.5:1 | Target high-intent keywords |
| Content Marketing | $8,000 | 6:1 | Video production & design |
| Events/Webinars | $12,000 | 5:1 | Lead generation focus |
| **Total** | **$60,000** | **4.2:1** | Q1 campaign budget |
## Success Metrics
**Primary KPIs**:
* 500 new trial sign-ups (target)
* 150 demo requests
* $200K pipeline generated
* 25% increase in organic traffic
**Secondary Metrics**:
* Email open rates >22%
* Social engagement +40%
* Webinar attendance >300
* Press coverage in 5+ publications
<Callout
body={<>
Track all metrics in our **Campaign Dashboard**. Weekly check-ins every Tuesday at 10 AM to review performance and adjust tactics.
</>}
variant="idea"
/>
## Emergency Contacts & Escalation
**Campaign Manager**: Sarah Kim (@sarah-kim, ext. 2845)\
**Creative Director**: Mike Chen (@mike-creative, ext. 2901)\
**PR Lead**: Jessica Torres (@jess-pr, ext. 2756)\
**Analytics**: David Park (@david-analytics, ext. 2612)
***
*Document Owner: Marketing Team | Next Review: March 1, 2025*

View File

@@ -0,0 +1,211 @@
---
seo:
title: TinaDocs Type Definition
title: Library (API) Example
last_edited: '2025-07-15T07:43:31.405Z'
tocIsHidden: false
---
> This example content is a random page taken from the [PlateJS documentation](https://platejs.org/docs/api/slate/location-ref).
Location references are objects that keep specific locations (paths, points, or ranges) in a document synced over time as new operations are applied to the editor.
You can access their `current` property at any time for the up-to-date location value. You can access their `current` property at any time for the up-to-date location value.
## Types
***
#### `PathRef`
Path reference objects keep a specific path in a document synced over time. Created using `editor.api.pathRef`.
<typeDefinition
property={[
{
name: "current",
description: "The current path value, updated as operations are applied.\n",
type: "Path | null",
required: true,
experimental: false,
typeUrl: ""
},
{
name: "affinity",
description:
"The direction to prefer when transforming the path:\n\n* 'forward': Prefer the position after inserted content\n* 'backward': Prefer the position before inserted content\n* null: No preference\n",
type: "'forward' | 'backward' | null",
required: false,
experimental: false
},
{
name: "unref( )",
description:
"Call this when you no longer need to sync this path. Returns the final path value.\n",
type: "( ) => Path | null"
}
]}
/>
#### `PointRef`
Point reference objects keep a specific point in a document synced over time. Created using `editor.api.pointRef`.
<typeDefinition
property={[
{
name: "current",
description:
"The current point value, updated as operations are applied.\n",
type: "Point | null",
required: true,
experimental: false,
typeUrl: ""
},
{
name: "affinity",
description:
"The direction to prefer when transforming the point:\n\n* 'forward': Prefer the position after inserted content\n* 'backward': Prefer the position before inserted content\n* null: No preference\n",
type: "'forward' | 'backward' | null",
required: false,
experimental: false
},
{
name: "unref( )",
description:
"Call this when you no longer need to sync this point. Returns the final point value.\n",
type: "( ) => Point | null"
}
]}
/>
#### `RangeRef`
Range reference objects keep a specific range in a document synced over time. Created using `editor.api.rangeRef`.
<typeDefinition
property={[
{
name: "current",
description:
"The current range value, updated as operations are applied.\n",
type: "TRange | null",
required: true,
experimental: false,
typeUrl: ""
},
{
name: "affinity",
description:
"The direction to prefer when transforming the range:\n\n* 'forward': Both points prefer after inserted content\n* 'backward': Both points prefer before inserted content\n* 'inward': Range tends to stay same size when content is inserted at edges\n* 'outward': Range tends to grow when content is inserted at edges\n* null: No preference\n",
type: "'forward' | 'backward' | 'inward' | 'outward' | null",
required: false,
experimental: false
},
{
name: "unref( )",
description:
"Call this when you no longer need to sync this range. Returns the final range value.\n",
type: "( ) => TRange | null"
}
]}
/>
Example usage of a RangeRef:
```typescript
const selectionRef = editor.api.rangeRef(editor.selection, {
affinity: 'inward',
})
// Operations that might change the selection
Transforms.unwrapNodes(editor)
// Restore the selection using the ref
Transforms.select(editor, selectionRef.unref())
```
## `PathRefApi`
***
#### `transform`
Transform a path reference by an operation.
<typeDefinition
property={[
{
name: "ref",
description: "The path reference to transform.\n",
type: "PathRef",
required: true,
experimental: false,
typeUrl: ""
},
{
name: "op",
description:
"The operation to apply. The editor calls this automatically as needed.\n",
type: "Operation",
required: true,
experimental: false
}
]}
/>
## `PointRefApi`
***
#### `transform`
Transform a point reference by an operation.
<typeDefinition
property={[
{
name: "ref",
description: "The point reference to transform.\n",
type: "PointRef",
required: true,
experimental: false,
typeUrl: ""
},
{
name: "op",
description:
"The operation to apply. The editor calls this automatically as needed.\n",
type: "Operation",
required: true,
experimental: false
}
]}
/>
## `RangeRefApi`
***
#### `transform`
Transform a range reference by an operation.
<typeDefinition
property={[
{
name: "ref",
description: "The range reference to transform.\n",
type: "RangeRef",
required: true,
experimental: false,
typeUrl: ""
},
{
name: "op",
description:
"The operation to apply. The editor calls this automatically as needed.\n",
type: "Operation",
required: true,
experimental: false
}
]}
/>

View File

@@ -0,0 +1,6 @@
---
title: Pet Store All Routes
last_edited: '2025-07-15T07:34:30.319Z'
---
<apiReference schemaFile="Swagger-Petstore.json" />