We don't have a consistent path right now in the route handler.

The recent updates are nice, but I still feel that something is missing.

• Update the description so the text is bigger. 16px font
• 100% height of the flex container
• Make the description blockquoted... indent and add a border left

I’m a GDE—honest!—so I hope you don’t mind me adding my site to the list.

It might be prudent if the HTML is available to render the first couple of feeds... really, this is to game PSI, not sure if it's worth it.

Anyone who uses the module should be able to easily provide their own templates.

• Add the ability to have custom CSS
• Add the ability add extra images
• Add the ability to change the templates.
  • We should just basically have a folder for the assets and if the file exists use that, else use the base...
• Service Worker needs to know about all the new assets and updates, right now it's a static build.

There is quite a lot to think about

• Add in a custom server route
• Add in a central location of config files and work out how to serve them
• Add in a way to debug when on localhost
• Ensure aliasing works correctly.
• The all feed needs to be fixed up properly

Think about word boundaries, or ellipsis...

Make it so that it maps to some configure origin...

• Text is illegible, needs to be over 14px.
• Needs a meta description

A 500 error for a proxied RSS feed causes issues with the XML parser in the page. We should only really process the feed if its a 200 range response (or cached etc.)

Currently it share's from my account or at least references me.

cc @nomadkoala

Need to keep it contained in the current file though.

I removed it earlier on, we should add it back in.

It's large, and it shouldn't be included.

• DOM is too big. 6,224 nodes, aim to be less than 1500.
• Meaningful first paint is at 1s, but Consistently interactive is 8s. Have a think...
• Perceptual Speed Index is too high.
• Suggests to minify JS, however there is an issue somewhere.

I got really frustrated with the styling.

• Make it cleaner
• Subtle accents
• Center the heading.

The UI is there, it should really do something useful on desktop.

This can be seen when new templates are updated, for some reason once installed and activated the new template is not compiled and the old one is used...

Suspect it's because of parse URL

Be a good citizen.

• Make a postinstall build step, if this is deployed anywhere every thing needs to be built so it can run
• Work out a way to start the server - it might have to be a custom index file
• Refactor configuration so that it can be specified outside of the package

Right now, the proxy server will hit the network to update it's resources, it has no need to because all the data is currently held in a memory cache...

Clean up this entire area.

Specifically 'all' should be ok and the main deck too.

this will work because we don't actually cache the HTML resposen, we have all the templates and the data so we stitch those together in the SW.

It looks like the proxy SW logic is trying to be too clever. Given that the SW can read from the cache, we should only ever return /proxy web requests from the network as the resilience is already in the SW...

Just add support for theming the header.

The proxy will race on the cache or the network to try and be as fast as possible, This presents some issues where data might be stale.

Move to a network first approach, always return from the network unless there is an error or a timeout,

Hello. I heard about this project while reading Paul's blog and when I visit https://webgdedeck.com on my Android phone, the browser (Chrome, Opera, Firefox Focus) triggers a download instead of opening the page. I haven't checked if this error happens in the desktop yet.