hoakiet98

8 ms·

61.
by hoakiet98 2y ago
Thanks tmolovinsky, we're already actively working on component creation so hoping to introduce that soon :)
62.
by hoakiet98 2y ago
Thanks au-arms! Webflow is definitely the best option out there. But for devs, we're hoping to address the lock-in and get back some of the flexibility of owning the code
63.
by hoakiet98 2y ago
thank you for checking it out :)
64.
by hoakiet98 2y ago
Feel free to share your tool if it's open source. I'd love to see how you approach this problem. Happy to share more technical details if it helps your product. Chrome inspector does so much more like clip support and media querie
65.
by hoakiet98 2y ago
> I assume then that the editor would only be used for editing css, not html It does edit html. Inserting html elements in this case. > I'm also curious how they determine where in source the code needs to change Right now we&#x2
66.
by hoakiet98 2y ago
Thanks for checking it out robzhu. Let me know of any feedback/issues :)
67.
by hoakiet98 2y ago
We work best for React (js/ts) and TailwindCSS. In-code UI libs like ShadCN also customizes better. Thanks for checking it out :)
68.
Show HN: An open-source, local-first Webflow for your own app(github.com)
227 points by hoakiet98 2y ago|51 comments
69.
by hoakiet98 2y ago
> I've just started working on a new portfolio site and was wondering if I could skip the Figma/whatever wireframe phase and just use a local WYSIWYG tool for a static page. Someone above suggested https://bootstraps
70.
by hoakiet98 2y ago
This looks nice. Sorry for off-loading the research to you but how does it compare to SingleFile (Chrome extension based)? I can't tell what the output would be. https://github.com/gildas-lormeau/SingleFile
71.
by hoakiet98 2y ago
> I hated having my projects under their control. This is my biggest objection as well. Along with not having my code locally. > I hope this project continues to grow by leaps and bounds! Thank you for the kind words!
72.
by hoakiet98 2y ago
That's very good results and nice UI. I hope we catch up to this level of quality one day. Thanks for sharing!
73.
by hoakiet98 2y ago
> Then for paid/hosted version, on top of it being hosted, you get full integration with github so PRs and diffs and things can be sent directly from the tool (which is great for designers) That's my impression too. Designers I
74.
by hoakiet98 2y ago
You can try it out below. It's not so evident from the demo but there's an inherent flaky feel to using a Chrome extension as a builder. You never feel sure your states are saved correctly and where you can go to review changes. T
75.
by hoakiet98 2y ago
Look awesome! Everyone has such nice sites, we need to catch up.
76.
by hoakiet98 2y ago
Not at the moment. I just want to keep scope to React for now. I imagine we will abstract the React part away into a plugin in the future.
77.
by hoakiet98 2y ago
Utopia is super cool. Thanks for sharing :) I believe someone from the team reached out
78.
by hoakiet98 2y ago
No problem. This is very poorly documented but this entire repo is built in Svelte. I'm porting over functionalities from it so this is a much more mature editor. If there's a specific implementation you want to learn about, let m
79.
by hoakiet98 2y ago
> Your first thought needs to be how to create a sustainable project otherwise you won't have a community. I agree. Do you have any tips here besides being good with answering questions, documentation, and otherwise continuing to wo
80.
by hoakiet98 2y ago
Very cool!
81.
by hoakiet98 2y ago
> but if it's the ability to bring react components back into the editor, and have the designer WYSIWYG modify the props Haha yeah this is the plan. I really like Storybook for this reason but I loath the setup you need to do to ex
82.
by hoakiet98 2y ago
It pained me to do this. Everyone I talked to used React instead of Svelte. At some point, we realized we were spending half the time supporting Svelte just for ourselves for <10% of the return. I still love Svelte and will continue usin
83.
by hoakiet98 2y ago
To my understanding, Reka is more of a core no-code builder library while we're an implementation of it. Now I'm considering if we should use Reka to build out the rest of the editor. With Builder.io, you have to set up a componen
84.
by hoakiet98 2y ago
Good catch, thank you. Changed it to schedule a demo.
85.
by hoakiet98 2y ago
> 1. Are you planning to monetize? If so, what are some of your ideas? Yes, though my plan is not concrete, yet. I plan to offer a hosted version for teams with fewer technical members to be able to contribute the same way a front-end en
86.
by hoakiet98 2y ago
> I only saw install instructions for NPM so maybe it just needs built executables Sorry for the confusion, this is an Electron app. I just didn't ship an executable with it at the moment. > I could see an easy integration to pus
87.
by hoakiet98 2y ago
> because my suspicion is that since this tool just exports React, you could relatively easily achieve this using Next.js SSG building At the core, we generate pure HTML and CSS, then serialize those into React and Tailwind. It would be
88.
by hoakiet98 2y ago
How cool! There's a lot to learn from here. Thank you for sharing.
89.
by hoakiet98 2y ago
Point taken, we'd do better without the headache for now until further legal counseling. Changing the tagline now. Thank you all for the suggestion!
90.
by hoakiet98 2y ago
> that just serves locally and you hit it with your browser This is an interesting take. My interpretation: You can host this on a server, then expose a port remotely which will have all the access of the electron app, making it a pseudo

More ›