Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »

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.

Review Suggested Edit

You can't approve or reject suggested edits because you haven't yet earned the Edit Posts ability.

Approved.
This suggested edit was approved and applied to the post 9 months ago by Monica Cellio‭.

12 / 255
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](https://cooking.codidact.com/) of Codidact: https://cooking.codidact.com/help/how-to-ask
  • What?
  • -
  • There are two occurences of this bug.
  • 1. 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".
  • 2. 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, but fixing it would make the page look better.
  • **What are the community's thoughts on this?**
  • Where?
  • -
  • The bug appears to be there at a specific help center page of the [Cooking site](https://cooking.codidact.com/) of Codidact: https://cooking.codidact.com/help/how-to-ask
  • What?
  • -
  • There are two occurences of this bug.
  • 1. 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".
  • 2. 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.