WelcomeWEFreedomWindsorEssexCounty-ActionCommunicationsRalliesResourcesSocialEventsWednesdayNightMeetings-ActivismAgoraAgorismCanadaCommonLawCommunityDataCentersDataCentresDoocracyFarmersMarketIntroductionsNaturalLawNewslettersOntarioOrganizingOutreachProjexProjexWikiRalliesResistanceAnalysisSoireesSoiréesWikiSpooksWindsorElectionsTop Subs
8
MatrixDev - - (+7|-0)
Some updates and additions to Matrixdown(self)
4 commentsbyx0x7

There are just two small updates. But as small as they are, it's worth telling you about them. First is a fix to allow you to make an inline image that links elsewhere.

If you don't know how to make inline links in Markdown, they work like this:

[My text](https://example.com)

Extended markdown lets you do this with an image like so:

! [] (https://img.gvid.tv/i/someimage.jpg) Remove the spaces.

You can also do this more intuitively with a special Matrixdown command:

!IMG img-url

There already exists a trick that lets you combine markdown syntax, and I was using it to make these inline images link to the image as well. It would modify the text like this:

! [] (img-url) -> [![](img-url)](img-url)

This makes it so that an image will link to the full image. The problem was that if you wanted to use that syntax yourself, the code would step on its own feet. That's fixed now. So you can link to an arbitrary place with an image.

[![](img-url)](target-url)

I also added a more intuitive !IMGLINK syntax. It supports both a single-line variant and a multi-line variant.

!IMGLINK img-url target-url

or

!IMGLINK
img-url
target-url

I was able to use this on the /Donation page, as an example.

The next addition is going to be a rare one for most people. You can now comment out content. Let's say you are editing some text and you want to see how it looks when omitting some text. But you don't want to erase it in order to refer back to it. You might want that for your own notes or to add back later. Programmers are used to being able to comment out code to refer to later. The syntax for this makes use of markdown blocks.

::: comment

My text that won't get rendered forward.

:::

Maybe that is useful for people writing long-form content. It's helpful to me when editing any of the official pages because I can refer back to prior wording or play around with it more easily. I made it so this comment block will not create HTML. It's not just styled out. So it is secure against inspection from other users. When you edit your comment or post, you will be able to see your comments.

The last topic is really a poll for you guys. It might not be hard for me to add LaTeX formula support. I know @LarrySwinger was in favor of it. My questions are this. Is there interest? Do you guys have a preference for any of the libraries I could weave in?

Comment preview

[-]JasonCarswell1(+1|0)

Images good.

Confused about the latter half.

Neato.

[x] Oblivious to all of this.

parentlinkreply
[-]LarrySwinger0(0|0)

Nice! I find the combined syntax complicated looking. Okay, from taking a closer look, I see the logic behind it and now I can reason my way there. Anyway, I really like !IMG. I have a further recommendation to allow it to be lower-case and to simplify everything to that.

!img image-url target-url

No need for a separate command for adding a target URL; just make it so that !img takes either one or two arguments.

parentlinkreply
[-]x0x70(0|0)

The capital letters reduces the chance for collision with regular text, and makes an easy way to talk about it without needing escape characters, but maybe. Having seperate commands is useful because it simplifies the regex. And also, because these images can be inline, there can be text after the use of !img that someone doesn't want captured by it.

I could go full Erlang and have users specify the arity of the command. !img/1 img-url. !img/2 img-url target-url.

parentlinkreply
[-]LarrySwinger0(0|0)

And also, because these images can be inline, there can be text after the use of !img that someone doesn't want captured by it.

That's easily fixed if it checks whether or not the second command is an actual URL.

I could go full Erlang and have users specify the arity of the command. !img/1 img-url. !img/2 img-url target-url.

pls no

parentlinkreply