-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transition to a Hugo Module? #4
Comments
Too advanced for me. The docunentation seems too cryptic. Maybe in the
future.
…On Wed, Sep 2, 2020, 1:52 PM Jim Garrison ***@***.***> wrote:
Have you considered making victorhugo into a Hugo Module
<https://gohugo.io/hugo-modules/>? Some examples of this in action are at
https://github.com/gohugoio/hugo-mod-jslibs. I think it might make
victorhugo even easier to hook into a web site; it will allow users to more
easily keep their version of victorhugo up-to-date; and it will likely mean
you can modify victorhugo in ways that could make it more maintainable,
rather than have it continue to be one big file.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#4>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKXOCHUMAEIDCHIBKVQMX5DSDZZ4FANCNFSM4QTKTAFQ>
.
|
I agree that the Hugo Modules documentation currently is not very good. That's why I linked to hugo-mod-jslibs. For instance, the wrapping there of turbolinks is pretty simple and straightforward. |
I'm giving it a try later today. Thank you for letting me know, I hadn't
seen that bit ypu you mention. That said, I've found the lack of official
support from Hugo to be really demoralizing, to the point where I'm
considering moving the project outside Hugo. Wordpress supported their
plugging devs 100% all the way when they first launched. I don't see the
same from Hugo. It would explain the lack of themes and modules (or
pluggings). Yeah, modules are pretty new but... even then. It is almost
like they can't be bothered with it.
…On Wed, Sep 2, 2020, 3:34 PM Jim Garrison ***@***.***> wrote:
I agree that the Hugo Modules documentation currently is not very good.
That's why I linked to hugo-mod-jslibs. For instance, the wrapping there
of turbolinks
<https://github.com/gohugoio/hugo-mod-jslibs/tree/master/turbolinks> is
pretty simple and straightforward.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKXOCHSAGJREJDNLGYVEGE3SD2F2ZANCNFSM4QTKTAFQ>
.
|
Hot damn James, you are a theoretical physicist! Congrats on you, man! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Have you considered making victorhugo into a Hugo Module? Some examples of this in action are at https://github.com/gohugoio/hugo-mod-jslibs. I think it might make victorhugo even easier to hook into a web site; it will allow users to more easily keep their version of victorhugo up-to-date; and it will likely mean you can modify victorhugo in ways that could make it more maintainable, rather than have it continue to be one big file.
The text was updated successfully, but these errors were encountered: