Replies: 1 comment 4 replies
-
Thank you so much for this feedback! It is really useful and I'll make sure to document about the folder structure. Could you clarify what you want to do? Is it basically just create your own UI instead of the default views? If so, all you need to do is publish the base components for each page type you want to use. Then you can change which template you want to use. Perhaps if this is a common use case we could make this dynamic and configurable? If that would help we can put it on the roadmap! |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm interested in HydePHP as an alternative to Jekyll and Hugo for a blog-centric SSG.
Jekyll is getting old, and it's harder to incorporate new web technologies and techniques. Hugo's Go Lang template language is a bit obscure and doesn't get syntax highlighting in my editor of choice (Zed).
HydePHP uses Laravel, so I get modern underpinnings in a language I understand (PHP and Blade). HydePHP V2 may have Vite and TailwindCSS support -- both of which are important to me.
My experiments with HydePHP V1.7.6 are promising. I'd like a bit more documentation about the proper folder structure for creating my own site without the use of resources/views/vendor/hyde views. Browser hot reloads are a big missing feature that may be fixed in V2.
After V2 is available, I'll dive back in, hoping to migrate from Hugo to HydePHP.
Beta Was this translation helpful? Give feedback.
All reactions