Hi HN. primo is an IDECMSCLSSG (short for IDE, CMS, Component Library, Static Site Generator) I’ve been working on for a few months. The idea came from wanting to host a Notion page at a domain name and not being able to. Once I made the initial version - a basic text editor - the rest of the features just came naturally (except for the SSG, which came from not wanting to deal with hosting). I’d written off freelance…
Looks amazing ! +1 on Svelte ! My new goto tool and very refreshing :)
Show HN: Primo – all-in-one IDE, CMS, component library, static site generator
21–30 of 214 posts
Re: Show HN: Primo – all-in-one IDE, CMS, component library, static site generator
#22It sounds great, but the permissions it needs is too much for me: > Repositories > Public and private > This application will be able to read and write all public and private repository data. Would it be possible to use deploy keys for specific repositories instead?
Too bad, looks like a really good product.
Re: Show HN: Primo – all-in-one IDE, CMS, component library, static site generator
#23Re: Show HN: Primo – all-in-one IDE, CMS, component library, static site generator
#24Hi HN. primo is an IDECMSCLSSG (short for IDE, CMS, Component Library, Static Site Generator) I’ve been working on for a few months. The idea came from wanting to host a Notion page at a domain name and not being able to. Once I made the initial version - a basic text editor - the rest of the features just came naturally (except for the SSG, which came from not wanting to deal with hosting). I’d written off freelance…
overscroll-behavior-x: none;Re: Show HN: Primo – all-in-one IDE, CMS, component library, static site generator
#25However, of late, I've taken to hand-writing HTML and CSS for some small static sites I manage. I still use Hugo and Sass for my personal site, though.
Re: Show HN: Primo – all-in-one IDE, CMS, component library, static site generator
#26- How optimal/minified is the generated code?
- FYI, if you have third party cookies blocked, logging in with GitHub will fail (the login popup opens then immediately closes with no error indication). While failure might be expected, it would be nice to give the user a hint on what might have gone wrong.
Re: Show HN: Primo – all-in-one IDE, CMS, component library, static site generator
#27Or am I missing the feature (I did try and look)?
Re: Show HN: Primo – all-in-one IDE, CMS, component library, static site generator
#28I’ve been moving towards implementing an API based CMS, specifically prismic.io which allows me to setup content elements that marketing staff can edit. Can you explain a bit more about the non-tech user experience for content editors? Would love to find a magic Wordpress replacement with a proper git & tailwind supported workflow for devs and a simple interface for content editors. I’m hoping this fits the bill.
So there's a simplified toolbar (no dev stuff) but they can still add page sections and components from the component library. And when they edit components they only see the fields. You'll be able to control which stuff they have access to in the future.
Re: Show HN: Primo – all-in-one IDE, CMS, component library, static site generator
#29Hi HN. primo is an IDECMSCLSSG (short for IDE, CMS, Component Library, Static Site Generator) I’ve been working on for a few months. The idea came from wanting to host a Notion page at a domain name and not being able to. Once I made the initial version - a basic text editor - the rest of the features just came naturally (except for the SSG, which came from not wanting to deal with hosting). I’d written off freelance…
What's the idea behind calling it Primo?
Re: Show HN: Primo – all-in-one IDE, CMS, component library, static site generator
#30- Is it possible for the generated static site to be HTML+CSS only (no JavaScript)? - How optimal/minified is the generated code? - FYI, if you have third party cookies blocked, logging in with GitHub will fail (the login popup opens then immediately closes with no error indication). While failure might be expected, it would be nice to give the user a hint on what might have gone wrong.
- It's pretty optimal. It's not minifying the HTML so you can see the tree in Github and see changes. But PurgeCSS gets run on the bundle before it builds out, so your css should be as small as possible.
- Hadn't considered that, thanks!