Running our React sample app
In this guide, you'll get a brief introduction to website development practices with Kentico Kontent. You'll start by running a React sample application on your machine and updating an article in the Sample Project. Then you will explore how the content of the article is structured.
New to Content as a Service?
If you are new to the world of Content as a Service (CaaS), you might want to start by building a Hello world application.
After you grasp the core idea behind CaaS, everything in the sample application will make a lot more sense much faster.
Table of contents
Sample project for the app
The sample app displays data from the Sample Project that demonstrates our best practices and features of Kentico Kontent. If you don't have it yet, create your own sample project, it only takes a minute.
This full-featured project contains marketing content for Dancing Goat – an imaginary chain of coffee shops. Once you run the sample app, you'll see content from the Sample Project displayed in your browser.
Running the React sample app
Before going any further, make sure you have the following:
- Node and npmOpens in a new window installed
- Kentico KontentOpens in a new window account with a Sample Project (you can also set one up during app configuration)
- Your favorite code editor, for example, Visual Studio CodeOpens in a new window
1. Download the app
The source code of the sample application lives in a Github repositoryOpens in a new window.
If you are used to working with GitOpens in a new window, you can clone the repository to your computer by typing the following into your console:
- shellgit clone https://github.com/Kentico/kontent-sample-app-react.git
git clone https://github.com/Kentico/kontent-sample-app-react.git
If you don't have Git installed, you can directly download the sample application as a ZIP fileOpens in a new window, extract it, and continue from there.
2. Configure the app
Navigate to the root folder of the application in the command line and install the required npm packages.
- shellnpm install
3. Run the app
Start a Node development server.
- shellnpm start
The application will open automatically in your browser at
http://localhost:3000Opens in a new window.
4. Connect your Kontent project
When you run the application for the first time, you will see a Configuration page. Use it to connect the app to your Sample Project in Kentico Kontent:
- Click Get project ID from Kentico Kontent. A new browser window will open.
- Sign in to your account or create a new one.
- From the list of your projects, select the Sample Project.
- Click Select project.
The application now displays content from your Sample Project.
You can also set the project ID manuallyOpens in a new window.
Now, let's explore the Sample Project and update its content so that you can see the changes reflected in your locally running application.
Making changes to your project
After you sign in to Kentico Kontent, you'll see your Sample Project to play around with. We recommend you get familiar with content items and how to find stuff in your projects. It's simple yet powerful.
Try to edit an article from the sample project:
- From the app menu, choose Content & Assets.
- Open a published article, for example, the Coffee processing techniques one.
- Look for items with a green Published label and the word Article in the Type column.
- Create a new version to edit the article.
- Make a change in the article, for example, edit the Title text or some other element.
- Publish the changes to see them in the sample app.
Voila! You have successfully updated content in your Sample Project. Refresh the browser window with your application to see the changes on the website.
Feel free to further explore how the content in your sample project is structured.
Exploring content structure
To see details about the opened content item, go back to Kentico Kontent and click Content details in the top right. Under Content type, notice that the item is based on the Article content type.
To open the content type for editing, click Article in the content details.
How content is structured in Kentico Kontent
Content item is any piece of content in your project. It is made up of elements, such as texts, images, files, etc.
Each content item is based on a single content type. A content type is a template that defines the structure of the content item – which elements it contains, their names, limitations, guidelines, and so on.
Mix and match the available elements to define your own content types.
Deploying the React sample app
When using a headless CMS like Kentico Kontent to power a single page application, you don't necessarily have to write any server-side code. Because the application only requires static resources, you have many interesting deployment options available to you.
Here, we are going to use SurgeOpens in a new window to deploy your React sample application:
- Navigate to the root folder of the application in the command line.
npm install --global surgeto install Surge on your computer.
npm run buildto build the application and make it production-ready.
cd buildto navigate to the build folder.
surgeto deploy your application. The first time you do this, Surge will prompt you to set up your account. Every other time it will confirm the build directory and generate a funny subdomain for your app.
You can change the subdomain if you like and can even use your own domain, all for free. After that, you’re done. The site is deployed and ready to be accessed on the domain specified during deployment.
Kentico Kontent makes no assumptions about how your content is displayed. It simply delivers it via a RESTful Delivery API to any application that asks for it – be it a website, mobile app, chatbot, electronic billboard, virtual voice assistant or an internet-enabled toaster.
We deliver the content, you do whatever you want with it – using the technology of your choice.
A traditional CMS would force you to put your content into neatly arranged boxes to fit inside a pre-defined template. The power of Kentico Kontent comes from not getting in your way. Content structure and content presentation are truly separated and you have the flexibility to define both according to the needs of your project.
- Angular – Angular 9Opens in a new window sample app, Angular Universal StarterOpens in a new window, and Angular progressive web appOpens in a new window (PWA)
- Express.js web app with examples of Algolia search integration and automated content translation via webhooks
- SvelteOpens in a new window web app with Kontent in a JAMStack scenario
- Vue.js single page app