6 ms·

Resources for Frontend development

35 points by codingknight 6y ago

codingknight 6y ago
Here is an exhaustive list of all the resources you might need for frontend development
- purplecats 6y ago
  what are the most practical strategies to maneuver such a resource? there's too many to go through one by one, and i just want to know what stack i want to use. it'd be cool if there was a tool that leveraged all this knowledge and presented a wizard that helped you find the best stack based on your preferences and needs.
  - codingknight 6y ago
    The best way to go through this resource is to use it as a reference which is actually its main purpose. Its practically impossible to go through all of it one by one. I'd say figure out the stack you wish to use and then go to the resource as a reference to the resources out there. Check them out and use the one that appeals to you.
  - deleted 6y ago
    [deleted]
  - ratww 6y ago
    > and i just want to know what stack i want to use This is mostly geared towards basic learning and documentation, so you definitely kinda need something else for finding a stack. You can pick one of the tutorials and use it as a guide for your future work. I mean, it pretty much only covers React as far as frameworks go, so I guess if you follow it you'll pick React plus some CSS framework? There's still other stuff you need other than that for a "stack".
- ratww 6y ago
  You can't really call it exhaustive. Exhaustive means "Including or considering all elements or aspects; fully comprehensive". This list only covers the basics of React, and doesn't even include tooling.
  - franciscop 6y ago
    I personally consider Create React App and React Router as basic if not needed tools for modern React dev
    - bryanrasmussen 6y ago
      Why do you consider Create React App as basic? I tend to just set up my environment by hand.
    - ratww 6y ago
      A passing mention to one piece of tooling that works with one single framework doesn't really count when the title says it's an "exhaustive list".
  - codingknight 6y ago
    You're right....but this is not everything. I still intend to continue adding resources
    - ratww 6y ago
      > You're right....but this is not everything That's the point :) Unless you add every single resource it's not exhaustive. It's possible to have exhaustive lists for lots of things, but for this? Maybe not.
anticristi 6y ago
Next person to complain about backend development and Kubernetes will be punished with getting this URL.
username3 6y ago
Where’s svelte?
- deleted 6y ago
  [deleted]
- codingknight 6y ago
  Perhaps you would like to contribute resources for it?
areactnativedev 6y ago
I'm wondering, why starting a new repo instead of adding / contributing to the already quite successful https://github.com/kamranahmedse/developer-roadmap https://github.com/kamranahmedse/developer-roadmap which you credit and took inspiration from?
- codingknight 6y ago
  Because that is a roadmap....this has resources. It's not the same thing
  - areactnativedev 6y ago
    Ok thanks, I thought the above was pointing to resources as well but they're just roadmaps. Great work then! Offering pointers to resources sounds like a great addition onto these learning roadmaps. I'm curious, have you tried opening a PR / adding them onto the super popular roadmaps repo? I've been thinking quite a bit about the value of sharing such roadmaps and resources in the past, even pondered working on such things but decided not to in the end. Hence my interest and 2-cent ideas.
    - areactnativedev 6y ago
      Wait, actually they do have resources as well. See the website version: https://roadmap.sh/frontend/resources https://roadmap.sh/frontend/resources And people are invited to contribute.
      - codingknight 6y ago
        Oh wow I never they had resources. I saw there was an issue on the repo about the same thing but I don't think anything was ever done about it.
redis_mlc 6y ago
tldr; vi and vanilla-js
- jansan 6y ago
  And Stackoverflow and Google.
Etheryte 6y ago
Sorry to be blunt, but what you've done here is not legal. The source you've copied all this content from is not permissively licensed [0] and you can't relicense your copy as MIT and then write your name as the sole author as you've done currently in the readme. [0] https://github.com/kamranahmedse/developer-roadmap/blob/master/LICENSE https://github.com/kamranahmedse/developer-roadmap/blob/mast...
- colourgarden 6y ago
  Thanks for pointing this out. Does anyone know the correct way to report this? I can only find how to report abuse from a specific user, not to flag a repo.
  - Etheryte 6y ago
    I filed an issue on the original repository [0], most likely they can file a DMCA complaint [1] as the copyright owners, if nothing else. [0] https://github.com/kamranahmedse/developer-roadmap/issues/809 https://github.com/kamranahmedse/developer-roadmap/issues/80... [1] https://github.com/contact/dmca https://github.com/contact/dmca
- codingknight 6y ago
  Hey..I didn't realize this. Thanks for pointing it out. This is my first open source project so you can understand that there's alot of stuff that I don't know. I will correct this Immediately. Thanks
brabel 6y ago
Wrong. This is all you need for web development (the author seems to confuse front end development with web development, so there you go): https://developer.mozilla.org/en-US/docs/Learn/Getting_started_with_the_web https://developer.mozilla.org/en-US/docs/Learn/Getting_start...

35 points by codingknight 6y ago

codingknight 6y ago

Here is an exhaustive list of all the resources you might need for frontend development

purplecats 6y ago
what are the most practical strategies to maneuver such a resource? there's too many to go through one by one, and i just want to know what stack i want to use. it'd be cool if there was a tool that leveraged all this knowledge and presented a wizard that helped you find the best stack based on your preferences and needs.
- codingknight 6y ago
  The best way to go through this resource is to use it as a reference which is actually its main purpose. Its practically impossible to go through all of it one by one. I'd say figure out the stack you wish to use and then go to the resource as a reference to the resources out there. Check them out and use the one that appeals to you.
- deleted 6y ago
  [deleted]
- ratww 6y ago
  > and i just want to know what stack i want to use This is mostly geared towards basic learning and documentation, so you definitely kinda need something else for finding a stack. You can pick one of the tutorials and use it as a guide for your future work. I mean, it pretty much only covers React as far as frameworks go, so I guess if you follow it you'll pick React plus some CSS framework? There's still other stuff you need other than that for a "stack".
ratww 6y ago
You can't really call it exhaustive. Exhaustive means "Including or considering all elements or aspects; fully comprehensive". This list only covers the basics of React, and doesn't even include tooling.
- franciscop 6y ago
  I personally consider Create React App and React Router as basic if not needed tools for modern React dev
  - bryanrasmussen 6y ago
    Why do you consider Create React App as basic? I tend to just set up my environment by hand.
  - ratww 6y ago
    A passing mention to one piece of tooling that works with one single framework doesn't really count when the title says it's an "exhaustive list".
- codingknight 6y ago
  You're right....but this is not everything. I still intend to continue adding resources
  - ratww 6y ago
    > You're right....but this is not everything That's the point :) Unless you add every single resource it's not exhaustive. It's possible to have exhaustive lists for lots of things, but for this? Maybe not.

anticristi 6y ago

Next person to complain about backend development and Kubernetes will be punished with getting this URL.

username3 6y ago

Where’s svelte?

deleted 6y ago
[deleted]
codingknight 6y ago
Perhaps you would like to contribute resources for it?

areactnativedev 6y ago

I'm wondering, why starting a new repo instead of adding / contributing to the already quite successful https://github.com/kamranahmedse/developer-roadmap https://github.com/kamranahmedse/developer-roadmap which you credit and took inspiration from?

codingknight 6y ago
Because that is a roadmap....this has resources. It's not the same thing
- areactnativedev 6y ago
  Ok thanks, I thought the above was pointing to resources as well but they're just roadmaps. Great work then! Offering pointers to resources sounds like a great addition onto these learning roadmaps. I'm curious, have you tried opening a PR / adding them onto the super popular roadmaps repo? I've been thinking quite a bit about the value of sharing such roadmaps and resources in the past, even pondered working on such things but decided not to in the end. Hence my interest and 2-cent ideas.
  - areactnativedev 6y ago
    Wait, actually they do have resources as well. See the website version: https://roadmap.sh/frontend/resources https://roadmap.sh/frontend/resources And people are invited to contribute.
    - codingknight 6y ago
      Oh wow I never they had resources. I saw there was an issue on the repo about the same thing but I don't think anything was ever done about it.

redis_mlc 6y ago

tldr; vi and vanilla-js

jansan 6y ago
And Stackoverflow and Google.

Etheryte 6y ago

Sorry to be blunt, but what you've done here is not legal. The source you've copied all this content from is not permissively licensed [0] and you can't relicense your copy as MIT and then write your name as the sole author as you've done currently in the readme. [0] https://github.com/kamranahmedse/developer-roadmap/blob/master/LICENSE https://github.com/kamranahmedse/developer-roadmap/blob/mast...

colourgarden 6y ago
Thanks for pointing this out. Does anyone know the correct way to report this? I can only find how to report abuse from a specific user, not to flag a repo.
- Etheryte 6y ago
  I filed an issue on the original repository [0], most likely they can file a DMCA complaint [1] as the copyright owners, if nothing else. [0] https://github.com/kamranahmedse/developer-roadmap/issues/809 https://github.com/kamranahmedse/developer-roadmap/issues/80... [1] https://github.com/contact/dmca https://github.com/contact/dmca
codingknight 6y ago
Hey..I didn't realize this. Thanks for pointing it out. This is my first open source project so you can understand that there's alot of stuff that I don't know. I will correct this Immediately. Thanks

brabel 6y ago

Wrong. This is all you need for web development (the author seems to confuse front end development with web development, so there you go): https://developer.mozilla.org/en-US/docs/Learn/Getting_started_with_the_web https://developer.mozilla.org/en-US/docs/Learn/Getting_start...