Original Draft Date: 2022-08-20
Original Publish Date: 2022-08-20
Last Update Date: 2023-11-28
From this moment on, my ink will only be written on things that’s worthwhile - arts and creations, and on things that’s out of necessity: communication.
Posting on social media is dangerous and harmful. It hurts not just the yongsters through comparing and peer pressure, but also hurts the authors because of all the delicate feelings - even Tom Holland quits social media due to mental health concerns. I will not argue how bad social media might have been, but in this post I will briefly share from a technical point of view how I ended up with building the website as you see now.
The direct inpsiration for all of this, ironically, is an instant inspirational.
title TotalImagine.com Timeline
: GoDaddy 希亘部落 (Some forum framework and GUI setup)
: CloudBook (PhP)
: Adobe Portfolio
: Templated Charles Zhang totalimagine.com (ASP.Net Core)
: Inspiration from Project Nayuki
: Redream subsite (tiddly wiki)
: Incorporating diverse social media sources (WeChat, Instgram, Pininterest, Steam portfolio and Artstation)
: The Final Iteration (So-far) - New simple single-ended Github static pages
Future candidate of embeddable components with cloud hosting services:
Originally I made website for fun, during very early times I thought of making a tech blog for money. Latter it’s just my “face” and a representation of my work. Throughout I always wanted to build some space. Nowadays it serves mostly as a reference function for myself. One always need to be careful putting only very very original stuff on it, and limit its reference functions to public-facing aspects (e.g. Crate Universe is a BAD idea) - this is achieved by limiting its functionalities to linking and redirections, and avoid dynamically built solutions and custom content hosting. Focus on texts. And it will look more like a blog. Anyway, attracting audience or be useful to others is not our goal.
Historically, it served the following purposes:
Maintability and ease of use are the greatest; Simplicity is key; Infrastructure-based but light. ASP.Net Core is too bad. Static is key.
Why not use a static webpage builder?