Closed hollowaykeanho closed 1 year ago
Appearently, HestiaHUGO is capable of laying out the foundation easily for the actual code libraries. Working on it alongside Issue #59 .
HestiaLIBS foundation in HestiaHUGO is established. Commit ID: 41db825cec958413ed21e6e2211fd3350d7fda7f
Any update?
Yeah.. a lot of good news so far...
1) template
method does not requires file reading like partial
== significantly reduces the IOCTL storm (Issue #59).
2) Most recent https://discourse.gohugo.io/t/how-to-pass-gos-pipeline-into-string-or-vice-versa/43289/9 resolves the template pipeline gap we had for all the content pages.
3) Phase 2 hestiaLIBS
directory planning is done simultenously.
We will see a huge bump in performance once we release Phase 1.2 hestiaHUGO.
Item 1, you serious?
https://github.com/ZORALab/Hestia/tree/experimental/hestiaHUGO/layouts/partials/Hestia
See for yourself. It really works like charm.
Great. Proceed further then. I assume this can be done in this week?
Pretty much. It's just switching the API adapter. No much of novel development anyway.
Since this is heavily influencing the writing of getting started (Issue #67), please see it done before continue writing the them.
No longer works for HestiaHUGO
so let's scrap it and only focus on HestiaGO + HestiaRS.
new findings?
Yeap.. updating the list of registered functions.
Updated expected output. Completed hestiaHUGO's API reviews and merges.
Restructuring API and directory layout again as we had decided to drop the Rust where it overly dictates naming convention pattern against all languages.
Updated to the latest structure. Pending commit.
Perfect. Looks like taking Rust in was a bad decision during prototyping stage. You're right. Once everything is stable, then we will consider writing for it (knowing you, I know how it ends haha). Great job!
All hestiaGUI ported and stabilized. hestiaGO and hestiaNIM can be included in. Mark this ticket as completed.
Released in version v.1.2.0
.
Description
While performing library assimilations across the globe, we should plan out and plot the hestiaLIBS API before it reaches the same point of no return like any other libraries.
Expected Behavior
The hestiaLIB layouts and API foundations are tested and constructed.
implemented across all packages:
Reviewed Languages
hestiaHUGO
hestiaGO
hestiaRS
hestiaNIM
Current Absent Behavior
hestiaLIB layouts and API foundations are not tested yet and it's still in idea phase.
Attachment