41
submitted 11 months ago by ernest@kbin.social to c/kbinDevlog@kbin.social

Today, I continue preparations for refactoring. Szymon updated the environment and added a spoiler tag in the markdown editor. Additionally, there were several fixes and improvements related to collections and the People page.

https://codeberg.org/Kbin/kbin-core/pulls/1325
https://codeberg.org/Kbin/kbin-core/pulls/1327

You can track changes in the official repository
https://codeberg.org/Kbin/kbin-core

or on Github
https://github.com/ernestwisniewski/kbin

you are viewing a single comment's thread
view the rest of the comments
[-] ThatOneKirbyMain2568@kbin.social 9 points 11 months ago

Great changes! A spoiler tag button is really nice, especially since the formatting for it can be a bit clunky. On that note though, I think it'd be nice to have an alternate format for making spoilers that doesn't literally have the word spoiler in it.

It's also awesome to see that official collections are explicitly marked, but the way it's done is rather odd. It's a button that creates an "Are you sure?" prompt on the screen when you click it. It seems like something that's meant for instance owners.

I think something less obtrusive next to the collection's name would be better for marking official collections. I implemented that with a checkmark in my userstyle, and I prefer it to the button. Maybe have the text "official" show when you hover over it to indicate what it means.

[-] cacheson@kbin.social 2 points 11 months ago* (last edited 11 months ago)

Like this?
Do you mean just displaying something other than "spoiler" in the header? Or not using the word "spoiler" when writing the tag at all? If the latter, I believe it's done that way to match how it works on lemmy.

[-] ThatOneKirbyMain2568@kbin.social 3 points 11 months ago

I mean not having the word spoiler when writing the tag. I get that it's done for Lemmy compatibility, which is why I suggest an alternative way to do it (like how italics can be written like _this_ or like *this*).

[-] DessertStorms@kbin.social 3 points 11 months ago* (last edited 11 months ago)

(like how italics can be written like this or like this).

How do you get that to display without italicising/bolding the text? (E: like has clearly happened to me lol)

[-] ThatOneKirbyMain2568@kbin.social 3 points 11 months ago

Backslashes. To get _this_, you type \_this\_. In fact, you can backslash backslashes, which is how I showed the backslashes here.

[-] DessertStorms@kbin.social 3 points 11 months ago* (last edited 11 months ago)

Amazing, thanks!
(now to hope I actually remember lol)

[-] Kierunkowy74@kbin.social 3 points 11 months ago

StackExchange Flavoured Markdown features spoilers done like this:

>! Hidden text

! Hidden text

Well, @ernest is aware of way, how spoilers are done on Wykop, being simply ! Hidden text

[-] ThatOneKirbyMain2568@kbin.social 2 points 11 months ago* (last edited 11 months ago)

True, though this doesn't give the spoiler a header.

Maybe something like ||header|content||, based off how Discord handles spoilers, could work.

So

don't click if you're 8 or younger
santa isn't real

could be written as

||don't click if you're 8 or younger|santa isn't real||

Edit: Backslashing doesn't seem to work on colons for whatever reason, so I removed that example of how the spoiler could be written.

[-] DessertStorms@kbin.social 2 points 11 months ago* (last edited 11 months ago)

nope

spoiler
testing

(E: I've tried several ways to get it to work, once I got the little triangle but also the word "spoiler" on the end, the rest of the times I got variations of what it looks like now. Am on desktop)
(E2: it's now settled on a little triangle, it was showing the ::: bits before, I swear ๐Ÿ˜‚)

this post was submitted on 02 Dec 2023
41 points (100.0% liked)

/kbin devlog

2 readers
1 users here now

founded 2 years ago