Show HN: Exposé – a static site generator for photos and videos
github.com
github.com
Last time I was on HN there was some interest in what I was using for the backend, so I cleaned up the code a bit and put it on github
As much as it's the artist over the tool - I think I'm going to invest in this camera as my next step into photography. I've seen nothing but praise for the GX7.
Figure if I like the output I may as well invest in similar tools and practice. :) (Unless most of those photos are w/ the vintage lens that went unnamed...)
I chose the GX7 because it's really small and light with decent image quality. If I were getting started now I'd be taking a serious look at the sony A7 M1.
http://www.imaging-resource.com/cameras/olympus/e-m1/vs/sony...
Were the video's created using the GX7 time lapse feature?
For anyone looking to use the polygon word wrap feature as in the demo on the Github page with the Eiffel Tower, take a look at its responsive behavior before you make that post. As you shrink the window down on jack.ventures, some text can be cut off, or no longer show up on a clear portion of the image like a wall.
This isn't a bug with the software so much as a flaw with the magazine "words on image clearing" style layout that doesn't translate perfectly to the web medium.
So if you resize the window and reload the page it should fit everything correctly again.
A rough design pattern I've seen is Desktop resolutions: use layout in terms percent. For instance: left side of text begins at 50% of image width.
Tablet and mobile resolutions: fixed layouts for each resolution supported.
If you're doing the polygon containment using javascript, I imagine implementing such behavior might get really complex.
My philosophy for mobile resolutions is to just deliver the desktop experience. The text will be tiny yes, but you can just pinch to zoom. Sites that lock down the zoom kind of annoy me personally so that's why I did it that way.
The second theme does have media queries for mobile sizes though, since it doesn't rely on the text being in a particular spot to be readable.
Interested in making things at Flickr? Drop me a line at eric at flickr.com :)
command -v convert >/dev/null 2>&1 || { echo "ImageMagick is a required dependency, aborting..." >&2; exit 1; }
Reminds me of ThumnsUp: https://github.com/rprieto/thumbsup
just added MIT license.txt
Here is the output if someone is interested to brainstorm about this problem. I edited the output a bit to make it slightly more readable.
<begin output>
Scanning directories.
Populating nav.
Reading files...........................
................................
................................
............................................
<some_conversion_errors_b/c_of_corrupted_file_ommited>
..............................................................
..............................................................
..............................................................
..............................................................
..............................................................
.........................
Building
HTML..........................................................
..............................................................
..............................................................
..............................................................
..............................................................
..............................................................
..............................................................
................................................/Users/my_user
_name/Downloads/Expose-master/expose.sh: line 139:
/usr/bin/sed: Argument list too long
Starting encode
fotos0001
fotos0002
fotos0003
...
<huge_error_of_same_corrupted_image_omitted>
...
fotos0489
fotos0490
fotos0491
</end output>
Anyways, I checked the image which was indeed corrupted, so ImageMagick was right on the money on that one. I still don't get it though why there's no HTML in the HTML file.
Maybe all of the filenames are passed as a single argument to sed?
Interestingly, 200 didn't work, but it also gave the "/Users/mettamage/Downloads/Expose-master/expose.sh: line 139: /usr/bin/sed: Argument list too long" error, while the others did not.
Edit: tested out all combinations. Argument list too long is indeed the error.
I got this with 188 pictures: Scanning directories. Populating nav. Reading files......................................................................................................................................................................................... Building HTML........................................................................................................................................................................................ Starting encode fotos0001 fotos0002 .. etc.
And I got this with 189 pictures.
Scanning directories. Populating nav. Reading files.......................................................................................................................................................................................... Building HTML........................................................................................................................................................................................./Users/mettamage/Downloads/Expose-master/expose.sh: line 139: /usr/bin/sed: Argument list too long
Starting encode fotos0001 fotos0002 ... etc.
xargs it is!
Do you still get the error if the corrupted image is removed? If the files aren't too big, could you post it somewhere?
I was using a tool one of my friends made, with a similar idea, just put images and videos in directories and have a script automatically generate a nice output. It can be found at https://github.com/jlaine/django-coconuts, but yours looks spectacular. I'm tempted to switch.
In a similar vein, I have a Jekyll plugin that reads folders of images and can create galleries: https://github.com/callmeed/jekyll-image-set
Nice that you have video support. Can't wait to give this a try.
I appreciate the use of simple bash shell script instead of a scripting language with lots of runtime dependencies.
I want to add that sites look awesome and this is perfect for large number of people, I just want to thank you one more time for making this, it is also excellent starting point for photo sites.
Same here, it has been floating around my mind for a couple of weeks now and then this shows up :)
Since most of my photographs are organized by trip or theme, this is perfect.
Also, it's not at all responsive to different viewport sizes; this might be a good thing to address.
EDIT: Oof, that's a kick in the karma. Aah, well.
Also it's "sort of" responsive, it just doesn't handle window resize right now. I didn't think that was an important use case, but now multiple people have pointed it out so I'll add it.
And I like your sites! Now... all I need is to be a better photographer, then I'd be able to actually create something nice with your script. Hahaha.
Do you have any other sites doing photo/video stories which have been an inspiration for this project?
and the the NY times multimedia presentations: http://www.nytimes.com/newsgraphics/2013/12/30/year-in-inter...
On mobile it should load the mobile-size version, which is much smaller than what you see on the desktop.
Would you consider making a pull request with an alternate theme (there are two already included)? You could adjust the styling as you see fit, and so forth. Best of all, were you to actually use this, you could modify the compression settings and even the scaling in a way that fits your needs, even if you don't end up making a PR on the original.
Looking at this, there are lots of ways where it feels like there could be things added to this to make it better -- a photo reorganizer, or something that would let you auto-tag / order photos from within the interface. Those kinds of things would be really neat, but are likely outside the scope of the (amazing) tool that Jack was kind enough to give us. If one were to go far enough down those rabbit-holes, pretty soon one would have rewritten it as a CMS. ;)
I have little else to add, but I wanted to let you know anyway :) Keep it up!
I wish I had that freedom.
Unless you're just trying to get away with hosting your whole site as a GitHub page ;)
I don't understand why people use a database for content that (for the most part) doesn't need one.
You could easily replace his rsync with an s3cmd sync to ship the stuff straight to the S3 bucket.
Sure, S3 may cost more per byte shipped than serving it yourself, but probably not for a personal site (if you factor in the need to pay for a running server and the extra hassles and time cost involved with maintaining that server). You can pay for a lot of S3 bandwidth with what you pay for even a cheap VPS.
At the end of your day your content is already being stored in a database or in some custom format to be able to generate the static site aways. You have a lot more options if you go through a database first vs a custom static format.
Simplicity? If the content is not an application but a static publication I'm left wondering how making it dynamic would improve anything...