Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Buggy text in Cooking site's help center
Where?
The bug appears to be there at a specific help center page of the Cooking site of Codidact: https://cooking.codidact.com/help/how-to-ask
What?
There are two occurences of this bug.
-
Under "Make sure your question is in scope" subheading, there is a paragraph like so (only raw text is shown below, and I have bolded the erroneous part):
Every Codidact site has its own guidelines for what topics are able to be asked about on that site. You wouldn't want to ask about frying eggs on Writing, or bicycle maintenance on Cooking. See $SiteName's scope guidelines here.
There is "$SiteName" on the last line, I suggest that it should be changed to "this site" or "Cooking".
-
Under "Do some research" subheading, there is a paragraph like so (only raw text is shown below, and I have bolded the erroneous part):
Before asking a new question, first take a look around. Has your question been asked before here on $Sitename Codidact? You can do a search for keywords related to your question, or take to your favorite search engine to see if your answer is already there on Codidact.
Notice "$Sitename" again, this time with the "n" lowercase. This should also have the same improvement made as stated above.
Why?
While it is not a critical error, fixing it would make the page look better.
1 answer
I've fixed this - it looks like either that placeholder was never replaced or it was overwritten at some point and we didn't notice (we had an overwriting issue a few months or so ago that possibly could have caused this).
As a side note, for anything only applicable to one Codidact community, such as Cooking, I'd recommend posting in the Meta category for that community rather than the network-wide Meta here. But thanks for the report!
0 comment threads
0 comment threads