mmmateo

8 ms·

1.
Show HN: Tinykit – self-hosted Lovable, deploys to itself(tinykit.studio)
6 points by mmmateo 9mo ago|0 comments
2.
by mmmateo 3y ago
Ahh okay that makes sense. Just updated it, thanks.
3.
by mmmateo 3y ago
Thanks for making it! And that's great to know - I've always wondered
4.
by mmmateo 3y ago
Is your concern with the fact that clients can lay out their sites with blocks? Note that they can't edit any of the visual aspects unless you create a field for those specifically (e.g. making an image a circle or square). If it'
5.
by mmmateo 3y ago
haha good point, but no it wasn't intentional. Wanted to replace the hot red & black design I had before with something besides blue.
6.
by mmmateo 3y ago
That's true, but it does communicate something important to companies and individuals looking to use, contribute, or build on the project to say what kind of open source it is, rather than just saying its open-source IMO. Would be in
7.
by mmmateo 3y ago
thanks so much swyx!
8.
by mmmateo 3y ago
Could you elaborate? Tailwind CSS is MIT but it's still under a for-profit company.
9.
by mmmateo 3y ago
> However, based on my long experience, you really don't want your client to touch the HTML/CSS of your site. Certainly, and in the same vein you don't want your client touching the design of the site. Clients can barely w
10.
by mmmateo 3y ago
It's hard to think of something I wish I knew earlier tbh. Svelte (and SvelteKit) are just so simple and approachable that I feel like whenever I need to do something new I can just try what feels most intuitive and it just works. I&#x
11.
by mmmateo 3y ago
That's awesome! So glad you like it
12.
by mmmateo 3y ago
I definitely understand with the struggle to balance design freedom and brand identity (or good design). But wouldn't you still have the issue of content editors wanting to right align text and turn it blue regardless of the CMS you&#x
13.
by mmmateo 3y ago
Primo itself is a SvelteKit application, so I don't know how possible it would be to run it on a LAMP server, but you could certainly deploy the static sites it generates on one.
14.
by mmmateo 3y ago
I agree! That's why Primo generates static HTML & CSS & only includes [vanilla] JS when its necessary to hydrate any interactive components. All using the Svelte compiler under the hood.
15.
by mmmateo 3y ago
good point, shame I can't edit the title
16.
by mmmateo 3y ago
Possibly for the database but authentication and file storage would still need to be taken care of
17.
by mmmateo 3y ago
Ah yeah I forgot Dreamweaver does give you access to the code, in that regard it's similar. But, speaking as a user of Primo (and echoing what I've heard from a lot of other users), I haven't found anything that rides the lin
18.
by mmmateo 3y ago
I just tried it out with web components using Lit and it seems to work pretty well ( https://i.imgur.com/PFvMgFp.png ), allowing you to pass in on-page editable fields. But I'd be interested to hear where web components
19.
by mmmateo 3y ago
This looks perfect! Just signed up
20.
by mmmateo 3y ago
Totally understand the interpretation, but if you take a closer look I think you'll find Primo is actually the opposite. Site builders like Dreamweaver, Squarespace, Wix, Webflow, Weebly, etc. (and even WordPress now) replace code with
21.
by mmmateo 3y ago
Thanks so much! Would love to hear how it works for you & help where I can. Lots still to come :)
22.
by mmmateo 3y ago
The biggest difference from any existing CMS is the integration of a code-editor and Svelte components, but also the on-page editing is more user-friendly than most CMSs or site builders. Specifically: It’s a monolithic CMS, unlike Strapi,
23.
by mmmateo 3y ago
No, you’d use an external service for stuff like that (I use Getform for emails).
24.
by mmmateo 3y ago
Thanks! I could definitely see the value in that. Once we make it possible to fetch content dynamically it should be easy to fetch Markdown from a repo and render it anywhere on the page. Or it might be simpler to keep SvelteKit/Astro
25.
by mmmateo 3y ago
I’ve always appreciated how Svelte keeps things as simple as possible without sacrificing capability, and how that results in more productivity and enjoyment in building. Really this is a visual layer over that to make it even more approach
26.
by mmmateo 3y ago
Definitely possible in the future, although to keep the project focused I'd imagine using a plugin or fetching that content from a separate CMS tailor-made for that kind of content would be ideal.
27.
by mmmateo 3y ago
Thanks! And yeah I agree it's a bit mislabeled; the goal was to enable people to put up their own server as easily as possible, which meant plugging into those services. We are working on decoupling the backend so you could self-self-h
28.
by mmmateo 3y ago
Yup! Makes it super easy to spin up a server. We're working on making it backend-agnostic to open it up to more people, but Supabase has always been my go-to.
29.
by mmmateo 3y ago
Sure thing! Just changed it from AGPL actually. It would be ideal if anyone forking it would contribute changes, but I was worried that would keep them from using it to build internal tools or separate products, and all the underlying tech
30.
by mmmateo 3y ago
Sweet! Let me know if you need any help

More ›