emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Masterson <dsmasterson@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Suggestion: User-contributed use-cases on orgmode.org ?
Date: Wed, 15 Nov 2023 18:58:02 -0800	[thread overview]
Message-ID: <LV8P223MB092066309BEEECEC54A02E3FA2B0A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <ZVTImwOHJCc3MuXP@swain.home.arpa> (Russell Adams's message of "Wed, 15 Nov 2023 14:33:15 +0100")

Russell Adams <RLAdams@adamsinfoserv.com> writes:

> On Tue, Nov 14, 2023 at 06:14:43PM -0800, David Masterson wrote:
>> Russell Adams <RLAdams@adamsinfoserv.com> writes:
>>
>> > On Mon, Nov 13, 2023 at 09:09:54PM -0800, David Masterson wrote:
>> >> Just a suggestion (or maybe this is already handled?).
>> >>
>> >> Was thinking I'd like to see an archive of tagged use-cases for Org that
>> >> could be searched via tags or regexp.  The use-cases should include a
>> >> description of the problem, a general description of the answer, blocks
>> >> of elisp (general code) to setup the answer, and how to use the code to
>> >> do the work of the use-case.  In fact, it could be recommended that the
>> >> use-cases be written in literate programming style (the first use-case
>> >> would have to provide the recommended example).  As such, if written
>> >> properly in Org, it could (after a once over by maintainers) be exported
>> >> to HTML for inclusion on orgmode.org.
>> >
>> > Have you looked at Worg?
>>
>> Yes. and that's a beginning.  I'm just wondering if something could be
>> made to encourage simple use-cases to be uploaded by anyone to provide a
>> deeper cookbook.  Perhaps I'm thinking of a wiki where people could add
>> their own use cases and comment on other people's use cases,  The wiki
>> would provide structure and search tools for new Org users.
>
> That's Worg. It's written in Org via Emacs, and publishes to the
> web. It does use git, but the codebase is very open. You only have to
> ask for an account and start writing.

This sounds good.

-- 
David Masterson


      reply	other threads:[~2023-11-16  2:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  5:09 Suggestion: User-contributed use-cases on orgmode.org ? David Masterson
2023-11-14  8:36 ` Russell Adams
2023-11-14 10:31   ` Max Nikulin
2023-11-15  2:16     ` David Masterson
2023-11-15  3:23       ` Corwin Brust
2023-11-16  2:56         ` David Masterson
2023-11-16  9:43           ` Ihor Radchenko
2023-11-17  5:13             ` David Masterson
2023-11-17  9:31               ` Ihor Radchenko
2023-11-17 18:26                 ` David Masterson
2023-11-18 10:51                   ` Ihor Radchenko
2023-11-18 19:18                     ` David Masterson
2023-11-19 15:38                 ` Bastien Guerry
2023-11-15  2:14   ` David Masterson
2023-11-15 13:33     ` Russell Adams
2023-11-16  2:58       ` David Masterson [this message]

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=LV8P223MB092066309BEEECEC54A02E3FA2B0A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM \
    --to=dsmasterson@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).