Rebuild Elmentor Program Website Using Clean Version With Key Enhancements

[MohamedRadwan-DevOps]

Description

The current Elmentor Program website is incomplete and deviates from the previously approved clean version. This issue focuses on rebuilding the site using the clean, structured version as the base and incorporating essential enhancements.
Better Version

This update should:

• Replace the current structure with the clean implementation
• Add the two missing Gathering images to the clean version
• Review and update all relevant internal and external links (e.g., DevOps Visions, Community Blog)
• Ensure full alignment with the latest information shared here:
  DevOps Visions Blog – About Section

Objectives

• Restore the clean version of the Elmentor website
• Incorporate missing elements and fix inconsistencies
• Ensure all pages and links (e.g., DevOps Visions, Community Blog) are accurate and functional
• Prepare the updated version for public use

Checklist

• Restore the clean version of the website
• Add the two Gathering images
• Review and update all internal/external links
• Match visual and content alignment with the blog’s latest “About” section

Related

• Architect Repositories for Main Websites (DevOps Visions, Elmentor Program, Community Blog) DevOpsVisions/devopsvisions.github.io#12

Deliverables

• https://elmentorprogram.github.io/

Action Taken

1. Update Vite Configuration

• Set the base in vite.config.ts to '/':

  export default defineConfig(() => ({
    // ...existing code...
    base: '/'
  }))

2. TypeScript Installation

• Install TypeScript as a dev dependency:

  npm install --save-dev typescript

3. Manual Root Deployment

• Build your project:

  npm run build

• Copy the contents of the dist folder to the root of your repository (this will overwrite your source files):

  cp -r dist/* .

• Commit and push to the main branch:

  git add .
  git commit -m "Deploy production build to root"
  git push origin main

• On GitHub, go to Settings → Pages and set the source to the main branch (root).
• Your site will be live at: https://elmentorprogram.github.io

4. GitHub Actions Workflow

• The GitHub Actions deployment workflow was initially giving errors
• To prevent it from being triggered on every push, it was converted into a manual workflow dispatch.

5. Submodule Error Fix

• If you see an error about a missing submodule (e.g., .temp/pr-fixes/devops-step-by-step):
  • Remove the submodule reference:

    git rm --cached .temp/pr-fixes/devops-step-by-step
    rm -rf .temp/pr-fixes/devops-step-by-step
    git commit -m "Remove broken submodule reference"
    git push

6. Notes

• The gh-pages branch is not needed for this repository name because GitHub Pages for user/organization sites (repos named username.github.io) always serves from the root of the main branch. The gh-pages branch is only required for project sites (repos named something other than username.github.io).

[MohamedRadwan-DevOps]

@RehabAbotalep Thank you, it looks very good. I have a few comments. Since Ayman will be joining us to work here, it would be better to move this item to the public repo on Elmentor Org. Although there isn't a direct method for this, the last comment suggests a workaround. Also, for any items related to our blog, DevOps Visions Website, or Elmentor Website, let's keep them on public repos.
https://github.com/orgs/community/discussions/5766

[aymanaboghonim]

It is not clear for me what is meant by the better version here ?
Also, The link is raising 404 error.

[MohamedRadwan-DevOps]

@aymanaboghonim this was the forked repo from your account and Rehab just renamed it to the current website repo.

[aymanaboghonim]

So I think we should edit the URL to https://github.com/ElmentorProgram/elmentorprogram.github.io.

[MohamedRadwan-DevOps]

@aymanaboghonim if you say so then sure 😍 Done!