Closed hollowaykeanho closed 1 year ago
Optimized toc_hestiaUI
component.
Optimized all note_hestiaUI
component.
Optimized badge-shields_hestiaUI
component.
Optimized table_hestiaUI
component.
Assimilation completed. HestiaHUGO is ready for content building.
Description
While the idea direction was to fully develop HestiaGO and hestiaRUST for pure WASM deployment after its discovery, it will take some time if we implement the unit-testing way (great but it's just a lot of homework for quality assurance and warranted performance). However, as Hestia's size is growing bigger, we have to establish the documentations site before any knowledge leak. Re-using ZORALab's Bissetii is a no-go because hestiaHUGO fixed A LOT of Hugo's bugs. The only sensible way is to assimilate Bissetii's component UI into https://github.com/ZORALab/Hestia/tree/experimental/hestiaHUGO/layouts/partials/Hestia/functions/render/components folder manually first, then work towards WASM goal.
Expected Behavior
hestiaHUGO is at least fully functional for static website and static data server usage. Future ZORALab and customers's public facing sites can no longer need to suffer the never-ending bug and inconsistencies from Hugo. Among the components:
code
part)pre
part)Current Absent Behavior
hestiaHUGO fixed and stabilize Hugo capabilities and even offer powerful features like built-in social media artifacts rendering, proper PWA implementations with offline and caching capabilities and etc. It's missing the UI component design to be fully operable and is pemeared due to project execution timeline.
Attachment