Hi Matt.
I have a suggestion to do...

I think that onramp should not separate the resources by language.

When I first saw that you were adding language support to onramp, I tought that it was only a site content translation, and I think it is very nice, but I dont think that onramp should separate the resources by language.

It is not very clear that the resources when working on es are different than the resources when working on en. My main language is Spanish but I can properly understand resources in English, and many people can too... and that makes both of these resources useful for my learning. I think these resources should remain together or at least tagged or categorized but still in the same page view.

Just a suggestion 😇
Thank you so much...

Footer text ("From the lovely folks at Tighten", "Source & Roadmap"), header ("Login", "Register"). Content on the log in and register pages.

Don't need to translate the home page because it's all going to change soon anyway.

I'm imagining maybe this:

Welcome to Onramp!

Here are a few technologies that, if you're already familiar with, will impact the training we suggest. Choose as many as you need:

[HTML]
[CSS]
[Basic JavaScript]
[jQuery]
[WordPress implementation]
[WordPress plugin development]
[Git]
[Agile]

That's not an exhaustive list but it could be a good start. Then, when they choose them, we save it to their profile, and contextualize it.

Most of these options would just mean "don't show resources related to this because we assume they already know it." But at least WordPress would be a special case; that would add references designed specifically to help WP people transition.

But for now just have it use the same learn.php array as its data source.

https://www.producthunt.com/posts/open-doodles

https://exercism.io/tracks/php

Somehow/somewhere

I'm thinking it might be better if there were clearer modules:

• Basic web page creation
• Terminal and git
• Basic PHP
• Advanced PHP
• OOP
• Basic Laravel
• Advanced Laravel
• APIs
• Basic JavaScript
• Basic Vue/React/whatever
• Moving from WordPress (maybe more than one)
• Basic Design Patterns (and other things that should target people brand-new to programming)
• Basic application security practices

That way the organization of everything would be clearer, but also it'd be easier to turn certain chunks on and off based on the user's track.

https://twitter.com/le_debut/status/1164414438570627072

From here:
https://twitter.com/jonodonovan/status/1154762467979014144

Linked to here:
https://docs.google.com/document/d/13SzMxBBG7wQuq_yqaBhkyyRQlp5sYue14hBOBcvPnik/edit

Questions about adding these.

1. Are they any good?
2. Are they comprehensive?
3. Are they modern?
4. Is Udacity legit? (I remember them having some shady policies toward folks re-posting Jeffrey Way's content and others... is that resolved?)

Content:

Computer Science
https://udacity.com/course/intro-to-computer-science--cs101
https://edx.org/course/introduction-computer-science-harvardx-cs50x

General Web Courses
https://udacity.com/course/web-development--cs253
https://udacity.com/course/full-stack-foundations--ud088
https://udacity.com/course/mobile-web-development--cs256

Design
https://udacity.com/course/responsive-web-design-fundamentals--ud893
https://udacity.com/course/responsive-images--ud882

HTML
https://udacity.com/course/intro-to-html-and-css--ud304
https://udacity.com/course/html5-canvas--ud292

CSS
https://udacity.com/course/intro-to-html-and-css--ud304

Javascript
https://udacity.com/course/javascript-basics--ud804
https://udacity.com/course/object-oriented-javascript--ud015
https://udacity.com/course/intro-to-ajax--ud110

JQuery
https://udacity.com/course/intro-to-jquery--ud245

Databases
https://udacity.com/course/intro-to-relational-databases--ud197

Advanced
https://udacity.com/course/html5-game-development--cs255

While Valet is a fantastic tool, it's only for Mac users and one of the pain points I've experienced myself and heard from others is trying to get a development environment installed on Windows.

If we can provide a simple set of instructions for getting started with development on Windows, that would probably be a great addition to the section on Development Environment.

If no one beats me to it, I'll try to write up some documentation on Homestead, since that works on all 3 platforms and is something I'm comfortable writing about, but that's not necessarily the "simple" setup either.

Maybe some kind of setup guide using XAMPP and php artisan serve?

E.g.
https://testautomationu.applitools.com/java-programming-course/

The only reason to do this would be if there was clear indication the existing free resources were not doing the job well.

Possibly suggesting an app that they can build, step-by-step, as a later add-on? So each module would have a goal that your app could do, and then when you're done with Onramp you have built an entire app from scratch in Laravel

https://dev.to/taeluralexis/break-git-down-how-to-create-a-branch-from-master-and-make-your-first-commit-2960

I talked with @mattstauffer a bit at Laracon about adding a section for WordPress devs getting into Laravel. A lot of WordPress folks like myself are using more and more Laravel and it would be good to help translate some concepts from WordPress to Laravel to help.

Some ideas:

• WordPress vs MVC (https://tommcfarlin.com/wordpress-and-mvc/)
• Build a blog with Nova (https://nick-basile.com/blog/post/getting-started-with-laravel-nova)
• Laravel CMSes: Stamatic, Twil, etc.
• Routing, Controller and Blade vs themes and rewrite rules.
• Artisan vs WP-CLI
• Using Corcel to directly query WordPress data.
• Using the WordPress REST API to provide content to a Laravel app (I remember a post on this for Laravel News awhile ago.)
• Laravel Package equivelents -> Nova/ Advanced Custom Fields, Spark/ WooCommerce, etc.

I'll ask @twigpress if he has ideas about this.

https://daylerees.com/php-pandas/

https://phpapprentice.com/

Provide a translated glossary of terms where users can easily find explanations of key Laravel/PHP terminology explained in their own language.

When it comes to learning git I've found that this resource is really really good.
http://rogerdudler.github.io/git-guide/

It's not overwhelming but gives you a good idea about how to work with git.
Works very well as a reference in the beginning after you've learned why to use git in the first place.

W3Schools is a great resource for basic (and not so) SQL queries and what is it all about. Without overwhelming theory.

https://www.w3schools.com/sql/

I'd place it under the CSS section since one I/O device is the web, another can be CLI, and the other is for sure the database. It's better to have some understanding of it.
Besides, it makes you think on a declarative language which is how we want Laravel to be, it forms your brain into asking the computer what do you need instead of trying to make the computer do something.

https://www.learnrxjs.io/

Hey Tighten, this is a cool project of yours I just discovered.

One thing I have been floundering around, is trying to figure out which markdown
you guys are running in Jigsaw.
Is it the Commonmark markdown?
Maybe this page should have a comment regarding which markdown is available??

Also, maybe a link on the onramp page would be helpful for those new to markdown.

Sorry if I am suggesting too much.

https://laraveldaily.teachable.com/

A paid content, but I think Povilas's content is good quality. He posts a lot of live-coding sessions on YouTube too, you can check out his teaching style there (for example this video: https://www.youtube.com/watch?v=YUUokBJyJzw).
He has a website full of Laravel tutorials and tips: https://laraveldaily.com/.

https://dotnet.microsoft.com/platform/community

There was chat elsewhere today about things like:

• What is on different branches of this repo?
• How PR's work
• Which livestream videos should I watch? All of them? The latest?
• Details of the database seeding

And I have my own questions about exactly what this repo is and if/how I can contribute.

I'll copy some conversation below for reference.

My reaction was to pop in here and see what the readme and contrinuting.md say, and that lead me to opening this issue to try and improve those documents.

@mattstauffer said:

one of the things i think would be really cool is if we can make this not only super easy for new folks to use, but also super easy for them to contribute to, AND we can maybe even use it and its readme/contributing.md/etc. as examples of how to make open source laravel projects friendly to new folks

So let's do that. I'll try and start making some improvements to the docs over the next couple of days. But feel free to chip in if I can't.

Relevant extracts/questions

How do the migrations/seeding work?

php artisan migrate:fresh —seed

What IS the mes/database-backed-learning branch? Which should I use if contributing?

??? - need a general overview of branches - presumably this is explained in the videos?

How do PR's work with merging? (This started as a question along the lines of: "If I fork the repo and work on the master, then create a PR with my changes, won't it create conflicts if it's merged after other changes on master?")

Probably need to point off to another resource on "How to PR with Git/GitHub". This is old and JavaScripty, but may be a helpful 38 mins of free (I think!) video: https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github

Consider moving Basic Terminal Commands below HTML and CSS. Starting with the tools/technologies that can equip the learner to create something the fastest is more likely to keep them in the game and motivated. Also, I don't think the current HTML and CSS resources depend on knowing terminal commands.

"I can help you translate the content to portuguese.."
https://twitter.com/r2luna/status/1154586763043713026

"I would love to see (link: https://onramp.dev/) onramp.dev with a version with spanish resources."
https://twitter.com/claudiamarquezp/status/1154492036260749313

https://www.codecademy.com/learn/learn-php
https://www.codecademy.com/learn/learn-html
https://www.codecademy.com/learn/learn-css
https://www.codecademy.com/learn/learn-javascript
https://www.codecademy.com/learn/make-a-website

Never used this site. Is it good? Any other things?

https://dash.generalassemb.ly/

https://frontendmasters.com/bootcamp/

Easy to learn, dificult to master. It's better to have a look, even if you don't dominate, but at least know about and can search on later.

Easy to access, read and understand Design Patterns. Maybe not so accurate with some but better to approach than any other resource out there.
https://github.com/kamranahmedse/design-patterns-for-humans/blob/master/README.md

If you find links like this post please add on the comments for:
Data Structures
HTTP stack
Architecture concepts
etc.

This briefly came up during the chat yesterday.

A Code of Conduct is used to make sure that everybody knows the social rules and what will happen if you don't abide by them.

I suggest we use https://www.contributor-covenant.org as it's widely adopted.

Each item could have a link to any free Laracasts, blog posts, docs, etc.

https://twitter.com/aspittel/status/1173973375259152384?s=21

• New to coding
• Frontend programmer
• WordPress programmer

Hi!
I want to propose to change the focus of development based on macOS as a de facto platform. Most future developers out there may not have access to a macbook or similar hardware so all the docs should include Windows and GNU/Linux links for tooling instalation and configuration on par with the huge amount of links we can find all over the place for macOS users.
I have been a Laravel (& Symfony) developer for the past 3 years (working on home projects with Windows 10 and at companies using GNU/Linux) and i've yet to try a mac. I don't need it, i don't want it and i don't hate it

(sic) Simon Sinek.

We need to let them know why we (as a more experience programmers) think they should complete this specific skill, at this specific stage. And we need to freshen up the idea of why we think this or that is important, and how it changed our lifes when we learned it.

This could become a UI/UX problem but never the less, keeping this in mind might be of use.
We should add an overview (with a tooltip or something more powerful, like media content of our own).
I think this should be added meta-content made from anyone who adds the contribution. This makes this site different from any wiki guide and reflects upon the mission and vision of this app.

for example, when (if) we add the section of SQL tutorial (#52 ), we explain why we think it would be beneficial, with something like:

At this stage, you're probably thinking something along the lines of "i'd love to make the computer do something!". The problem is that shouldn't try to hack your way through it, you could, but there is a better way. Why instead of hacking and forcing, we can just ask the right questions to get propper information? Why instead of making the computer do something, we can ask for it, and get it. Enter the void of the main data driven declarative language, SQL (Structured Query Language) !

😊

Make sure we're not missing anything; give sub items to any that deserve it.

I'm not sure the best way to learn PHP from scratch, but I'm very aware there's a lot of really not positive and really not modern PHP resources out there.

What's the best free way to learn PHP? And, if not free, what's the best single comprehensive paid resource (books, video tutes, online courses, etc.)?

Preferably answered by people who've actually done it recently, rather than those of us who've been writing PHP since the dinosaurs but have heard of a thing once (e.g. me lol)

Perhaps there is a reason for not doing this, but I think all links in the "Learn Laravel" section should have the target attribute set to _blank. Just as I did, other users will likely explore these sites further and navigating back can become a nuisance once you've gone down the rabbit hole.

Overall I'm really optimistic about onramp; I certainly wish this was around when I started and it never hurts to go back to basics, especially in our ever-changing industry. I look forward to using and sharing this great resource with friends and colleagues!

Just giving this a look and thinking about what might be useful to add, I noticed there's not really a defined structure for how things should be formatted. Bullet points, paragraphs, etc?

Otherwise looks like a very promising resource.