Was this article helpful?
Thanks for your feedback
Angular is an application design framework and development platform for creating efficient and sophisticated single-page apps.
This guide will help you create a starter website built with minimal steps. It uses Contentstack Javascript SDK to store and deliver the website content.
Note: For this tutorial, we have assumed that you are familiar with Contentstack and Angular. If not, please refer to the Contentstack docs and Angular docs for more details.
Here is an overview of the steps involved in creating our Angular app:
To use the North American, European, or Azure North American endpoint, run the following command in your terminal (command prompt):
csdx config:set:region <<region>>
Note: - For North American users, set the region as NA.
- For European users, set the region as EU.
- For Azure North American users, set the region as AZURE-NA.
To import content to your stack, first, you’ll need to log in to your Contentstack account via CLI by running the following command in your terminal:
csdx auth:login
This command will ask you to provide your Contentstack’s account credentials (email and password).
The ‘seed’ command lets you import content to your stack in a few steps. To do so, run the following command in your terminal:
csdx cm:seed -r "contentstack/stack-starter-app"
This command will prompt the following options as follows:
Stack preference:
Next, you need to select your choice to create a new stack:
Tip: To avoid the chances of any error, we recommend that you select the option of creating a new destination stack. If you choose to import content to an existing stack, ensure that the stack is empty.
Finally, you’ll get the content imported to your stack.
A delivery token lets you fetch published content of an environment.
You can create a delivery token for the “development” environment for running the website on localhost. Later, while deploying your site, you can create tokens for other environments.
Fire up your terminal, navigate to your project folder, and run the following command to create a configuration file named .env.
cp .env.sample .env
Note: If you are a Windows user, replace cp with copy in the command given above.
The .env file contains all the necessary config parameters. Open it in any code editor or IDE of your choice, provide your stack credentials as shown below, and save the file.
CONTENTSTACK_API_KEY = <api_key_of_your_stack> CONTENTSTACK_DELIVERY_TOKEN = <delivery_token_of_the_environment> CONTENTSTACK_ENVIRONMENT = <environment_name>
Note: The below code is for North America region users only. Refer the configuration code for European region and Azure North American region on the regions configuration page.
CONTENTSTACK_MANAGEMENT_TOKEN = <management_token_of_the_environment> CONTENTSTACK_APP_HOST = app.contentstack.com CONTENTSTACK_API_HOST = api.contentstack.io CONTENTSTACK_LIVE_PREVIEW = true #By default the live preview feature is enabled for this project. To disable it, set "CONTENTSTACK_LIVE_PREVIEW= false".
Note: Make sure your management token has READ permission only.
Additional Resource: Go to our Live Preview documentation to learn more about the Live Preview feature in Contentstack.
Fire up your terminal, point it to your project location, and run the following commands:
npm install npm start
That’s it!
You can now view the website at http://localhost:3000. And you also have the stack that has all the content and resources for the website. Try experimenting by creating new entries and publishing on the “development” environment. You should be able to see the changes on the website at the localhost.
Note: In order to use Live Preview, your plan must include this feature. Check our pricing page for more details.
The next step is to set up and enable live preview for your website. Follow the steps below to set up live preview feature for your website:
This completes your live preview set up. Now, you can deploy the website using Vercel.
The easiest and the quickest way to deploy a website on production is to use Vercel. You need a Vercel account before you start deploying.
Note: While deploying the starter website to Vercel, make sure to enable/ disable the live preview environment variable as per your requirement.
Was this article helpful?
Thanks for your feedback