Giter Site home page Giter Site logo

maxipavlovic / docs.konghq.com Goto Github PK

View Code? Open in Web Editor NEW

This project forked from kong/docs.konghq.com

0.0 0.0 0.0 537.39 MB

๐Ÿฆ Source code for docs.konghq.com website

Home Page: https://docs.konghq.com

License: MIT License

Ruby 1.28% HTML 54.94% CSS 18.69% JavaScript 2.40% Dockerfile 0.04% Makefile 0.18% Shell 0.22% Lua 9.59% Less 12.66%

docs.konghq.com's Introduction

Netlify Status

KONG's Documentation Website

This repository provides the source code and content for Kong's documentation website. It is a Jekyll website deployed with Netlify.

Not sure where to start? Head on over to the issues tab to and look for the good first issue label. These are issues Kong has identified as beginner friendly. Many of these can be addressed with the GitHub UI and do not require pulling the repository and building locally.

First-time contributors, check out our contributing guide on the website, and the linked resources there.

Building locally

If you're making more than a small typo or grammar change, we ask that you pull down the repository and build locally.

Develop locally with Docker

make install-prerequisites
make develop

Running a local build with Docker

Install tools:

make install

Run the build:

make run

Check the build output at http://localhost:3000.

Testing links with Docker

make check-links

Develop locally without Docker

Prerequisites

Install

gem install bundler
npm install

Run

npm start

Generate the PDK, Admin API, CLI, and Configuration documentation

The PDK docs, Admin API docs, cli.md and configuration.md for each release are generated from the Kong source code.

To generate them, go to the Kong/kong repo and run:

scripts/autodoc <docs-folder> <kong-version>

For example:

cd /path/to/kong
scripts/autodoc ../docs.konghq.com 2.4.x

This example assumes that the Kong/docs.konghq.com repo is cloned into the same directory as the Kong/kong repo, and that you want to generate the docs for version 2.4.x. Adjust the paths and version as needed.

After everything is generated, review, open a branch with the changes, send a pull request, and review the changes.

You usually want to open a PR against a release/* branch. For example, in the example above the branch was release/2.4.

cd docs.konghq.com
git fetch --all
git checkout release/2.4
git checkout -b release/2.4-autodocos
git add -A .
git commit -m "docs(2.4.x) add autodocs"
git push

Then open a pull request against release/2.4.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.