fix headlines order for better accessibility and seo.

Author: nisarhassan12

src/blog/bitbucket.md

@@ -13,7 +13,7 @@ Simply type `gitpod.io/#` in front of any Bitbucket repository URL, and get a fu
 
 `youtube: hIpFTGwsv-o`
 
-# Getting Started with Gitpod for Bitbucket
+<h2 class="h1">Getting Started with Gitpod for Bitbucket</h2>
 
 Starting a fresh dev environment for a Bitbucket project works just as with GitLab and GitHub: Simply prefix your Bitbucket project URL with `gitpod.io/#`.
 
@@ -47,15 +47,15 @@ The new local branch will be named like `<username>/<issue-title>-<issue-nr>`, i
 
 ![GitLab Issue Context](./gitlab-support/gitlab-issue-context-status.png)
 
-## Configure your project
+<h3 class="h2">Configure your project</h3>
 
 To get the most out of Gitpod, you should describe your project's dev environment with code. Dev environments are based on containers which you can configure through a custom `Dockerfile`.
 
 Furthermore you can specify which tasks should run after a fresh checkout in a `.gitpod.yml` file. Usually these tasks include build steps, downloading dependencies and running some unit tests. Read the section below on prebuilds to make Gitpod automatically run these steps ahead of time, as a CI pipeline whenever some changes are pushed to your project.
 
 There is much more you can do to make sure every team member gets a ready-to-code dev environment when they need one. Please refer to the [docs](/docs/configuration/) for details.
 
-## Prebuilds
+<h3 class="h2">Prebuilds</h3>
 
 Gitpod’s [prebuilt workspaces](/docs/prebuilds/) are key to providing ephemeral, ready-to-code dev environments for your branches and projects. You can configure Gitpod to run your project's build asynchronously every time someone pushes new commits or branches to your repository. So when a developer wants to start coding, she can start immediately, because everything is already prepared.
 

src/blog/build-a-webhook-for-google-assistant.md

@@ -142,5 +142,5 @@ Refer to the links below to add your own functionalities.
 Gitpod can make your life much simpler by automating your development setup just by adding a simple configuration file to your repo. You can refer to the Gitpod [Docs](https://www.gitpod.io/docs/) to learn more about the platform. Gitpod lets you work with unlimited workspace but with 100hrs/month runtime. It also provides Personal and unlimited plans as well. If you are a student then you can claim Gitpod Unlimited plan for just $9.
 
 ![Animated character waving hand with a smile](https://res-3.cloudinary.com/anudeepc/image/upload/q_auto/v1/blog-images/character.gif)
-# Happy coding with Gitpod ✨
+<h1>Happy coding with Gitpod ✨</h1>
 

src/blog/docker-in-gitpod.md

@@ -13,7 +13,7 @@ Since we released Gitpod into Public Beta it has been incredibly exciting to see
 
 Of course, there is always room for improvement, especially with a service as new as Gitpod. Luckily, people have started to share their questions and ideas with us on [https://github.com/gitpod-io/gitpod](https://github.com/gitpod-io/gitpod). One of the most often asked questions was:
 
-### “How do I add tool XYZ to my workspace?”
+<h2 class="h3">“How do I add tool XYZ to my workspace?”</h2>
 
 And indeed that hasn’t been straight forward. You had to:
 
@@ -33,7 +33,7 @@ And indeed that hasn’t been straight forward. You had to:
 
 That was way too tedious for everyone to start playing around.
 
-### Let Gitpod do the heavy lifting
+<h2 class="h3">Let Gitpod do the heavy lifting</h2>
 
 To improve this experience we introduced[ Dockerfile support (#62)](https://github.com/gitpod-io/gitpod/issues/62), which lets you reference your Dockerfile directly from inside your .gitpod.yml file:
 
@@ -42,7 +42,7 @@ To improve this experience we introduced[ Dockerfile support (#62)](https://gith
 
 Now, Gitpod knows about the Dockerfile and builds that image for you. Whenever you access the repository on Gitpod it checks whether the Dockerfile has been updated and rebuilds the image if needed. When this happens you’ll be shown the log output of the build for easier debugging, too.
 
-### An example, please!
+<h2 class="h3">An example, please!</h2>
 
 Let’s get concrete. As an exercise we’ll use [a minimal REST service](https://github.com/lankydan/rust-web-with-rocket) written in[ Rust](https://www.rust-lang.org/) using Rocket and Diesel that talks to a PostgreSQL DB. It also has a nice[ blog post](https://lankydanblog.com/2018/05/20/creating-a-rusty-rocket-fuelled-with-diesel/) to get started.
 

src/blog/github-codespaces.md

@@ -9,7 +9,7 @@ Today, GitHub announced the private beta of [GitHub Codespaces](https://github.c
 
 This is great news, because it really helps to explain why this is going to change professional software development entirely.
 
-### Dev Environment As Code
+<h2 class="h3">Dev Environment As Code</h2>
 
 Describing development environments in code has many benefits:
 
@@ -23,7 +23,7 @@ Describing development environments in code has many benefits:
 
 It is our vision that **everybody can immediately start working in a fully set-up dev environment on any project, any branch, with any device, and at any time.**
 
-### A Lifesaver for Professional Teams
+<h2 class="h3">A Lifesaver for Professional Teams</h2>
 
 As software systems become more complex so do dev environments. Have you ever tried to develop a Kubernetes application locally, set up all the required infrastructure, and launch all microservices on your local machine? Halfway through you’ll find that your expensive MacBook Pro is not a suitable replacement for a datacenter. Even if you eventually manage to get things working it won’t be smooth or remotely close to what you run in production.
 
@@ -33,13 +33,13 @@ For the past year the whole team has developed Gitpod in Gitpod. Everyone in the
 
 `youtube: dFMpXUsJcGM`
 
-### Pre-build Everything!
+<h2 class="h3">Pre-build Everything!</h2>
 
 When reviewing a PR or starting work on that new cool feature, no developer wants to accidentally work with an old state. Imagine wasting hours hunting a bug that’s already fixed on master. Fresh working copies—and ideally dev environments—for each task would be great.
 
 Once dev environments have become code you can pre-build those dev environments ahead of time. **Think CI for your development setup**: on each change in the repository, Gitpod prepares a new dev environment for that change. Rather than having to manually adjust the tool versions, wait for all dependencies to download and for the code to compile, things are ready when you are. We call this [continuous dev environments](/blog/continuous-dev-environment-in-devops/).
 
-### At Last a Good Browser IDE
+<h2 class="h3">At Last a Good Browser IDE</h2>
 
 Given all these benefits, you might wonder why no one did this earlier. After all, developers automate the world on a daily basis. Thinking about it, it’s strange that most developers still set things up manually before they can get down to business.
 
@@ -54,23 +54,23 @@ This new generation of Theia-based Web-IDEs go way beyond online-playgrounds whi
 <sub>*) To avoid misunderstandings: Theia has technically nothing in common with the classic Eclipse IDE, but is an independent project under the umbrella of the Eclipse Foundation.</sub>
 
 
-### What About GitLab, Atlassian’s Bitbucket, and Other Git Hosting?
+<h2 class="h3">What About GitLab, Atlassian’s Bitbucket, and Other Git Hosting?</h2>
 
 We are thrilled to see GitHub/Microsoft investing in automated development environments as it will help convince developers around the world and get this new way of developing software adopted faster.
 
 But most professional development happens on other platforms such as GitLab, Atlassian’s stack and of course good old GitWeb. Oftentimes companies even employ a mixture of these.
 
 To also serve users beyond just GitHub, we have been focussing on integrating Gitpod with other platforms as well. In December we released support for GitLab, and integration with Atlassian’s Bitbucket (and Jira) will be available soon.
 
-### Closer to Home: Gitpod Self-Hosted
+<h2 class="h3">Closer to Home: Gitpod Self-Hosted</h2>
 
 Chances are that you host your Git repositories or other dev infrastructure in a private cloud, or on a local network where they can't be accessed from the outside. Thus, a hosted IDE service must be on the same private cloud or network. This is possible with [Gitpod Self-Hosted](/self-hosted/) which can be installed on Kubernetes and does not require a connection to the public internet.
 
 Today we are releasing a new version which brings Gitpod Self-Hosted on par with Gitpod.io. The new release includes better GitLab integration and a new admin UI. With Gitpod Self-Hosted you can now enjoy this liberating way of developing software with your own GitLab installation.
 
 **Gitpod Self-Hosted is free for up to five users, and a free trial month for unlimited users is available, too.**
 
-### Summary
+<h2 class="h3">Summary</h2>
 
 We are quickly headed into a wonderful future, where developers are no longer intimidated by tedious and outdated setup procedures. Professional software projects will provide automated, prebuilt development environments that enable teams to start contributing, doing code reviews, reproducing bugs or just exploring new ideas immediately from any device securely.
 

src/blog/gitlab-integration.md

@@ -11,7 +11,7 @@ At Gitpod we want to make developers’ lives easier. Starting automated dev env
 Recently we asked ourselves how we could streamline the integration with your daily routine even more. Today, we are super excited to share that we’ve partnered with GitLab and built a [native Gitpod integration in GitLab’s UI](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/37985).
 
 
-# The last missing piece in your GitLab DevOps pipeline
+<h2 class="h1">The last missing piece in your GitLab DevOps pipeline</h2>
 
 GitLab is one of the most popular DevOps tools/platforms out there, used by more than 100,000 organizations across the globe. Through its Web IDE, simple edits can already be made today from within the application. However, for more advanced programming tasks, developers require a full development environment.
 
@@ -26,7 +26,7 @@ GitLab and Gitpod started a partnership to bring Gitpod's ready-to-code dev envi
 ![Gitpod button on GitLab project page](/gitlab-integration/gitpod-button-on-gitlab.png)
 
 
-# “Everyone can contribute”
+<h2 class="h1">“Everyone can contribute”</h2>
 
 GitLab’s credo “Everyone can contribute” is a perfect fit for Gitpod because contributing becomes much simpler when you allow anyone to spin up a ready-to-code development environment in a few seconds.
 
@@ -37,21 +37,21 @@ We are currently helping the GitLab team [to build a fully-automated Gitpod conf
 [![GitLab integration quote](/gitlab-integration/gitlab-integration-quote.png)](https://gitlab.com/gitlab-org/gitlab-development-kit/-/issues/1076#note_419638250)
 
 
-# Hook up your GitLab Self-Managed with Gitpod.io
+<h2 class="h1">Hook up your GitLab Self-Managed with Gitpod.io</h2>
 
 The Gitpod integration is already live on gitlab.com today and is going to be part of [GitLab&nbsp;13.5](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/61933) which is released on October 22nd. At that point, you’ll be able to connect your GitLab self-managed installation to gitpod.io, through a new feature that lets you register additional Git providers.
 
 Furthermore, you can [self-host Gitpod](https://www.gitpod.io/self-hosted/) (which is [open source](https://github.com/gitpod-io/gitpod)) on your own Kubernetes cluster and configure it with your GitLab instance. We have convenient installation scripts for GCP and AWS.
 
 
-# What’s next?
+<h2 class="h1">What’s next?</h2>
 
 We are continuously working on improving the GitLab integration and implementing new features for GitLab users (e.g. managing merge requests within Gitpod, [adding a Gitpod button on Merge Requests](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/43352), etc.). You can also install the [GitLab VS Code Extension](https://open-vsx.org/extension/GitLab/gitlab-workflow) in Gitpod to interact with GitLab. Just go to the Extensions view (in the left vertical menu), search for “GitLab” and choose “Install”.
 
 ![Gitpod button on GitLab project page](/gitlab-integration/gitlab-vscode-extension.png)
 
 
-# Try the Gitpod integration now!
+<h2 class="h1">Try the Gitpod integration now!</h2>
 
 The GitLab integration is available at GitLab.com and in your [self-managed GitLab](https://gitlab.com/help/integration/gitpod.md) soon. Don’t have a project at hand? Try the demo project [Spring PetClinic](https://gitlab.com/gitpod/spring-petclinic) which has a proper Gitpod configuration committed.
 

src/blog/gitlab-support.md

@@ -10,7 +10,7 @@ We are happy to announce that you can finally enjoy Gitpod's frictionless ready-
 
 ![gitpod loves gitlab](./gitlab-support/teaser-gitlab-gitpod.jpg)
 
-# Getting Started with GitLab and Gitpod
+<h2 class="h1">Getting Started with GitLab and Gitpod</h2>
 
 Starting a dev environment for a GitLab project works just as with GitHub, i.e. you prefix any GitLab project URL with `gitpod.io/#`.
 

src/blog/gitpod-self-hosted-0.4.0.md

@@ -8,7 +8,7 @@ teaserImage: /cloud-download.png
 ---
 We are excited to announce the new release of Gitpod Self-Hosted in version 0.4.0. Gitpod Self-Hosted allows everyone to set-up and run  a service with the same features as gitpod.io in your cloud or corporate network.
 
-### How Does it Work?
+<h2 class="h3">How Does it Work?</h2>
 
 Gitpod Self-Hosted runs on Kubernetes and is easily installed via "helm install". On gitpod.io you can find detailed documentation and some automation to install Gitpod on [vanilla Kubernetes](https://www.gitpod.io/docs/self-hosted/0.4.0/install/install-on-kubernetes/) or [on Google Cloud Platform](https://www.gitpod.io/docs/self-hosted/0.4.0/install/install-on-gcp-script/). For the next release, we plan to add support for AWS, Azure, and OpenShift.
 
@@ -21,7 +21,7 @@ Operating Gitpod in production on gitpod.io has enabled us to battle-harden this
 This release ships a plethora of bugfixes and improvements, particularly in the area of GitLab integration.
 There is one major feature that I want to show in more detail since you can't try this on gitpod.io:
 
-### New Admin UI
+<h2 class="h3">New Admin UI</h2>
 
 This release ships with a new web UI for administrative tasks. The UI is particularly handy when providing support fo users.
 It allows for easy listing and searching of users and worksapces.
@@ -33,7 +33,7 @@ When selecting a user, the UI will show the user's details and workspaces, as yo
 
 To try the new admin interface in Gitpod Self-Hosted, you'll need to assign the "admin" privilege to your user and open /admin in your browser.
 
-### Getting Started
+<h2 class="h3">Getting Started</h2>
 
 The fastest way to get started is by installing Gitpod Self-Hosted [on Google Cloud Platform](https://www.gitpod.io/docs/self-hosted/0.4.0/install/install-on-gcp-script/). There is also more in-depth documentation available on how to install Gitpod on [vanilla Kubernetes](https://www.gitpod.io/docs/self-hosted/0.4.0/install/install-on-kubernetes/).
 

src/blog/moving-software-development-to-the-cloud.md

@@ -13,21 +13,21 @@ Since [we've started building Gitpod in July-2017](/blog/gitpod-online-ide/), we
 
 We certainly welcome the additional push Codespaces will bring, but it is important to communicate how [Gitpod compares to Codespaces](/gitpod-vs-github-codespaces/).
 
-### Gitpod is Open-Source, Multi-Cloud, and Works With GitLab, GitHub, and Bitbucket
+<h2 class="h3">Gitpod is Open-Source, Multi-Cloud, and Works With GitLab, GitHub, and Bitbucket</h2>
 
 Gitpod is an **open-source platform** which means you get full transparency over how Gitpod works and can even contribute to it. The [vibrant open-source community](https://community.gitpod.io/) of Gitpod welcomes everyone, and empowers them to develop additional features without restrictions.
 
 Furthermore, you can run Gitpod on your own infrastructure and any cloud provider. **Gitpod seamlessly works with GitHub, GitLab and Bitbucket** and can be deployed to public, private or hybrid clouds, neatly integrating into your infrastructure, **giving you full control of your system and your source code**.
 
-### Gitpod is Powerful
+<h2 class="h3">Gitpod is Powerful</h2>
 
 As a highly-optimized Kubernetes application **Gitpod is built on next-gen container technology** instead of VMs. This allows Gitpod to be extremely resource efficient giving you the best 💥 for the 💵
 
 Compared to virtual machines, isolating workspace containers from each other is harder. At Gitpod we’ve integrated the latest container isolation mechanisms that securely allow users to benefit from the resource efficiency of containers while still having root privileges. For the user this means full access to `sudo` and `docker` 🐳 Here’s a [great technical presentation](https://youtu.be/l4I2TVAnBuw?t=174) explaining how we make this happen.
 
 The result is that Gitpod offers more powerful dev environments with a small ecological footprint. Furthermore, we run Gitpod.io on a 100% carbon-neutral cloud service ❤️🌍
 
-### Gitpod is Fast
+<h2 class="h3">Gitpod is Fast</h2>
 
 Gitpod is not only extremely fast because of the higher efficiency, but also because of what we call [prebuilds](https://www.gitpod.io/docs/prebuilds/). Let’s take a closer look.
 
@@ -43,7 +43,7 @@ The advantages of having your dev environments prebuilt can not be overstated. F
 
 We believe prebuilding dev environments the way Gitpod does it, is key towards [“dev environments as code”](https://www.gitpod.io/blog/dev-env-as-code/). Without prebuilds, developers have to manually maintain and reuse their dev environments, because of the manual labour put into them. Those stateful environments drift apart over time and teams are once again working in very different setups, wasting time and energy with the resulting problems and surprises. With Gitpod "it works (or doesn't work) on my machine is a thing of the past.
 
-### The Road Ahead
+<h2 class="h3">The Road Ahead</h2>
 
 The real competition is the habit of maintaining stateful environments on overpowered local machines. We welcome GitHub and Microsoft to join forces in convincing developers around the world about the workflow and productivity benefits of automated, cloud-based dev environments 🥰
 

src/blog/node-js-development.md

@@ -15,7 +15,7 @@ In this blog post, I will show you a transparent way of getting started with Nod
 
 The dev environment is called [Gitpod](https://www.gitpod.io/) and is entirely free for open-source development.
 
-### Table of Contents
+<h2 class="h3">Table of Contents</h2>
 
 * [Hello World](#hello-world)
 

src/blog/opensource.md

@@ -11,7 +11,7 @@ As of today Gitpod is open source under the AGPL license at [github.com/gitpod-i
 
 For those of you who know us, this probably does not come as a big surprise. Working in open source is in our DNA and everything we’ve created over the past 10 years, including [Theia](https://github.com/eclipse-theia/theia), [Xtext](https://github.com/eclipse/xtext), [Open VSX](https://github.com/eclipse/openvsx) and many other projects have been open source. In fact, Gitpod was our only closed-source project and it is a relief to change that going forward.
 
-# Open-Source Contributions
+<h2 class="h1">Open-Source Contributions</h2>
 
 Contributing to Gitpod should be easy and accessible for everyone. All contributions are welcome, including pull requests, issues, documentation as well as updates and tweaks, blog posts, tutoials, and more. Please head over to [Github](https://github.com/gitpod-io/gitpod) to find out about the various ways you can contribute and join our [Gitpod Community](https://community.gitpod.io/).
 
@@ -59,7 +59,7 @@ Sven will run a webinar next week on Thursday, where we will showcase how we use
     </a>
 </div>
 
-# Gitpod Self-Hosted is Now Free
+<h2 class="h1">Gitpod Self-Hosted is Now Free</h2>
 
 The [SaaS offering of gitpod.io](https://www.gitpod.io/pricing/#) remains the easiest way to streamline your development workflows with continuously prebuilt dev environments.