Skip to content

ues-io/docs

Repository files navigation

uesio docs

The Uesio documentation site (https://docs.ues.io)

All actual documentation is written in Markdown files, which live within data/articles/docs

First-time setup

To get your local environment setup, first ensure that:

  1. The ues.io CLI is installed (Run uesio -h to ensure it's available)
  2. Node 18+ is installed
  3. You are added to the "Maintainers" team of the "uesio/docs" app. Ask someone at ues.io who is a maintainer to add you to the team, then verify that you can access the app by logging in to the Studio and verifying that you can see "uesio/docs" as one of the apps.
  4. Run this to get setup locally:
git clone git@github.com:TheCloudMasters/docs.git
cd docs
npm run init
  • Select "uesio/docs" as the app.

Development

You can develop both locally and/or in the Studio.

  1. Pull (Studio to local): npm run pull
  2. Push (local --> Studio): npm run push

This will push to whatever Studio workspace you have configured with uesio work (e.g. dev).

NOTE If working in a shared workspace, remember to pull before you push!

Continuous integration

The main branch will automatically be built and deployed to the prod site (https://docs.ues.io)

You can also manually initiate this using the "Manual patch release" workflow.

  1. Pack and deploy the app's bundle
  2. Upsert docs articles

Release to prod

Use the "Manual patch release" workflow to initiate a Prod deployment to the prod site in the Uesio "prod" environment (accessible at https://docs.ues.io). Select "prod" as the environment target.

To manually upsert documentation articles into a site, use ./seedprod.sh, which will upsert doc article changes to whatever site is configured with uesio siteadmin

Editing documentation articles

The docs site is built on the uesio/cms app, which includes an article collection. All documentation content is organized within articles, with the content being written in Markdown and stored as a User File attached to the "uesio/cms.content" field.

Markdown content can be written and previewed locally using VS Code's Markdown Preview plugin, or it can be previewed in a Studio Workspace or Site.

Articles can reference local images or other content as long as they are siblings, via a normal relative image reference, e.g.

![New app dialog](./newappdialog.png "new app dialog")

All articles and associated files are uploaded via the "seed" script.

Simply run npm run push-content to upload all docs articles and images, etc.

Edit docs articles in a Workspace

npm run push

does the following:

  1. Deploys the uesio docs app to your workspace
  2. Upsert doc articles and static content

About

The uesio docs app

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages