adds first blog post

.gitignore

@@ -18,3 +18,5 @@
 npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
+
+.obsidian

docs/platform_enjineering.md → blog/2024-07-04-platform-engineering.md

@@ -1,19 +1,18 @@
 ---
-slug: platform_engineering
-title: Platform Engineering
-sidebar_label: Platform Engineering
-sidebar_position: 1
+slug: platform-engineering-developer-bottlenecks
+title: Platform Engineering and Solving Developer Bottlenecks
+authors: [mojtaba]
+tags: [kuberise, platformengineering]
 ---
 
-## What are the problems that platform engineering and internal developer platform is going to solve? 
+## What are the problems that platform engineering and internal developer platform is going to solve?
 
 - Developers often spend a significant portion of their time on peripheral tasks instead of focusing on their core software development. These tasks can include setting up databases, configuring identity and access management, managing image repositories, implementing security measures, networking, etc. An internal developer platform automates these processes, allowing developers to concentrate on writing code that adds direct value to their projects.
 
 - Developers are experts in programming, not necessarily in database management, networking, or identity and access services. When developers handle these side services, it often leads to issues, such as opening unwanted internet access or improperly setting up database backups and recovery. An internal developer platform standardizes and secures these services, reducing the risk of such errors.
 
--  Development teams within an organization may use different tools and methodologies, which complicates coordination and collaboration between groups. It also makes it challenging for infrastructure teams to support these varied environments efficiently. For example, different programming teams might use their preferred tools for automating software pipelines or different databases. An internal developer platform provides a unified set of tools and technologies, enhancing consistency and interoperability across teams.
+- Development teams within an organization may use different tools and methodologies, which complicates coordination and collaboration between groups. It also makes it challenging for infrastructure teams to support these varied environments efficiently. For example, different programming teams might use their preferred tools for automating software pipelines or different databases. An internal developer platform provides a unified set of tools and technologies, enhancing consistency and interoperability across teams.
 
 - Frequently, different software groups in a company need to contact the infrastructure team for their requirements, such as server access, networking, permissions, and storage. This demand is particularly burdensome in large companies, slowing down operations and overwhelming the infrastructure team with requests. An internal developer platform can streamline these requests by offering self-service capabilities and automating common infrastructure provisioning tasks, thereby accelerating development cycles and reducing bottlenecks.
 
-
 By centralizing and standardizing development tools and processes, an internal developer platform not only improves efficiency but also enhances security, reduces operational risks, and promotes a more collaborative and agile development environment.

blog/tags.yml

@@ -1,12 +1,16 @@
 kuberise:
   label: kuberise
   permalink: /kuberise
-  description: kuberise idp platform
+  description: Kuberise Internal Developer Platform
 idp:
   label: idp
   permalink: /idp
   description: Internal Developer Platform
 kubernetes:
   label: kubernetes
   permalink: /kubernetes
-  description: kubernetes platform
+  description: Kubernetes Platform
+platformengineering:
+  label: platformengineering
+  permalink: /platformengineering
+  description: Platform Engineering

docs/01.intro.md

@@ -0,0 +1,40 @@
+---
+slug: intro
+title: Intro
+sidebar_label: Intro
+sidebar_position: 1
+---
+
+![kuberise logo](../static/img/docs_images/full-logo.svg)
+# kuberise.io
+
+kuberise.io is a free open source internal developer platform for Kubernetes environment. The goal is to provide tools and templates in Kubernetes environment by a fast and easy installation to help developers focus on the development of the business applications rather than installation and configuration of side tools and preparations of the environments and automation.
+
+## Prerequisites
+
+- CLI tools: kubectl, helm, htpasswd, git, openssl
+- A Github account or another git repository system
+- [K9s](https://k9scli.io/topics/install/) for dashboard (recommended)
+- A [kind](https://kind.sigs.k8s.io/docs/user/quick-start#installation) kubernetes cluster for local installation (`kind create cluster`) or any other kubernetes cluster
+- [cloud-provider-kind](https://github.com/kubernetes-sigs/cloud-provider-kind) for loadBalancer services and ingresses in kind cluster.
+
+## Installation
+
+1. Fork this repository [https://github.com/kuberise/kuberise.io](https://github.com/kuberise/kuberise.io) into your Github account.
+2. Clone your new repository in your local computer and enter to the folder.
+3. Run this command:
+```bash
+./scripts/install.sh [CONTEXT] [NAME] [REPO_URL] [REVISION] [DOMAIN] [TOKEN]
+```
+- [CONTEXT] This is your kubernetes context. You can find your current kubernetes context by running this command: `kubectl config current-context`
+- [NAME] This is the name of your platform. For this name there should be a values-[NAME].yaml in app-of-apps folder and also a [NAME] folder in values folder for all configurations.
+- [REPO_URL] This is the url of your forked repository.
+- [REVISION] This is the branch or commit sha or tag of the commit that you want to use for this installation. For example you can write "main" to deploy from the main branch. 
+- [DOMAIN] This is the domain for the cluster. All platform services and applications would be subdomain of this domain, for example: keycloak.[DOMAIN]. If you are deploying into minikube you can choose minikube.kuberise.dev for the domain then your keycloak address would be keycloak.minikube.kuberise.dev
+- [TOKEN] If you are pushing this code to a private repository, you have to put a token here so the ArgoCD can access your repository. If your repository is public, skip this parameter. 
+
+Example: If you deployed a kubernetes cluster using `minikube start` and your platform name is `local-example` then this would be the installation command: 
+```bash 
+./scripts/install.sh minikube local-example https://github.com/kuberise/kuberise.git main minikube.kuberise.dev
+```
+