@eventcatalog/create-eventcatalog 4.3.3 → 4.3.4

package/templates/default/domains/Subscriptions/services/SubscriptionService/queries/GetSubscriptionStatus/versioned/0.0.1/schema.json

@@ -1,54 +0,0 @@
-{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "title": "GetSubscriptionStatusResponse",
-  "type": "object",
-  "properties": {
-    "userId": {
-      "type": "string",
-      "description": "The unique identifier for the user."
-    },
-    "subscriptionStatus": {
-      "type": "string",
-      "enum": ["active", "canceled", "expired", "pending"],
-      "description": "The current status of the user's subscription."
-    },
-    "subscriptionPlan": {
-      "type": "string",
-      "description": "The name or tier of the subscription plan."
-    },
-    "nextBillingDate": {
-      "type": "string",
-      "format": "date-time",
-      "description": "The date and time of the next billing or renewal."
-    },
-    "billingFrequency": {
-      "type": "string",
-      "enum": ["monthly", "yearly"],
-      "description": "The frequency of the billing cycle."
-    },
-    "amount": {
-      "type": "number",
-      "description": "The amount to be billed for the subscription."
-    },
-    "currency": {
-      "type": "string",
-      "description": "The currency in which the subscription is billed (e.g., USD, EUR)."
-    },
-    "lastPaymentDate": {
-      "type": "string",
-      "format": "date-time",
-      "description": "The date and time when the last payment was processed."
-    }
-  },
-  "required": [
-    "userId",
-    "subscriptionStatus",
-    "subscriptionPlan",
-    "nextBillingDate",
-    "billingFrequency",
-    "amount",
-    "currency",
-    "lastPaymentDate"
-  ],
-  "additionalProperties": false
-}

package/templates/default/domains/Subscriptions/ubiquitous-language.mdx

@@ -1,129 +0,0 @@
----
-dictionary:
-  - id: Subscription
-    name: Subscription
-    summary: 'A recurring agreement where a customer pays for access to a product or service at regular intervals.'
-    description: |
-      A subscription represents an ongoing relationship between customer and provider. Key aspects include:
-
-      - Subscription plan details
-      - Billing frequency
-      - Access rights and limitations
-      - Start and end dates
-      - Auto-renewal settings
-
-      Subscriptions provide predictable revenue for businesses and convenient access for customers.
-    icon: Repeat
-  - id: Billing Cycle
-    name: Billing Cycle
-    summary: 'The recurring period for which a subscription is billed.'
-    description: |
-      Billing cycles define when payments are collected and services are provided. They include:
-
-      - Cycle duration (monthly, annually, etc.)
-      - Billing date
-      - Payment due dates
-      - Pro-ration rules
-      - Grace periods
-
-      Clear billing cycles help manage customer expectations and cash flow.
-    icon: Calendar
-  - id: Plan
-    name: Plan
-    summary: 'A specific subscription offering with defined features, pricing, and terms.'
-    description: |
-      Subscription plans define the service levels available to customers. They specify:
-
-      - Feature sets and limitations
-      - Pricing structure
-      - Billing frequency options
-      - Usage allowances
-      - Additional benefits
-
-      Well-designed plans cater to different customer segments and needs.
-    icon: Layout
-  - id: Trial Period
-    name: Trial Period
-    summary: 'A promotional period allowing customers to test a subscription service before committing.'
-    description: |
-      Trial periods help customers evaluate the service risk-free. They include:
-
-      - Duration of trial
-      - Available features
-      - Conversion process
-      - Payment information requirements
-      - Trial end notifications
-
-      Effective trials can increase conversion rates to paid subscriptions.
-    icon: Clock
-  - id: Auto-Renewal
-    name: Auto-Renewal
-    summary: 'Automatic continuation of a subscription at the end of each billing period.'
-    description: |
-      Auto-renewal ensures service continuity for customers. The process includes:
-
-      - Renewal notifications
-      - Payment processing
-      - Service extension
-      - Failed payment handling
-      - Cancellation options
-
-      Auto-renewal reduces churn and maintains steady revenue streams.
-    icon: RefreshCw
-  - id: Upgrade
-    name: Upgrade
-    summary: 'The process of moving to a higher-tier subscription plan.'
-    description: |
-      Upgrades allow customers to access more features or capacity. This involves:
-
-      - Plan comparison
-      - Pro-rated billing adjustments
-      - Feature activation
-      - Data migration if needed
-      - Service level changes
-
-      Smooth upgrade processes encourage customer growth.
-    icon: ArrowUpCircle
-  - id: Downgrade
-    name: Downgrade
-    summary: 'The process of moving to a lower-tier subscription plan.'
-    description: |
-      Downgrades adjust service levels to match customer needs. This includes:
-
-      - Feature reduction
-      - Billing adjustments
-      - Data retention policies
-      - Service level changes
-      - Customer retention strategies
-
-      Flexible downgrade options can prevent complete cancellations.
-    icon: ArrowDownCircle
-  - id: Cancellation
-    name: Cancellation
-    summary: 'The termination of a subscription service.'
-    description: |
-      Cancellation processes handle the end of subscription relationships. They cover:
-
-      - Notice periods
-      - Final billing
-      - Data retention/export
-      - Service access termination
-      - Reactivation options
-
-      Clear cancellation policies protect both customer and provider interests.
-    icon: XCircle
-  - id: Usage Limit
-    name: Usage Limit
-    summary: 'Restrictions on service usage within a subscription plan.'
-    description: |
-      Usage limits define the boundaries of service consumption. They include:
-
-      - Quantitative restrictions
-      - Monitoring systems
-      - Overage handling
-      - Alert mechanisms
-      - Upgrade triggers
-
-      Well-defined limits help manage resources and encourage appropriate plan selection.
-    icon: Gauge
----

package/templates/default/teams/full-stack.mdx

@@ -1,26 +0,0 @@
----
-id: full-stack
-name: Full stackers
-summary: Full stack developers based in London, UK
-members:
-  - dboyne
-  - asmith
-  - msmith
-email: test@test.com
-slackDirectMessageUrl: https://yourteam.slack.com/channels/boyney123
----
-
-## Overview
-
-The Full Stack Team is responsible for developing and maintaining both the front-end and back-end components of our applications. This team ensures that the user interfaces are intuitive and responsive, and that the server-side logic and database interactions are efficient and secure. The Full Stack Team handles the entire lifecycle of web applications, from initial development to deployment and ongoing maintenance.
-
-## Responsibilities
-
-### Key Responsibilities
-
-- **Front-End Development**: Design and implement user interfaces using modern web technologies (e.g., HTML, CSS, JavaScript, React).
-- **Back-End Development**: Develop and maintain server-side logic, APIs, and database interactions (e.g., Node.js, Express, SQL/NoSQL databases).
-- **Integration**: Ensure seamless communication between the front-end and back-end components.
-- **Performance Optimization**: Optimize the performance and scalability of web applications.
-- **Testing and Debugging**: Write and maintain unit, integration, and end-to-end tests to ensure the quality and reliability of the applications.
-- **Deployment**: Manage the deployment of applications to production environments using CI/CD pipelines.

package/templates/default/teams/mobile-devs.mdx

@@ -1,23 +0,0 @@
----
-id: mobile-devs
-name: The mobile devs
-summary: Mobile application development team for iOS and Android platforms
-members:
-  - dboyne
----
-
-The Mobile Devs team is responsible for the development and maintenance of Acme Inc mobile applications. This includes the iOS and Android apps that customers use to interact with our services, make purchases, and manage their accounts. The team ensures that the mobile apps are user-friendly, secure, and performant.
-
-## Responsibilities
-
-### 1. Mobile Application Development
-
-- **Platform Support**: Developing and maintaining apps for iOS and Android platforms.
-- **Feature Implementation**: Implementing new features based on product requirements and user feedback.
-- **User Interface Design**: Ensuring a consistent and intuitive user interface across all mobile platforms.
-- **Performance Optimization**: Optimizing the performance of mobile apps to ensure fast and smooth user experiences.
-
-### 2. Integration with Backend Services
-
-- **API Integration**: Integrating mobile apps with backend services using RESTful APIs and other communication protocols.
-- **Real-time Updates**: Implementing real-time data updates and synchronization with backend services.

package/templates/default/users/aSmith.mdx

@@ -1,27 +0,0 @@
----
-id: asmith
-name: Amy Smith
-summary: Product Owner of the Full Stackers team
-avatarUrl: https://randomuser.me/api/portraits/women/48.jpg
-role: Product owner
----
-
-Hello! I'm Amy Smith, the Product Owner of the innovative Full Stackers team. With a strong focus on delivering exceptional value, I specialize in connecting business objectives with technical solutions to create products that users love.
-
-### About Me
-
-With a comprehensive background in product management and a solid understanding of software development, I bring a unique perspective to the table. My career has been driven by a passion for understanding user needs, defining clear product visions, and leading teams to successful product deliveries.
-
-### What I Do
-
-As the Product Owner for Full Stackers, my role involves a wide range of responsibilities aimed at ensuring our products are both high-quality and user-centric. Key aspects of my role include:
-
-- **Product Vision & Strategy**: Defining and communicating the long-term vision and strategy for our products, ensuring alignment with the company's objectives and market demands.
-- **Roadmap Planning**: Developing and maintaining a product roadmap that highlights key features and milestones, prioritizing tasks based on their business value and user feedback.
-- **Stakeholder Management**: Engaging with stakeholders across the organization to gather requirements, provide updates, and ensure everyone is aligned on the product's direction.
-- **User-Centric Design**: Championing the end-users by conducting user research, analyzing feedback, and ensuring our products effectively solve their problems.
-- **Agile Leadership**: Leading the development process using Agile methodologies, facilitating sprint planning, and ensuring the team has clear priorities and objectives.
-
-My mission is to deliver products that not only meet but exceed customer expectations. I thrive on the challenge of translating complex requirements into simple, intuitive solutions.
-
-If you’re interested in product management, user experience, or discussing the latest trends in technology, feel free to reach out!

package/templates/default/users/mSmith.mdx

@@ -1,9 +0,0 @@
----
-id: msmith
-name: Martin Smith
-summary: Senior Mobile Developer on The Mobile Devs team
-avatarUrl: 'https://randomuser.me/api/portraits/men/51.jpg'
-role: Senior software engineer
----
-
-As a Senior Mobile Developer on The Mobile Devs team, I play a key role in designing, developing, and maintaining Acme Incs mobile applications. My focus is on creating a seamless and intuitive user experience for our customers on both iOS and Android platforms. I work closely with cross-functional teams, including backend developers, UX/UI designers, and product managers, to deliver high-quality mobile solutions that meet business objectives and exceed user expectations.