This project is not used since a long while >> horrible structure and tech debt, not proud of this one.
Design-wise: great - tech debt wise and structure: I'm not proud.
This project is made public FOR LEARNING PURPOSES ONLY, it is not meant as a template, nor as a starting point.
Feel free to go through the components and structure, there ARE mistakes. Current project is on Adonis Inertia React with much better structure and architecture. I have no idea what I was thinking separating items based on pages/routes vs global utils, components, helpers, and functions.
To take a bullet: I hate making this public. However, it is a testament to how far I've grown as a developer - being able to look at this code and cringe, maybe is a privellage?
Either way, this was my first production project using a de-couple frontend/backend, and sadly there was a lot of planning done (might not seem visible at first), a lot of silly looking commits, crash-out commits - BUT remember: this was done by a developer that was getting one of his first production projects out, and I've learned a great deal building this.
-
Using Cloudinary to store image files and getting URL back (can use previous storage drive implementation for inspiration)
-
There must be two types of images: (optional now, mandatory in production)
- Main image that MUST exist on a blog
- Secondary, user Images that can exist anywhere in the blog, however with a forced resolution and alt text below
Blog cards will be auto made like this
[IMAGE] - Title [IMAGE] - Description
King Ko version depreciated >> new version is Adonis, and the backend is in Adonis
Close proximity tasks are (on top of blog cards for blog parser and fetcher):
1 - Blog parser for the frontend (done >> needs to be remade with UI/UX considerations)
3 - Blog resource fetcher with no authentication required for the frontend (TODO)
4 - Caching of heavy pages, like blogs. (TODO)
!! Watch for ignore pages in astro.config.mjs >> don't accidentaly ignore pages that we will later re-add
24-04-2025: I really dislike my current structure: It was done in good faith, but it has created a problem it was meant to prevent - and makes finding files a bit tricky and uncomfortable.
There is too much un-necessary component separation going on, especially on the Home and Dashboard pages (TODO)
Ironically - I did keep it live so you can see the project live. Again, it's depreciated in favor of a monolith Adonis web app - but feel free how each part works and interacts with each other.
Also - the blog system is horrendous lol, I've since made a significantly better version.
Vlad out -
--- Local anchors work for SEO --- Backlinks from authoritative site work well too --- Long term: build site authority
--- No follow / No index on Login, Register, Admin Panel, and other parts of the site (I forgot what I meant here)