First blog stable version

.github/workflows/deploy.yml

@@ -0,0 +1,39 @@
+name: Deploy to GitHub Pages
+
+on:
+  push:
+    branches:
+      - main
+    # Review gh actions docs if you want to further define triggers, paths, etc
+    # https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#on
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+jobs:
+  deploy:
+    name: Deploy to GitHub Pages
+    runs-on: ubuntu-latest
+    environment:
+      name: github-pages
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 18
+          cache: npm
+
+      - name: Install dependencies
+        run: npm ci
+      - name: Build website
+        run: npm run build
+
+      - name: Set build folder as artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          name: github-pages
+          path: ./build
+
+      - uses: actions/deploy-pages@v4

.gitignore

@@ -0,0 +1,20 @@
+# Dependencies
+/node_modules
+
+# Production
+/build
+
+# Generated files
+.docusaurus
+.cache-loader
+
+# Misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

README.md

@@ -0,0 +1,41 @@
+# Website
+
+This website is built using [Docusaurus](https://docusaurus.io/), a modern static website generator.
+
+### Installation
+
+```
+$ yarn
+```
+
+### Local Development
+
+```
+$ yarn start
+```
+
+This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
+
+### Build
+
+```
+$ yarn build
+```
+
+This command generates static content into the `build` directory and can be served using any static contents hosting service.
+
+### Deployment
+
+Using SSH:
+
+```
+$ USE_SSH=true yarn deploy
+```
+
+Not using SSH:
+
+```
+$ GIT_USER=<Your GitHub username> yarn deploy
+```
+
+If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the `gh-pages` branch.

babel.config.js

@@ -0,0 +1,3 @@
+module.exports = {
+  presets: [require.resolve('@docusaurus/core/lib/babel/preset')],
+};

blog/2023-12-19-resizes-mission.md

@@ -0,0 +1,26 @@
+---
+slug: resizes-mission
+title: Resizes Mission
+authors: alex
+tags: [DevOps, PlatformEngineering, CloudNative, DeveloperExperience, Innovation]
+---
+
+🚀 Embracing DevOps and Platform Engineering for Modern Businesses 🚀
+
+In the ever-evolving tech landscape, DevOps is more alive than ever. At Resizes, we're harnessing the power of DevOps methodologies and best practices to revolutionize Internal Developer Platforms (IDPs) and implement Platform Engineering across companies of all sizes.
+
+<!--truncate-->
+
+🔑 Our goal? To fulfill the original DevOps promise: “you build it, you run it”.
+
+💡 Enhancing Developer Experience with Cloud Native Tech: With the latest in Cloud Native technologies, we're here to dramatically improve your Developer Experience (DevEx). Our approach ensures that your development teams are not bogged down by repetitive tasks, fostering high performance and reducing dependency on Ops teams.
+
+🌟 The Secret to High-Performing Teams? Teams that excel have one thing in common: they've built an Internal Developer Platform that's pivotal to their DevOps success. These platforms not only boost developer experience and productivity but also utilize a blend of open-source and proprietary tools, treating the platform as a critical product.
+
+🛠️ Build or Be Built: Remember, if you don't proactively build your platform, it will inevitably build itself. The real question is whether you standardize this process or leave it to chance.
+
+📊 DORA Metrics in Focus: We're keeping a keen eye on key DORA metrics like deployment frequency, change lead time, change failure rate, and MTTR (service production restoration time) to ensure peak performance.
+
+📦 Containerization: The Scale Game-Changer: In our journey, containerization has emerged as the essential element for scaling apps efficiently.
+
+Join us at Resizes in shaping the future of DevOps and Platform Engineering. Let's create systems that not only work but excel in the modern digital era.

blog/2023-12-26-idp-and-platform-engineering.md

@@ -0,0 +1,28 @@
+---
+slug: idp-and-platform-engineering
+title: IDPs and Platform Engineering
+authors: rober
+tags: [PlatformEngineering, InternalDeveloperPlatforms, TechInnovation, SoftwareDevelopment, DigitalTransformation, DevOps]
+---
+
+🚀 Embracing Innovation in Tech: The Power of Platform Engineering and Internal Developer Platforms (IDPs) 🌟
+
+In the rapidly evolving landscape of technology, two game-changers have emerged as key players: Platform Engineering and Internal Developer Platforms (IDPs). These innovative approaches are reshaping how we build, deploy, and manage software. Let's dive into their transformative benefits:
+
+- Streamlined Development Process: IDPs provide a unified platform for development teams, significantly reducing the complexity involved in software creation. This streamlined approach accelerates development cycles, enabling quicker deployment and faster time-to-market.
+
+<!--truncate-->
+
+- Enhanced Collaboration: Platform Engineering fosters a collaborative environment where developers, operations teams, and other stakeholders can work seamlessly together. This synergy not only boosts productivity but also enhances the quality of the end product.
+
+- Scalability and Flexibility: With the scalability offered by Platform Engineering, businesses can effortlessly adapt to changing demands. IDPs complement this by offering flexible tools that cater to various development needs, ensuring that scalability does not compromise performance.
+
+- Consistency and Standardization: IDPs establish standardized processes and toolsets across projects, leading to consistency in development practices. This uniformity is crucial for maintaining quality and reliability in software products.
+
+- Empowering Developers: By abstracting away the complexities of infrastructure management, IDPs allow developers to focus on what they do best – coding. This empowerment leads to higher job satisfaction and increased innovation.
+
+- Cost-Effective Solutions: Platform Engineering can lead to significant cost savings by optimizing resource utilization and reducing the overhead associated with managing disparate systems and tools.
+
+- Enhanced Security and Compliance: With a centralized platform, enforcing security protocols and compliance standards becomes more manageable, ensuring that all development activities adhere to the highest security norms.
+
+🌐 Looking Ahead: As we embrace these technologies, the potential for innovation is boundless. Platform Engineering and IDPs are not just tools; they represent a paradigm shift in how we approach software development, promising a future of efficiency, collaboration, and excellence in technology.

blog/2024-01-03-cicd-oidc.mdx

@@ -0,0 +1,54 @@
+---
+slug: cicd-oidc
+title: CI/CD with OIDC
+authors: [resizes]
+tags: [CI/CD, OIDC, GitHub, GitLab, Terraform, AWS, Security]
+---
+
+🚀 Leveraging OIDC for Enhanced Security and Efficiency Between GitHub Actions/GitLab CI and AWS 🔒
+
+In the rapidly evolving landscape of DevOps and cloud computing, the integration of GitHub Actions or GitLab CI with AWS using OpenID Connect (OIDC) stands out as a game changer. Here's why embracing OIDC can significantly benefit your CI/CD pipelines:
+
+<!--truncate-->
+
+1. Enhanced Security: OIDC eliminates the need to store long-lived credentials like AWS access keys in your GitHub or GitLab repositories. This reduces the risk of credential leakage and enhances the overall security of your deployment processes.
+
+2. Seamless Identity Federation: OIDC allows AWS to trust GitHub Actions or GitLab CI to authenticate users, streamlining the identity verification process. This simplifies user management and ensures a more secure and efficient authentication mechanism.
+
+3. Automated Role Assumption: With OIDC, specific AWS roles can be assumed directly in GitHub Actions or GitLab CI pipelines. This facilitates granular permission control and ensures that only necessary permissions are granted for each task, enhancing both security and compliance, following the principle of least privilege.
+
+4. Scalability and Flexibility: OIDC enables a more scalable and flexible approach to managing cloud resources. As your project grows, it's easy to update and manage permissions without altering the underlying infrastructure.
+
+5. Cost-Effective: By leveraging OIDC, there's a reduction in the management overhead associated with credential rotation and management, potentially leading to cost savings and reduced operational complexity.
+
+🔗 Integrating OIDC with your CI/CD pipelines in GitHub Actions or GitLab CI not only fortifies your security posture but also streamlines your operational workflows. It's a win-win for teams looking to enhance their cloud capabilities in a secure and efficient manner.
+
+:::info Official Documentation
+
+- [GitHub Actions OIDC Integration](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services)
+- [GitLab CI OIDC Integration](https://docs.gitlab.com/ee/ci/cloud_services/aws)
+
+:::
+
+Note that other cloud providers like Azure or GCP have also OIDC integrations with GitHub Actions or GitLab CI. And other CI/CD tools like Azure DevOps may have OIDC integrations with cloud providers. Find your best combination!
+
+If you are using GitHub Actions and AWS, you can use our [open sourced Terraform module](https://github.com/resizes/platform-terraform-module-github-oidc-aws-role) to create IAM related resources and handle permissions for different branches or tags:
+
+```terraform
+module "github-oidc-aws-role" {
+  source            = "github.com/resizes/platform-terraform-module-github-oidc-aws-role?ref=main"
+  name              = ${ROLE_NAME}
+  org_name          = ${ORG_NAME}
+  condition_test    = ${CONDITION_TEST}
+  actions = [ ${ALLOWED_ACTIONS} ]
+  assume_role_policy_condition_values = [
+    "repo:${ORG_NAME}/${REPO}:ref:refs/heads/${BRANCH}",
+    "repo:${ORG_NAME}/${REPO}:ref:refs/tags/${TAG}"
+  ]
+}
+```
+
+If you like our repository, please give us a star ⭐️ and follow us on [GitHub](httos://github.com/resizes)!
+
+<iframe src="https://ghbtns.com/github-btn.html?user=resizes&repo=platform-terraform-module-github-oidc-aws-role&type=star&count=true&size=large" frameborder="0" scrolling="0" width="170" height="30" title="GitHub"></iframe>
+<iframe src="https://ghbtns.com/github-btn.html?user=resizes&type=follow&count=true&size=large" frameborder="0" scrolling="0" width="230" height="30" title="GitHub"></iframe>

blog/2024-01-10-dora-metrics/index.md

@@ -0,0 +1,26 @@
+---
+slug: dora-metrics
+title: DORA Metrics
+authors: [rober, alex]
+tags: [DevOps, DORAMetrics, PerformanceOptimization, Automation, PerformanceEngineering, PlatformEngineering]
+---
+
+📌 Elevate your team's performance with DORA Metrics! 📊 
+
+Unlock insights into lead time, deployment frequency, mean time to recovery and change failure rate. Learn how to optimize your DevOps practices for success. 💡
+
+![Dora Metrics](./dora-1.png)
+
+<!--truncate-->
+
+![Lead Time For Changes](./dora-2.png)
+
+![Deployment Frequency](./dora-3.png)
+
+![Mean Time To Recovery](./dora-4.png)
+
+![Change Failure Rate](./dora-5.png)
+
+![Dora Metrics](./dora-6.png)
+
+🚀 DORA Metrics: The Key to DevOps Success 🚀