I'm a fan of static generators too, but one large con for a lot of people is lack of commenting. Personally I like the article-with-no-comments format, but it's not for everyone. You can use Disqus or similar, but it has its own issues starting with the fact that you give all your data to someone else. More pros for static generators are that you can use whichever editor you want and you get version control easily too.
On 22 July 2013 10:33, Steven Degutis <sbdegu...@gmail.com> wrote: > The more I think about the static blog generator idea, the more I think > it's different enough to be a separate project. > > But anyway, I already wrote this list of pros/cons to why I think static > blog generators are better, so might as well post it: > > Pros: > > - Runs anywhere you can host HTML, such as Github Pages (which is free > btw) > - No need for authentication/authorization code > - No need for WYSWYG editor > - No need for server component > - No need for a database > - No need for an admin console (probably replaced by config files) > - Import/export is probably easier, since blog entries are just files > > Cons: > > - Can't make middleware plugins (but I can't think of a need for one) > - Probably would need ugly/tedious user-editable config files > - Can't remember the last one, but (or thus?) it probably wasn't > important > > -Steven > > > On Sun, Jul 21, 2013 at 5:23 PM, Steven Degutis <sbdegu...@gmail.com>wrote: > >> Lately, a lot of people are moving away from dynamic blog engines like >> Wordpress, and starting to use static blog generators like Jekyll. >> >> You may want to consider this route instead. I'm sure a plugin system >> would still be relevant and useful for a static blog generator. >> >> -Steven >> >> >> On Thu, Jul 18, 2013 at 9:24 AM, Timothy Washington >> <twash...@gmail.com>wrote: >> >>> Hello, >>> >>> I'm thinking of how to build a composable blogging engine in Clojure. >>> There have been a few attempts at this, with >>> cow-blog<https://github.com/briancarper/cow-blog>and >>> my-blog <https://github.com/georgerogers42/my-blog>. But these seem to >>> be abandoned, and not heavily used. Vijay Kiran, last year, even wrote a >>> series of blog posts (see >>> here<http://www.vijaykiran.com/2012/01/17/web-application-development-with-clojure-part-2/>) >>> about building a blog engine. As far as a list of posts goes, the data >>> structure for each record was simple: >>> >>> - title >>> - content >>> - status >>> - created-date >>> - published-date >>> - author >>> >>> >>> I think this is the most basic thing you could do, to get running. But >>> I'm thinking of approaching the feature set of >>> Wordpress<http://codex.wordpress.org/WordPress_Features>. >>> So I'm thinking of the Data Structure(s) of features like: >>> >>> - Web UI component; wyswyg editor, themes >>> - Server component; embeddable in Compojure or Pedestal >>> - Database component; >>> - raw data structures, txt, rtf, images, audio, videos, documents >>> - adapters for Datomic, SQL(Postgres, etc), NoSQL (Mongo, etc) >>> - tags / categories for content >>> - Authentication & Authorization; OpenID >>> - Workflow component; preview, collaboration & editor review >>> - Commenting component; default or an external comments service, >>> like disqus <http://disqus.com> or discourse<http://www.discourse.org> >>> - Administration Console >>> - Plug-in support >>> - Import / Export >>> - Multi-lang / Internationalization >>> >>> >>> I know that I currently wish I had a Clojure weblog engine that I could >>> stick into a site I'm building. If there's already something available, >>> I'll obviously just use that. But otherwise, is this something that would >>> be interesting to people? >>> >>> >>> Thanks >>> >>> Tim Washington >>> Interruptsoftware.ca / Bkeeping.com >>> 416.843.9060 >>> >>> -- >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To post to this group, send email to clojure@googlegroups.com >>> Note that posts from new members are moderated - please be patient with >>> your first post. >>> To unsubscribe from this group, send email to >>> clojure+unsubscr...@googlegroups.com >>> For more options, visit this group at >>> http://groups.google.com/group/clojure?hl=en >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to clojure+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> > -- > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with > your first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Clojure" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
