emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Brett Viren <bv@bnl.gov>
To: Rainer Hansen <rainer.hansen@gmx.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Best way to create blog for company web site with Orgmode
Date: Wed, 09 Mar 2016 12:47:33 -0500	[thread overview]
Message-ID: <ir4bn6nwnka.fsf@lycastus.phy.bnl.gov> (raw)
In-Reply-To: <87io0wae5h.fsf@gmx.net> (Rainer Hansen's message of "Tue, 08 Mar 2016 21:49:30 +0100")

[-- Attachment #1: Type: text/plain, Size: 946 bytes --]

Rainer Hansen <rainer.hansen@gmx.net> writes:

> I wonder what is the best way to create a blog for a company website
> with Orgmode. I do not want to use a static web site generator. The
> design of the web site is relying on Bootstrap and customs CSS.

Just curious, why does wanting to use Bootstrap rule out an Org-based
static site generator for you?

I'm slowly developing just such a beast.  It Works For Me(TM) but is
still a bit raw for others unless they can deal with some Python
hacking and spotty documentation.

> It should be easy to setup and to maintain for me?

I think maybe you can better define what you mean by "easy"?  

In the end, developing my own generator was easier than trying to adapt
existing ones.  There are a lot of great ones out there, especially if
you expand to allow Markdown ones (either native authoring or using
Org's Markdown export), but none do exactly what I wanted.

-Brett.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 800 bytes --]

  parent reply	other threads:[~2016-03-09 17:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 20:49 Best way to create blog for company web site with Orgmode Rainer Hansen
2016-03-09  9:45 ` Arkadiusz Drabczyk
2016-03-09 20:11   ` Rainer Hansen
2016-03-09 17:47 ` Brett Viren [this message]
2016-03-09 19:18   ` Rainer Hansen
2016-03-09 21:15     ` Rainer Hansen
2016-03-09 23:33       ` Brett Viren
2016-03-10  7:37     ` Alan Schmitt
2016-03-10  9:11       ` Eric S Fraga

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ir4bn6nwnka.fsf@lycastus.phy.bnl.gov \
    --to=bv@bnl.gov \
    --cc=emacs-orgmode@gnu.org \
    --cc=rainer.hansen@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).