#21

The CSS for the one with comments looks off. There’s no padding at all :-/

Also what makes a reply “notable?” Are folks who made comments that don’t get “elevated” to the blog front end going to feel slighted? Are there criteria / a threshold of some sort that determines this?

I just think one of the maxims of UX is that users are lazy, so if the form isn’t right there, it’s absolutely going to be a deterrent to people leaving comments. Maybe that’s by design! I know many comments on any public blog are fail and if this discourages that then great. But if this is not an intended effect I’d rethink it.

#22

It would help but not fully address the lack of an embedded form.

Something like (in normal size text perhaps italicized):

Your comments on this post are welcome and appreciated! We manage comments using discussions.fedoraproject.org, so please click the link below to leave a reply to this post:

Leave a reply <= (bigger bolder text, ideally a button style)

I’d also suggest the leave a reply link pointing to the start of the comments on the article in discourse rather than the top, bc when youre thinking youll leave a comment and get a differently-formatted version of the article you just read on WP, it’s a bit confusing.

#23

I’m not sure it discourages comments — Ben’s PgM updates have gotten 0 comments for the past few months, and this time around someone read it enough to notice a problem in one of the linked items and comment. Not a very big sample size, admittedly, but… greater than 0.

The benefit is more conversation next to other conversation rather than in a silo… I try to follow the commblog but rarely have a chance to notice the comments, especially from something that might be pushed down the page on the blog. Here, when someone comments it bumps the topic.

#24

Yes. It can be set so only replies with a certain number of :heart:s are shown, or even only ones liked by a moderator. The former might make sense for a very busy blog and the latter for someone’s personal curated site, but for here we set them to show all … well, currently, the first ten comments. I could increase that. Anyway, that text is customizable too and I changed it to just say “Comments” rather than the default “notable replies”.

#25

Before

Screenshot from 2021-01-18 14-28-38
Screenshot from 2021-01-18 14-28-381283×1042 125 KB

After

Screenshot from 2021-01-18 14-44-37
Screenshot from 2021-01-18 14-44-371097×994 98.5 KB

Still not happy with the “continue the discussion at” thing but this is a start :slight_smile:

.discourse-comments-area {
  padding: 5.5%;
}

.discourse-comments-area .avatar {
  margin-right: 15px;
}

.discourse-comments-area .comment-content {
  margin-left: 65px;
  line-height: 200% !important;
}

.discourse-comments-area blockquote {
  color: #aaa;
  font-style: oblique !important;
  margin-bottom: 1.2em
}

.discourse-participants {
  margin-bottom: 1em !important;
}

/* fix cut off bottom padding for empty author bio take it or leave it */


.post-authorbio {
  min-height: 180px;
}
#26

Ok so we’ll call a horse a horse and it’s basically a benefit for discourse web interface users

#27

Awesome thanks. Yeah, it would be nice if there were a comment form there directly but it’s not implemented that way. I can change the actual text to anything you suggest (including the link text, which just defaults to the site hostname).

1 Like
#28

@bcotton when you get a chance can you add this to the site CSS?

#29

Well, phone app too. And I suppose if you want it gives a way to engage via email that wasn’t there before; you can now effectively subscribe to the commblog as a mailing list.

#30

the wordpress comment system has an email interface… if anybody was subscribed to it before i guess theyre not now?

#31

I assume that anyone who was subscribed to get notified of whole new posts still is. That’s a question for Ben too I guess because I don’t see anything about it anywhere in the WordPress admin UI.

Old posts don’t allow comments, so those aren’t a concern anyway.

#32

Just FYI, I have discourse email me everything “mailing list mode”. Those blog posts appear, but because they aren’t using mime, my mail reader doesn’t know that they are in html and they look like a pile of raw html. ;( That may just be a limitation of the discourse mail mode, but I suppose it could also be the way it’s posting them? Anyhow, just thought I would mention it… they aren’t too nice looking for mailing list mode people.

#33

That is less than ideal. I suppose what they are is “technically markdown”, which is “plain text but actually all HTML is totally valid”. I’ll see what I can find about that.

#34

@kevin, I find mailing list mode really confusing and misleading for what it actually does! You might find the advice I shared in this thread useful about how to have better control over notifications and emails:

#35

Well it looks like updating a post will cause a new topic to be created. That’s annoying.

#36

That is annoying. I wonder if there’s a setting for it to not do that – and ideally to also update the post here.

#37

Hmmm, @bcotton

… it looks like this should work but not be automatic.

#38

Hm. My test post update used the classic editor instead of the block editor (because I copied in HTML and the HTML editor forces classic mode) so that option isn’t available. I’ll have to remember to force a conversation to blocks before I publish the weekly reports.

#39

You can paste rendered HTML into the block editor and it does the right thing, btw. I do that all the time.

1 Like
#40

Right, but that requires adding a few steps to my workflow. It’s easier to just click the “No, WordPress, make this blocks” button.