darwin / index forked from hashpage/index

Index for HashPage resources

This URL has Read+Write access

darwin (author)
Wed Jul 08 18:33:43 -0700 2009
commit  eed67a838c84fae3f8f7f41d7178a5763131d98c
tree    ee636031ad63e29d3a31928796b4922b0d6cf238
parent  05dc8b7bdee952e23b3e8048135c505de4d009b3
index /
name age message
file .gitignore Loading commit data...
file .gitmodules
submodule engine - 3c30b71
file rakefile
file readme.md
directory skins/
directory widgets/
readme.md

HashPage Index

This is the collaborative space for HashPage developers.

How does it work?

We automatically bake skins and widgets from this repository and publish them on live hashpage.com to make them available to users.

Structure

Just look around. It should be self-explanatory.

Skins and widgets have following directory structure:

/skins/<author>/<name>/<version>/**
/skins/<author>/<name>/readme.md
/skins/<author>/<name>/meta.yaml

Default and required version is "master". Other versions are optional. File meta.yaml contains meta data about widget or skin. Use your github username in place of author (it is easier for us to track).

How can I add my asset into index?

  1. fork index repository
  2. add your author and widget/skin directory
  3. hack!
  4. send pull request to user "hashpage" on GitHub

How are the assets deployed on hashpage.com ?

Every time we run deploy script, all assets are baked for production and uploaded to HashPage server. You can see current index version in top-right corner in HashPage editor.

You can browse current production state here: