CieloForge Website dev log

Short notes written while building CieloForge Website: what changed, what I decided, and what went wrong.

What Changed ?

Originally I had build a custom wordpress website using Oxygen-Builder for the purpose of chance of obtaining some admin-assistant jobs or Virtual Assistant like jobs back when I was still basing most of my work out of Canada. Now that I’ve fully moved and some of the paper-works have been completed and I’m studying…I decided to build a fully custom website with more coding required and be more secure and preformant than Wordpress…cause oh boy is wordpress slow.

What I decided :

I had decided to go with Astro, as I used it for an assigment for school once, and I quite liked the way it does things…granted with that school project it was a struggle to make Astro export evverything to a single directory for specific reasons it was required. I then choose to use the starlight template on initial setup because I really liked the look of it and the functionality of it. I felt it would be a great tool for me to self-document and keep things organized.

I proceeded to add TailwindCSS just because its simple, works well and seems to be popular. I then decided to split the architecture with starlight being only for specific things and native astro pages for the normal website pages. As starlights mdx pages do have some missing functionality compared to native astro pages.

What went wrong :

Well for starters I had intially setup a testing project and tried using starlight only but didn’t work well for standard website page things. Which made me choose to go with a split design, but then I had issues with seemeless appearance items and intergrating them well…eventually I got the hang of it and started from scratch with this current rendition.