yetangitu/photo-documentation
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity
photo-documentation/docs
History
sushimustwrite fd859f855b finally figured out a way to reorganize plans/features pages
2013-10-25 11:56:16 -04:00
..
api GET /photos.json should be GET /photos/list.json 2013-07-07 15:04:52 +01:00
configs added contact info 2013-06-04 18:08:43 -04:00
contribute finally fixed that markdown formatting issue 2013-05-14 18:16:23 +01:00
faq finally figured out a way to reorganize plans/features pages 2013-10-25 11:56:16 -04:00
guides minor updates and grammar 2013-08-29 14:56:24 -04:00
hooks Initial checkin of docs 2013-01-28 22:49:14 -05:00
libraries Updating more faqs 2013-10-24 18:12:20 -04:00
plugins created readme for plugins 2013-05-30 19:39:05 -03:00
schemas Initial checkin of docs 2013-01-28 22:49:14 -05:00
stories Formatting changes for story 2013-03-27 14:02:19 -07:00
Readme.markdown updated readme 2013-06-18 15:10:09 -04:00

Readme.markdown

Trovebox / Documentation

Whether you’re looking to install Trovebox yourself or build something with our API, you’re in the right place.

What you’ll find here

Guides

Our guides walk you through installing Trovebox Community Edition.

API

The Trovebox API makes it easy for you to read and write data from your Trovebox site as well as creating Trovebox clients.

Libraries

Trovebox’s language libraries make getting started with our API even easier. Download one of our language libraries, get to know it by reading its documentation, and start hacking.

Plugins

Trovebox comes with a set of plugins you can enable. The plugins section will eventually provide documentation for these plugins as well as how to write your own. Bug someone to write this.

Contributing

The main Trovebox code is released under an open source license, so you can fork the code, install it yourself, and modify the code. If you’re interested in contributing your modified code back to our codebase, our contributors section tells you everything you need to know.

Found a bug?

We track our bugs in Github, and we welcome all bug reports, no matter how small.

Questions?

If you have any questions, we’re here to help. Email our mailing list at openphoto@googlegroups.com or ask in #openphoto on Freenode.