Huamo has just gone through one of its more comprehensive rounds of refinement. The update focuses on two things that have been bothering me for a long time: performance and visual consistency. The result is a faster site, a cleaner color system, and a much more comfortable reading experience for Markdown content.
At a glance, the changes come down to three points:
- The entire visual system now revolves around light brown, dark brown, and white.
- Markdown pages have been redesigned in a style closer to VitePress.
- Lazy loading has been introduced, so content that is not immediately visible will only load when needed.
A more consistent visual language
The project’s color palette has been narrowed down to light brown, dark brown, and white. These colors are now managed through global design variables, which makes the interface more consistent and makes future adjustments easier.
The days of unexpected greens, blues, and other unrelated colors appearing across the site should be over. The new palette gives Huamo a clearer visual identity and makes different parts of the site feel like they belong to the same system.
Markdown is easier to read now
Markdown presentation was one of the main targets of this update. For a long time, I felt that the reading experience in the main body of the blog was far from ideal. The typography and spacing made longer pieces harder to follow, and this was a problem I kept putting off.
The content area has now been reorganized around a new set of rules for headings, paragraphs, blockquotes, tables, code blocks, and other common Markdown elements. The overall result is closer to the visual style used by VitePress, with clearer hierarchy and more comfortable spacing.
The font setup has also been updated. Huamo now globally loads Inter, the typeface used by VitePress, while adding fallback fonts for Chinese text and emoji so that mixed-language content remains visually stable.
A lighter first load
Performance work has focused especially on the initial view. Non-critical elements now use deferred rendering, which means components such as the footer and the back-to-top button no longer need to be loaded immediately as part of the first screen.
The mobile header drawer has also been changed to load on demand. This reduces the amount of code needed at startup. Event coalescing-related configuration has been enabled as well, helping lower the change-detection cost caused by high-frequency events.
There is a trade-off: the first time Huamo loads, switching routes may feel slightly less immediate. With the CDN in place, however, subsequent loads become considerably smoother.
Fewer unnecessary requests
The request layer now includes a unified caching mechanism. A cache-enabled GET method has been abstracted into HttpService, with support for TTL-based caching, deduplication of concurrent requests, and cache invalidation.
This reduces duplicate network requests and makes the interface less sensitive to fluctuations in API response times. List switching and repeat visits should also feel more stable because previously fetched data can be reused when appropriate.
What still needs work
Even though I already like Huamo’s current appearance much more than before, there are still several areas worth improving.
For stability, the historical files could use a consistent encoding format. A visual regression check of key pages would also be useful, reducing the chance that future style changes quietly reintroduce old problems.
There is more room for performance work on image assets as well. Possible improvements include standardizing image dimensions, adding WebP or AVIF versions, refining the lazy-loading strategy, and continuing to optimize chunk splitting through bundle analysis. On the API side, stale-while-revalidate, failed-request retries, and fallback caching could make the data layer more resilient.
As for features, I may eventually add something similar to a social-feed or “moments” section, or bring back the old food-related module. Before that happens, the API and ERP backend projects may need to be refactored first.
For now, this version of Huamo is faster, more coherent, and much closer to the visual experience I wanted from the beginning.