Show HN: Review my project: Git Code Press, blogging via git
gitcp.com
gitcp.com
The image fails in your test: http://gitcp.com/sorenbs/Git-Code-Press/markup-test
Rather than four hands showing you what to do having the numbers 1, 2, 3, and 4 as circle dots or something would be more clear.
How do I customize the header/footer?
I find Blogger and the other online wysiwyg style systems to be too much of a hazzle to work with. I wasn't aware of github pages, but it looks really nice. I will probably find some inspiration there. From what i can tell github pages lets you create an arbitrary website structure with arbitrary styling, whereas the goal with gcp.com is ease of use and a nice standard layout (sort of like latex). That is also why i haven't added header and footer support, but i should probably make some minimal customaization available, like name and tagline.
.textile is sort of a convention for files with textile markup. I could add support for other markup formats. What would you suggest?
"I find Blogger and the other online wysiwyg style systems to be too much of a hazzle to work with" Can you be more specific? blogger lets you go to plain text editor and not use the wysiwyg so that is a moot point. I have issues with blogger, but that isn't what I would pick on.
What i believe gitcp.com does better than blogger is this: No need for a web interface (might be negative for some); textile markup is much easier to write than html or using some gui editor, and gives a much nicer result than raw text; syntax highlighting of code snippets (this is the primary use case for me).
From a blog I expect at least an RSS feed of posts, a publishing date on each post, and comments.
You could also embrace the possibilities of git, and for example provide previous versions of blog posts, or even highlight differences between versions.
Example blogs: http://shebang.ws/, http://a3nm.net/blog/, http://vlog.antonin.delpeuch.eu/ :-).
As you can see, I find there are a couple of unanswered questions. Maybe you could add a simple FAQ or something :) Still, the landing page does a great job at picking someone's interest, so good wok for that.
I'm glad you like the landing page. I have added an example showing the markup that generated the frontpage. Hopefully that will make it more clear how the system transforms textile into html.
Nonetheless, the result looks nice :)
What kind of documentation would you like. A tutorial or rather a complete documentation of the markup?
When i receive such a request i use the object api http://develop.github.com/p/object.html to get a list of files in the repo, and then fetch *.textile and .png files which are new or have a new hash. I don't use their libraries, i just consume the rest interface directly.
I store the files in mongodb together with some metadata, and for processing i use a nice scala web framework called liftweb. For textile parsing i use http://www.eclipse.org/mylyn/downloads/ And for code formatting i use google-code-prettify
Anything else?