Support other Templating Engines like React #8
Replies: 5 comments 13 replies
-
|
Is there a mailing list I can sign up for so I can get updates on the project? I subscribed to the github releases too :) |
Beta Was this translation helpful? Give feedback.
-
|
Not yet, this blew up more than I anticipated! Can you send me a quick email to hi@livebud.com? I'll add you to a list manually for now :) |
Beta Was this translation helpful? Give feedback.
-
|
Mee too please, email sent. |
Beta Was this translation helpful? Give feedback.
-
|
Add me as well please!! this project is something I actually wanted to start myself. Looking forward to also contributing to it! |
Beta Was this translation helpful? Give feedback.
-
|
Will do, thanks for your interest! Bud is going through a bit of a transition at the moment, but looking forward to sharing an update soon! |
Beta Was this translation helpful? Give feedback.
-
|
First of all, congrats for the project; it looks awesome and quite promising! Since you have mentioned the possible plan to support React, logically the next thing would be to support Vue as well. Sounds fair, right? Now a naive question here: how difficult would it be to go full vanilla JS instead of depending on third parties and such, whenever is necessary that is? Also, about using Go's Edit: Seems like @josebalius asked the same thing as I in #23. |
Beta Was this translation helpful? Give feedback.
-
|
@matthewmueller would it be possible to have a concept of "renderers" through the plugin API? Maybe it would map a file extension to a function that implements whatever template API it is that Bud needs? That way you could support any frontend framework via plugins. I work on Astro and this is what we do. Either way I do think including React by default makes a lot of sense for popularity reasons. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @matthewp, nice to see you here! Bud indeed has a rudimentary plugin system. I took it just far enough to know I could render both Svelte and React. It sounds like I should be studying Astro for a more complete solution. Could you point me in the right direction where I can learn more? |
Beta Was this translation helpful? Give feedback.
-
|
@stefanos82 FYI, I just created a discussion for Vue support: #39 |
Beta Was this translation helpful? Give feedback.
-
|
Hey @matthewmueller w.rt learning Astro, besides the official docs, you can find a lot of good resources here. I'm loving how seamlessly Svelte fits as the view layer in the overall scheme of things in Bud, but renderers are an amazing concept which Astro pioneered in a way, and definitely seems like a great way to let the developers bring their own template engine. Astro's latest releases call it just integrations now, with rendering as a subset of job and has the API docs available here(checkout Renderers under examples), but when they were just renderers I wrote something that you might find a bit useful. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing your expertise @one-aalam! I'll definitely look into Astro when we start supporting other renderers. |
Beta Was this translation helpful? Give feedback.
-
|
Not interested in React and any JS trash (I mean it. fight me.), just bare HTML. Does bare HTML belong in this issue or should it be a new one? |
Beta Was this translation helpful? Give feedback.
-
|
There will be no fighting here 😇 I just split HTML support into a new discussion: #40 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Is React somewhere on the timeline? |
Beta Was this translation helpful? Give feedback.
-
|
Not yet! I'm still working out the direction to take view support (see this comment for details). |
Beta Was this translation helpful? Give feedback.
-
|
Maybe we can start thinking about create plugins. |
Beta Was this translation helpful? Give feedback.
-
Right now Bud ships with out-of-the-box Svelte support. It's also designed to support React.
I picked Svelte because it already has solutions for scoped CSS and dynamically changing the
<head>. I'm tempted to wait on introducing React support until we have both of these features. Something like including Next.js'sstyled-jsx+<Head/>. Is this worth waiting for or does it not matter?Admittedly while Svelte is growing rapidly, React is the standard here and we need to meet people where they are.
I'd also like to support 2 other templating languages:
Which probably wouldn't ship with scoped CSS support (or should they?). That make me wonder what "baseline" of support I should provide and starting with basic React, then adding scoped CSS + dynamic head later would be desired.
Update: I just wrote a long brain dump of all my thoughts on current view support and ideas for the future. Please have a read and let me know what you think! #188 (comment)
Beta Was this translation helpful? Give feedback.
All reactions