primo
marko
Our great sponsors
primo | marko | |
---|---|---|
26 | 40 | |
1,837 | 13,079 | |
3.9% | 0.6% | |
8.5 | 9.5 | |
9 days ago | 7 days ago | |
Svelte | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
primo
-
Soupault: A static website management tool
> Why is are all static site generators (that I am aware of) are CLI? What prevent simplistic drag and drop GUI/WYSIWYG that generates those clean static files?
Check:
- Tina CMS: https://tina.io/
- Primo CMS: https://primocms.org/
Anyway, you seem to be holding the wrong end of the stick. Static generation is the easy part, what you're looking for is a subset that falls under the CMS umbrella, just search for `CMS+SSG` you'll find a diverse set of solutions.
You can also setup any generic Headless CMS to trigger generation for a static site. Why would someone build a full fledged CMS and limit it to a niche market inside a niche?
- Show HN: Primo – a visual CMS with Svelte blocks, a code editor, and SSG
-
Can a CMS be connected to a static HTML/CSS website?
The easiest thing would probably be Primo, you’ll just have to copy+paste your code in & write some Svelte to set up the content fields.
-
Suggestions for a CMS
Check out Primo it’s FOSS & easy for nontechnical content editors, but you won’t be able to use Hugo with it
-
Tool like WordPress without javascript
Check out [Primo](https://primocms.org)
-
Just got asked by one of my neighbor to create them a website, after they got to know I am a web developer. I want to, but I am not sure how to.
Check out https://primo.so as a way to build static sites for free using HTML & CSS
-
What would you recommend for building a 'brochure' site?
Check out Primo as a way to build a static site & give him an easy editing experience. Not many templates yet but if you find one you like it would be perfect for a small site like that.
-
Show HN: Open-Source Page Block Builder with Remix and Tailwind CSS
The problem you're describing is exactly why I'm working on [Primo](https://primo.so).
WordPress makes content editing easier, but damages the developer experience. So devs reach for JS frameworks in search of more productivity, but then the content editing experience suffers.
I found the solution was to embed a code editor in the CMS itself. As strange as it sounds, removing the distance between the content and code means that devs can build and modify components and whole sites (which are made of both) in a tenth of the time while giving content editors the page-building powers they love.
-
Yes, SvelteKit for the frontend (win)! But what about a CMS dashboard for clients?
Primo
-
What CMS / Frameworks do you use for websites (for clients)?
Primo is simple, super easy for non-technical editors, and FOSS
marko
-
The Best UI Libraries for Cross-Platform Apps with Tauri
SolidJS and Tauri form another potent combination for creating performant, lightweight, and secure experiences. SolidJS is a reactive UI library that is similar to Svelte in the way it compiles away reactivity and updates the DOM directly, but it also incorporates a fine-grained reactivity system reminiscent of libraries like Marko, Knockout, and MobX.
- Mudanças na DevPT
- FLiP Stack Weekly for 06 February 2023
- Marko: An HTML-Based Language
-
The Qase for Qwik: Love At First TTI
Marko is a huge leap in the right direction. It has streaming, partial hydration, a compiler that optimizes your output, and a small runtime. I’ve also heard through the grapevine that Marko V6 also adds resumability to the framework as well.
-
Movies app in 7 frameworks - which is fastest and why?
Nevertheless, the future of JS frameworks is exciting. As we’ve seen from the data, Astro is doing some things right alongside Qwik. However, more noteworthy frameworks such as Marko and Solid are also paving the path forward with some similar traits and better performance benchmarks. We’ve come back full circle in web development - from PHP/Rails to SPAs and now back to SSR. Maybe we just need to break the cycle.
-
Repeating Navigation, Header, and Footer in CSS and HTML?
If you want more, take a look on Marko, fresh, qwik or pug. Dind't tested yet but they look like same as Nunjucks.
-
Client-side Routing without the JavaScript
And that is a similar feeling to the exploration we've been doing recently. Inspired equal parts from React Server Components and Island solutions like Marko and Astro, Solid has made it's first steps into Partial Hydration.
-
Astro 1.0
I haven’t done any serious work with either, but I’ve been following both closely (and have contributed a bit to Astro early on). So this isn’t the hands-on response you specifically asked for, and may not contain new information to you. I’m posting anyway in case it adds context for others.
Qwik City[1] is probably more directly analogous to Astro, Qwik being more analogous to Astro’s integrated renderers. But that highlights one of the key differences.
Astro’s compiler mostly focuses on server rendering of static content (.astro templates, MDX) and bundling client resources along with the logic necessary to hydrate islands. Astro defers to those renderers (and in some cases their own compilers) for any further optimization of the client bundle.
Qwik’s compiler optimizes the component code directly, serializing state into the HTML it renders server-side, for the client bundle to resume from that state. Its output is conceptually similar to Phoenix LiveView (which was mentioned in another sub-thread).
Both are compelling approaches. I think Qwik’s will probably (eventually) have an optimization advantage because that’s a core focus of the client library. Astro will likely have an adoption advantage because it’s client-library-agnostic.
Another framework in the space often gets passed over: Marko[2], which has been doing partial hydration for years at eBay. Marko is probably more similar in approach to Qwik (and as I understand it, getting more similar as they’re going resumable too), but like Astro has its own templating language which enables its compiler optimizations.
Also worth watching SolidJS[3] (whose creator has also worked on Marko), which is tracking partial hydration/resumability on its roadmap. I’m not sure what their approach will look like but there’s quite a lot of insight both in the issue and the creator’s tweets/replies on the topic.
Personally I think there’s a gap between all of these approaches which could leverage type-level analysis to go much further. But that isn’t really feasible when types being available or accurate isn’t a safe assumption.
-
Syntax highlighting library support for modern frontend frameworks
There is no support for newer frameworks like Marko, which have their own file extension (format).
What are some alternatives?
astro - The web framework for content-driven websites. ⭐️ Star to support our work!
Jade - Pug – robust, elegant, feature rich template engine for Node.js
EJS - Embedded JavaScript templates -- http://ejs.co
handlebars.js - Minimal templating on steroids.
solid - A declarative, efficient, and flexible JavaScript library for building user interfaces. [Moved to: https://github.com/solidui/solid]
nunjucks - A powerful templating engine with inheritance, asynchronous control, and more (jinja2 inspired)
qwik - Instant-loading web apps, without effort
doT - The fastest + concise javascript template engine for nodejs and browsers. Partials, custom delimiters and more.
dustjs - Asynchronous Javascript templating for the browser and server
hogan.js - A compiler for the Mustache templating language
JavaScript-Templates - 1KB lightweight, fast & powerful JavaScript templating engine with zero dependencies. Compatible with server-side environments like node.js, module loaders like RequireJS and all web browsers.
eta (η) - Embedded JS template engine for Node, Deno, and the browser. Lighweight, fast, and pluggable. Written in TypeScript