Question:
[ ] JavaScript Lingo: MDN and Documentation [ ] JavaScript Lingo: Value Types [ ] JavaScript Lingo: Variables & camelCase [ ] JavaScript Lingo: Arrays & Objects [ ] JavaScript Lingo: Finding and Indexing Data in Arays [ ] JavaScript Lingo: Manipulating Data [ ] JavaScript Lingo: Math [ ] JavaScript Lingo: Loops [ ] JavaScript Lingo: Regular Expressions
Working on this one

] ], "type": "hike",  "challengeType": 6   "challengeType": 6, "id": "56b15f15632298c12f315185", "nameEs": "JavaScript Lingo: expresiones regulares (RegExp)", "descriptionEs": [ "Las RegExp no siguen el formato del resto de JS, y pueden requerir una curva de aprendizaje.", "Las epresiones regulares (abreviado RegExp) también pueden ser una herramienta muy útil y eficiente.", "Usando RegExp, puedes hacer coincidir, reemplazar, buscar y dividir una cadena, uno de los tipos más difíciles de manipular.", "Al igual que con todos los otros videos, no vamos a entrar en detalles, pero quiero mostrar algunos ejemplos donde las RegExp son útiles.", "Si quisieras crear una página de registro que verifique las contraseñas para que contengan al menos un número y una letra mayúscula, puedes usar expresiones regulares.", "Si quieres asegurarte de que las fechas introducidas en una página sean todas fechas válidas en el futuro, puedes usar RegExp.", "Si bien hay infinitas maneras de utilizar RegExp, muchas de estas incluyen validaciones o ediciones automáticas de información." ]  } ] }


Question:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.124 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:
If you scroll down on the left section of the page below the Run Tests button you can see the results of the tests for your code. In this instance, the test fails because you have a capitalization error. For help with writing code, please consult the . Issues are for reporting bugs with the challenges or website. Happy coding!
thanks for help :) i have found the error it was on the coding i was placing another anchor tag while i supposed to use the existing one thank you :+1:
thanks for the help diagnosing the issue! Closing this issue as it looks like the issue has been resolved. Happy coding!

"name": "Sorted Union", "difficulty": "2.07", "description": [ <del> "Write a function that takes two or more arrays and returns a new array of unique values sorted in order." </del> <ins> "Write a function that takes two or more arrays and returns a new array of unique values in the order of the original provided arrays.", "The unique numbers should be sorted by their original order, but the final array should not be sorted in numerical order.", "Check the assertion tests for examples." </ins> ], "challengeSeed": "function unite(arr) {n  return arr;rn}nnunite([1, 2, 3], [5, 2, 1, 4], [2, 1]);", "tests": [


Question:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.124 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. My code:
If you scroll down on the left section of the page below the Run Tests button you can see the results of the tests for your code. In this instance, the test fails because you have a capitalization error. For help with writing code, please consult the . Issues are for reporting bugs with the challenges or website. Happy coding!
thanks for help :) i have found the error it was on the coding i was placing another anchor tag while i supposed to use the existing one thank you :+1:
thanks for the help diagnosing the issue! Closing this issue as it looks like the issue has been resolved. Happy coding!

"assert.deepEqual(inventory([[0, 'Bowling Ball'], [0, 'Dirty Sock'], [0, 'Hair pin'], [0, 'Microphone']], [[1, 'Hair Pin'], [1, 'Half-Eaten Apple'], [1, 'Bowling Ball'], [1, 'Toothpaste']]), [[1, 'Bowling Ball'], [1, 'Dirty Sock'], [1, 'Hair pin'], [1, 'Half-Eaten Apple'], [1, 'Microphone'], [1, 'Toothpaste']]);" ] } <del> ] </del>  No newline at end of file <ins> ] </ins>


Question:
My challenge is makes sure all p elements have closing tag
Thanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding.

var isCompletedDate =  Math.round(+new Date() / 1000); var bonfireHash = req.body.bonfireInfo.bonfireHash; var isSolution = req.body.bonfireInfo.solution; <del> // TODO debug(isCompletedWith, 'Is completed with'); </del> if (isCompletedWith) { var paired = User.find({"profile.username": isCompletedWith}).limit(1);


Question:
My challenge is makes sure all p elements have closing tag
Thanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding.

throw err; } if (user && paired) { <del> res.redirect('/bonfires'); </del> <ins> res.send(true); </ins> } }) }); } }) } else { req.user.completedBonfires.push({ _id: bonfireHash, completedWith: null,


Question:
My challenge is makes sure all p elements have closing tag
Thanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding.

}) var index = req.user.uncompletedBonfires.indexOf(bonfireHash); if (index > -1) { req.user.uncompletedBonfires.splice(index,1) } req.user.save(function(err, user) { if (err) { throw err; } if (user) { <del> res.redirect('/bonfires'); </del> <ins> debug('Saving user'); res.send(true) </ins> } }); } }); // Unique Check API route


Question:
My challenge is makes sure all p elements have closing tag
Thanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding.

return res.redirect('bonfires/meet-bonfire'); } var currentTime = parseInt(+new Date() / 1000); <del> if (currentTime - req.user.lastContentSync > 86400) { </del> <ins> if (currentTime - req.user.lastContentSync > 10) { </ins> req.user.lastContentSync = currentTime; var completed = req.user.completedBonfires.map(function (elem) { return elem._id;


Question:
My challenge is makes sure all p elements have closing tag
Thanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding.

} } }); <del> } if (allTestsPassed) { allTestsPassed = false; showCompletion(); </del> <ins> if (allTestsPassed) { allTestsPassed = false; showCompletion(); } </ins> } };


Question:
My challenge is makes sure all p elements have closing tag
Thanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding.

$('#complete-bonfire-dialog').modal('show'); // Only post to server if there is an authenticated user if ($('.signup-btn-nav').length < 1) { <del> $.ajax({ type: 'POST', data: { </del> <ins> $.post( '/completed-bonfire', { </ins> bonfireInfo: { completedWith : didCompleteWith, solution: bonfireSolution, bonfireHash: thisBonfireHash } }, <del> url: '/completed-bonfire/' }); </del> <ins> function(res) { if (res) { window.location.href = 'http://localhost:3001/bonfires' } }) </ins> } } <ins> $('.next-bonfire-button').on('click', function() { var bonfireSolution = myCodeMirror.getValue(); var thisBonfireHash = passedBonfireHash || null; var didCompleteWith = $('#completed-with').val() || null; completedBonfire(didCompleteWith, bonfireSolution, thisBonfireHash); }); </ins> $('.all-challenges').on('click', function() { $('#all-challenges-dialog').modal('show'); });


Question:
My challenge is makes sure all p elements have closing tag
Thanks for reporting this. But your code is incorrect. GitHub Issues are for reporting bugs on the website only. Please use the for getting challenge related help. Happy Coding.

}); <del> $('.next-bonfire-button').on('click', function() { var bonfireSolution = myCodeMirror.getValue(); var thisBonfireHash = passedBonfireHash || null; var didCompleteWith = $('#completed-with').val() || null; completedBonfire(didCompleteWith, bonfireSolution, thisBonfireHash); window.setTimeout(function() { // TODO window.location = '/bonfires'; }, 100); }); </del> // Bonfire instructions functions $('#more-info').on('click', function() {


Question:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. I feel like while the above code works it simply fails to communicate the purpose of the exercise by delivering a visible change in the resulting page at the right side of the screen. For comparison's sake, this is how it looks like when the code is executed in JSFiddle Given that the page display is narrow, my proposal is to change the required positioning entirely, so that the student will be able to see more clearly the results of the absolute positioning.
Hi - thanks for pointing this out. Yeah, the narrow output screen unfortunately doesn't show the change at all. We could change the requirements to use to make it more obvious. You titled the issue "Replace the example..." though, so if you had ideas to re-work this even more, let us know your thoughts!

"The next option for the CSS position property is absolute, which locks the element in place relative to its parent container. Unlike the relative position, this removes the element from the normal flow of the document, so surrounding items ignore it. The CSS offset properties (top or bottom and left or right) are used to adjust the position.", "One nuance with absolute positioning is that it will be locked relative to its closest positioned ancestor. If you forget to add a position rule to the parent item, (this is typically done using position: relative;), the browser will keep looking up the chain and ultimately default to the body tag.", "
",  "Lock the #searchbar element to the top-right of its section parent by declaring its position as absolute. Give it top and right offsets of 0.5 pixels each."   "Lock the #searchbar element to the top-right of its section parent by declaring its position as absolute. Give it top and right offsets of 50 pixels each."  ], "challengeSeed": [ "


Question:
Challenge has an issue. User Agent is: <codeMozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36</code. Please describe how to reproduce this issue, and include links to screenshots if possible. I feel like while the above code works it simply fails to communicate the purpose of the exercise by delivering a visible change in the resulting page at the right side of the screen. For comparison's sake, this is how it looks like when the code is executed in JSFiddle Given that the page display is narrow, my proposal is to change the required positioning entirely, so that the student will be able to see more clearly the results of the absolute positioning.
Hi - thanks for pointing this out. Yeah, the narrow output screen unfortunately doesn't show the change at all. We could change the requirements to use to make it more obvious. You titled the issue "Replace the example..." though, so if you had ideas to re-work this even more, let us know your thoughts!

], "tests": [ "assert($('#searchbar').css('position') == 'absolute', 'message: The #searchbar element should have a position set to absolute.');",  "assert($('#searchbar').css('top') == '0.5px', 'message: Your code should use the top CSS offset of 0.5 pixels on the #searchbar element.');", "assert($('#searchbar').css('right') == '0.5px', 'message: Your code should use the right CSS offset of 0.5 pixels on the #searchbar element.');"   "assert($('#searchbar').css('top') == '50px', 'message: Your code should use the top CSS offset of 50 pixels on the #searchbar element.');", "assert($('#searchbar').css('right') == '50px', 'message: Your code should use the right CSS offset of 50 pixels on the #searchbar element.');"  ], "solutions": [], "hints": [],


Question:
According to Google Analytics, the is way too hard, and is taking campers an average of 6 minutes and 35 seconds to finish (if they finish - a lot of them seem to give up). According to this table, campers spend more time on it than they do on the algorithm challenges. ! We need to either reword this or simplify the challenge so it can be completed in closer to 3 minutes. Otherwise, we should move it back to the algorithm section.
This challenge does have a large amount of constant strings which could cause users to take a longer time than a typical challenge. Maybe we could provide an array of the responses in the seed code. Make the seed code: This could help in two ways. The first is the users can save time by not having to type out each response. The second is this approach could minimize errors from typos in the response phrases (i.e. Hole-in-one! vs. Hole in one!). We could remove the number of different responses. Maybe remove Eagle and Double Bogey.
yes - that is a great suggestion. I think leaving all the names is fine but we should pre-populate the array with the names. Since this was your suggestion, would you be interested in tackling this and submitting a PR?
Yes, I would like to tackle this and submit a PR.
The Golf Code challenge did take me longer that the other challenges. I did not initially realize that golfScore() had BOTH strokes and par as parameters. With the other IF ELSE challenges we were only dealing with one argument to pass into the IF ELSE condition. I found myself in that "flow" and completely overlooked that two parameters were available to work with in the IF ELSE condition. I also found myself looking at the Strokes/Par table thinking, "How will IF( <= par-2) work?" After a little head scratching, I realized the values under the Strokes column were what you were supposed to compare Strokes to (i.e. IF (strokes <= par-2)). Hopefully, this feedback is helpful. I think the confusion is coming from the wording of the challenge and suddenly going from using one passed in parameter to two in your IF ELSE condition.
Awesome. has a PR open already. Could you take a look at that first and let me know what you think of his proposed changes?
I agree with MiloATH's proposed changes. Would definitely reduce the potential for typos when working the problem. As a side note, feel free to let me know if I am breaking any GitHub etiquette at any point. Zero experience providing input on collaborative projects. Looking for to learning and have really enjoyed FreeCodeCamp thus far. You guys and gals are doing awesome work. :)
Sure - we will let you know in a polite way if you break GitHub etiquette. Thanks for being receptive to feedback :)

], "tests": [ "assert(typeof timesFive === 'function', 'message: timesFive should be a function');",  "assert(code.match(/timesFive(s*d+s*)/g), 'message: function timesFive should be called with a number');",   "assert(code.match(/timesFive(s*d+s*)/g), 'message: function timesFive should be called with a number');",  "assert(timesFive(5) === 25, 'message: timesFive(5) should return 25');", "assert(timesFive(2) === 10, 'message: timesFive(2) should return 10');", "assert(timesFive(0) === 0, 'message: timesFive(0) should return 0');"


Question:
According to Google Analytics, the is way too hard, and is taking campers an average of 6 minutes and 35 seconds to finish (if they finish - a lot of them seem to give up). According to this table, campers spend more time on it than they do on the algorithm challenges. ! We need to either reword this or simplify the challenge so it can be completed in closer to 3 minutes. Otherwise, we should move it back to the algorithm section.
This challenge does have a large amount of constant strings which could cause users to take a longer time than a typical challenge. Maybe we could provide an array of the responses in the seed code. Make the seed code: This could help in two ways. The first is the users can save time by not having to type out each response. The second is this approach could minimize errors from typos in the response phrases (i.e. Hole-in-one! vs. Hole in one!). We could remove the number of different responses. Maybe remove Eagle and Double Bogey.
yes - that is a great suggestion. I think leaving all the names is fine but we should pre-populate the array with the names. Since this was your suggestion, would you be interested in tackling this and submitting a PR?
Yes, I would like to tackle this and submit a PR.
The Golf Code challenge did take me longer that the other challenges. I did not initially realize that golfScore() had BOTH strokes and par as parameters. With the other IF ELSE challenges we were only dealing with one argument to pass into the IF ELSE condition. I found myself in that "flow" and completely overlooked that two parameters were available to work with in the IF ELSE condition. I also found myself looking at the Strokes/Par table thinking, "How will IF( <= par-2) work?" After a little head scratching, I realized the values under the Strokes column were what you were supposed to compare Strokes to (i.e. IF (strokes <= par-2)). Hopefully, this feedback is helpful. I think the confusion is coming from the wording of the challenge and suddenly going from using one passed in parameter to two in your IF ELSE condition.
Awesome. has a PR open already. Could you take a look at that first and let me know what you think of his proposed changes?
I agree with MiloATH's proposed changes. Would definitely reduce the potential for typos when working the problem. As a side note, feel free to let me know if I am breaking any GitHub etiquette at any point. Zero experience providing input on collaborative projects. Looking for to learning and have really enjoyed FreeCodeCamp thus far. You guys and gals are doing awesome work. :)
Sure - we will let you know in a polite way if you break GitHub etiquette. Thanks for being receptive to feedback :)

"In the game of golf each hole has a par meaning the average number of strokes a golfer is expected to make in order to sink the ball in a hole to complete the play. Depending on how far above or below par your strokes are, there is a different nickname.", "Your function will be passed par and strokes arguments. Return the correct string according to this table which lists the strokes in order of priority; top (highest) to bottom (lowest):", "

Strokes	Return

1	"Hole-in-one!"

<= par - 2	"Eagle"

par - 1	"Birdie"

par	"Par"

par + 1	"Bogey"

par + 2	"Double Bogey"

>= par + 3	"Go Home!"

",  "par and strokes will always be numeric and positive."   "par and strokes will always be numeric and positive. We have added an array of all the names for your convenience."  ], "releasedOn": "January 1, 2016", "challengeSeed": [  "var names = ["Hole-in-one!", "Eagle", "Birdie", "Par", "Bogey", "Double Bogey", "Go Home!"];",  "function golfScore(par, strokes) {", "  // Only change code below this line", "  ",


Question:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Tests are not passing with correct code. Curiously, the "The fifth div should have a height of 25 pixels" test is passing, but none of the others. DOM elements are rendering correctly with appropriate inline style. Browser Name: Chrome Browser Version: 68 Operating System: Chrome OS !
it passed for me on firefox and chrome with the code in the picture - were you able to get it to pass?
Oddly enough, no. I find it very strange that I can get the fifth test to pass, but none of the others, no matter what I do.
yea, im not sure - did you try resetting the code and doing it again? is there any errors in the console? Try another browser maybe
Yes to reset, no to errors. If it's a browser problem, that's an issue for people using Chromebooks like myself.
I got the same scenario as . Only the fifth test is passing. Browser Name: Chrome Browser Version: Version 71.0.3578.98 (Official Build) (64-bit) Operating System: MacOS Mojave Version 10.14.2 I tried completing the challenge in Firefox and it passed. Similar users are having problems:
does not work on Chromium - Version 75.0.3770.100 (Official Build) Arch Linux (64-bit) works on Firefox 67.0.3
my browser: Versione 77.0.3865.120 (Build ufficiale) (a 32 bit) on Windows 10 Home v1803 no test passes with callback
Pretty sure the problem is similiar to the problem on
Yep looks like yet another zoom bug with Chrome. We can check the inline styles set instead for the test. I will make a PR.

```yml tests: - text: The first <code>div</code> should have a <code>height</code> of 12 pixels. <del> testString: assert($('div').eq(0).css('height') == '12px'); </del> <ins> testString: assert($('div').eq(0)[0].style.height === '12px'); </ins> - text: The second <code>div</code> should have a <code>height</code> of 31 pixels. <del> testString: assert($('div').eq(1).css('height') == '31px'); </del> <ins> testString: assert($('div').eq(1)[0].style.height === '31px'); </ins> - text: The third <code>div</code> should have a <code>height</code> of 22 pixels. <del> testString: assert($('div').eq(2).css('height') == '22px'); </del> <ins> testString: assert($('div').eq(2)[0].style.height === '22px'); </ins> - text: The fourth <code>div</code> should have a <code>height</code> of 17 pixels. <del> testString: assert($('div').eq(3).css('height') == '17px'); </del> <ins> testString: assert($('div').eq(3)[0].style.height === '17px'); </ins> - text: The fifth <code>div</code> should have a <code>height</code> of 25 pixels. <del> testString: assert($('div').eq(4).css('height') == '25px'); </del> <ins> testString: assert($('div').eq(4)[0].style.height === '25px'); </ins> - text: The sixth <code>div</code> should have a <code>height</code> of 18 pixels. <del> testString: assert($('div').eq(5).css('height') == '18px'); </del> <ins> testString: assert($('div').eq(5)[0].style.height === '18px'); </ins> - text: The seventh <code>div</code> should have a <code>height</code> of 29 pixels. <del> testString: assert($('div').eq(6).css('height') == '29px'); </del> <ins> testString: assert($('div').eq(6)[0].style.height === '29px'); </ins> - text: The eighth <code>div</code> should have a <code>height</code> of 14 pixels. <del> testString: assert($('div').eq(7).css('height') == '14px'); </del> <ins> testString: assert($('div').eq(7)[0].style.height === '14px'); </ins> - text: The ninth <code>div</code> should have a <code>height</code> of 9 pixels. <del> testString: assert($('div').eq(8).css('height') == '9px'); </del> <ins> testString: assert($('div').eq(8)[0].style.height === '9px'); </ins> ```


Question:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Tests are not passing with correct code. Curiously, the "The fifth div should have a height of 25 pixels" test is passing, but none of the others. DOM elements are rendering correctly with appropriate inline style. Browser Name: Chrome Browser Version: 68 Operating System: Chrome OS !
it passed for me on firefox and chrome with the code in the picture - were you able to get it to pass?
Oddly enough, no. I find it very strange that I can get the fifth test to pass, but none of the others, no matter what I do.
yea, im not sure - did you try resetting the code and doing it again? is there any errors in the console? Try another browser maybe
Yes to reset, no to errors. If it's a browser problem, that's an issue for people using Chromebooks like myself.
I got the same scenario as . Only the fifth test is passing. Browser Name: Chrome Browser Version: Version 71.0.3578.98 (Official Build) (64-bit) Operating System: MacOS Mojave Version 10.14.2 I tried completing the challenge in Firefox and it passed. Similar users are having problems:
does not work on Chromium - Version 75.0.3770.100 (Official Build) Arch Linux (64-bit) works on Firefox 67.0.3
my browser: Versione 77.0.3865.120 (Build ufficiale) (a 32 bit) on Windows 10 Home v1803 no test passes with callback
Pretty sure the problem is similiar to the problem on
Yep looks like yet another zoom bug with Chrome. We can check the inline styles set instead for the test. I will make a PR.

## Solution <section id='solution'> <del> ```js // solution required </del> <ins> ```html <style> .bar { width: 25px; height: 100px; display: inline-block; background-color: blue; } </style> <body> <script> const dataset = [12, 31, 22, 17, 25, 18, 29, 14, 9]; d3.select("body").selectAll("div") .data(dataset) .enter() .append("div") .attr("class", "bar") .style('height', d => `${d}px`) </script> </body> </ins> ``` </section>


Question:
from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at  When you make a PR for this particular issue, do not tag it with instead just reference it with
Hey ! How could I claim so we don't double work? Thanks
Hi ! Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours. Happy translating.
I just open a PR for
thanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often Happy contributing.
Done translating ! My PR is available at ! Thanks for all you do, freeCodeCamp
I have sent a translation proposal for /docs/how-to-work-on-guide- PR Hope it will help!
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
Hello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-
Working on /docs/spanish/how-to-work-on-guide-
Hello, I've improved the file
Hello, Improving docs/spanish/how-to-catch-outgoing-emails-
Hi, I'm improving docs/spanish/how-to-work-on-coding-
Hi, can I help with /docs/spanish/how-to-setup-freecodecamp-
Sorry, I opened a bad PR regarding but already closed it. I found there was still an English part to be translated
Hi! Is there any remaining documentation where I can help translate?
you can improve or fix redaction and spelling errors.
Hi there, It would be good if at the top are checked so we can see what is left to be translated. Thanks
Where I can start helping?
sorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are a total crap (Like ) . I guess you opened a Pandora Box with your articule about HacktoberFest.
Hey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. . or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder
Hola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages. In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal. Another thing that could be specified in the guidelines is: Challenges translations. Should they be translated? Referrals to types and attributes (which need to be in English for proper coding). For example, type "date" not type "fecha". If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it). Hey I would like to know your thoughts about this. Thanks to you all and happy coding!
I agree that we should standardize around informal. I agree with you that we should look out for words like "fecha" that have been accidentally translated during our automated translation process.
Hi all I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment. What do people think about translating "array" as "arreglo"? I think this is a big mistake that has been repeated since somebody made that bad translation many years ago. As any Spanish speaker know, "arreglo" means "repair" (), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way. I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that "arreglo" was the (really bad) translation of "array". Then I could read the text as if I was reading an encoded message that had to be deciphered. I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is "ristra". According to the : Which basically means: "A group of things placed one after another" They also share all the phonems in "array", with the adittion of /r/ (rolling r) and /t/ in "ristra". I'm open to other candidates, but please, let's take "arreglo" out of the Spanish version. The word "array" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like "list", "function", "import", "scope", etc. [1]: [2]:
Hello guy, I vote for yes, let’s do the change and I think will create a huge impact around of the world! Please let me know if you have more question questions or concerns. Andres Haro Cell: (619) 534-3190
Thanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join if you need help getting set up
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
Thanks for working on the translations for the "Contributing to freeCodeCamp". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.

</tr> </table> <del> # Contribution Guidelines </del> <ins> # Como trabajar con correos salientes localmente (para el flujo de trabajo de correo electrónico) </ins> <del> Hello 👋 ! </del> <ins> > **Nota:** Hay un **Opcional** Paso - Solo es requerido cuando trabajamos con el cuando se trabaja con flujos de trabajo de correo electrónico </ins> <del> These instructions have not been translated yet. Please check this issue for details: [`#18312`](https://github.com/freeCodeCamp/freeCodeCamp/issues/18312) </del>  No newline at end of file <ins> ## Introducción Algunos flujos de trabajo del correo electrónico, como la actualizar el correo electrónico de un usuario, requieren de una API, en el backend para mandar correos electrónicos. mientras desarrollamos podemos usar una herramienta para obtenerlos localmente, en lugar de tener que usar un proveedor de correo electrónico y enviar un correo electrónico real. MailHog es una de las muchas herramientas de email para probar en el entorno de desarrollo para desarrolladores, que capturará los correos electrónicos de su instancia local que freeCodeCamp está enviando. ## Instalando MailHog Como podemons instalar y usar MailHog depende del sistema operativo - [Instalando MailHog en macOS](#installing-mailhog-on-macos) - [Instalando MailHog en Windows](#installing-mailhog-on-windows) - [Instalando MailHog en Linux](#installing-mailhog-on-linux) ### Instalando MailHog en MacOS Aquí podemos ver como instalar MailHog en macOS [Homebrew](https://brew.sh/): ``` bash brew install mailhog brew services start mailhog ``` Esto emepezara un servicio de mailHog en segundo plano. Siguiente, puedes ir a [using MailHog](#using-mailhog). ### Instalar MailHog en Windows Descarga la versión mas reciente de MailHog de [MailHog's official repository](https://github.com/mailhog/MailHog/releases). Click en el link dependiendo de tu versión de Windows (32 ó 64 bit) y el archivo .exe será descargado en tu computadora. Una vez que termine la descarga, haga clic en el archivo. Probablemente recibirá una notificación de firewall de Windows donde tendrá que permitir el acceso a MailHog. Una vez que lo haga, se abrirá una línea de comando estándar de Windows con MailHog ya en ejecución. Para cerrar MailHog, cierre el símbolo del sistema. Para volver a ejecutarlo, haga clic en el mismo archivo .exe. No necesitas descargar uno nuevo. Siguiente, Puedes ir a [using MailHog](#using-mailhog). ### Instalando MailHog en Linux Primero instalar [Go](https://golang.org). Para sistemas basados en Debian como Ubuntu y Linux Mint, en la terminal: ``` bash sudo apt-get install golang ``` Para CentOS, Fedora, Red Hat Linux, y otros sistemas basados en RPM-based, en la terminal: ``` bash sudo dnf install golang ``` O: ``` bash sudo yum install golang ``` Establecer path para Go: ``` bash echo "export GOPATH=$HOME/go" >> ~/.profile echo 'export PATH=$PATH:/usr/local/go/bin:$GOPATH/bin' >> ~/.profile source ~/.profile ``` Despues instalar y correr MailHog: ``` bash go get github.com/mailhog/MailHog sudo cp /home/$(whoami)/go/bin/MailHog /usr/local/bin/mailhog mailhog ``` Siguiente, Puedes ir a [using MailHog](#using-mailhog). ## Using MailHog ## Usando MailHog Una vez que hayas instalado MailHog y lo hayas iniciado, debes abrir tu bandeja de entrada de MailHog en tu navegador, y abre una nueva pestaña o ventana y navegar a [http://localhost:8025] (http://localhost:8025). Ahora debería ver una pantalla como la siguiente: ![MailHog Screenshot 1](images/mailhog/1.jpg) Cuando la instalación de freeCodeCamp envíe un correo electrónico, verás que aparece aquí. Como aquí abajo: ![MailHog Screenshot 2](images/mailhog/2.jpg) Abre el correo y verás dos pestañas donde puedes ver el contenido: texto sin formato y fuente. Asegúrate de que estás en la pestaña de texto sin formato. ![MailHog Screenshot 3](images/mailhog/3.jpg) Cualquier enlace en el correo electrónico debe ser seleccionable. ## Enlaces útiles - Para cualquier otra pregunta relacionada con MailHog o para obtener instrucciones sobre configuraciones personalizadas, consulte el repositorio [MailHog] (https://github.com/mailhog/MailHog). </ins>  No newline at end of file


Question:
from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at  When you make a PR for this particular issue, do not tag it with instead just reference it with
Hey ! How could I claim so we don't double work? Thanks
Hi ! Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours. Happy translating.
I just open a PR for
thanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often Happy contributing.
Done translating ! My PR is available at ! Thanks for all you do, freeCodeCamp
I have sent a translation proposal for /docs/how-to-work-on-guide- PR Hope it will help!
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
Hello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-
Working on /docs/spanish/how-to-work-on-guide-
Hello, I've improved the file
Hello, Improving docs/spanish/how-to-catch-outgoing-emails-
Hi, I'm improving docs/spanish/how-to-work-on-coding-
Hi, can I help with /docs/spanish/how-to-setup-freecodecamp-
Sorry, I opened a bad PR regarding but already closed it. I found there was still an English part to be translated
Hi! Is there any remaining documentation where I can help translate?
you can improve or fix redaction and spelling errors.
Hi there, It would be good if at the top are checked so we can see what is left to be translated. Thanks
Where I can start helping?
sorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are a total crap (Like ) . I guess you opened a Pandora Box with your articule about HacktoberFest.
Hey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. . or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder
Hola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages. In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal. Another thing that could be specified in the guidelines is: Challenges translations. Should they be translated? Referrals to types and attributes (which need to be in English for proper coding). For example, type "date" not type "fecha". If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it). Hey I would like to know your thoughts about this. Thanks to you all and happy coding!
I agree that we should standardize around informal. I agree with you that we should look out for words like "fecha" that have been accidentally translated during our automated translation process.
Hi all I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment. What do people think about translating "array" as "arreglo"? I think this is a big mistake that has been repeated since somebody made that bad translation many years ago. As any Spanish speaker know, "arreglo" means "repair" (), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way. I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that "arreglo" was the (really bad) translation of "array". Then I could read the text as if I was reading an encoded message that had to be deciphered. I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is "ristra". According to the : Which basically means: "A group of things placed one after another" They also share all the phonems in "array", with the adittion of /r/ (rolling r) and /t/ in "ristra". I'm open to other candidates, but please, let's take "arreglo" out of the Spanish version. The word "array" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like "list", "function", "import", "scope", etc. [1]: [2]:
Hello guy, I vote for yes, let’s do the change and I think will create a huge impact around of the world! Please let me know if you have more question questions or concerns. Andres Haro Cell: (619) 534-3190
Thanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join if you need help getting set up
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
Thanks for working on the translations for the "Contributing to freeCodeCamp". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.

Puedes realizar los cambios sin tener que ejecutar nada desde tu sistema local. <del> Después de que encuentres el archivo que quieras modificar desde la interfaz de GitHub, haz clic en el icono de lápiz para comenzar a editar el archivo. Esto automáticamente creara una bifurcación del proyecto, si es que no tienes una todavía. </del> <ins> Después de que encuentres el archivo que quieras modificar desde la interfaz de GitHub, hace clic en el icono de lápiz para comenzar a editar el archivo. Esto automáticamente creara una bifurcación del proyecto, si es que no tienes una todavía. </ins> También puedes clonar el proyecto y editarlo de manera local en tu ordenador. Si necesitas ayuda al respecto, dale un vistazo a la [guía principal de contribución](/CONTRIBUTING.md). ### Patrón de los Desafíos. <del> He aquí un patrón de cómo se verán los archivos markdown correspondientes a los desafíos. </del> <ins> He aquí un patrón de cómo se verán los archivos reduccion correspondientes a los desafíos. </ins> ````md ---


Question:
from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at  When you make a PR for this particular issue, do not tag it with instead just reference it with
Hey ! How could I claim so we don't double work? Thanks
Hi ! Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours. Happy translating.
I just open a PR for
thanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often Happy contributing.
Done translating ! My PR is available at ! Thanks for all you do, freeCodeCamp
I have sent a translation proposal for /docs/how-to-work-on-guide- PR Hope it will help!
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
Hello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-
Working on /docs/spanish/how-to-work-on-guide-
Hello, I've improved the file
Hello, Improving docs/spanish/how-to-catch-outgoing-emails-
Hi, I'm improving docs/spanish/how-to-work-on-coding-
Hi, can I help with /docs/spanish/how-to-setup-freecodecamp-
Sorry, I opened a bad PR regarding but already closed it. I found there was still an English part to be translated
Hi! Is there any remaining documentation where I can help translate?
you can improve or fix redaction and spelling errors.
Hi there, It would be good if at the top are checked so we can see what is left to be translated. Thanks
Where I can start helping?
sorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are a total crap (Like ) . I guess you opened a Pandora Box with your articule about HacktoberFest.
Hey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. . or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder
Hola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages. In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal. Another thing that could be specified in the guidelines is: Challenges translations. Should they be translated? Referrals to types and attributes (which need to be in English for proper coding). For example, type "date" not type "fecha". If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it). Hey I would like to know your thoughts about this. Thanks to you all and happy coding!
I agree that we should standardize around informal. I agree with you that we should look out for words like "fecha" that have been accidentally translated during our automated translation process.
Hi all I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment. What do people think about translating "array" as "arreglo"? I think this is a big mistake that has been repeated since somebody made that bad translation many years ago. As any Spanish speaker know, "arreglo" means "repair" (), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way. I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that "arreglo" was the (really bad) translation of "array". Then I could read the text as if I was reading an encoded message that had to be deciphered. I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is "ristra". According to the : Which basically means: "A group of things placed one after another" They also share all the phonems in "array", with the adittion of /r/ (rolling r) and /t/ in "ristra". I'm open to other candidates, but please, let's take "arreglo" out of the Spanish version. The word "array" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like "list", "function", "import", "scope", etc. [1]: [2]:
Hello guy, I vote for yes, let’s do the change and I think will create a huge impact around of the world! Please let me know if you have more question questions or concerns. Andres Haro Cell: (619) 534-3190
Thanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join if you need help getting set up
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
Thanks for working on the translations for the "Contributing to freeCodeCamp". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.

## Descripción <section id='description'> <del> Una descripción del desafío y de los requerimientos aprobatorios </del> <ins> Una descripción del desafío y de los requisitos aprobacion </ins> </section> ## Instrucciones


Question:
from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at  When you make a PR for this particular issue, do not tag it with instead just reference it with
Hey ! How could I claim so we don't double work? Thanks
Hi ! Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours. Happy translating.
I just open a PR for
thanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often Happy contributing.
Done translating ! My PR is available at ! Thanks for all you do, freeCodeCamp
I have sent a translation proposal for /docs/how-to-work-on-guide- PR Hope it will help!
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
Hello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-
Working on /docs/spanish/how-to-work-on-guide-
Hello, I've improved the file
Hello, Improving docs/spanish/how-to-catch-outgoing-emails-
Hi, I'm improving docs/spanish/how-to-work-on-coding-
Hi, can I help with /docs/spanish/how-to-setup-freecodecamp-
Sorry, I opened a bad PR regarding but already closed it. I found there was still an English part to be translated
Hi! Is there any remaining documentation where I can help translate?
you can improve or fix redaction and spelling errors.
Hi there, It would be good if at the top are checked so we can see what is left to be translated. Thanks
Where I can start helping?
sorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are a total crap (Like ) . I guess you opened a Pandora Box with your articule about HacktoberFest.
Hey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. . or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder
Hola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages. In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal. Another thing that could be specified in the guidelines is: Challenges translations. Should they be translated? Referrals to types and attributes (which need to be in English for proper coding). For example, type "date" not type "fecha". If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it). Hey I would like to know your thoughts about this. Thanks to you all and happy coding!
I agree that we should standardize around informal. I agree with you that we should look out for words like "fecha" that have been accidentally translated during our automated translation process.
Hi all I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment. What do people think about translating "array" as "arreglo"? I think this is a big mistake that has been repeated since somebody made that bad translation many years ago. As any Spanish speaker know, "arreglo" means "repair" (), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way. I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that "arreglo" was the (really bad) translation of "array". Then I could read the text as if I was reading an encoded message that had to be deciphered. I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is "ristra". According to the : Which basically means: "A group of things placed one after another" They also share all the phonems in "array", with the adittion of /r/ (rolling r) and /t/ in "ristra". I'm open to other candidates, but please, let's take "arreglo" out of the Spanish version. The word "array" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like "list", "function", "import", "scope", etc. [1]: [2]:
Hello guy, I vote for yes, let’s do the change and I think will create a huge impact around of the world! Please let me know if you have more question questions or concerns. Andres Haro Cell: (619) 534-3190
Thanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join if you need help getting set up
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
Thanks for working on the translations for the "Contributing to freeCodeCamp". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.

Puedes:  - [Ayudarnos creando y editando artúclos de la Guía](#steps-for-creating-and-editing-guide-articles).   - [Ayudarnos creando y editando articulos de la Guía](#steps-for-creating-and-editing-guide-articles).  - [Ayudarnos a revisar Pull Requests para artículos de la guía]() ## Pasos para crear y editar artículos de la Guía 1. 🍴 [Fork este repositorio](https://github.com/freeCodeCamp/freeCodeCamp#fork-destination-box)  2. 👀 Sgiue las normas de controbución expuestas a continuación. 3. 🔧 Propón cambios asombrosos!   2. 👀 Sigue las normas de contribución expuestas a continuación. 3. 🔧 Propóne cambios asombrosos!  4. 📖 Lee la [guía de buenas prácticas de estilo](/docs/style-guide-for-guide-articles).  5. 👉 [Haz una Pull Request](https://github.com/freeCodeCamp/freeCodeCamp/compare)   5. 👉 [Hace un Pull Request](https://github.com/freeCodeCamp/freeCodeCamp/compare)  6. 🎉 Consigue que aprueben tu Pull request - Éxito!  O siemplement [crea un tema](https://github.com/freeCodeCamp/freeCodeCamp/issues) - toda pequeña ayuda cuenta! 😊   O simplemente [crea un tema](https://github.com/freeCodeCamp/freeCodeCamp/issues) - toda pequeña ayuda cuenta! 😊  ### [Sigue estas recomendaciones de nuestra guía de estilo para crear un artículo atractivo](/docs/style-guide-for-guide-articles.md)  ### Crear Pull Request para propoenr cambios   ### Crear Pull Request para proponer cambios   Hay dos formas de proponer cambios en el repositorio tras editar o añadir un articulo:   Hay dos formas de proponer cambios en el repositorio despues de editar o añadir un articulo:   - [Utilizando la interfaz de GitHub en tu navegador](#using-the-github-web-interface-on-your-browser). - [Trabajando en tu ordenador personal](#working-on-your-local-machine) (_recomendado_ para previsualiar cambios).   - [Utilizando el sistema de comunicacion de GitHub en tu navegador](#using-the-github-web-interface-on-your-browser). - [Trabajando en tu maquina local](#working-on-your-local-machine) (_recomendado_ para pre-visualiar cambios).   #### Utilizar la interaz web de GitHub   #### Utilizar el sistema de comunicacion web de GitHub  Mira este vídeo de demostración o sigue los siguientes pasos:  **[TODO]** Update the GIF recording.   **[TODO]** Actualizar la grabacion GIF.   ![GIF showing the GitHub interface steps](#)   ![GIF mostrando los pasos de la interfaz de GitHub](#)   1. Ve a la carpets **"páginas"** (situado en [`guide`](/guide)) donde encontrarás el artículo raiz que quieras editar.   1. Ve a las carpetas **"páginas"** (situado en [`guide`](/guide)) donde encontrarás el artículo raiz que quieras editar.  > Todas las raíces estarán en un archivo index.md  2. Pincha en Editar este archivo y haz tus cambios al archivo en la consola de edición de GitHub.   2. Pincha en Editar este archivo y hace tus cambios al archivo en la consola de edición de GitHub.  > Si el icono aparece gris y te muestra la alerta "Debes estar en una rama para hacer o proponer cambios a este archivo", significa que probablemente estés en la rama de otra persona. En la parte superior izquierda de la página hay una casilla desplegable que dice: "Árbol: #######". Pincha en el desplegable y cambia la rama a maestra. El icono de edición debería estar disponible ahora.


Question:
from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at  When you make a PR for this particular issue, do not tag it with instead just reference it with
Hey ! How could I claim so we don't double work? Thanks
Hi ! Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours. Happy translating.
I just open a PR for
thanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often Happy contributing.
Done translating ! My PR is available at ! Thanks for all you do, freeCodeCamp
I have sent a translation proposal for /docs/how-to-work-on-guide- PR Hope it will help!
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
Hello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-
Working on /docs/spanish/how-to-work-on-guide-
Hello, I've improved the file
Hello, Improving docs/spanish/how-to-catch-outgoing-emails-
Hi, I'm improving docs/spanish/how-to-work-on-coding-
Hi, can I help with /docs/spanish/how-to-setup-freecodecamp-
Sorry, I opened a bad PR regarding but already closed it. I found there was still an English part to be translated
Hi! Is there any remaining documentation where I can help translate?
you can improve or fix redaction and spelling errors.
Hi there, It would be good if at the top are checked so we can see what is left to be translated. Thanks
Where I can start helping?
sorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are a total crap (Like ) . I guess you opened a Pandora Box with your articule about HacktoberFest.
Hey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. . or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder
Hola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages. In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal. Another thing that could be specified in the guidelines is: Challenges translations. Should they be translated? Referrals to types and attributes (which need to be in English for proper coding). For example, type "date" not type "fecha". If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it). Hey I would like to know your thoughts about this. Thanks to you all and happy coding!
I agree that we should standardize around informal. I agree with you that we should look out for words like "fecha" that have been accidentally translated during our automated translation process.
Hi all I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment. What do people think about translating "array" as "arreglo"? I think this is a big mistake that has been repeated since somebody made that bad translation many years ago. As any Spanish speaker know, "arreglo" means "repair" (), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way. I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that "arreglo" was the (really bad) translation of "array". Then I could read the text as if I was reading an encoded message that had to be deciphered. I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is "ristra". According to the : Which basically means: "A group of things placed one after another" They also share all the phonems in "array", with the adittion of /r/ (rolling r) and /t/ in "ristra". I'm open to other candidates, but please, let's take "arreglo" out of the Spanish version. The word "array" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like "list", "function", "import", "scope", etc. [1]: [2]:
Hello guy, I vote for yes, let’s do the change and I think will create a huge impact around of the world! Please let me know if you have more question questions or concerns. Andres Haro Cell: (619) 534-3190
Thanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join if you need help getting set up
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
Thanks for working on the translations for the "Contributing to freeCodeCamp". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.

Documentos: Actualizadas recomendaciones de contribución ``` <del> Se breve, no más de 50 caracteres. Puedes añadir información extra en la descripción del mensaje. </del> <ins> Sea breve, no más de 50 caracteres. Puedes añadir información extra en la descripción del mensaje. </ins> esto no supone ningún esfuerzo adicional respecto a mensajes como 'update file' o 'add index.md'


Question:
from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at  When you make a PR for this particular issue, do not tag it with instead just reference it with
Hey ! How could I claim so we don't double work? Thanks
Hi ! Actually we just merge in the first PR for open issues. And your comment on this thread is enough. So, its yours. Happy translating.
I just open a PR for
thanks a lot that was fast! Would you be interested in translating these in future as well? If yes, please keep a watch on this thread. We will be updating on the progress often Happy contributing.
Done translating ! My PR is available at ! Thanks for all you do, freeCodeCamp
I have sent a translation proposal for /docs/how-to-work-on-guide- PR Hope it will help!
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
Hello, I'm starting to help on the translation of the document /how-to-set-up-freecodecamp-
Working on /docs/spanish/how-to-work-on-guide-
Hello, I've improved the file
Hello, Improving docs/spanish/how-to-catch-outgoing-emails-
Hi, I'm improving docs/spanish/how-to-work-on-coding-
Hi, can I help with /docs/spanish/how-to-setup-freecodecamp-
Sorry, I opened a bad PR regarding but already closed it. I found there was still an English part to be translated
Hi! Is there any remaining documentation where I can help translate?
you can improve or fix redaction and spelling errors.
Hi there, It would be good if at the top are checked so we can see what is left to be translated. Thanks
Where I can start helping?
sorry to put it in this issue, but is there any way somebody could help with the pull requests? I mean, there are 5K+ opened already, people are sending them in troves, and I suspect a lot of them are a total crap (Like ) . I guess you opened a Pandora Box with your articule about HacktoberFest.
Hey all, not a translation, but fixes for the language bar of HTML links on the README file for Spanish, and markdown links to the How To guides that everyone has been translating. . or anyone else looking to do translations in Spanish, you could make a copy of the 2 style guides to translate into Spanish from the English version in the doc folder. It looks like those weren't in to the Spanish folder originally or included on this issue. Just leave the title the same, but put it in the Spanish folder
Hola! to all. I believe we should have guidelines for Spanish translations, which include what treatment (formal or informal) to use when referring to actions or the user. For example, Agregue (formal) or Agrega (informal). - I don't know if this kind of things are found in other languages. In the last articles I've read I've seen a mix between formal and informal, and I think we should standardize (I have done it with some articles). I propose to always use informal. Another thing that could be specified in the guidelines is: Challenges translations. Should they be translated? Referrals to types and attributes (which need to be in English for proper coding). For example, type "date" not type "fecha". If there is a guideline already, please let me know, if not, I would be happy to start one (just let me know where to put it). Hey I would like to know your thoughts about this. Thanks to you all and happy coding!
I agree that we should standardize around informal. I agree with you that we should look out for words like "fecha" that have been accidentally translated during our automated translation process.
Hi all I'm not sure if this is the right issue to discuss this, or if I should open a new one. I'm happy to open a new one if that makes things easier to track. I'll keep it here for the moment. What do people think about translating "array" as "arreglo"? I think this is a big mistake that has been repeated since somebody made that bad translation many years ago. As any Spanish speaker know, "arreglo" means "repair" (), and it makes any programming related text even harder to understand. This is especially true for programming texts because it's full of abstract nouns and things that are not easy to represent in a tangible way. I learned to code in English (mainly FCC and Coursera), and after a while, I stumbled upon a programming text written in Spanish. I couldn't understand what it was talking about until I found out that "arreglo" was the (really bad) translation of "array". Then I could read the text as if I was reading an encoded message that had to be deciphered. I propose that the Spanish version of FreeCodeCamp doesn't carry on with that translation, which is just based on the similarity of the spelling but has nothing to do with the meaning of the words. I think the right term in Spanish is "ristra". According to the : Which basically means: "A group of things placed one after another" They also share all the phonems in "array", with the adittion of /r/ (rolling r) and /t/ in "ristra". I'm open to other candidates, but please, let's take "arreglo" out of the Spanish version. The word "array" has been used in Spanish texts before and even though it's not a Spanish word, I think it's still better than a word that exists with a different meaning. And to be honest, anyone learning how to code will have to become familiar with certain English terms like "list", "function", "import", "scope", etc. [1]: [2]:
Hello guy, I vote for yes, let’s do the change and I think will create a huge impact around of the world! Please let me know if you have more question questions or concerns. Andres Haro Cell: (619) 534-3190
Thanks - I agree that these machine translations need improvement. I encourage you to dig in and start fixing them. Be sure to join if you need help getting set up
There is still work pending on this. When you make a PR for this particular issue, do not tag it with instead just reference it with
Thanks for working on the translations for the "Contributing to freeCodeCamp". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.

5. En la siguiente pantalla, puedes añadir más detalles sobre tu PR, luego pincha en <kbd>Crear pull request</kbd>. <del> Enhorabuena 🎉! Acabas de crear una pull request. </del> <ins> Felicidades 🎉! Acabas de crear un pull request. </ins> #### Trabajar desde tu sistema local (_recomendado_ para revisar cambios) <del> No es obligatorio que trabajes en tu sistema personal, salvo que desees previsualizar tus cambios, o trabajar con mejoras y arreglos de UI. También es recomendable si tienes problemas con git como errores de integración, rebase, etc. </del> <ins> No es obligatorio que trabajes en tu sistema personal, salvo que desees pre-visualizar tus cambios, o trabajar con version actualizada y arreglos de UI. También es recomendable si tienes problemas con git como errores de integración, rebase, etc. </ins> <del> ##### Lee sobre esta recomendaciones en [Cómo configurar freeCodeCamp localmente](/docs/how-to-setup-freecodecamp-locally.md) </del> <ins> ##### Lee sobre estas recomendaciones en [Cómo configurar freeCodeCamp localmente](/docs/how-to-setup-freecodecamp-locally.md) </ins> ### Aceptación de la PR <del> Estas son algunos criterios utilizados por los revisores cuando evalúan PRs: </del> <ins> Estos son algunos criterios utilizados por los criticos cuando evalúan PRs: </ins> - Descripción y título relevantes - La PR respeta la [guía de estilo](/docs/style-guide-for-guide-articles) - Consejos generales de QA de las [recomendaciones para Moderadores](https://forum.freecodecamp.org/t/freecodecamp-moderator-guidelines/18295) <del> - Siempre y cuando la PR suponga una mejora o ampliación de la guía, será aceptada aunque tenga errores gramaticales o contenido parcial </del> <ins> - Siempre y cuando el PR suponga una mejora o ampliación de la guía, será aceptado aunque tenga errores gramaticos o contenido parcial </ins> - Las PR más antiguas se revisan primero #### Etiquetas - **contenido** es para Pull Requests que modifican el contenido de artículos en la guía (añaden un nuevo artículo o actualizan uno existente) <del> - **duplicada** es para Pull Request que contienen el mismo contenido que otra PR abierta - **cambios solicitados** es para Pull Requests que necesitan algún cambio antes de ser integradas - **pasada** es para Pull Requests que con etiqueta _"changes requested"_ que no han tenido actividad durante al menos 2 semanas y serán por tanto cerradas - Una  pull request _pasada_ debe cerrarse. </del> <ins> - **duplicada** es para Pull Request que contienen el mismo contenido que otro PR abierto - **cambios solicitados** es para Pull Requests que necesitan algún cambio antes de ser integrados - **pasada** es para Pull Requests que con etiqueta _"changes requested"_ que no han tenido actividad durante al menos 2 semanas y serán por tanto cerrados - Un  pull request _pasado_ debe cerrarse. </ins> - Este es [un ejemplo](https://github.com/freeCodeCamp/freeCodeCamp/pull/235). #### Contenido conflictivo/duplicado <del> Se considera **duplicada** una PR si hace cambios al mismo artículo que otra PR. </del> <ins> Se considera **duplicado** un PR si hace cambios al mismo artículo que otro PR. </ins> En general el revisor: <del> 1. Organizará las PR desde la más antigua </del> <ins> 1. Organizará los PR desde lo más antiguo </ins> 2. Buscará para PRs con contenido similar <del> 3. Integrará desde la más antigua a las más nueva </del> <ins> 3. Integrará desde lo más antiguo a los más nuevos </ins> <del> Muy probablemente aparecerán conflictos al integrar PRs duplicadas. </del> <ins> Muy probablemente aparecerán conflictos al integrar PRs duplicados. </ins> <del> Los revisores harán todos los esfuerzos posibles para resolver estos conflictos e integrar las PRs. </del> <ins> Los revisores harán todos los esfuerzos posibles para resolver estos conflictos e integrar los PRs. </ins> #### Solicitar cambios <del> Si la Pull Request no es perfect el revisor podría: </del> <ins> Si el Pull Request no es perfecto el revisor podría: </ins> - solicitar cambios al contribuidor y añadir la etiqueta *cambios solicitados* <del> - solucionar errores menores y hacer un envío encima de la PR </del> <ins> - solucionar errores menores y hacer un envío encima de el PR </ins> #### Travis CI Build <del> Todas las PRs deben superar los test de Travis CI antes de poder ser integradas. </del> <ins> Todos los PRs deben superar los test de Travis CI antes de poder ser integrados. </ins> <del> Si una PR rompe la ejecución (un test de Travis CI falla y muestra una "X" roja) hay tres cauas probables y tendrás que resolver el problemas antes de que podamos integrar la PR: </del> <ins> Si un PR rompe la ejecución (un test de Travis CI falla y muestra una "X" roja) hay tres causas probables y tendrás que resolver el problema antes de que podamos integrar el PR: </ins> <del> 1. Tu PR crea un nueva artículo pero la falta un archivo `index.md` en algún lugar. </del> <ins> 1. Tu PR crea un nuevo artículo pero le falta un archivo `index.md` en algún lugar. </ins> - Cada directorio en `src/pages` necesita un archivo `index.md` en él (y debe llamarse `index.md`). - Dos escenarios muy probables son - llamaste al archivo de forma distinta a `index.md`, o


Question:
from its english version at from its english version at from its english version at from its english version at from its english version at from its english version at
Please, review
[x] [x] /docs/russian/how-to-work-on-coding- [] ()
Fixes the html links in the top language bar for all language README docs. Not a translation, but just link fixes. Once the Russian README files get merged, we can add the markdown style for links to all the articles in Russian too!
started to review PRs. ping me if more help needed reviewed and requested changed at LGTM from native russian speaker view LGTM Resolve conflict is needed
Hi, guys! Please review my PR
Thanks for working on the translations for the "Contributing to freeCodeCamp". Here on we are making contributing to translations for contribution docs ad hoc. You are free to make pull-requests for improving these translations. We are closing the issue as these do not need tracking per se. You can raise a fresh issue if you find something incorrect in the existing docs.

<ins> <!-- do not translate this --> | [Read these guidelines in other languages](/docs/i18n-languages) | |-| <!-- do not translate this --> # Как создать Pull Request (Пулл Реквест) ## Как сделать хороший заголовок для Pull Request: Создавая Pull Request (PR), воспользуйтесь данной таблицей, чтобы решить, как правильно озаглавить PR в формате: `fix/feat/chore/refactor/docs/perf (scope): PR Title` Например: `fix(learn): Fixed tests for the do...while loop challenge`. | Область | Описание | |---|---| | `learn`,`curriculum` | Для PR'ов, которые вносят изменения в учебный план. | | `client` | Для PR'ов, которые вносят изменения в логику клиентской платформы или пользовательский интерфейс. | | `guide` | Для PR'ов, которые вносят изменения в инстукции. | | `docs` | Для PR'ов, которые вносят изменения в документацию. | ## Создание Пулл Реквеста (PR) 1. После того, как вы внесёте какие-нибудь изменения в свой форк репозитория, GitHub предложит вам создать PR ![Изображение - Предложение о создании PR](/docs/images/github/compare-pull-request-prompt.png) 2. По умолчанию все PR создаются в ветку `master` основного репозитория freeCodeCamp При создании PR, убедитесь, что в поле "base fork" указан репозиторий freeCodeCamp/freeCodeCamp ![Изображение - Сравнение форков при создании PR](/docs/images/github/comparing-forks-for-pull-request.png) 3. Нажать на кнопку "Create pull request", для создания PR из вашей верки в ветку `master` freeCodeCamp. 4. В поле описания PR добавьте более подробный отчёт сделанных вами изменений и причины по которым появилась такая необходимость - Вам будет предоставлен шаблон, который содержит контрольные список пунктов, которые вам необходимо выполнить, прежде чем вы создадите PR. - Заполните эти пункты. Опираясь на них, будет приниматься решение о рассмотрении и принятии вашего PR - Если PR предназначен для исправления существующей ошибки/проблемы, то в конце описание вашего PR добавьте ключевое слово `closes` и #xxxx (где xxxx это номер выпуска). Например: `closes #1337`. Так GitHub поймёт, что при успешном принятии PR нужно автоматически закрыть Issue с указанным номером 5. Укажите, тестировали ли вы локальную копию сайта или нет. Тестирование необходимо, когда вы не просто меняете какой-то текст (например, статью руководства), а изменяете JavaScript, HTML или CSS файлы, которые могут изменить функциональность или макет страницы. </ins>


Question:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: Link to the guide on the challenge Data Visualization: Data Visualization with D3: Use the and Functions to Find Minimum and Maximum Values in a Dataset is pointing to the wrong place Incidentally, the challenge page uses the d3-max and d3-min in the url while the guide page uses and Add a Link to the page with the problem: Get a Hint button brings the camper to which is 404 - Page not found Correct link is Tell us about your browser and operating system: Browser Name: Mozilla Firefox for Ubuntu canonical - 1.0 Browser Version: 62.0.3 Operating System: Ubuntu 18.04 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):
/ If you can guide me to where this file might be located. I can check....
Solution <body<scriptconst positionData = [[1, 7, -4],[6, 3, 8],[2, 9, 3]] // Add your code below this line const maxX = (positionData, (d) =d[2]); const output = maxX ; // Change this line // Add your code above this line ("body") .append("h2") .text(output) </script</body

--- title: Use the d3.max and d3.min Functions to Find Minimum and Maximum Values in a Dataset --- ## Use the d3.max and d3.min Functions to Find Minimum and Maximum Values in a Dataset This is a stub. Help our community expand it. This quick style guide will help ensure your pull request gets accepted.


Question:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: Link to the guide on the challenge Data Visualization: Data Visualization with D3: Use the and Functions to Find Minimum and Maximum Values in a Dataset is pointing to the wrong place Incidentally, the challenge page uses the d3-max and d3-min in the url while the guide page uses and Add a Link to the page with the problem: Get a Hint button brings the camper to which is 404 - Page not found Correct link is Tell us about your browser and operating system: Browser Name: Mozilla Firefox for Ubuntu canonical - 1.0 Browser Version: 62.0.3 Operating System: Ubuntu 18.04 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box):
/ If you can guide me to where this file might be located. I can check....
Solution <body<scriptconst positionData = [[1, 7, -4],[6, 3, 8],[2, 9, 3]] // Add your code below this line const maxX = (positionData, (d) =d[2]); const output = maxX ; // Change this line // Add your code above this line ("body") .append("h2") .text(output) </script</body


Question: <!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --Describe your problem and how to reproduce it: The formatting of the header-tag page in the guide is wrong. I checked the codebase and there are missing back-ticks for some of the html tags in the markdown page. Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: Version 70.0.3538.102 (Official Build) (64-bit) Operating System: MacOS 10.14.1 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): !

The `<header>` tag is a container which is used for navigational links or introductory content. It may typically include heading elements, such as `<h1>`, `<h2>`, but may also include other elements such as a search form, logo, author information etc. <del> <h1> corresponds to the most important heading. As we move to other tags like <h2>, <h3>, etc the degree of importance decreases. </del> <ins> `<h1>` corresponds to the most important heading. As we move to other tags like `<h2>`, `<h3>`, etc the degree of importance decreases. </ins> Although not required, the `<header>` tag is intended to contain the surrounding sections heading. It may also be used more than once in an HTML document. It is important to note that the `<header>` tag does not introduce a new section, but is simply the head of a section. Here's an example using the `<header>` tag:


- text: No global myVar variable testString: assert(typeof myVar === 'undefined', 'No global myVar variable'); - text: Add a local myVar variable  testString: assert(/vars+myVar/.test(code), 'Add a local myVar variable');   testString: assert(/functions+myLocalScopes*(s*)s*{s[sS]+s*vars*myVars*(s*|=[sS]+)s*;[sS]+}/.test(code), 'Add a local myVar variable');  ```


Question:
Expected behavior Please see attached screenshot for more details. Basically: [x] "Contact email" should be "Email Us" [x] We should get rid of the outbound link icons [ ] The footer should always go below the tallest element. Currently on the Guide, it seems to go under the least tall element. Screenshots <img width="1246" alt="echoandprint_freecodecamp_guide" src="https://user-"
Side note (perhaps a separate issue): the footer on the page is difficult to get to due to the loading of content on a scroll down. So you have to keep scrolling and keep loading content until there's no more to load to reach the footer. I suppose there would be a similar issue on the forum or anywhere else that uses the loading on a scroll.
I'll give it a try.
I have fixed the first two issues but couldn't quite reproduce the third one either in Chrome or Firefox(In Windows 10). cc - !
There is a UX trade off for doing that for implementing the third one. In order for the footer to go under the tallest element, both elements should have the height of 100% (no-scroll). In that case, when user clicks on a side nav that is taller than the content, the page should either go to the top to show the top of the content (loses the location of the scroll), or keep its scroll which means the user will scroll up and down just to change the tabs. here is a demo: ! with no footer, our layout would have behaved similar to the default Gatsby sidebar example. With the footer, the optimal solution would be to add some javascript and have a floating sidebar that stops at the footer. We could also have a fixed sidebar that the footer would overlap at the end of the page. imho, the current setup does the job, but please let me know which solution you would like me to explore.
Hi I agree with I think the key here is to use the site as an end user, and then decide on the tradeoff. I agree that the current sidebar is far better UX for the user, who are more likely browsing through an article and have it in view rather than have them scroll a long way to switch to the next topic of their interest. That will definitely increase a session time and reduce bounce rate.
That is fine. People will scroll. I think you all are dramatically overestimating the inconvenience of scrolling. On mobile, this will all be a single column layout anyway. This is what people thought was the optimal solution back in the 1990s. In practice, it's confusing to users. Users would much rather scroll up and down a page then have to move their mouse around to different "frames" and scroll up and down within those in a more confined space. Just look at this page here on GitHub. The footer is always at the bottom of the tallest column, which in this case is the middle one. If I want to see who this issue is assigned to, yes - I have to scroll back up to the top of the page. That's no big deal - it takes less than a second. We should use a similar approach with footers everywhere on freeCodeCamp. Separate horizontal scrolling portions are bad enough, and I'd like to move away from them - let alone separate vertical portions. Here's an example of how having separate scrolling areas is hurting usability on learn: <img width="1415" alt="learnbasichtmlandhtml5fillintheblankwithplaceholdertextfreecodecamporg" src="https://user-"A new user might not even realize that there are buttons and tests underneath the "run test" button. The footer should always be at the bottom of whichever column is tallest, and we should not have independently scrolling columns. At some point in the past year or two, the independently scrolling columns were introduced. could you start working on a version that puts the footer at the bottom of the tallest column?
I strongly recommend testing the app as user would to derive the best UX for our app's use case. For the Guide, I think the tallest element principle does not work in practice, you can test that locally yourself, it's just weird to scroll through whitespace vs content. People will scroll through content, not whitespace? For Learn I had given my feedback in a comment here: But, we quickly realized that the tallest element won't work either. Here is what we should do though is to use the buttons as a fixed component on learn. This gives us the ability to scroll the "content" as much as we want, while keeping the most used component buttons in our case in view. ! Also, I would like to bring light to the fact that several feedback (fairly frustrated) threads that we have had here on GitHub and forum is the ability to use the challenge map about scrolling. It works when you are casually browsing, not when you are looking for something specific. But that's a different problem unrelated to this thread. Anyways, let's start working on a version that does put the footer at the bottom of the tallest element and do a A/B test.
I will make a MVP and have you test it ASAP. Here is how Khan academy does it when the scroll meets the footer. Notice the shadow indicating that side nav is continuing and scrollable <img width="504" alt="screen shot 2019-02-12 at 9 29 49 pm" src="https://user-".
Please let me know if you wanna move forward with this design, and if you want the user to go to the top of the page after clicking the side nav or not so I could adjust it accordingly.
Please take a look at this document: Also consider this: very few people are actively looking for the footer. And if they are, they're just going to swipe down really fast and get there immediately, regardless of how tall the page is. The main purpose of the footer is SEO and for the 0.001% of people who are actively looking for it. (how many times a day do you find yourself trying to scroll down to content in a footer?) The Guide's sidebar is only 109 entries tall. It's not going to be that much space. If they have one of the bigger categories expanded, yes, it could be more. But I don't think the footer is important enough to warp the experience of the guide.
A good example of how to handle a documentation page with expandable side menu items, and a footer, without extra scrolling is the MDN: When you expand the menu items on the left, the footer just gets pushed further down the page.
with these changes, this issue will back Or am I missing something?
so I think wants the page scroll to go to zero only when a node with no children is clicked on the side nav. I cannot think of a way that I could implemented it without recording and resetting the scroll with JS, so if anything comes to your mind, let me know.
Nodes with children also have articles.
very good point, so we would be reverting to the bug, then. if the height of both elements are set to 100% our footer would be pushed down when an element is expanded; however, in the mozilla doc, Nodes with children do not have articles. So users can click on an end node on the side nav and then it page goes to the top. in our case, if a user wants to visit for example . She would be scrolling the whole side nav 3 times. If we really need to go in that direction, the other option would be not take the users to the top of the page regardless of where they click on the nav. but when they reach their destination in the sidenav tree, they will have to scroll up to see the article's beginning.
Hi IMHO, and all honesty I really do not care about the footer. Meaning we are on the same page about its priority. The idea is the best usability of the site itself. I am not advocating that we should not make it so that people do not have to scroll. All I am interested in is making the UX intuitive and not painful from a user's viewpoint. I completely agree on your well researched thoughts about scrolling. But I keep re-iterating to test the site ourselves in A/B strategy and see what works best for us. In my tests, I found it weird and awkward to scroll when I am working through challenges, or looking through guide articles (not casually browsing like on a news site). So, from my tests: On the guide, the footer should be below the content element (the right guide article itself). The content element will expand in height depending on its content. This will keep the footer out of the view at all times. That is The footer can be hidden out of view under the viewport. Your MDN example, does something same. At all times, the content block is on the top of the footer. On the learn, I think we should get rid of the internal scrolls. But this also means, we should keep three things always in view: editor (labeled 2 on my screenshot) buttons preview panel (labeled 4 on my screenshot) These are the most interacted elements on the learn app. Only the instructions (without the buttons, will scroll) The footer can be hidden out of view under the viewport.
Maybe for the challenges and guide page we could make a smaller footer similar to the one github uses.
!
Re-opening. GitHub closed it automatically. This issue will be taken care of in repeated iterations.
I believe the decision is to make the sidebar more concise so there would not be a need to scroll. Although displaying the sibling nav items were discussed, I think it would be best to move forward with something similar to the following convention where only children and parent nodes are in the sidebar. !
Yes, let's get a variation that you propose in, and test it out.
I have a couple of suggestions on the footer: I feel the links are too cramped and need a little more padding between them Headings can be simplified There should be substantial space between the block of text on the left and the links At the end, it could look somewhat like this: !
I really like your design, it definitely looks better than the current one. Here are a couple of considerations. The logo looks great, but it makes the footer area taller. As a general rule we would like to save as much screen real state as possible. To be accessible we need a way other than color to establish visual hierarchy between headings and footer items. I encourage you to take screenshot of both the current version and your design so we could compare their sizes and their white space allocation better. After that let's have a pr and merge the changes.
Also I don't think you're allowed to change the colour of logo according to https://design-style-
let us address side-nav related suggestions and improvement in the above-referenced issue so it does not get confused with the footer.
Here are the screenshots for screenshots for comparison. ! ! !
would you be interested in making the footer titles more concise as suggested?
I always have this message always poping up when i run my code "Your Footer do not all have a white color" i have done all i could but cannot detect any fault in my code. this stopped my html from running further. I gave an inline style with white as color yet the problem continued. I just don't know what to do again

import React from 'react'; import { Link as GatsbyLink } from 'gatsby'; import { Grid, Row, Col } from '@freecodecamp/react-bootstrap'; <del> import FontAwesomeIcon from '@fortawesome/react-fontawesome'; import { faExternalLinkAlt } from '@fortawesome/free-solid-svg-icons'; </del> import './footer.css';