Skip to content

Latest commit

 

History

History
304 lines (163 loc) · 18.9 KB

CONTRIBUTING.md

File metadata and controls

304 lines (163 loc) · 18.9 KB
Raw

In this Guide

Installing the Docs Library

Linode's documentation library uses a static site generator, Hugo, to build the website from Markdown (.md) files. Building the site requires Node.js, NPM, and Go.

Install prerequisites

Install Go

Some parts of the Linode documentation environment require the GO programming language. In most cases, you should install the latest version of Go.

Install Go on macOS and Windows

The Go package can be found on the official downloads page. Install the latest package available for your operating system. Since the latest version that is available at the time of this writing is 1.19.1, links to that version are used below:

For Windows and macOS users, click the link above to download the software and run it.

For Linux users, run the following commands to download the file, extract it into the /usr/local folder, and add the folder to your PATH variable:

wget https://go.dev/dl/go1.19.1.linux-amd64.tar.gz
tar -C /usr/local -xzf go1.19.1.linux-amd64.tar.gz
export PATH=$PATH:/usr/local/go/bin

You can ensure that go has been installed by checking the version currently in use:

go version

Install Node.js

To support the JavaScript runtime environment used by the Linode documentation site, Node.js must be installed on your system.

Install Node.js on macOS and Linux

To install Node.js on Linux and macOS, we recommend using the Node Version Manager (NVM) to switch between other versions of Node you may be using now or may use in the future.

NVM can be installed by entering the following command, which downloads and runs an install script.

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash

Close out of your terminal session and open up a new one. You may receive a warning similar to the following: zsh compinit: insecure directories, run compaudit for list. Ignore insecure directories and continue [y] or abort compinit [n]? y. If you do, enter y to access your terminal and then run compaudit for a list of affected directories. Likely, the directories are within /usr/local/share/zsh. Run the following command against that folder to update the permissions and prevent the same warning message from appearing the next time you open a terminal session.

chmod -R 755 /usr/local/share/zsh

Using NVM, install the latest Node.js 18.x release and set it as the currently active version.

nvm install 18
nvm use 18

You can confirm the version of NVM and Node.js by running the following commands.

nvm -v
node -v

Install Node.js on Windows

To Install the latest Node.js LTS release on Windows, navigate to the downloads page and install the appropriate .msi installer file for your type of processor (32-bit or 64-bit). Open the file and follow the prompts to complete the installation process. To confirm that Node and NPM has been installed successfully, open up your command prompt and enter the following command to check your version:

node -v
npm -v

Install Hugo

The Linode documentation library is built using Hugo, an open-source static site generator. In order to preview your guide before submission, you need to install Hugo on your local computer. This site currently uses Hugo v0.125.7. To remain consistent in the testing and development process, it's recommended to install this version instead of using a newer version.

Note: If you observe any issues on a newer version, please file an issue in the docs GitHub repository.

macOS and Linux

To install Hugo, download the appropriate binary for your system, extract it, and move it to a directory within your PATH.

  1. Download the file below that corresponds with the OS and platform on your local system. If you don't see your system on this list, you can find additional files on the Hugo v0.125.7 GitHub release page under Assets.

    You can download this file through a terminal using the curl command, replacing [url] with the URL for your platform:

    curl -OL [url]

  2. Extract the archive file using the tar command, replacing [file] with the correct filename.

    tar -xvzf [file]

    Once extracted, there should be a hugo file in the same directory. This is used to run Hugo.

  3. Move the hugo file to a location within your system's PATH variable. For most systems, the /usr/local/bin path can be used.

    mv hugo /usr/local/bin

    You may need to use sudo to run this command successfully:

    sudo mv hugo /usr/local/bin

    If you do not have permission to move the file to one of the system folders, you can instead add it to a location in your home directory and then set that location in your PATH:

    mkdir ~/bin
mv hugo ~/bin
export PATH=$HOME/bin:$PATH

    Make sure to also add the final export PATH line in the above snippet to your terminal's configuration file, like ~/.zshrc on macOS.

  4. Test Hugo by running hugo version. This should output a long string indicating the version. If the correct version is not used, review the prior steps and the Install Hugo from Tarball section of the Hugo documentation.

Windows

While macOS and Linux are preferred by most of the core Linode Docs team, it's also possible to use Hugo on Windows.

  1. Download the hugo_extended_0.125.7_windows-amd64.zip file. Additional files for other operating systems can be found on the Hugo v0.125.7 GitHub release page under Assets.

  2. Extract the file to the directory you'd like to install Hugo under, such as C:\Hugo\bin.

  3. Add the directory to your PATH. In powershell, this can be accomplished with the following command:

    set PATH=%PATH%;C:\Hugo\bin

Fork and Clone the Linode Library

All of our guides are stored in the github.com/linode/docs repository. You will need to fork this repository and clone your fork to your local computer.

For more information about using Git, refer to the official Git documentation. If you're a Git beginner, both GitHub and GitLab offer excellent primers to get you started.

  1. On Github, navigate to the linode/docs repository. Click fork on the top right corner. When creating your fork, you only need to copy the develop branch.

  2. Clone your fork of the repository using either the SSH URL or the HTTPS URL. In whichever command you run below, replace USERNAME with your GitHub username. Running either command creates a linode-docs directory in your terminal's working directory.

    • SSH URL (the preferred method): This requires that you have a public/private key pair installed on your local system. If you do not have one, create one now. Once you have a key pair, upload the public key to your GitHub account. For further instructions, see Adding a new SSH key to your account. When running the command below, you will be prompted for a password. Enter your SSH passphrase in this prompt.

      git clone git@github.com:USERNAME/docs.git linode-docs

    • HTTPS URL: When prompted for your password, enter your personal access token from GitHub. For instructions on creating this token, see Creating a Personal Access Token.

      git clone https://github.com/USERNAME/docs linode-docs

    This may take a few minutes to copy all of the files and images to your machine.

  3. Navigate to the project directory:

    cd linode-docs

  4. After you first clone the repository, you should be on the develop branch by default:

    git status

    On branch develop
Your branch is up-to-date with 'origin/develop'.

nothing to commit, working directory clean

  5. Add the linode/docs repository that you forked from as the upstream Git remote for your local repository:

    • SSH URL: git remote add upstream git@github.com:linode/docs.git
    • HTTPS URL: git remote add upstream https://github.com/linode/docs.git

  6. View your remote repositories by running:

    git remote -v

    This command outputs all remote repositories and should match the following.

    origin	git@github.com:USERNAME/docs.git (fetch)
origin	git@github.com:USERNAME/docs.git (push)
upstream	git@github.com:linode/docs.git (fetch)
upstream	git@github.com:linode/docs.git (push)

    Most importantly, the origin should be your fork and the upstream should be the linode/docs repository. If you cloned the repository (or added the upstream remote) using the HTTPS URLS, the output will use those URLs instead.

  7. Install the Node dependencies for the repository:

    npm ci

Tailwind v3 upgrade

This section is only relevant to contributors who have previously worked on the docs repo prior to the Tailwind v3 upgrade (which occurred on July 6th, 2023 in docs release v1.252.0). After you merge in changes from this release (and onward), you will likely notice display issues when previewing the site locally. This is due to Tailwind v3 and the way it integrates with Hugo (and our theme). To complete the upgrade locally and fix any display issues, follow the steps below.

  1. Upgrade Hugo to v0.125.7. On macOS, run the following commands in a temporary folder (not in your docs repo):

    curl -OL https://github.com/gohugoio/hugo/releases/download/v0.125.7/hugo_extended_0.125.7_darwin-universal.tar.gz
tar -xvzf hugo_extended_0.125.7_darwin-universal.tar.gz
mv hugo /usr/local/bin

    If you are using a different operating system, refer to the Install Hugo section above.

  2. Once hugo has been upgraded, navigate to your docs repo.

  3. Make sure you are working with the latest commits in the docs repo.

    • For the develop branch, run:

        git pull upstream develop

    • For any other branches you may be working on:

        git merge upstream/develop

  4. Within the docs repo, remove the current node_modules directory and then reinstall dependencies.

    rm -rf node_modules
npm ci

  5. Now, preview the site locally and verify that the site looks as expected in your web browser.

    hugo server

Contributing to the Docs Library

This guide describes how to write and submit a guide for the Linode docs. If you would like to write on a topic, please visit our Contribute page to choose a topic and submit a writing sample. When you have received an email notifying you that your topic has been accepted, you are ready to follow the steps in this guide.

Fixing an Issue

If you want to start contributing by helping us correct existing issues, go to our GitHub Issues page and look for issues with the label help wanted. Read through the comments and make sure there is not an open pull request against the issue, and that nobody has left a comment stating that they are working on the issue (3 days without activity is a good rule of thumb). Leave a comment stating that you would like to work on the issue.

Create a New Guide

This section takes you through the process of creating a new guide, using the topic of installing nginx on Debian as an example. You will use a Hugo archetype to simplify the process.

  1. Checkout the develop branch:

    git checkout develop

  2. Update the develop branch with the latest changes from the upstream repository:

    git pull upstream develop

  3. Create a new branch for your guide:

    git checkout -b nginx-on-debian

  4. From the root of the Docs repository, run the following example command:

    hugo new guides/web-servers/nginx/how-to-install-nginx-on-debian/index.md --kind content

    • By running this command, you're specifying that the guide should be listed under the guides/web-servers/nginx/ section.

    • The guide itself will later be published under the /docs/guides/how-to-install-nginx-on-debian/ URL path. Note that the URL for the guide will not include the web-servers/nginx/ section information. This is intentional, as the docs website publishes guides under a flattened URL structure.

    • The index.md file will contain the Markdown content for your guide.

    • The --kind content option specifies that the content archetype will be used to populate the new Markdown file with sample content. The archetypes available can be found under the archetypes/ directory in the repository.

  5. The command will output the location of your new guide on your filesystem:

    /Users/your-computer-user/linode-docs/docs/guides/web-servers/nginx/how-to-install-nginx-on-debian/index.md created

    Note that the guide is created under a docs/ subdirectory that's within the docs repository (e.g. /Users/your-computer-user/linode-docs/docs/), which can be a little confusing initially. The root of the docs repository (e.g. /Users/your-computer-user/linode-docs/) contains other non-content files that are needed for publishing the site: Hugo's configuration file, theme information, unit testing information, etc.

  6. Start the local Hugo web server:

    hugo server

    This starts a local server you can use to view the Linode library in your browser on http://localhost:1313/docs/.

    Note: The first time Hugo is run on your workstation, it needs to compile a cache of web-optimized images for each guide in the documentation library. This process can take 10-20 minutes. If you run Hugo again in the future, the cache from your first build is reused and the startup time is much faster.

  7. In a web browser, navigate to the location of your new guide. The example nginx guide will be located at http://localhost:1313/docs/guides/how-to-install-nginx-on-debian/.

    Note that you will not be able to navigate to the new guide within the local website's Explore Docs menu, or through the search feature. This is because these features rely on a central search index, and this index is not updated until the production docs website is published.

Write and Submit

  1. Make edits or write new content using any text editor, though we recommend a code editor like Visual Studio Code. Your local Hugo development server has live preview functionality, so you will be able to view changes to your guide as you save them. Review our Linode Writer's Formatting guide for more information on how to make edits and for formatting / style guidelines.

    Any images that you include in the guide should be added inside the same directory as the new index.md file. Images should be linked to using their filename as the relative URL: ![Image Title](image.png). See the Images section of the writer's formatting guide.

  2. Stage your changes to your local branch. As a best practice, use a command like git status to verify you're working out of the correct branch and view a list of files that have been changed. If the output shows only the files that you've explicitly edited, you can stage them all at once using git add . Otherwise, add each one individually by referencing the file path in that command.

    git add docs/guides/web-servers/nginx/how-to-install-nginx-on-debian/

  3. Once the changes are staged, commit them using the command below. Your commit message should summarize the changes that were made.

    git commit -m "Initial draft of guide"

  4. Push the local branch to your remote fork (the origin remote repository).

    git push origin nginx-on-debian

  5. In your web browser, you can now navigate to https://github.com/linode/docs and open a pull request. When creating a pull request, provide a detailed overview of the changes.

Your guide is now submitted. Thank you for contributing to Linode! A member of the content team will review your guide and contact you if any changes are required.

Run Tests

Tests are automatically run by Travis CI for every pull request that is submitted. To view the results of these tests, navigate to the end of the pull request's conversation, and then click on the details link for the Travis CI - Pull Request check. You may need to click the Show all checks link to see this feature. After clicking the details link, an overview of the Travis CI tests appears.

In the Travis CI overview, under the Jobs and Stages header, three tests are present:

  • Vale: An automatic spell-checking service

  • Blueberry: A custom script which ensures that a guide's frontmatter section follows certain guidelines

  • Docs404: A custom script that scrapes the site and reports any internal 404 links. This script does not currently check for external 404 links.

To review the output of a given test, click on the link for the corresponding Travis CI job.