Lua filters deserve BETTER MARKETING.

[stroobandt]

Lua filters deserve BETTER MARKETING.
Currently. Lua filters look more like an afterthought at the bottom of the Extras page.
When one eventually lands on this README.md, it becomes a GitHub dumpster dive to find out which Lua filter does what. I would suggest adding one paragraph descriptions to the general README.md and do something similar on the Extras page.

Feel free to discuss this here.

[averms]

When one eventually lands on this README.md, it becomes a GitHub dumpster dive to find out which Lua filter does what. I would suggest adding one paragraph descriptions to the general README.md and do something similar on the Extras page.

Agree with the first part. We could write a script that merges all the READMEs
and appends them to the root README. Maybe we could use include-files.lua?

[tarleb]

See branch html-pages for my plans to improve on the current situation. I'd like to have a separate website, with a separate page for each filter, and an overview page featuring the paragraph between the main heading and first second-level heading. Example filter page:
pagebreak.zip

[tarleb]

We've created a new org pandoc-ext to make filters more visible. New filters are announced on Mastodon. Quarto-related pages like awesome-quarto mention the filters, too.

While we could still do more, it's enough for me to consider this done.

[stroobandt]

@tarleb Great! But what needs to be done for my math2svg Lua filter to make it onto the list?

[alerque]

@tarleb I know my attention has been devoured in other directions lately, but I do come round to Pandoc & especially Lua stuff now and then. If you want triage/maintenance/ci help on the new org feel free to invite and I'll pitch is as time permits.

[tarleb]

@tarleb Great! But what needs to be done for my math2svg Lua filter to make it onto the list?

The filter migration is work in progress, I didn't get to math2svg yet. I generally encourage contributors to maintain filters under their own namespace and to mention them in pandoc-ext/info (e.g., https://github.com/b3/include-code-files), but I'm also happy to move the code to a repo in pandoc-ext and give the maintainer access (as happened with list-table). Just let me know your preference.

[tarleb]

If you want triage/maintenance/ci help on the new org feel free to invite and I'll pitch is as time permits.

Thanks, I'll gladly take you up on that.

[stroobandt]

move the code to a repo in pandoc-ext and give the maintainer access

I prefer the above option for math2svg. Thanks!

[tarleb]

I've created the repo and given you access. It's set to "private" for now, because I aim for all repos in the pandoc-ext org to follow a few common patterns, which we'll have to add to math2svg first. I've yet to write those patterns down in detail, but the gist is:

• Good docs
• MIT license
• Usable as a Quarto extension (if the filter makes sense in that context)
• Options should be taken from an object with the same name as the filter, e.g.,

  my-filter:
    setting1: true
    setting2: [this, that]
    # etc.

I plan to publish another filter that will create this structure from myfilter_foo and myfilter.bar values, so old math2svg configs will still be usable.

[bpj]

Den lör 29 apr. 2023 21:12Albert Krewinkel ***@***.***> skrev:

If you want triage/maintenance/ci help on the new org feel free to invite and I'll pitch is as time permits. Thanks, I'll gladly take you up on that.

I might be able to lend a hand as well as and when I have time. —

…

Reply to this email directly, view it on GitHub <#121 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAI3OUZ3ID64SYEPSB73ZY3XDVRXXANCNFSM4SUPEIIA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>