emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Phil Estival <pe@7d.nz>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Sébastien Gendre" <seb@k-7.ch>,
	mbork@mbork.pl,
	"General discussions about Org-mode" <emacs-orgmode@gnu.org>,
	yuri <wmstarting@yandex.com>
Subject: Re: Examples of online documentation written with Org-mode
Date: Mon, 12 Aug 2024 12:18:48 +0200	[thread overview]
Message-ID: <5a2ccb97-db6e-4644-8fbd-89255d055905@7d.nz> (raw)
In-Reply-To: <87a5hjj9nw.fsf@localhost>


* [2024-08-11 18:39] Ihor Radchenko:
> Phil <pe@7d.nz> writes:
> 
>> (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.
>>
> 
> While reading it, I did not immediately figure out what that thing is
> for and how to use it.

Hi. An other reader interested in the topic got it right.
https://gitlab.com/7dnz/org-weblog/-/issues/1
We had a few words by email last year. CCing him.

> For now, it looks more like a personal config file; not like a project
> to be used by others.

Was your intent really to write that ?
Because you well know a personal config file is something else.

 > There is even no license.

Everybody is free to ask, preferably nicely, if someone else is
willing to license or re-license code. This is an open source community
after all and source is open indeed.

> https://one.tonyaldon.com/docs/getting-started/ (one.el) project appears
> to have a similar spirit. You may get an inspiration from there.

Saw the presentation at the last Emacs conf'.
The common ground is a static site generator for Emacs+org
but the spirit is different.

Don't get me wrong, I'm not looking for inspiration and I already wrote
and discussed requirements and specifications for such a project.
As I said /supra/ I don't mind letting it the current state.

 > I recommend going through the process of publishing package via
 > ELPA/non-GNU ELPA. It will give you a chance to improve the code,
 > docs, and polish the package in general.

Have I some energy and motivation left, I would do so. But Since I'm
not trying to shine among the community — and I'm not saying it's a bad
thing, I prefer to share raw materials for learning purposes rather
than go through one more standard procedure in the era of total
bureaucracy. I was just demonstrating what, IMHO, works smooth for
online documentation.

Phil


  reply	other threads:[~2024-08-12 10:22 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
2024-08-11 16:39         ` Ihor Radchenko
2024-08-12 10:18           ` Phil Estival [this message]
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=5a2ccb97-db6e-4644-8fbd-89255d055905@7d.nz \
    --to=pe@7d.nz \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbork@mbork.pl \
    --cc=seb@k-7.ch \
    --cc=wmstarting@yandex.com \
    --cc=yantar92@posteo.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).