├── .github └── workflows │ └── jekyll-gh-pages.yml ├── README.md └── portfolio-website ├── _config.yml ├── _includes ├── footer.html └── testimonials.html ├── assets ├── css │ └── styles.css └── js │ └── scripts.js └── index.html /.github/workflows/jekyll-gh-pages.yml: -------------------------------------------------------------------------------- 1 | # Sample workflow for building and deploying a Jekyll site to GitHub Pages 2 | name: Deploy Jekyll with GitHub Pages dependencies preinstalled 3 | 4 | on: 5 | # Runs on pushes targeting the default branch 6 | push: 7 | branches: ["main"] 8 | 9 | # Allows you to run this workflow manually from the Actions tab 10 | workflow_dispatch: 11 | 12 | # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages 13 | permissions: 14 | contents: read 15 | pages: write 16 | id-token: write 17 | 18 | # Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued. 19 | # However, do NOT cancel in-progress runs as we want to allow these production deployments to complete. 20 | concurrency: 21 | group: "pages" 22 | cancel-in-progress: false 23 | 24 | jobs: 25 | # Build job 26 | build: 27 | runs-on: ubuntu-latest 28 | steps: 29 | - name: Checkout 30 | uses: actions/checkout@v4 31 | - name: Setup Pages 32 | uses: actions/configure-pages@v5 33 | - name: Build with Jekyll 34 | uses: actions/jekyll-build-pages@v1 35 | with: 36 | source: ./ 37 | destination: ./_site 38 | - name: Upload artifact 39 | uses: actions/upload-pages-artifact@v3 40 | 41 | # Deployment job 42 | deploy: 43 | environment: 44 | name: github-pages 45 | url: ${{ steps.deployment.outputs.page_url }} 46 | runs-on: ubuntu-latest 47 | needs: build 48 | steps: 49 | - name: Deploy to GitHub Pages 50 | id: deployment 51 | uses: actions/deploy-pages@v4 52 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | This repository is empty. Any task executed on it should be considered a new capability and needs to be created. 2 | -------------------------------------------------------------------------------- /portfolio-website/_config.yml: -------------------------------------------------------------------------------- 1 | # Jekyll configuration file 2 | 3 | title: "My Portfolio Website" 4 | description: "A portfolio website showcasing my free courses and testimonials." 5 | baseurl: "" # the subpath of your site, e.g. /blog 6 | url: "https://yourusername.github.io" # the base hostname & protocol for your site 7 | 8 | # Build settings 9 | markdown: kramdown 10 | theme: minima 11 | 12 | # Exclude these files from the site 13 | exclude: 14 | - Gemfile 15 | - Gemfile.lock 16 | - node_modules 17 | - vendor/bundle/ 18 | - vendor/cache/ 19 | - vendor/gems/ 20 | - vendor/ruby/ 21 | 22 | # Plugins 23 | plugins: 24 | - jekyll-feed 25 | - jekyll-seo-tag 26 | 27 | # Social media handles 28 | social: 29 | twitter: your_twitter_handle 30 | github: your_github_handle 31 | linkedin: your_linkedin_handle 32 | youtube: your_youtube_channel 33 | -------------------------------------------------------------------------------- /portfolio-website/_includes/footer.html: -------------------------------------------------------------------------------- 1 | 9 | -------------------------------------------------------------------------------- /portfolio-website/_includes/testimonials.html: -------------------------------------------------------------------------------- 1 |
"This course was amazing! I learned so much about DevOps."
4 |- Subscriber 1
5 |"The AWS Zero to Hero course helped me land my dream job."
9 |- Subscriber 2
10 |"Azure Zero to Hero is a must for anyone looking to get into cloud computing."
14 |- Subscriber 3
15 |Learn DevOps from scratch and become a hero in the field.
19 |Master AWS and become a cloud expert.
23 |Get started with Azure and become a cloud professional.
27 |