The slides for the presentation are available in the repository under the slides
folder.
If you encounter any issues, you can log an issue on the repository or reach out via LinkedIn. We will do our best to assist you.
Create a Data Extension with the following specifications:
Name: Survey_Results
External Key: Survey_Results
Field Name | Data Type | Length | Default Value |
---|---|---|---|
SurveyID | Number | ||
SubmissionDate | Date | Current Date | |
Response | Text | VARCHAR(MAX) |
- Create a new Code Resource for JSON.
- Copy the contents from
Server\app.js
and paste them into the JSON Code Resource.
- Open the
.env
file in your project directory. - Update the file with your Code Resource Server URL.
- Open a terminal in your project directory.
- Install the dependencies:
npm install
- Run the following command to build the project:
npm run build
Create the following assets on Marketing Cloud and populate them with the respective files:
-
CSS Code Resource:
- Use the file located at
build\static\main.*.css
.
- Use the file located at
-
JavaScript Code Resource:
- Use the file located at
build\static\main.*.js
.
- Use the file located at
-
Landing Page:
- Use the file located at
build\index.html
. - Edit the paths of the CSS and JavaScript files to reflect the Code Resource URLs.
- Use the file located at
This project was bootstrapped with Create React App.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.
You may also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build
folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject
, you can't go back!
If you aren't satisfied with the build tool and configuration choices, you can eject
at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject
will still work, but they will point to the copied scripts so you can tweak them. At this point you're on your own.
You don't have to ever use eject
. The curated feature set is suitable for small and middle deployments, and you shouldn't feel obligated to use this feature. However we understand that this tool wouldn't be useful if you couldn't customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify