Feedback about SitePoint on Discourse



It is - top left hand corner above the tab key.

Of course it might not be on some foreign language keyboards but it is there on the Australian and USA ones.


Brilliant. I'd never have found that on my own. Thanks.



It's not on yours? As felgall said, on ours it's up in the top left above the tab key.


He's a furrener...


Yep smiley
This is mine...
I'll just stick to the button then


I discovered that after typing a character (which displays all of the Category names containing that character), if you Backspace and remove the character, a full list of all Categories not Muted is displayed. It wouldn't disappoint me if it displayed the list of unmuted Categories when one first clicked and created the little box. It seems odd to presume that someone knows the names of any of the Categories beforehand.


Ha exactly how I feel WebMachine.
Finding it very hard to use, everything seems so big and tucked away.
Hopefully I'll get used to it though kind of finding different ways to fix problems because the hard usability.

Probably because I've used the old sitepoint for so many years.



Discourse has a lot of features that are not documented but are "discoverable" to "power users"

I still don't know how I feel about this, but that's the way it is.


I-tell-ya, I-tal-ya has a strange keyboard. :stuck_out_tongue:

Surely there's a key combination that will bring it up?


I moved a post to a new topic: Hoping for some help with URL rewrite


I was trying different things in my preferences last night - added about 15 topics to my 'watching' list. This morning my email inbox was jammed with 30 emails from new posts in these topics, at least half of which were spam posts that had since been moderated and removed.

Is this a common problem, where notifications get emailed to members before the posts are even moderated? I hope it can be fixed somehow. I really like the concept of getting notifications.

In the meantime, I just unselected all the topics and will hunt for new threads to watch myself.


This is probably better since Jeff Atwood is on the team and I think Discourse uses some libraries recommended by it:

Kinda funny the drama that's happening with it. Apparently the darginfireball guy made them change the name from Standard Markdown to Common Markdown then made them remove the Markdown part all together and now it's CommonMark. Screw that guy.


In his defense, the original license did state that the name wasn't to be used in any other form. Jeff seems to acknowledge that.

I just chose that reference because it's the original one and quite a simple overview of the process.


Yeah, but that doesn't mean he had to enforce it instead of supporting the attempt at standardization.


Oh no - someone has disabled the ability it zoom in on tablets/phones, that's not very good at all. I was just looking at a thread on my ipad and wanted it zoom into the image but couldn't.

Please remove zoom disabling!


As far as I understand, that's a Discourse issue, not a SitePoint issue, and it's been reported:


Thanks @TechnoBear - haven't sitepoint got access to forums templates/files then?


@cpradio or @HAWK have a better idea of how Discourse works than I do, and can give you a more accurate answer, but I think basically, if it can be done in CSS, we can fix it ourselves; if it's a core Discourse issue, there are problems with us doing our own fix, which might break something further down the line if there are changes/updates to Discourse centrally.


The zoom is disabled via the viewport meta tag they are using.
<meta name="viewport" content="width=device-width, minimum-scale=1.0, maximum-scale=1.0, user-scalable=no">

I don't know know why they are using that as I never use that in my sites. I recommend this method:

<meta name="viewport" content="width=device-width, initial-scale=1.0">

Of course there may be a good reason why discourse does this but as far as I am concerned you should never disable zooming unless its for a native app. When developers disable zooming they are usually more concerned about their design than they are about their users which is the wrong way around.