Without one of the most important things to have up and running when looking for potential new jobs as a developer is a Github account, and have a clue on version control and using Git.
I have noticed over the community some people are having trouble getting up and running with this, and perhaps feel intimidated contributing to large projects at such an early stage. This has in turn lead me to create a community project that everyone can feel free to get involved in and get practice in Github and learn the various benefits of the platform.
I have set up a repo called the āFront End Bibleā mainly with the vision of having a large database of tricks and effects that people can add to their portfolios. Yes, it isnāt going to be breaking any boundaries, but hopefully this doesnt feel so intimidating for people with little experience to get involved in.
As you can see, the layout is very simple. A folder for CSS and a folder for JS. As time goes on I will look (or be open to suggestions) to change this into a more database style structure. If you click on any of the files that are already there, you will see they contain the necessary snippets of code to get the effect up and running on your website.
All contributions will be welcomed no matter how big or small, and all contributors will be linked on the readme file. This is a good step up from the various Github tutorials that are out there, and gives you something to fork to your page and start commiting too.
I think as a platform it is quite intimidating for those that are new to it. I still am nervous of actually contributing to anything of scaleā¦ hopefully one day soon! Yet it is so important!
I have seen practice repos, but some of the time they arenāt actually building anything of use.
I thought this would be a cool concept for people who were new, right through to more experienced folk. Maybe at some point it will grow past front-end, but who knows. The more the merrier!
I donāt have a contribution per se, but Iāve got a highly disorganized casserole of web development topics that I havenāt found in other study guides here. Feel free to clone, fork, copy and paste any of this information you want.
Youāre welcome! Thank you for letting me contribute!
What do you think about including examples for these tricks/effects? When I made my contribution, I thought about putting a Codepen example URL in a comment, but I wasnāt sure if it was appropriate. I think being able to see what the tricks/effects would look like would be helpful, but Iām not sure the best way to implement such a thing (if you would want it implemented, of course).
Do you think this format is okay (see below), or did you have something else in mind?
/*
Make links display on a web page with a gradient underline. Also, make that underline gradient expand to cover the link text when you hover your cursor over the link.
See an example: https://codepen.io/jeremybbauer/pen/zPVKmR
*/
@jeremybbauer yes that format looks spot on! Thanks very much for getting involved mate. We have a number of people showing interest, I think the more it grows the more people will get involved with their own contributions.
I would be massively appreciative at some point if we could get a review/overview of the freecodecamp course by someone who has got some (or at least one) of the certs.
Awesome! Iām happy to help, and I appreciate the opportunity to contribute!
I think it would be great for a cert. holder to review freeCodeCamp. Iām still in the JavaScript section, or Iād be happy to do it myself. Maybe someday .
@DarrenfJ
I think I get what you are trying to say, that could be alright as it fits the theme of their project but that would mean that we create a click-ception on our part, we could do it, but without linking it our project.
We want to get people to click our project, see the quick todo list, go step by step and voila, first commit.
I wanted to refactor some of the readme to serve that purpose anyway, what do you think?
Or a special note like āfor guides on git/github check out our friendsā @JABedford/Front-End-Bible code vaultā in the readme if they want more concise instructionsā¦
they all sound goodā¦ a click-ception guide for this project, links to it in ours, and a very basic read.me in our to get people startedā¦ something like that
.