emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Phil <pe@7d.nz>
To: "Sébastien Gendre" <seb@k-7.ch>, mbork@mbork.pl
Cc: General discussions about Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Examples of online documentation written with Org-mode
Date: Sun, 11 Aug 2024 09:59:58 +0200	[thread overview]
Message-ID: <f312396e-832f-4439-9180-7b7e7943ac51@7d.nz> (raw)
In-Reply-To: <878qx37f92.fsf@localhost>






* [2024-08-11 08:19] Ihor Radchenko:
> mbork@mbork.pl writes:
> 
>> On 2024-08-10, at 17:13, Ihor Radchenko <yantar92@posteo.net> wrote:
>>
>>> Many blogs are also made with Org mode. Not sure if it qualifies for
>>> documentation.
>>
>> ... my custom blog engine
>> (https://gitlab.com/mbork_mbork_pl/org-clive).  It is a testament to the
>> power of Org that Org Clive is less then 400 lines of Elisp - most of
>> the heavy lifting is done by Org itself.
> 
> Note that it is listed in https://orgmode.org/tools.html since long ago ;)
> 

Mine too (https://gitlab.com/7dnz/org-weblog) lands in this
category, with an emphasize on a — very verbose I admit — but strict
literate programming. It's a 99KB file, with tests, attempts,
explanations, explorations, etc.
The page documentation is produced as blog post by evaluating
directly from the code and documentation being redacted.

It doesn't use the tangle processor but evaluates one section
after the other. This is how I learned Lisp. It may stay as a
beginner's work forever but I don't mind, it works, and I like it.

Here are the functions it lacks to make it a complete blogging engine :
search, archival by year/month, previous/next post, pagination, one 
folder by post, and a few custom properties :
the author of a post and a custom stylesheet per post among others.

Cheers

--
Philippe Estival
https://7d.nz


  reply	other threads:[~2024-08-11  8:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-10  7:50 Examples of online documentation written with Org-mode Sébastien Gendre
2024-08-10 12:41 ` Samuel Loury
2024-08-10 17:01   ` Sébastien Gendre
2024-08-10 17:13 ` Ihor Radchenko
2024-08-10 19:48   ` András Simonyi
2024-08-11  5:17   ` mbork
2024-08-11  6:19     ` Ihor Radchenko
2024-08-11  7:59       ` Phil [this message]
2024-08-11 16:39         ` Ihor Radchenko
2024-08-12 10:18           ` Phil Estival
2024-08-18 12:26             ` Ihor Radchenko
2024-08-11 17:21         ` Thomas Redelberger
2024-08-11  7:45 ` Juergen Fenn
2024-08-11 18:30 ` Steve Downey
  -- strict thread matches above, loose matches on Subject: below --
2024-08-11  2:41 Sébastien Gendre
2024-08-11  2:44 Sébastien Gendre

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=f312396e-832f-4439-9180-7b7e7943ac51@7d.nz \
    --to=pe@7d.nz \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbork@mbork.pl \
    --cc=seb@k-7.ch \
    /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).