lwc-recipes VS ecars

You can get a free developers org (developer.salesforce.com) and play with it, which I suggest.

What I can do is point to a number of case studies where a company created a platform and then encouraged a community of 3rd party entities to build on top of that platform. Salesforce, Amazon Web Services, Lego, and pretty much any game developer, like Paradox, that supports a modding community, .

as a follow up comment, you can leave all the detail you want, they won't read it at first and ask you for details. I've written all kinds of painstaking details, and gotten "well, try this URL from developer.salesforce.com"

You can do the free courses and also spin up your own developer org: http://developer.salesforce.com

When you write JavaScript, your code editor is able to provide some sort of auto-completion based on the code you previously wrote. It does not work very well with plain JavaScript and we will see how to improve that by modifying the todoList.js file from Salesforce's LWC recipes repository. We are using Visual Studio Code as our code editor, but other IDE also have similar features.

There are also three good official blog sites admin.salesforce.com developer.salesforce.com and architect.salesforce.com with additional resources. I'd look at the Architecture and Admin ones in particular.

For the eCars app that we’re building, the activity will be to write an APEX test class for the PdfCreateService that we used in the prior session to call a Heroku microservice for generating PDF documents. The eCars code can be found at the linked Github repo and I have also included a link to the specific PdfCreateService class. If you have not gone through the exercise of pulling the code into a Salesforce Developer org or a scratch org, you’ll want to review some of the previous articles to take that pre-requisite step or follow the instructions in the Github repo on how to clone and deploy the application.

The Javascript car configurator app we are going to test can be found on the eCars app Github repository. If you’ve been following along with this series, then you should have already done some previous setup work installing the repo in VS Code and deploying it to a Salesforce scratch org.

I'll share a step-by-step tutorial building the app, what I've learned, some of the highlights, and my take on some of the content. You can find all the code for the project here.

To start, let’s review the steps for Automated Deployment as also listed on the readme section in the Github repo. Julian has created a script (a Node.js program that will make this process easier) to get this up and running in the Salesforce and Heroku platforms. All of the installation pre-reqs, keys, and steps to configure your operating system before we move forward with deployment can be found here.