21 points | by steveharing1 4 days ago ago
7 comments
No examples, no mention of why someone would want this, site is broken on mobile.
Hm... A Twitter comment is not documentation, but:
> every skeleton screen you've ever hand-coded is a waste of time
> you're literally measuring padding and guessing widths to build a worse version of a layout that already exists in your DOM
> so I made a package that just reads the real one
Linked from the readme.
But it has animated logo (that you have to click on to start) and chart of GitHub stars progression in time!
Their doc linked at the bottom actually has a pretty nice example.
https://boneyard.vercel.app/how-it-works
This is cool but I'm confused - it says it generates the bones at "build time" not at "runtime." But you're calling this headless bone generator while your app is running, right? That sounds like runtime.
I love seeing things that support Svelte.
I have no idea what this means, and I don't think I'm alone. Make a video dammit.
No examples, no mention of why someone would want this, site is broken on mobile.
Hm... A Twitter comment is not documentation, but:
> every skeleton screen you've ever hand-coded is a waste of time
> you're literally measuring padding and guessing widths to build a worse version of a layout that already exists in your DOM
> so I made a package that just reads the real one
Linked from the readme.
But it has animated logo (that you have to click on to start) and chart of GitHub stars progression in time!
Their doc linked at the bottom actually has a pretty nice example.
https://boneyard.vercel.app/how-it-works
This is cool but I'm confused - it says it generates the bones at "build time" not at "runtime." But you're calling this headless bone generator while your app is running, right? That sounds like runtime.
I love seeing things that support Svelte.
I have no idea what this means, and I don't think I'm alone. Make a video dammit.