Jacob Paris

I was having the same error. Running on the theory that it was a loading order issue (possibly due to similarity to accounts packages) I changed the name in package.js...

Oh clever – I think this is actually caused by operating under a fork, and it can see both my remote (for the PR) and your upstream. If that's correct...

I've only spent a few minutes with it so far, definitely fond of the concept but I'll have to dedicate more time to see if I like the workflow before...

Thanks, that works. I am calling the template with `{{> project-card title="TITLE"}}` but I don't believe I can set arrays or objects with such a format, which necessitates helpers.

If the core of this feature request is "add some way to serialize data before storing with gp env", then I think Base64 is the best way to encode but...

Relevant doc https://developer.mozilla.org/en-US/docs/Web/Performance/Lazy_loading#images_and_iframes ``

My use case here is uploading avatars for user profiles, and eventually images for forum posts. Verifying the file type would definitely cut down on the ability to upload arbitrary...

@nisarhassan12 Rather than setting heights based on the breakpoints, I set the aspect ratio so the height is automatically calculated. Experimented a bit and `64/50` seems to be the shortest...

I also added the open graph meta copy

I don't get that at any screen size, can you try incrementing the aspect ratio until they go away? Not sure exactly what the difference would be between my screen...