docs(faq): add CI/CD guide and improve CD explanation

- Added detailed CI/CD guide with benefits, components, and challenges.
- Fixed formatting in Continuous Delivery FAQ for better readability.

Author: mahatmamahardhikach

pages/faq/software_development/server/what_is_ci_cd.md

@@ -0,0 +1,87 @@
+---
+layout: default
+title: What is CI/CD?
+parent: What is a Server?
+grand_parent: Software Development
+description: "What is CI/CD?"
+---
+
+# What is CI/CD?
+
+## Table of Contents
+
+- [Introduction](#introduction)
+- [Definition of CI/CD](#definition-of-ci-cd)
+- [How CI/CD Works](#how-ci-cd-works)
+- [Benefits of CI/CD](#benefits-of-ci-cd)
+- [Key Components of CI/CD Pipelines](#key-components-of-ci-cd-pipelines)
+- [Challenges in CI/CD Implementation](#challenges-in-ci-cd-implementation)
+- [Best Practices for CI/CD](#best-practices-for-ci-cd)
+- [Conclusion](#conclusion)
+
+## Introduction
+
+In the fast-paced world of software development, delivering high-quality applications efficiently and consistently is
+paramount. **CI/CD**, which stands for Continuous Integration and Continuous Delivery/Deployment, is a methodology that
+addresses this need by automating the processes of integration, testing, and deployment.
+
+## Definition of CI/CD
+
+**Continuous Integration (CI)** is a practice where developers frequently merge code changes into a shared repository,
+followed by automated testing and builds.
+
+**Continuous Delivery (CD)** extends CI by automating the release process, ensuring that the codebase is always ready
+for deployment.
+
+**Continuous Deployment** is a further step where every change that passes automated tests is automatically deployed to
+production without manual intervention.
+
+Together, CI/CD represents a streamlined approach to building, testing, and releasing software.
+
+## How CI/CD Works
+
+1. **Code Commit**: Developers push code changes to a version control system (e.g., Git).
+2. **Automated Build**: CI tools compile the application to verify that the code integrates seamlessly.
+3. **Automated Testing**: Various tests (unit, integration, performance) are executed to validate code changes.
+4. **Release to Staging**: CD pipelines deploy the application to a staging environment for further validation.
+5. **Production Deployment**: The application is released to production, either manually (Continuous Delivery) or
+   automatically (Continuous Deployment).
+
+## Benefits of CI/CD
+
+- **Faster Development Cycles**: Speeds up the process of delivering features and updates.
+- **Improved Quality**: Automated testing ensures that only validated code reaches production.
+- **Reduced Risk**: Incremental updates lower the chance of deployment failures.
+- **Enhanced Collaboration**: Encourages teamwork between development, testing, and operations teams.
+- **Streamlined Processes**: Eliminates manual steps, reducing errors and delays.
+
+## Key Components of CI/CD Pipelines
+
+- **Version Control System**: Tools like Git to manage and track code changes.
+- **Build Automation**: Tools like Jenkins or GitLab CI/CD to compile the application.
+- **Testing Frameworks**: Suites for unit, integration, and performance testing.
+- **Deployment Automation**: Scripts or tools for deploying applications (e.g., Kubernetes, Docker).
+- **Monitoring Tools**: Systems to track performance and detect issues post-deployment.
+
+## Challenges in CI/CD Implementation
+
+- **Complex Setup**: Designing effective pipelines can be time-intensive.
+- **Test Maintenance**: Keeping tests updated with evolving code is essential.
+- **Cultural Adaptation**: Teams may resist transitioning to automated workflows.
+- **Resource Costs**: CI/CD tools and environments can require significant investments.
+
+## Best Practices for CI/CD
+
+- **Automate Tests**: Ensure comprehensive test coverage for all stages of the pipeline.
+- **Commit Often**: Smaller, frequent updates reduce the risk of conflicts and errors.
+- **Monitor Pipelines**: Regularly review logs and performance metrics to identify bottlenecks.
+- **Use Feature Toggles**: Enable incremental feature rollouts without affecting the main codebase.
+- **Foster Collaboration**: Encourage open communication between development, QA, and operations teams.
+
+## Conclusion
+
+CI/CD is a cornerstone of modern software development, enabling teams to deliver high-quality applications faster and
+more reliably. By automating the integration, testing, and deployment processes, CI/CD reduces manual effort and
+enhances the overall development workflow. While challenges exist, adopting best practices ensures successful
+implementation and maximizes the benefits of CI/CD pipelines.
+

pages/faq/software_development/server/what_is_continuous_delivery.md

@@ -21,8 +21,8 @@ description: "What is Continuous Delivery?"
 
 ## Introduction
 
-As software development evolves, the need for faster and more reliable delivery processes becomes essential. *
-*Continuous Delivery (CD)** ensures that code changes are automatically prepared for deployment, streamlining the path
+As software development evolves, the need for faster and more reliable delivery processes becomes essential.
+**Continuous Delivery (CD)** ensures that code changes are automatically prepared for deployment, streamlining the path
 from development to production.
 
 ## Definition of Continuous Delivery