Introduction
EasyLearn365 started as more than just an idea for a personal website. It became my first real project for bringing together my learning, technical notes, blog content, professional profile, and portfolio direction in one place.
Before this project, my content and learning journey were spread across different places. I had older blog posts on Bytes & Clouds, notes in documentation, career information in CV files, and project ideas that were not yet presented in a structured way.
I wanted EasyLearn365 to become the main platform for all of that.
The goal was simple: build a clean, practical, and maintainable website that could grow with my learning.
Why I Started This Project
I built EasyLearn365 because I wanted a public space to document my progress in technology.
My long-term focus is moving across modern workplace technologies, identity and security, Azure, automation, DevOps practices, AI enablement, and eventually AI platform engineering. That kind of journey needs more than private notes. It needs structure, reflection, and proof of work.
EasyLearn365 is meant to become:
- A personal website
- A technical blog
- A project portfolio
- A professional profile
- A public learning journal
I did not want the site to look perfect on day one. I wanted it to be useful, clear, and real.
That is why the site follows the same learning philosophy I want to apply to everything here:
Learn -> Document -> Build -> Improve
What I Built
The first version of EasyLearn365 is a static website hosted with GitHub Pages and connected to the custom domain easylearn365.com.
The site includes the main pages needed for a professional learning platform:
- Home
- About
- Blog
- Portfolio / Projects
- Services
- CV / Resume
- Contact
I also connected the custom domain, enabled HTTPS, preserved Microsoft 365 email functionality, migrated selected blog content, and embedded a Microsoft Form for contact submissions.
This made the project more than just a website design task. It became a practical exercise across multiple real-world areas:
- Git and GitHub workflow
- GitHub Pages hosting
- DNS configuration
- Custom domain setup
- Microsoft 365 email continuity
- Static website structure
- Content planning
- Blog migration
- Documentation-driven development
That combination made the project valuable as a first portfolio item.
Why I Chose GitHub Pages
For this stage of the project, I wanted to avoid unnecessary complexity.
I did not need WordPress, a CMS, a database, or a heavy hosting platform just to publish a simple learning website. What I needed was a clean foundation that helped me practice the basics properly.
GitHub Pages made sense because it allowed me to:
- Host a static website for free
- Use Git and GitHub as part of the workflow
- Publish from the main branch
- Connect a custom domain
- Keep the site simple and maintainable
- Learn through real version control and deployment habits
This also aligned well with the overall purpose of EasyLearn365. The website itself became part of the learning process.
Instead of only writing about technology, I was using real tools to build, publish, troubleshoot, and improve something public.
The DNS and Email Part Was Important
One of the most important parts of this project was connecting the custom domain without breaking email.
The domain easylearn365.com is also used for Microsoft 365 email. That meant DNS records had to be handled carefully.
The website needed GitHub Pages records, but Microsoft 365 still needed its own records for email and service functionality.
That included keeping records such as mail-related, Autodiscover, and other Microsoft 365-related DNS entries intact while updating the website records.
This was a useful reminder that DNS changes are not just a website task. If the same domain is used for email, identity, or business services, every change needs to be made carefully.
After the DNS changes, I verified that:
- The custom domain loaded the website
- HTTPS was enabled
- Microsoft 365 email could still send and receive messages
- The contact form worked correctly
That validation step made the project feel complete.
What This Project Taught Me
This project reinforced something simple but important: practical learning works best when it is documented.
Building EasyLearn365 helped me practice:
- Planning a website before styling it
- Using GitHub as a source of truth
- Publishing through GitHub Pages
- Understanding the difference between a GitHub Pages URL and a custom domain
- Updating DNS records carefully
- Preserving Microsoft 365 email records
- Testing after each major change
- Improving pages gradually instead of trying to perfect everything at once
It also helped me separate different types of content.
The Blog section is where I can explain ideas, lessons, decisions, and reflections. The Projects section is where I can publish repeatable step-by-step tutorials with screenshots and validation checks.
That distinction is important because it keeps the website organized. Blog posts explain the thinking. Projects show the implementation.
How This Fits the EasyLearn365 Direction
EasyLearn365 is designed to grow over time.
The current direction of the site aligns with my professional learning path:
Modern Workplace -> Identity & Security -> Azure -> Automation & DevOps -> AI Enablement -> AI Platform Engineering
This first project may look simple from the outside, but it creates the foundation for everything that comes next.
Now the site has a place for:
- Technical blog posts
- Project tutorials
- Portfolio evidence
- CV and professional positioning
- Contact and service conversations
- Future Microsoft 365, Azure, automation, and AI-related work
That makes this project an important starting point.
It is not the final version of EasyLearn365. It is the foundation.
Key Takeaways
- EasyLearn365 was built as a real learning-in-public project.
- GitHub Pages was a good fit because the site needed simplicity, version control, and easy publishing.
- DNS changes had to be handled carefully because the same domain is used for Microsoft 365 email.
- The project helped define the difference between Blog content and Project content.
- Blog posts will explain ideas and lessons, while Projects will focus on repeatable step-by-step implementation.
- This website is now ready to grow through regular blog posts and practical project documentation.
Closing Thoughts
Building EasyLearn365 helped turn a scattered learning journey into a structured public platform.
It gave me a real foundation for documenting my progress, sharing technical learning, building a project portfolio, and developing a professional presence around Microsoft 365, cloud, automation, security, and AI enablement.
This is only the first project, but it matters because it creates the space where future work can live.
EasyLearn365 will continue to grow step by step:
Learn -> Document -> Build -> Improve