calpoly-csai / csai-docs Goto Github PK

For Python-based getting started pages, an embedded notebook would be super helpful. We just have to integrate this component and add documentation for this process

Page location in repo: /src/pages/teams/nlp.mdx
Check out the App Dev team page for structural reference.

Describe the team, its responsibilities, and the getting started process

Its got a few bugs

• Enter doesn't submit form
• Grows infinitely when pressing enter
• No error handling for server errors
• No handling for offline
• Can submit blank strings
• Doesn't fit on iPhone SE viewport

We want the new user flow to go something like:

Club Overview => *picks a team => *reads about team => Getting Started section on that team page => General tutorials to understand how the team integrates with the whole.

A general getting started page with these interactive choice points in a guide would be useful so people don't get lost. The page is already created: @/pages/getting-started/getting-started.mdx

Users should be able to easily move to the next section after reading through the current one. Add a react component that has a next and previous section button (arrows) and the title of the corresponding section inline for reference. Check out Vue Docs as an example.

Page location in repo: /src/pages/teams/database-development.mdx
Check out the App Dev team page for structural reference.

Describe the team, its responsibilities, and the getting started process.

Page location in repo: /src/pages/teams/data-aquisition.mdx
Check out the App Dev team page for structural reference.

Describe the team, its responsibilities, and the getting started process.

Page location in repo: /src/pages/projects/swanton-ranch-ai.mdx

With the CZU Lightning Complex Fires, this project seems to be up in the air. Just check out the current state of the docs and add anything that's missing.

Plz write about your team and include a getting stared section.

Page location in repo: /src/pages/teams/hardware.mdx
Check out the App Dev team page for structural reference.

Write a general team description and a getting started process.

Theme UI has an awesome set of atomic layout components that'd make our component development much more intuitive. But when I import them, the components are undefined 😱. Let's fix that somehow.

The most common current node install is node v12. The project was originally built with v14. It'd be great if we didn't have to pull every contributor up to v14. Check out the error messages on v12 and see if we can make the project backwards compatible.