rubyworks / brite Goto Github PK

Ultimately I want to be able to serve Brite sites via the rack server without having to generate the site on disk. Currently the rack server provided simply serves up a disk location, so generating the site first is necessary.

This feature would allow brite sites to be served by rack-capable hosting services (like Heroku) very easily.

hi.

as3:/brite-site# brite
/usr/local/ruby/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in require': cannot load such file -- facets/hash/rekey (LoadError) from /usr/local/ruby/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:inrequire'
from /usr/local/ruby/lib/ruby/gems/2.0.0/gems/neapolitan-0.4.1/lib/neapolitan/core_ext.rb:1:in <top (required)>' from /usr/local/ruby/lib/ruby/gems/2.0.0/gems/neapolitan-0.4.1/lib/neapolitan.rb:5:inrequire_relative'
from /usr/local/ruby/lib/ruby/gems/2.0.0/gems/neapolitan-0.4.1/lib/neapolitan.rb:5:in <module:Neapolitan>' from /usr/local/ruby/lib/ruby/gems/2.0.0/gems/neapolitan-0.4.1/lib/neapolitan.rb:1:in<top (required)>'
from /usr/local/ruby/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in require' from /usr/local/ruby/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:inrequire'
from /usr/local/ruby/lib/ruby/gems/2.0.0/gems/brite-0.7.0/lib/brite/controller.rb:1:in <top (required)>' from /usr/local/ruby/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:inrequire'
from /usr/local/ruby/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in require' from /usr/local/ruby/lib/ruby/gems/2.0.0/gems/brite-0.7.0/lib/brite.rb:10:in<top (required)>'
from /usr/local/ruby/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in require' from /usr/local/ruby/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:inrequire'
from /usr/local/ruby/lib/ruby/gems/2.0.0/gems/brite-0.7.0/bin/brite:2:in <top (required)>' from /usr/local/ruby/bin/brite:23:inload'
from /usr/local/ruby/bin/brite:23:in `

tks a lot

Consider MathML plug-in for future version.

Maybe it would be useful to add acquisition support akin to Zope.

Require backend engines only when used. Currently all are required when brite is executed.

Consider adding Sass support in the future. (http://sass-lang.com/)

Perhaps it would be best if Brite had support for an additional.style type of file, instead of overloading .page which is now used for creation of stylesheets.

Need to improve truncation of summaries. This is tricky for brite because it allows multiple formats per-document, so word counts aren't easily calculated with accuracy.

One alternative I noticed by another blog engine was to use a marker (eg. '~~') to indicate the cut-off point. This is nice b/c it allows the writer to decide where the summary cut-off should be.

Note we can also offer a summary field in the YAML front matter that would be used instead if present.

Need to add pagination support for blogging. Once could of course manually add pages that covered only a given period or number of posts, but it would be nice if this could be done automatically somehow.

Pagination can be a challenge for a static site, since each page must be a separate file. I think it would be best to keep the design highly structured around time periods. We could offer an option to paginate on a monthly or yearly basis (default to yearly), and set which page to be paginated. This would create multiple paged for the same template page, but each having the different set of posts.