/knowledge-center

This repository generates LivePerson's Knowledge Base -Gatsby/Kontent.

Primary LanguageJavaScriptBSD Zero Clause License0BSD

Logo

LivePerson Knowledge Center

⚠️ The LivePerson Knowledge Center has been moved to a new, internal-only repository. LivePerson teams can reach out to LivePerson’s DX team for further details.

This site is run by LivePerson’s Product Strategy and Experience team, and maintained by the Developer Experience team.

The repository generates LivePerson’s Knowledge Center, which can be found at knowledge.liveperson.com. The site is generated using Gatsby, while the content is managed using Kontent.ai. Please open an issue if you find an issue with the documentation, site structure, meta, or anything else.

(For developer documentation, visit the LivePerson Developer Center.)

🚀 Installation

Install with yarn:

  yarn
  yarn start

  yarn clean
  yarn format

Tooling

  • Gatsby
  • Kontent.ai for CMS
  • Gatsby Cloud

🧐 What’s inside?

A quick look at the top-level files and directories you’ll see in a Gatsby project like this one.

.
├── node_modules
├── src
├── .gitignore
├── .prettierrc
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── gatsby-ssr.js
├── LICENSE
├── package-lock.json
├── package.json
└── README.md

  1. /node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.

  2. /src: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser) such as your site header or a page template. src is a convention for “source code”.

  3. .gitignore: This file tells git which files it should not track / not maintain a version history for.

  4. .prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.

  5. gatsby-browser.js: This file is where Gatsby expects to find any usage of the Gatsby browser APIs (if any). These allow customization/extension of default Gatsby settings affecting the browser.

  6. gatsby-config.js: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you’d like to include, etc. (Check out the config docs for more detail).

  7. gatsby-node.js: This file is where Gatsby expects to find any usage of the Gatsby Node APIs (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process.

  8. gatsby-ssr.js: This file is where Gatsby expects to find any usage of the Gatsby server-side rendering APIs (if any). These allow customization of default Gatsby settings affecting server-side rendering.

  9. LICENSE: This Gatsby starter is licensed under the 0BSD license. This means that you can see this file as a placeholder and replace it with your own license.

  10. package-lock.json (See package.json below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. (You won’t change this file directly).

  11. package.json: A manifest file for Node.js projects, which includes things like metadata (the project’s name, author, etc). This manifest is how npm knows which packages to install for your project.

  12. README.md: A text file containing useful reference information about your project.