Pull request #3: Added article about Backstage and it's plugins

Merge in IPCEICIS/ipceicis-developerframework from Backstage-description-and-existing-plugins to development

* commit 'edd39e938a':
  Added article about Backstage and it's plugins

content/en/docs/tools/Backstage/Exsisting Plugins/_index.md

@@ -0,0 +1,49 @@
++++
+title = "Analysis of the CNOE competitors"
+weight = 4
++++
+
+1. **Catalog**:  
+   - Used for managing services and microservices, including registration, visualization, and the ability to track dependencies and relationships between services. It serves as a central directory for all services in an organization.
+
+2. **Docs**:  
+   - Designed for creating and managing documentation, supporting formats such as Markdown. It helps teams organize and access technical and non-technical documentation in a unified interface.
+
+3. **API Docs**:  
+   - Automatically generates API documentation based on OpenAPI specifications or other API definitions, ensuring that your API information is always up to date and accessible for developers.
+
+4. **TechDocs**:  
+   - A tool for creating and publishing technical documentation. It is integrated directly into Backstage, allowing developers to host and maintain documentation alongside their projects.
+
+5. **Scaffolder**:  
+   - Allows the rapid creation of new projects based on predefined templates, making it easier to deploy services or infrastructure with consistent best practices.
+
+6. **CI/CD**:  
+   - Provides integration with CI/CD systems such as GitHub Actions and Jenkins, allowing developers to view build status, logs, and pipelines directly in Backstage.
+
+7. **Metrics**:  
+   - Offers the ability to monitor and visualize performance metrics for applications, helping teams to keep track of key indicators like response times and error rates.
+
+8. **Snyk**:  
+   - Used for dependency security analysis, scanning your codebase for vulnerabilities and helping to manage any potential security risks in third-party libraries.
+
+9. **SonarQube**:  
+   - Integrates with SonarQube to analyze code quality, providing insights into code health, including issues like technical debt, bugs, and security vulnerabilities.
+
+10. **GitHub**:  
+   - Enables integration with GitHub repositories, displaying information such as commits, pull requests, and other repository activity, making collaboration more transparent and efficient.
+
+11. **CircleCI**:  
+   - Allows seamless integration with CircleCI for managing CI/CD workflows, giving developers insight into build pipelines, test results, and deployment statuses.
+
+12. **Kubernetes**:  
+   - Provides tools to manage Kubernetes clusters, including visualizing pod status, logs, and cluster health, helping teams maintain and troubleshoot their cloud-native applications.
+
+13. **Cloud**:  
+   - Includes plugins for integration with cloud providers like AWS and Azure, allowing teams to manage cloud infrastructure, services, and billing directly from Backstage.
+
+14. **OpenTelemetry**:  
+   - Helps with monitoring distributed applications by integrating OpenTelemetry, offering powerful tools to trace requests, detect performance bottlenecks, and ensure application health.
+
+15. **Lighthouse**:  
+   - Integrates Google Lighthouse to analyze web application performance, helping teams identify areas for improvement in metrics like load times, accessibility, and SEO.

content/en/docs/tools/Backstage/General Information/_index.md

@@ -0,0 +1,24 @@
++++
+title = "Backstage Description"
+weight = 4
++++
+
+Backstage by Spotify can be seen as a Platform Portal. It is an open platform for building and managing internal developer tools, providing a unified interface for accessing various tools and resources within an organization.
+
+Key Features of Backstage as a Platform Portal:
+Tool Integration:
+
+Backstage allows for the integration of various tools used in the development process, such as CI/CD, version control systems, monitoring, and others, into a single interface.
+Service Management:
+
+It offers the ability to register and manage services and microservices, as well as monitor their status and performance.
+Documentation and Learning Materials:
+
+Backstage includes capabilities for storing and organizing documentation, making it easier for developers to access information.
+Golden Paths:
+
+Backstage supports the concept of "Golden Paths," enabling teams to follow recommended practices for development and tool usage.
+Modularity and Extensibility:
+
+The platform allows for the creation of plugins, enabling users to customize and extend Backstage's functionality to fit their organization's needs.
+Backstage provides developers with centralized and convenient access to essential tools and resources, making it an effective solution for supporting Platform Engineering and developing an internal platform portal.

content/en/docs/tools/Backstage/_index.md

@@ -0,0 +1,9 @@
++++
+title = "Backstage"
+weight = 4
+[params]
+    author = 'evgenii.dominov@telekom.de'
+    date = '2024-09-36'
++++
+
+Here you will find information about Backstage, it's plugins and usage tutorials

content/en/docs/tools/CNOE-competitors/_index.md

@@ -18,10 +18,6 @@ Kratix simplifies the development and delivery of applications by automating the
 ### Pros of Kratix:
 - Resource provisioning automation. Kratix simplifies infrastructure creation for developers through the abstraction of "Promises." This means developers can simply request the necessary resources (like databases, message queues) without dealing with the intricacies of infrastructure management.
 
-- Kubernetes support. Kratix operates on top of Kubernetes, making it compatible with popular containerization ecosystems. This means it easily integrates with existing Kubernetes clusters, expanding their functionality.
-
-- Scalability. Like Kubernetes, Kratix is scalable and can be used both in small teams and in large organizations with distributed systems.
-
 - Flexibility and adaptability. Platform teams can customize and adapt Kratix to specific needs by creating custom Promises for various services, allowing the infrastructure to meet the specific requirements of the organization.
 
 - Unified resource request interface. Developers can use a single API (Kubernetes) to request resources, simplifying interaction with infrastructure and reducing complexity when working with different tools and systems.