The one stop shop for CSAI documentation and onboarding. We want to make information accessible throughout the club and provide members with the tools to ramp up quickly and get to work on the team of their choosing.
If you have knowledge to share or you've got a bug to squash, please submit a PR!
Lets get you up and running! If you haven't already, install node before proceeding.
- Clone the repo:
git clone https://github.com/calpoly-csai/csai-docs.git
- Navigate to project:
cd csai-docs
- Install associated libraries:
npm install
- Start the dev server (you will likely need version 14+ of Node.js):
npm run dev
- Look in the readout from the previous command and find the
localhostlink (it may not be at the end of the output, scroll up if you can't find it). Copy and paste it into your favorite browser.
From here, you can make changes to the project files in a code editor and see the updates render live! Writing pages is as easy as creating a .mdx file and defining the associated title and route in the document header:
---
name: React Poem
route: /react-poem
---
# React Oh How I Love Thee - A Web Developer Poem:
lorem ipsum :)
This page is built on a powerful stack of React-based packages that you can leverage in you documentation:
- For more info on document formatting and site structure, see the Docz docs.
- For design system and theme information, see Theme UI
- For CSS-In-JS styling, use Emotion
- Wanna dive into the deep end and tweak some static site config, check out Gatsby
You can import these packages directly into your page or component to expose some desired functionality:
/** @jsx jsx */ // Comment used to enable Theme UI sx styling
import { useState, useEffect, useRef, useCallback } from "react"; // Some boilerplate react functionality
import { css, keyframes } from "@emotion/core"; // Pull in emotion for some styling
import { jsx } from "theme-ui"; // Theme UI for some theming :P
Accessing components or resources from a page with a relative path is a pain, so I added a couple aliases to make the job easier:
| alias | definition | example |
|---|---|---|
| @ | /src directory | import Project from "@/components/Project" |
| public | /public directory | import tensorflowIcon from "public/icons/tensorflow.png" |
When writing a new doc, It's good practice to mirror the structure of pages in the same category. Take a look at adjacent pages before adding your content. Both the Teams and Projects category have a defined header style which should be maintained for future entries.
New components should follow the defined UI theme of the site. Our theme is easily accessible through the <StyleGuide/> component. Adding this to any document will display the colors, fonts and type sizes that can be programmatically referenced using the sx prop. Just make sure that you remove the style guide before committing :).
After adding/deleting a file, the build broke:
- Try restarting the
npm run devprocess. - Could be a caching problem. Delete the
/.docz/.cachefolder and restart dev server.
My code edits aren't showing up on the localhost dev server:
- Try restarting the
npm run devprocess. - Browsers will often cache pages to avoid unnecessary fetches. To bust the cache, you can reload the page, open the page in a new window or restart your entire browser.