website
website copied to clipboard
NoAgenda
Update to Symfony 6.4 / AssetMapper
I love symfony/asset-mapper. I'm dropping webpack from all my projects, because it's so much easier to deploy front-end assets.
I'm happy to help with that if you're interested. Most of the javascript here is already in stimulus, so the basic website won't be hard to move.
The PWA stuff, though, I don't know about. Indeed, I came here looking for a Symfony site that is also a PWA.
I bumped my local version to 6.4, no issues. Some deprecation warnings which are easily fixed.
Switching to AssetMapper is a somewhat bigger step, but it would allow getting rid of the webpack/encore build step altogether. The javascript is mostly stimulus, and the stylesheets could be switched from scss to plain css.
It's a task I'm happy to take on if there's support for doing this.
I'm only semi-interested in doing it myself because I don't know enough about the component yet to decide. If you want to do create a PR I'm very likely to accept it.
Let me clean up the application a little bit before you start. I experimented with a lot of features that are now defunct and I don't want to support anymore so there's a lot of cruft right now. Are there any specific features you want to contribute to the site or is it simply for help with development? (both are appreciated)
Upgrading to AssetMapper makes deployment much easier. And makes development easier, too.
For some reason, I thought your app could be deployed as a PWA (Progressive Web App). I was mistaken, but it'd be a great candidate for one. Alas, I'm struggling with how to deploy that.
In my dev version of the app, I use sqlite, so it's super-easy to setup for development.
Needs a service-worker, icons, and routing, but honestly not that much. Then the app could work offline, which would be pretty cool.
I'd love to see this article re-written for Symfony: https://alicia-paz.medium.com/make-your-rails-app-work-offline-part-1-pwa-setup-3abff8666194
On Tue, Dec 12, 2023 at 9:41 AM Tim Goudriaan @.***> wrote:
Why isn't it a PWA? What are the criteria?
— Reply to this email directly, view it on GitHub https://github.com/NoAgenda/website/issues/73#issuecomment-1852168953, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEXIQKXJDUY3BJKDSUMMVTYJBUKJAVCNFSM6AAAAABAK7VHGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJSGE3DQOJVGM . You are receiving this because you authored the thread.Message ID: @.***>
Ow right. No that's true. I was working on that but I finished prematurely as the last rewrite was already taking up too much time, but I'd still be open to make it fully offline-capable.
If we do make it offline, I want users to be able to specify and see which episodes get downloaded and were downloaded in the past, so it would need a bunch of UI work as well.
As there are quite a few anti-JS people in the target audience, the website will always need to keep working without JS enabled though.
FYI, I created a separate branch cleanup where I removed a bunch of old code. If you want to start making changes, I would start there.
Hmm. Okay. Now that javascript can be used in a modern fashion directly in the browser and the build step is trivial, I'd rather have more javascript. Especially stimulus components.
But of course, running offline requires javascript.
I thought that AssetMapper was going to make PWA's easier, but it turns out that service-worker doesn't work with the importmap tag, so you have to have some sort of build system, to build the required javascript, like Google Workbox:
https://github.com/GoogleChrome/workbox https://medium.com/the-web-tub/build-a-pwa-using-workbox-2eda1ef51d88 https://github.com/GoogleChrome/workbox
I haven't done this yet, but I have an web-based application that needs for the users to easily browse some data and add photos. A PWA would be perfect, but I haven't found a Symfony-based PWA to use as a model.
I'll probably hold off on making too many changes until the cleanup branch is integrated, but then I'll jump in.
On Tue, Dec 12, 2023 at 2:11 PM Tim Goudriaan @.***> wrote:
Ow right. No that's true. I was working on that but I finished prematurely as the last rewrite was already taking up too much time, but I'd still be open to make it fully offline-capable.
If we do make it offline, I want users to be able to specify and see which episodes get downloaded and were downloaded in the past, so it would need a bunch of UI work as well.
As there are quite a few anti-JS people in the target audience, the website will always need to keep working without JS enabled though.
FYI, I created a separate branch cleanup where I removed a bunch of old code. If you want to start making changes, I would start there.
— Reply to this email directly, view it on GitHub https://github.com/NoAgenda/website/issues/73#issuecomment-1852649640, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEXIQJHWFZPDMAP2V6VJ6DYJCT4JAVCNFSM6AAAAABAK7VHGWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJSGY2DSNRUGA . You are receiving this because you authored the thread.Message ID: @.***>
I've been doing a lot of work with PWAs lately, but the bundle requires AssetMapper and stimulus to work. Do you think you'll be using it? If so, I think I can make some progress on turning install an installable app that runs offline (except for streaming the podcast, but there's surely a way to do that, too).