I think, it depends too many 3rd-party libraries. Could you just merge functions from these libraries? If it just depends on emacs and org-mode, that will be very nice.

Design

Current theme still has lots flaws and bugs, which may need some refinement and
redesign. For example, the TOC anchor doesn't locate to the right section due to
css margin.

Implementation

Pluskid's blog is really a good design using bootstrap, see
http://freemind.pluskid.org/, I'll import some elements from it.

Design

Static site need third-party tools to facilitate things like comments,
statistics, site search, etc. Org-site already has support for comments using
disqus, but still lacks support for site statistics, search engine, gravartar,
etc.

Implementation

• site statistics: google site?
• site search: google customize search?

Design

When you write page using org-site, most time you work with localhost, you need
quick site preview, quick publish to localhost, quick page modification and
refinement. You publish your site to public when you feel 100% comfortable with
your work.

That means you need a complete working environment which just works in
localhost, such as necessary css/js files of jquery/bootstrap/mathjax, etc. But
org-site don't really need this css/js files when publish to public, all it need
is some links to the official file links, something like
http://code.jquery.com/jquery-2.0.0.min.js. You don't want the compressed js
files to pollute your tuned org-site source files, right?

Implementation

• Add an optional argument org-site-mode to org-site-publish, which can be
  assigned to localhost or public, and the default value is
  localhost. When org-site-mode is localhost, set all css/js links to
  local disk css/js files, else, set all css/js files link to official public
  links. Pretty simple, ha.

Design

Org-mode support something like literate programming, you can see
http://orgmode.org/worg/org-papers.html for details. And what I want basically
is, when there're code in org article, there should be a downloadable tarball
which contains all code appeared in this article.

Implementation

Org-mode support something like code weave and tangle, deeper exploration is
needed to finish this feature.

Design

code block need some extra enhancement to make it work more fluent:

• it should be copiable with a single click
• it should be collapsible with a single click
• configurable line number support

Implementation

I guess these minor features need some work with js, which I'm not familiar
with, so, lots of learning work.

Design

Math support is important for science and technical writings. Org-mode have
math support through a LaTeX syntax, while export to html, org-mode invoke
MathJax for html rendering.

But MathJax itself is too big to be include locally as bootstrap/jquery by
org-site, so when preview html in =localhost= mode, we use a fallback
dvipng strategy provided by org-mode.

Implementation

• Add MathJax cdn link when org file contains math.
• Functions to check whether or not an org file contains math.
• Fallback to dvipng when localhost.

Design

This feature is inspired by pluskid, see http://freemind.pluskid.org/misc/printable-version-pdf-of-this-blog/.

In a word, each org article should be provide a downloadable pdf link beside the generated html page, of course, the pdf link should be a configurable option.

Implementation

Since org-mode has built-in support for pdf export, this should not be hard to implement. Problems may raise when considering CJK support, thus we need to define a proper org-to-latex settings.

If you view github-pages of org-site(http://xiaohanyu.github.io/org-site/) in mobile browser, or if you adjust you desktop browser to a small size, then the navbar items disappeared. Maybe it's a but related to bootstrap-responsive.

Design

org-publish has a :htmlized-source option, with which you can export htmlized
org source together with html files, see
http://orgmode.org/worg/worg-setup.org.html for a live example.

Implementation

The implementation should be easy:

• Add a :htmlized-source option to org-publish
• Add proper html links to generated html files

Design

org-site will generate some index files during org-site-publish process, which
will be deleted by org-site-post-publish process by default. Sometimes, we
need to keep these generated files for debug purpose, so an extra debug option
is needed.

Implementation

Just add a org-site-debug option in org-site-config.el, and set it to nil
by default. Check org-site-debug in related functions.

Design

These feature is not necessary for a static site, but when you use org-site as a
static blog generator, then category/tag/archive is a must.

Implementation

Like auto-generated index, we need some utility function to generate
category/tag/archive page.

Design

Currently, the home page of org-site is generated through a user provided
index.org file, this is flexible, while some other people don't like it. They
need something like blog's home page, which can generate home page contains a
list of recently published posts. An example see:
http://freemind.pluskid.org/

Implementation

• Add functions to get the abstract of posts
• Add functions to aggregate these abstract to form a home page.

Design

RSS support is a must of org-site.

Implementation

I'm not familiar with RSS, so may be there're lots of work to do.

Design

Theme support and easy customization is one of the most important design goals
of org-site. Internally, org-site use mustache.el and html template to
generate html pages, these process need a explicit interface guide to facilitate
third-party theme customization, for example, which variable represents:

• site title
• site author
• site url
• page toc
• page contents

And based on the detailed, explicit theme customization guide, we can provide
more built-in theme support.

Implementation

These feature contains documentation and coding work, and I think documentation
work is more time-consuming than coding work.

hi.

看了你页面https://github.com/xiaohanyu/org-site的Installation部分，我先去访问了https://github.com/dimitri/el-get里面所显示的链接地址http://tapoueh.org/emacs/el-get.html，
然后新建了~/.emacs,放入如下内容：

(require 'el-get)
(add-to-list 'el-get-recipe-path "~/.emacs.d/el-get/recipes")
(setq el-get-verbose t)
;; personal recipes
(setq el-get-sources
'((:name el-get :branch "master")
(:name magit
:before (global-set-key (kbd "C-x C-z") 'magit-status))
(:name expand-region
:before (global-set-key (kbd "C-@") 'er/expand-region))
(:name descbinds-anything
:after (progn
(descbinds-anything-install)
(global-set-key (kbd "C-h b") 'descbinds-anything)))
(:name goto-last-change
:before (global-set-key (kbd "C-x C-/") 'goto-last-change))))
;; my packages
(setq dim-packages
(append
;; list of packages we use straight from official recipes
'(gnus bbdb switch-window vkill google-maps pgdevenv-el
mbsync asciidoc smex geiser xcscope multiple-cursors
anything descbinds-anything pcmpl-git magit-view-file
emacs-goodies-el sicp auto-dictionnary keywiz pandoc-mode
pgsql-linum-format psvn rect-mark crontab-mode icomplete+
php-mode-improved rainbow-delimiters muse deft dpans2texi
markdown-mode color-theme-solarized protobuf-mode paredit)
(mapcar 'el-get-as-symbol (mapcar 'el-get-source-name el-get-sources))))
(el-get 'sync dim-packages)

然后运行emacs --load ~/.emacs就安装el-get成功了吗

Design

org-export-as-html will export a simple TOC(Table of Contents) by default, what I want is:

• configurable TOC, user can enable or disable TOC generation when publish org-site
• style improvement, this point is inspired by page like this: http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.html, I want something like this, floatable, collapsable, etc.

Implementation

• Do some hack about org-export-as-html, and seperable toc from <body>...</body>, then render it with mustache.el
• Need some CSS work, js may also needed.

Design

At first, I just want org-site to work, which means I should come up with a
workable projects. Now org-site has hundreds line of code, some of the code
is dependent tool functions, which can be unit tested easily. The core of
org-site is not easy to test(may need lots of mock and stubs), but the
tools function need some basic testing work. Travis CI maybe also be
imported in.

Implementation

• Write some ert test for tool functions.
• Basic Travis CI support.

Design

RSS support is a must of org-site.

Implementation

I'm not familiar with RSS, so may be there're lots of work to do.

Design

Org-mode has reached version 8.0, which is the most disruptive major version
of Org(http://orgmode.org/Changes.html). So maybe there're lots
incompatibities between current org-site and org-mode 8.0.

Implementation

First find out whether or not org-site works with org-mode 8.0, if not,
find the underline issues and make a compatibily layer.

Design

o-blog has a beautilful demo site, which is valuable for org-site to steal.
see http://renard.github.io/o-blog/features.html for a live demo and technical
details.

Implementation

There're lots of learning work, especially about web design, which I'm still not familiar with.

When I evaluate this:

(let ((el-get-sources))
(add-to-list 'el-get-sources
             '(:name org-site
                     :type github
                     :depends (mustache)
                     :pkgname "xiaohanyu/org-site"))
  (el-get 'sync (mapcar 'el-get-source-name el-get-sources))
  (require 'org-site))

I get this:

El-get can not find a recipe for package "mustache"