They're just using cloudflare, so it's super fast: https://jumpshare.com/v/vmE6WytGS3t1E3oE2YeR Another thing about WordPress is authorization. If you are using WordPress for auth/user management then it becomes very tricky caching pages for performance. I would break it down like this: Static/content based, no auth > Just WordPress and as J mentioned, utilize caching and don't worry about fancy frameworks Auth/ajax/built for speed > You can use the WordPress REST API and custom build the front end, but then have to figure out if SEO is important or not. If SEO is important, then you need to maintain your frontend views, and also provide the base content for search engines. So If you go to site.com/post - initally you see the post content and a basic header, but when the JS kicks in you bootstrap your SPA from there. That's the only viable way I've been able to execute a WordPress as an API app. Anything besides that, to my knowledge is a waste and you should just do something custom. There are plenty of Node CMS' and PHP CMS' that will help solve more complicated scenarios. If you just want faster loading, look into HTTP2, CDNs, CloudFlare, image compression, and do ALL that before considering trying to make WordPress fit into that mold.

This is a great response, things to think about. Just installing Cloudflare or the "W3 Performance" plugin and a CDN for WordPress will do wonders. People don't point out that enough that these frameworks do put a strain on the client. As smart phones and JS engines evolve though it becomes less and less of a problem and the bottleneck is the internet speed. This is where offloading more work to the client can be the best solution. It's so context specific though, depends on the region, demographic, site/app.

What's up I'm JP. Currently becoming an expert in Node/Express/Sails/Hapi/Etc (Rally/GraphQL et al probably also, and looking at things like RxJS and Cycle for the future). I came from PHP/WordPress, am a fullstack engineer and love programming. I've been dying to ge started with node for years and it happened finally in 2017. Anything node/react I will absorb, I think it's the latest trend. The future is when JavaScript compiles to native code, and that's in the works. Hit me up for questions of any kind and I love working, so of course that as well. Cheers!

By headless WordPress do you mean using the Rest API? I've done it and it's awesome. You will need helper functions and some business logic, but with the right server setup and caching, you can give your CMS editors/admins the same WordPress dashboard system and ditch the entire front-end for a custom roll out. React is my personal choice. I like all 3 to be honest but if I had to rank for my preferences I'd go with: React/Vue/Angular. React and Vue are both view layers whereas Angular gives you a lot more out of the box. If you're looking for a long term solution, Angular might be the best bet because if you just stick to Angular and do things in an Angular way, you can lean on the framework for a lot of what you need. With React or Vue, you'll have to figure out ajax, state management, where to put business logic, choosing the right router, and the list goes on. That's not to mention server side rendering, which is probably your biggest hurdle. You'll need some kind of server side rendering for SEO, I think that's where you should start. Also check out some Google searches, React vs Vue vs Angular. Good luck!

Post your answer mofo

I don't think I fully understand the question, but can point out a few things: My React Pointers Use this.setState({ ...newState }) You should have <ul> outside the map function and the key attribute should be on the <li> element. You can split this up into smaller bits and make it clearer for readers what the intention is. If the prop type is an <li> element, you should just make another component in my opinion. React is "declarative" as they say and the beauty is that when done correctly you shouldn't even be in this situation. You can also render children, and compose your component that way... There's a ton of resources online, but I would recommend you keep messing around and building stuff, and use online courses to get some structure: Basics: Tyler McGinneses (tylermcginnis.com) Complex: https://egghead.io/courses/advanced-react-component-patterns About Your Question In terms of what to do with combining: You need to perform the same check inside the savedInputs loop and move that above stepMsg. If it's an array you use .map and .replace inside that for the strings, if it's a string you use just use .replace: I'm also using ES6 syntax, which if you're into React you need to learn, in my opinion. I noticed some errors in the syntax, corrected below. Also, I haven't tested this it's theoretical code. Lastly, I think a lot of this should be done in a parent component, componentDidMount, and the rest in the render() function. The courses above will go through these life-cycle methods, and as always read the docs! Good luck, hope that made sense... // stepMsg could be 'Hello {input1}' or ['Hello', '{input2}'] // savedInputs is an array with dynamic content [{id: 1, value: 'yo'}{}...] // init let replacedStepMsg; let formattedStepMsg; // === STEP 1 === // Let's replace everything first // Replace helper const replaceValuess = (str) => savedInputs.reduce(el => str.replace( new RegExp( '{input' + el.id + '}' , 'g' ), el.value)); // Replace all text strings first, whether Array or not. if ( Array .isArray(stepMsg)) { replacedStepMsg = stepMsg.map(msg => { return replaceValues(msg); }); } else { replacedStepMsg = replaceValues(stepMsg); } // === STEP 2 === // By now everything is replaced, now we can build our HTML if ( Array .isArray(replacedStepMsg)) { if (this.props.type === 'li' ) { formattedStepMsg = <ul>{replacedStepMsg.map((msg, index) => ( <li key= "{index}" >{msg}</li> ))}</ul>; } else { formattedStepMsg = replacedStepMsg.map((msg, index) => <div key= "{index}" >{msg}</div> ); } } this.setState({ message: <div>{formattedStepMsg}</div> });

There is always pressure to finish things as fast as possible. The higher up the food chain you go the more pressure you face. Interestingly, most of the effective leaders I've interacted with in the upper echelons are incredible at handling pressure and managing people below them, so they don't feel the brunt of the pressure. That's one of the biggest thing that separates an effective leader from a bully. They lift you up and shield you from that pressure so you can perform your best. It's the only way I've been able to effectively manage people. With that said, what you're talking about seems to be a two-fold problem. There's the pressure and then there's the execution of getting the job done. If you're talking about using many frameworks, you should really only be using one framework and maybe a couple libraries. You should be highly skilled in a framework before moving on to the next one, and proficient enough to scan a library and test if it works for your needs. But that's ideally. What tends to happen (unless you're lucky) is you just get it done by any means necessary. Once you advance further in knowledge and your career, you'll be able to make better choices about where to work and find a place where it isn't so dysfunctional. TLDR; Yea, it's very common in my experience. With time and experience you'll have more leverage and can leave those kinds of situations behind.