Refactor from Angular to Jekyll for GitHub Pages compatibility

[Copilot]

This PR converts the RERUM website from an AngularJS single-page application to a Jekyll static site to improve GitHub Pages compatibility and eliminate client-side routing dependencies.

Problem

The original site used AngularJS with hash-based routing (#/welcome, #/api, etc.) which created several issues:

• Poor SEO due to client-side routing
• JavaScript dependency for basic navigation
• Suboptimal GitHub Pages integration
• Slower initial page loads due to Angular bootstrap

Solution

Implemented a hybrid approach that:

• Converts main content pages to Jekyll Markdown with shared layout
• Preserves interactive tool functionality where Angular is needed
• Eliminates hash-based routing in favor of clean URLs
• Maintains all existing content and styling

Technical Changes

Site Structure:

• Created _layouts/default.html Jekyll template from existing index.html
• Converted 7 main pages from Angular templates to Jekyll Markdown
• Added clean permalinks (/, /api/, /about/, etc.)
• Updated navigation links to use Jekyll relative_url filter

Before/After URL Structure:

Before: /#welcome, /#api, /#about (hash routing)
After:  /, /api/, /about/ (clean URLs)

Preserved Functionality:

• All content migrated exactly as-is
• CSS and assets unchanged
• Interactive tools in /app/tools/ remain Angular-powered
• Footer navigation and external links maintained

Benefits

• ✅ GitHub Pages native - no build process required
• ✅ SEO-friendly - search engines can crawl all pages
• ✅ Faster loading - static pages with no JavaScript bootstrap
• ✅ Mobile-friendly - works without JavaScript
• ✅ Better caching - static content caches efficiently

Testing

The converted site maintains full functionality while improving GitHub Pages compatibility. Main navigation now works as static pages, while specialized tools retain their interactive Angular functionality where needed.

 *Raw Markdown view - GitHub Pages will render this as proper HTML*

Fixes #78.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[cubap]

this fixes #78