Well a great resource is laracasts.com They have a ton of free courses and some really good paid ones. I would recommend to go with some of their laravel beginner courses, so you get a feeling how laravel & php are working.

I am using gloom https://github.com/hejrobin/gloom

Well, they will both co-exist. I don't think that one will "win". Vue is way easier to pick up and also very popular in the laravel community and in the asian region. Mostly it's all up to personal preference. However on big advantage of react is imo it's whole environment. And with react , react-native and react-vr you have three major fields in which you can build things, "just" with react.

https://github.com/apertureless Mostly open source projects, which took off earlier this year and generated some work :D

Well it's not complicated. You simply create an .env file, which holds your secrets. Like DB user, pw etc. And the wp-conf then reads this file. So you don't need to hardcode any secrets anywhere in your code. Sureley you need to ignore this .env file from your git. Well the manifest.json simply holds the current assets with their hash. So the wordpress header knows which to load. Like style01424123149.css etc. because of the hash you don't have problems with caching.

I am using Bedrock Stack and Sage Starter Theme from roots.io Bedrock Bedrock is a complete wordpress boilerplate. It implements the 12 factor app methology So, why it's cool? Dependencies managed over composer, Wp, plugins etc. Make use of .env variables so no more flickering in wp-config.php Easy deployments with capistrano. If you want to deploy your project simply type cap staging deploy or cap production deploy and you can even sync (pull /push) database and uploads. Dependencies got managed with composer. If you want to install wp plugins you can simply composer require packagename which is pretty neat! Sage Sage is a starter sceleton theme. It also comes with a ready to go workflow, which includes: Sass ES6 Webpack & Browsersync And I think they included laravels blade template engine recently Theme Wrapper However I have a fork of it, with some custom addtions. The stack is pretty solid, as it's also generating a manifest.json and hashed assets so you nomrally don't have problems with clearing chache etc. The Theme Wrapper is also awesome, because you can easily split everything into partials and DRY up your code. All in all it's a very solid stack which helps you to create a clean codebase and easy workflow. They have also a few awesome plugins like Soil to clean up wp_head()

Mostly following the principles of How to write Git Commit messages paired with Alfred Snippets for emoji commit messages. Started this a few years ago and now it's totally natural for me to write clean commit messages. However downsides of this is, that if you see some ungly commit messages, you get a baaaaad feeling bout it.

Well, a clean and focused design. Some nice screenshots of your product and some information and features that are on point. If I visit your page, I need to know what your product is about, without much hassle. It has to tell me, what your product does and why it's better then others.

Short answer: You can't. Long answer: Well there are plenty of websites like http://www.ideacheck.io/ or ideawatch and so so many other. However they all have a common problem: They don't have people of your focus group. This sites mostly get visited by entrepreneurs, developers and people who want to start a business. But not you customers. You should and have to decide by your own if your idea is good and what problems it should solve. A big mistake people are making is trusting on other people opinions. If you do so, your app / product will grow into a huge mutated tentacle monster. Because everyone has a different opinion and everyone wants only features, that solves their paticular problem. You have to analyze your market. What are the competitors. Are there any? How big is the market? Is it worth it? How big is the demand for your solution / product. And then you have to identify the key features / problem solvers of you product. Keep it simple but good. Later you can always implement more features. Maybe talk with some people directly that are potential customers and ask them, what there needs are and think about how this needs would fit in your product. Lean start: A lean start is a common thing to do. If you don't want to go all-in. Make some concepts of your product, think about your USP and make a damn good landingpage. Sell the feature and your USP to the people. Newsletter signup for beta access or notifications if it starts. You can gather a lot of data from a simple landingpage. First you get a feeling about how many people would be interested. Second you have a user base, if you start a beta. Which you should do! In the beta you can gather real feedback, from real users. You can also figure out pricing this way. Even if you're product is not launched, you can make a pricing page, with different tiers. And track the clicks on the pricing models. Sureley you should then build a modal or notificaton with: "Hey sorry, our product isn't launched yet, but you can sign up for beta". This way, you get some feedback how many people would go the free tier, how many would go a paid tier. Last, but not least Just launch! Not matter what. People will always bitch about your idea. And no landing page can proof them wrong. Only the final great product. I remember the start of dropbox. They posted a thread on HR and pitched their idea. Guess how many people were bitching about, that this is completly useless and why not use rsync?! etc.

Still using for most stuff sublime. It's just so fast... However for some projects I use atom mostly because of the API workspace extension for RAML definitions. For go projects however I use macvim.