Port front end demo projects to .rocks

[Goldac77]

The reference Tribute page used in the Tribute Page project opens in Codepen as well. Out of curiosity, I tried to copy and paste the code from the editor on the reference page to the Test Suite Template page made for the user. I wasn't really surprised but it works, there is nothing that prevents the user from copying and pasting code to pass tests.

My point is, this can lead to laziness in a way (if you just want to finish the course and have a certificate or something). Kindly do something about it, say using a different platform, or patterning with Codepen to design a custom environment for your projects. It can even deter people who require an environment where the user to forced to bring out fresh ideas, like myself.

The screenshot attached shows copied(highlighted)
code from the reference page

Not going to lie, I was feeling lazy and just went with it for this one, maybe I won't for the other ones. Please do something about this

[ShaunSHamilton]

Hello there,

On the one hand, in order to claim any certification, a camper has to agree to the Academic Honesty Pledge

Before you can claim a verified certification, you must accept our Academic Honesty Pledge, which reads:
"I understand that plagiarism means copying someone else’s work and presenting the work as if it were my own, without clearly attributing the original author."

"I understand that plagiarism is an act of intellectual dishonesty, and that people usually get kicked out of university or fired from their jobs if they get caught plagiarizing"...

And, most relevant (there is more in the link above):

"I pledge that I did not plagiarize any of my freeCodeCamp.org work. I understand that freeCodeCamp.org’s team will audit my projects to confirm this."

On the other hand, freeCodeCamp is not a policing-based course; it is a course which aims to teach. Part of teaching is guiding campers through projects with user stories. If any camper chooses to shoot themselves in the foot (so to say), by being lazy (in the projects, or throughout the course) and plagiarising, or just copying answers, then that is on them, and defeats the purpose of even completing any of the course.

My suggestion, if you do feel like you might be "lazy", is to not look at the example project, before starting.

[Goldac77]

Thanks for the reply, I completely understand and agree with you. In full honesty, I will redo the Tribute page project to get a chance to test new things I've learnt. Thank you for the good work

…

On Sun, Sep 13, 2020, 11:08 PM Shaun Hamilton ***@***.***> wrote: Hello there, On the one hand, in order to claim any certification, a camper has to agree to the Academic Honesty Pledge <https://www.freecodecamp.org/settings> Before you can claim a verified certification, you must accept our Academic Honesty Pledge, which reads: "I understand that plagiarism means copying someone else’s work and presenting the work as if it were my own, without clearly attributing the original author." "I understand that plagiarism is an act of intellectual dishonesty, and that people usually get kicked out of university or fired from their jobs if they get caught plagiarizing"... And, most relevant: "I pledge that I did not plagiarize any of my freeCodeCamp.org work. I understand that freeCodeCamp.org’s team will audit my projects to confirm this." On the other hand, freeCodeCamp is not a policing-based course; it is a course which aims to teach. Part of teaching is guiding campers through projects with user stories. If any camper chooses to *shoot themselves in the foot* (so to say), by being lazy (in the projects, or throughout the course) and plagiarising, or just copying answers. My suggestion, if you do feel like you might be "lazy", is to not look at the example project, before starting. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/freeCodeCamp/testable-projects-fcc/issues/1231#issuecomment-691738633>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APQMF4SDN4MSKYPKR722UXTSFVGFPANCNFSM4RK3X33Q> .

[kevinsmithwebdev-zz]

Rather than having the examples in codepen, would it be good to just have them built as static pages, that they can just look at? I don't know - just thinking out loud.

[naomi-lgbt]

That's not a bad idea, I think.
Campers can still use CodePen to build their own work if they choose, but the source code for the examples would be less readily available. Still accessible in the dev tools, I believe, but that is a better alternative IMO.

[kevinsmithwebdev-zz]

Yeah, a clever coder could still find the code, but many of the beginners wouldn't know how, and at least it would be more work in that case, less of a tempation.

[RandellDawson]

We are actually in the process of moving the front-end example projects off Codepen.

[Goldac77]

That would be awesome

[moT01]

Do we want to move these to .rocks or something else? I thought I remember a mention of github pages at one point.

[naomi-lgbt]

We could move some of them to GitHub Pages, though the ones built on React will take a bit of extra help to get deployed.

[moT01]

This may have previously been answered, but I'm curious why we won't just put them on .rocks with the rest of the projects. They would all be in one place.

[naomi-lgbt]

I don't remember seeing that discussion at all, tbh - and agree that .rocks would be the best solution.

[moT01]

If anyone is interested, the process would be to take the source code of each project from the testable-projects repo, maybe clean it up if needed at all, and move it to the demo-projects repo

[Sembauke]

Do we still want to do this as this is now a legacy Certification?

[ShaunSHamilton]

@Sembauke This is already done, as far as I am aware.

---

Remember, this is not a legacy certification; the content has just changed - certification is exactly the same, and we use the same example projects for the certification projects.

[ShaunSHamilton]

Actually. My bad. We have ported over the RWD projects, but we have not done so for the Front End Development Libraries or Data Vis.

I will create a new issue for those.