These are chat archives for internalfx/quickshot

31st
May 2016
Bryan Morris
@internalfx
May 31 2016 00:12
@/all Hey guys,
Just wanted to say quickshot has not been abandoned
progress on 2.0 marches forward.
blogs/upload, blogs/download, pages/upload and pages/download have all been rewritten in ES2015 JS
I have completely reworked the 'on-disk' format of the data
blogs are stored as so blogs/{blog-handle}/{article.id}-{article.title}/
example blogs/health-insights/34523453-Lactose Intolerance/
Bryan Morris
@internalfx
May 31 2016 00:18
This makes it much easier to navigate the data on your computer, but also allows me to parse it
within the folder there are now 3 files
article.html
article.json
metafields.json
article.html contains the body copy in its own html file.
making it super easy to make a few changes in your favorite editor
article.json contains the rest of the article data.
the html file is merged back into the article.json before uploading
metafields.json holds all the metafields.
pages work similarly to blogs...
As with Blogs and pages, Products also split out the html into a separate file, making editing the content a snap.
also, products now add the file extension to images, so that your operating systems ( and image editors) are less confused.
Bryan Morris
@internalfx
May 31 2016 00:23
The on-disk format is much more consistent (and sane) now.
Rick Davies
@rickydazla
May 31 2016 00:32
Dope!
Meta fields o
?
Bryan Morris
@internalfx
May 31 2016 00:33
yeah
metafields on articles, pages and products
Rick Davies
@rickydazla
May 31 2016 00:34
🎯
This is pretty random but would it be possible to have qs on a server and trigger it to run automatically?
Bryan Morris
@internalfx
May 31 2016 00:35
sure
Rick Davies
@rickydazla
May 31 2016 00:35
Yeah? Using gulp or something
Bryan Morris
@internalfx
May 31 2016 00:35
just cron would work
anything that can run a command at a set time
Rick Davies
@rickydazla
May 31 2016 00:36
Cool. Since users can upload things via theme settings I thought it would be cool to schedule a download, run assets thru image optim, commit to Git master and re-upload
Bryan Morris
@internalfx
May 31 2016 00:37
hmmm....I would be cautious about that.
You wont know which images have already been optimized...there is a risk of optimizing an optimized copy
Rick Davies
@rickydazla
May 31 2016 00:38
I like to do things pirate style. Shoot first and ask questions later
Bryan Morris
@internalfx
May 31 2016 00:38
Is that a real need? That problem could be solved pretty simply.
Rick Davies
@rickydazla
May 31 2016 00:38
Image optim won't do anything to an already optimized image
Bryan Morris
@internalfx
May 31 2016 00:39
oh really?
how does it know?
size/dimension spec
Rick Davies
@rickydazla
May 31 2016 00:39
Well, it's lossless compression so there's only so much it can do
Bryan Morris
@internalfx
May 31 2016 00:39
ohhhh ok
Im thinking jpegs
Rick Davies
@rickydazla
May 31 2016 01:49
Yeah JPEGs. I would probably do Image Optim then TinyJPG but I don't think either of them will "over optimize" an already optimized image. I would do it to catch those 4MB slider images that often ended up in rotation and cause bounce rate to spike wildly
I might do qs theme download assets/slide_
... I might even do it in two commits so that optimization can be rolled back if it really screws up the visual quality
Although there are bigger issues that Shopofy
needs to sort out
Bryan Morris
@internalfx
May 31 2016 15:05
interesting...