Rendora
kyoto
Our great sponsors
| Rendora | kyoto | |
|---|---|---|
| 2 | 18 | |
| 1,993 | 531 | |
| 0.5% | - | |
| 0.0 | 9.6 | |
| 3 months ago | almost 2 years ago | |
| Go | Go | |
| Apache License 2.0 | 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.
Rendora
-
Feasible approach to SSR?
If you only want to add better support for search engines maybe you can lookup into puppeter and have it SSR for bots and search engines in general. I think there was a golang proyect that did something similar but looks a little bit abandoned: rendora.
-
How to make Svelte play nice with backend and SEO
keep the strategy above, and use https://github.com/rendora/rendora but not sure if it would play nice with SEO/robots (haven't tried)
kyoto
-
Embed the backend as a web worker
the only thing i need to do is port the htmx code to golang and then cross compile to wasm for web and then to mobile and desktop. I am currently seeing that there are other htmx style systems out there that are already written n golang. for example: https://github.com/kyoto-framework/kyoto
- 京都项目正在从GitHub转移到Sourcehut (Kyoto project is moving from GitHub to Sourcehut)
- Kyoto framework is moving to sr.ht from GitHub
- Kyoto project is moving from GitHub to sr.ht
-
Is there some server site rendering Go library that would offer Nuxt like things?
But this baby here https://github.com/kyoto-framework/kyoto is in the early development stages, which is a nice approach imho.
-
Feasible approach to SSR?
htmx requires you to return markup for specific components. So, you’ll need to maintain component template definition in two ways: embed directly into page template, and serve it as an api. IMO htmx is cool, but requires some tooling around it to simplify work. Our team is developing and using kyoto library, focused on server rendering and components approach: https://github.com/kyoto-framework/kyoto
- kyoto: Important update
What are some alternatives?
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
vugu - Vugu: A modern UI library for Go+WebAssembly (experimental)
Sparta - go microservices, powered by AWS Lambda
go-app - A package to build progressive web apps with Go programming language and WebAssembly.
autobd - autobd is an automated, networked and containerized backup solution
forgefed - ForgeFed - Federation Protocol for Forge Services
Aegis - Serverless Golang deploy tool and framework for AWS Lambda
GoatCounter - Easy web analytics. No tracking of personal data.
consul - Consul is a distributed, highly available, and data center aware solution to connect and configure applications across dynamic, distributed infrastructure.
uikit - Wake up, Samurai. We have a project to build
nginx-prometheus - Turn Nginx logs into Prometheus metrics
gomodest-template - A template to build dynamic web apps quickly using Go, html/template and javascript