sethvincent

The deploy command is https. staticland doesn't use git at all, just deals with the built site produced by whatever static site generator you use.

I'll add some examples to the docs! Thanks for pointing that out.

For jekyll, the short version is you can do something like this:

> jekyll build

> staticland _site/ yourdomain.tld

Thanks, this is an important point. static.land itself may be best considered a demonstration of the open source software. If someone has significantly large files they're looking to host, they would want to host the staticland-api server themselves or consider other options. I'll add some text to the site about this.

Cool, that's a good idea! The granular nginx control definitely sounds nice.

So far not much interest, but this post is also the first time I've done any significant promotion. If you want to go with a really solid static site hosting company netlify.com seems like a great choice. You could also always set up a staticland-api server on your own. Right now I'm using static.land for 12+ of my own sites that I rely on and more on the way, so it's not going anywhere.

Definitely similar. I really love surge, and have too many static sites to pay the per-site costs to get SSL.

Thanks!

That is unfortunate! Looks like the two projects were started around the same time, too. I may add a note to the site/readme pointing people to that repo if they were looking for it.

Static site hosting is cheap, and I'm not super interested in competing with other services with per-site costs. staticland is primarily an open source project that I use for my own purposes, and I'm open to building out static site deployment projects that fit a company's specific use case based on staticland.

Yes. I'll add a note to the site about that. Installing the staticland command-line tool is `npm install -g staticland`

You can get at most of the data via Socrata's API, it's just not necessarily clear how. This new documentation from Socrata helps, though: http://dev.socrata.com/

Thanks! That's a good idea. I've been looking at using cocoonjs in particular as a final chapter on getting js/html5 games into stores: https://www.ludei.com/cocoonjs/

It might still take a few minutes for gh-pages to build the site, but here's the example repo: https://github.com/sethvincent/simple-game-example

I wasn't going to put up a demo since it's so little, but yes, that would be useful. Setting up the repo with github pages now.

Cool! I'm glad you liked it.

Cool, thanks!

You're right about that. For simple games this might not cause issues. For complex games things might get messy. This could be a good thing to work on for a pull request.

Good point. It doesn't. You could pair it with whichever sound library works best for you. I might use it with something like buzz.js (http://buzz.jaysalvat.com/), but there are quite a few others that would work well.

Check out this github repo/wiki of browserify-related game modules and projects: https://github.com/hughsk/game-modules

It's got links to some awesome stuff, including voxel.js (http://voxeljs.com), a set of tools for building minecraft-like games in the browser.

Relatedly, I've been working on a set of js game modules that rely on node.js/browserify called crtrdg: http://crtrdg.github.io – it's not very far along yet, but I'm having fun with it.

Also check out frozen: http://frozenjs.com/docs/ And pixi.js: http://www.pixijs.com/

Awesome! Yeah, I think it'll be a good choice for Ludum Dare.

style / laziness?

If you mean the demos in the coquette github repo, check out: http://coquette.maryrosecook.com/

and: http://coquette.maryrosecook.com/demos/advanced/

And you can see a demo of the game I made with coquette here: http://sethvincent.github.io/BlockSnot/

SEEKING WORK - Seattle, WA / Remote

Email: my hn username at gmail.com.

I'm a designer and developer experienced with Wordpress, Drupal, Django, and Rails/Sinatra. My personal goals are to be a great programmer in javascript and ruby, to learn java and objective-c, and to design beautiful interfaces for a wide range of platforms. I work daily at these goals. I have a strong passion for open source software and open civic data.

In late 2012 I created SeattleWiki.net and in January 2013 co-founded Code for Seattle, a local civic technology group with loose affiliations with Code for America. Along with Bruce Blood at the Seattle DoIT, I helped organize Hack for Change - Seattle, a hackathon held at City Hall on June 1.

I started learning CSS and HTML in 2005, started developing with Drupal in 2006, and have since developed sites with Wordpress, Django, Sinatra, Jekyll, and other content management systems and frameworks. I studied journalism and web development at The Evergreen State College, served as editor in chief of Evergreen's school newspaper, and worked as an advisor to the same school newspaper for 3 years after graduation. As an advisor I trained students on Drupal, CSS, HTML, Javascript, and broad web development/design/publishing concepts. I was responsible for maintaining the organization's websites, the web server, and the local file server.

Work examples:

http://codeforseattle.org The main site for the local civic technology organization, Code for Seattle. Created with Jekyll, CSS, HTML.

http://learnjs.io The site for a book I'm writing about javascript. Created with Jekyll, CSS, HTML.

http://superbigtree.com My "headquarters" website for freelancing and independent projects. Created with Jekyll, CSS, HTML. More work examples at http://superbigtree.com/projects

I'm more excited about this than Google Glass.

This has definitely been useful as a way of determining interest – based on reaction so far it seems like the book premise is good.

I decided to remove the percentage for now since it was an arbitrary number. I'm not even sure what will make the book 100% if I plan to go back and add/revise chapters as js libraries are updated/released. Using semantic version numbers and a roadmap would be better.

I'll add a list of completed/started/planned chapters to the book description soon, which will be much more useful than a percentage.

That's reasonable. I hoped the description would be enough info for people to decide if they are interested, but it makes sense to at least expect a sample chapter or two. I'll be adding a sample and probably doing the first release within the next week.