This is a technical news post about the developers' journey towards learning the three tools we're using for Iris: Rust, NextJS, Tauri, and git/GitHub! It would be amazing if all the devs shared their opinion here. :)
Getting Started
As usual, please pull this road-to-iris branch to your repo. You must edit the 09-20-road-to-iris.md file. You can do so like this:
At the top of the file, you will find an authors array. Please add yourself as an author using your UCI email!
Introducing yourself
When you begin writing your section (that is, a new ## heading), please make sure to introduce yourself with the following information:
Your name
How long you've worked with Ojos
Previous experience in what you do
Your responsibilities during the summer (frontend? backend? Tauri?)
... and any other info you'd like to share, such as UCI major, year, etc.
Starting a development environment
Just writing on the Markdown file should be enough, but if you'd like to see how the website would look with your changes, you can do this:
npm i
npm run clear
npm run start
This news post will be in the News tab on the website.
Before submitting your changes...
Before you submit your changes, please do the following:
npm run clear
npm run build
Building your project will point out any errors that might exist!
What should I write about?
Write about your experience in developing Iris, what you enjoyed, what was challenging, etc. Specifically, about our toolset! Any and all that may be relevant to you:
Rust / Tauri
React / NextJS
git / GitHub
How much should I write?
As much as you’d like! Though, please only have one h2 heading (##) per person, and as many h3 headings (###) as you need!
Description
This is a technical news post about the developers' journey towards learning the three tools we're using for Iris: Rust, NextJS, Tauri, and git/GitHub! It would be amazing if all the devs shared their opinion here. :)
Getting Started
As usual, please pull this
road-to-irisbranch to your repo. You must edit the09-20-road-to-iris.mdfile. You can do so like this:Add yourself as an author
At the top of the file, you will find an
authorsarray. Please add yourself as an author using your UCI email!Introducing yourself
When you begin writing your section (that is, a new
##heading), please make sure to introduce yourself with the following information:Starting a development environment
Just writing on the Markdown file should be enough, but if you'd like to see how the website would look with your changes, you can do this:
This news post will be in the News tab on the website.
Before submitting your changes...
Before you submit your changes, please do the following:
Building your project will point out any errors that might exist!
What should I write about?
Write about your experience in developing Iris, what you enjoyed, what was challenging, etc. Specifically, about our toolset! Any and all that may be relevant to you:
How much should I write?
As much as you’d like! Though, please only have one h2 heading (
##) per person, and as many h3 headings (###) as you need!Resources