Octopress + Github Pages + Dropbox ã§ããã°ãæ§ç¯ May 5th, 2012 VPSã§CMSå ¥ãã¦å度éç¨ãããããç¡æã®ããã°ãµã¼ãã¹ã§ä»ã«ç§»ãããããããè¿·ãã¾ããã èªåãã»ããæ©è½ãããã¦ã¿ãã¨ãã«ãã©ãããã£ããããªãã£ããã¨ãããåºæ¿ããªãã£ãã ããã§ããããªèªåã«ã¸ã£ã¹ããã¼ãããã®ãä¸è¨ã®Octopress + Github Pagesã Big Sky :: githubã¨jekyllã¨octopressã§ä½ãç°¡åã§ã¢ãã³ãªããã° API, appengine, blosxom, C, c, c++, chrome, firefox, freenode, git, github, go, golang, google, google app engine, google reader, greasemonkey, growl, gtk
The way Octopress is being distributed and maintained is nearing its end. There are many things I've always disliked about how Octopress works. So before I talk about the exciting part, I'd like to tell you what's wrong with Octopress. What's wrong? If I'm being harsh, I'll tell you that as it is now, Octopress is basically some guy's Jekyll blog you can fork and modify. The first, and most obviou
I don't want to waste time explaining why I use Emacs all day, every day, and eschew more traditional development environments. Either you already use Emacs and I'm preaching to the choir or you don't and are very unlikely to read this article. I will keep it short: Emacs is the easiest for me to customize, changing the way something works often requires nothing more than adding a couple lines of
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ã©ã³ãã³ã°
ãªãªã¼ã¹ãé害æ å ±ãªã©ã®ãµã¼ãã¹ã®ãç¥ãã
ææ°ã®äººæ°ã¨ã³ããªã¼ã®é ä¿¡
å¦çãå®è¡ä¸ã§ã
j次ã®ããã¯ãã¼ã¯
kåã®ããã¯ãã¼ã¯
lãã¨ã§èªã
eã³ã¡ã³ãä¸è¦§ãéã
oãã¼ã¸ãéã
{{#tags}}- {{label}}
{{/tags}}