Change name from "Free Code Camp" to freeCodeCamp everywhere

[QuincyLarson]

We're changing our community's written name from "Free Code Camp" to "freeCodeCamp".

In case your curious, here are some of the reasons our core team agreed that this way of writing it out is better:

• most people already type freecodecamp when they search for us on Google (via Google Trends), and 60% of them self-report that they type it without spaces (via Twitter poll)
  
  

• freecodecamp is easier and faster to type, and visually more

• SEO practitioners have told me that just using one name (not both) will improve our SEO (though Google is basically a black box, so there's no way to know whether they're right)

• with the optional lower-camel-casing, freeCodeCamp looks visually more interesting than Free Code Camp without singificantly affecting readability

• our logo, twitter handle, facebook page, youtube channel, medium publication - you name it - already use freecodecamp without spaces, so this is a step toward uniformity

Here are the places where we will need to update this:

• Our forum
• Gitter descriptions
• npm packages
• Twitter
• Facebook
• Medium publication
• GitHub README.md and other .md files
• References within Free Code Camp's codebase itself, including meta tags and challenge copy
• YouTube channel name and information
• YouTube video descriptions (these were slated to be updated anyway)
• LinkedIn (note that LinkedIn is transitioning their universities pages platform so we weren't able to change everything yet)
• Teespring
• codepen
• reddit

And anywhere else anyone notices it.

If you want to tackle a specific platform listed above, reply and call "dibs." And if you don't have permission to update it, reply to this issue with links to specific instances and someone will probably have permissions to go and update it.

Thanks for your help with this transition, everyone!

[Manish-Giri]

I call dibs on 'GitHub README.md and other .md files'!

+1 for the camelCase!

[erictleung]

The reddit page also needs to be changed https://www.reddit.com/r/FreeCodeCamp/. The URL, the page title, and the description need changing.

[raisedadead]

Updated, Codepen.io : Username / Display Name / Challenge Pen Titles / Icons

[no-stack-dub-sack]

Surprisingly, I found only 289 matches for "free code camp" (non-case-sensitive) across 40495 files in all of FreeCodeCamp/, though this of course does not account for instances of "freecodecamp" without the camel casing

[no-stack-dub-sack]

I call dibs on the codebase 😄

[HKuz]

The new challenges in the curriculum expansion that reference it use "Free Code Camp" in their copy. I think I based it off the front-end sections that use the "Free Code Camp Cat Photo API". Happy to help get those when The Merge is ready.

[raisedadead]

@no-stack-dub-sack I recommend, that you make a pull request per file/block as in one for all front end projects, one for all basic javascript and so on.

This will help a lot in rebasing the current open developments. (Also, it would be a life saver in QA, scrolling is a tough lol... 😅 )

[raisedadead]

@HKuz I think for the curriculum expansion we can have a separate PR that updates that branch, we need not wait for staging. It's ideal because the changes from curriculum branch would go on top of staging, so ideally nothing would be missed.

Let me knw, I can make a PR to help.

[Manish-Giri]

@raisedadead @erictleung Are there any other platform(s) that I can take up from the list above, without running into access issues?

[raisedadead]

@Manish-Giri how about forum?

[Manish-Giri]

@raisedadead Thanks! I'll go through the forum.

[no-stack-dub-sack]

@raisedadead So I was talking to @QuincyLarson about this last night actually, and he mentioned that perhaps I shouldn't touch the seed files since they will all be replaced when the curriculum expansion goes live anyway - did I understand that correctly @QuincyLarson?

So far I've done the following directories:

server/resources/testimonials .json
server/views/sponsors/sponsors.jade
server/boot/user.js
server/boot/a-extender.js
server/boot/randomAPIs.js
server/server.js

and I did this before I talked to Quincy:

seed/challenges/04-video-challenges/jslingo.json

So I guess I will finish the server directory and then make a PR, then do everything else directory by directory, except in the seed files, and file a PR for each.

Make sense @raisedadead?

Also, since the domain part of emails addresses is case insensitive, should I be replacing "freecodecamp" with "freeCodeCamp" in any instance of an email address that a user might see, or is that overkill?

[raisedadead]

I shouldn't touch the seed files since they will all be replaced when the curriculum expansion goes live anyway

Well this has a potential of missing out and NOT touching some lines or instances or occurrence of Free Code Camp or FreeCodeCamp

IMHO, we should have two activities of updating both branches on a chore activity. But yeah that will be identified easily as well, later on... no worries.

Let's make the changes for seed in the curriculum branch and audit everything once it's merged back to staging.

then do everything else directory by directory, except in the seed files, and file a PR for each

Perfect. Sounds good to me. Just check for open PRs, if any PR is having changes (files) that will be affected with your PR, refer to it in the PR comments, so that the PR owners can rebase and resolve conflicts.

Also, since the domain part of emails addresses is case insensitive, should I be replacing "freecodecamp" with "freeCodeCamp" in any instance of an email address that a user might see, or is that overkill?

No. DO NOT do that. It may not be an issue in browsers but there could be email clients that can break... also its an overkill.

Thanks.

[robbawebba]

@QuincyLarson @raisedadead @erictleung I noticed that the freeCodeCamp listing on up-for-grabs.net is using the old style for freeCodeCamp. Do you guys mind if I change it to the new style? I'll have to change this file and submit the PR to the up-for-grabs.net repo

[Manish-Giri]

@raisedadead As I was working through renaming in the .md files, I came across this file. The file name is LICENCE-Free-Code-Camp-Curriculum.md, and as the file will be renamed according to the new style, should I change LICENCE to LICENSE, while I'm at it? I noticed, in some other places, License is being used, like this file, so wanted to check with you.

[erictleung]

@robbawebba that sounds reasonable!

@Manish-Giri in my opinion, I was thinking the license file for the curriculum could be changed to LICENSE-freeCodeCamp-Curriculum.md, which uses freeCodeCamp and LICENSE over LICENCE. My two cents, but I'd wait on @QuincyLarson.

[erictleung]

FYI, the forum About page need to be updated.

[raisedadead]

@Manish-Giri Please proceed as Eric suggested. I must have messed up the spelling in the first place.

@robbawebba yes, thanks for that!

@m-henderson can you help with about page for the forum.

[Manish-Giri]

@erictleung @raisedadead Thanks guys! I'll wait on @QuincyLarson's final word for the change.

[m-henderson]

@raisedadead of course, bud. I updated the forum about page from "The Free Code Camp Forum" to "The freeCodeCamp Forum"

[QuincyLarson]

@erictleung I updated our subreddit. Reddit won't let you change the capitalization of the URL but I fixed everything else.

[no-stack-dub-sack]

@raisedadead @QuincyLarson with the PR I just made, all that is really left for the codebase is the .md files which I know @Manish-Giri is on, and the seed files - which I guess we are not doing for now, right? Or should I go ahead and make a PR against the curriculum branch?

[raisedadead]

@no-stack-dub-sack yup, sounds good.

[raisedadead]

@Manish-Giri whenever you are ready, we need that PR, 😉

[no-stack-dub-sack]

@QuincyLarson @raisedadead

Two issues/comments/questions:

1. I am going to leave any alt attributes I come across as "free code camp" since we want to ensure screen readers can pronounce this.
2. Challenge caesars cipher relies on a spelling of FREE CODE CAMP to pass the tests, so I am not changing this instance in our seed. I think it is probably not worth fixing, but wanted to mention it.

[systimotic]

Does anybody know whether https://github.com/freeCodeCamp/static is still in use? If so, it will also require some updates.

[systimotic]

Hello people! I checked the checklist to see what has been done, and what still has to be done.

Our forum
✔️ The title of the forum was updated
♻️ Wiki renaming is in progress

Gitter descriptions
✔️ I went through the official chatrooms and changed these.

npm packages
❓ All freeCodeCamp packages are named either with fcc or lower case freecodecamp, as makes sense with the naming conventions for packages. The only thing I could find that may need updating is fcc-express-background. /cc @Em-Ant

Twitter
and
Medium publication
✔️ Looks like this was done

GitHub README.md and other .md files
✔️ Done by Manish

Facebook
♻️❓ Looks like the description was updated, but the title hasn't been updated yet. From what I can tell, you have to do this through a request, so there's a chance this is already in progress, but I'm not sure.

References within Free Code Camp's [sic 😜] codebase itself, including meta tags and challenge copy
♻️ In progress, looks like the challenge part is waiting for #12570 and everything else is done.
Update: it looks like this has been done now

---

Edit 1: YouTube channel name and description was done, shop has PR

YouTube channel name and information
✔️ Done!

Shop
✔️ Done by Mrugesh

---

Another edit:

Teespring
✔️ Done!

LinkedIn
🤷‍ Quincy talked to LinkedIn, and with their current system, changing the name is not possible.

---

Todo

YouTube video descriptions (these were slated to be updated anyway)

---

That's great progress! Most of the name change went through in one week, nice work everyone!

@QuincyLarson I'm not sure of the right places and people to take these last bits on. I think most of them are up to you.

[raisedadead]

@QuincyLarson @systimotic PR freeCodeCamp/shop#1 up for the shop.

[Dazler]

Hi everyone! I have made some commits into my branch and trying to merge with master!! But it is asking for a reason ,,, i i have no idea how to continue ahead!! I have attached the screenshot.Please help.

[Dazler]

I was making changes in seed/challenges files which were using old style of "freeCodeCamp".

[raisedadead]

@Dazler reachout to the Contributors Chat room.

[no-stack-dub-sack]

I can go ahead and finish the codebase now that we've made the big curriculum merge into staging... I will work on a PR to finish this off in the next few days. Which is just seed files at this point for the codebase.

[no-stack-dub-sack]

@raisedadead @QuincyLarson I've been holding off on this task for a while, since there are SOOOOO many changes going on in the seed files right now... not sure when a good time to do this would be. I'm afraid doing it now would cause merge conflicts with open PRs, etc.

[raisedadead]

@no-stack-dub-sack please make a pull request when ready, we will take care of merging and rebasing PRs

[hisener]

Could someone change the description of the about repo?

freeCodeCamp/about#3

[no-stack-dub-sack]

@QuincyLarson @raisedadead Ah! I got one more place - Twitch! How could we forget!? 😄 Not sure who is in charge of this, but I just want to know for sure whether or not we can do it, because if I change to instructions for the twitch challenge to freeCodeCamp for "users who are usually online" not sure if the API will be sensitive to that case change or not...

just storing this here so I can use it as a flag to find this part of the seed easily later:

<code>[\"ESL_SC2\", \"OgamingSC2\", \"cretetion\", \"freecodecamp\", \"storbeck\", \"habathcx\", \"RobotCaleb\", \"noobs2ninjas\"]</code>
<code>https://api.twitch.tv/kraken/streams/freecodecamp</code>

[no-stack-dub-sack]

What a beautiful sight!

[QuincyLarson]

@no-stack-dub-sack thanks! I'll take care of Twitch :)

[chrisscotthall]

How can I help out?

[QuincyLarson]

All right everyone, the only thing left on this list is the YouTube descriptions. I'm going to create a separate issue for that. Thanks everyone!