Hey, what's good? I know no one's reading this right now, but I like writing and posting things on my website, so I'm just gonna keep doing that.
I added visuals to the homepage in this update along with what I guess would be called a blog section, so that's what I'm calling it. Never thought I'd have a blog, but I guess these things just happen sometimes. Everything's basic as hell right now, and that's okay. Like I talked about yesterday in my original index.html, I'm taking a strict iterative approach with the projects that I embark on from now on, and sometimes that means posting mismatched pages (like this one in comparison to the updated homepage) 'cause your you're gonna add dynamic page generation to reuse components efficienctly in a future update and the priority is having the thing be functional first, even if it's bare-bones. I guess I could copy/paste HTML from the homepage for now to replicate global components and that would work for something this tiny in scale, but I'm not exactly sure when I'm gonna make a database integration, and I don't want to have to keep updating the HTML of every blog post every time I make a change to any global components if I want to keep the reused assets the same. Guess I don't have to, but I'd rather just keep these entries basic HTML pages for now then put it all in a database and generate them dynamically later instead of having a bunch of blog entries showing different states of component development, although that would actually be pretty cool. That's a decision for a later update. This meets what I set out to do for now.
Anyways, like I said, I'll be adding dynamic page generation in the future. Probably pretty soon if I'm gonna be consistently adding to the site.
I don't know how often I'll be adding features / design changes to the site, at least once a week for the foreseeable future. Nah, more. Twice a week. Maybe even more!!! Really depends on how much I set for myself for each update. For example, if I focus on publishing small, frequent updates (which I currently am), then it could be a few times a week. I like that approach, because consistently finishing something (like this update) and publishing it feels good. There's also other benefits, like it forces me to intentionally split up large goals into smaller sub-goals over time that continously and incrementally provide tangible, functional, and published results instead of having a collection of never-released, unfinished, and non-functional projects gather dust because I refused to publish early, simple, functional versions of them out of ego (while letting feature-creep balloon their specs into v1.0 monoliths).
I also don't know how often I'll be making standalone blog posts. I'm considering this more of a separate update post. I think 1-2 per week, leaning towards 2, is a good number for now. Hm, am I gonna make a whole post with extended commentary and talk about future plans for every little update? Probably not, so I'll have a dedicated update log page and I'll consider this as fitting under the blog post umbrella, instead (update post special edition). Because of that, I'm gonna count this towards my weekly quota. I know, I know, but, I really didn't think I'd write more than a few sentences and I'll be damned if this won't count towards it.
This is a lot of fun. It's funny, usually the whole point of publishing things is for other people to see, but right now I don't care all that much about how many people end up seeing this. I'm having fun making it and publishing it for myself and the imaginary, abstract idea of a reader that I have in my head. This is something I've been meaning to do for a long time, among other things.
Anyways, I could write indefinitely, but at this point I'm eating into time I'd set aside to work on other things today (suspense, what could they be?). So, I'm gonna 'push this update' (drag and drop my website folder contents into a Google Cloud Platform Storage Bucket) and go work on those other things.
It'd be fun to setup an RSS feed, too.