search

vyelnats / frictionless-v

Open Knowledge Foundation Frictionless Fellowship personal repo for notes, code chunks etc.
0 stars 0 forks source link

Week 4-5 - November 8 - 19: Programming catch up #4

Open vyelnats opened 2 years ago

vyelnats commented 2 years ago

Goal: to make sure everyone feels comfortable with git, GitHub, the command line, (and optionally Python & R)

Week 1: Discuss imposter syndrome, problem solving skills, and read the Open Knowledge Foundation's Contributing Best Practices in resources. https://fellows.frictionlessdata.io/resources/#contributing Together, we will also set up your programming environment. We will do a quick GitHub tutorial & you will each post your blog following these GitHub instructions. https://fellows.frictionlessdata.io/syllabus/#:~:text=blog%20following%20these-,GitHub%20instructions,-.

Week 2: use the Coding Resources here https://fellows.frictionlessdata.io/syllabus/#:~:text=the%20Coding%20Resources-,here,-to%20watch%20videos to watch videos and do tutorials as needed. finish posting your blog (optional) Create a personalized profile README on GitHub using these instructions these instructions Remember to ask questions in Slack if you need help! Check in: Group meeting during week 1 Check in: One-on-one meetings during week 2

vyelnats commented 2 years ago

TO - DO:

vyelnats commented 2 years ago

GitHub instructions for the command line/terminal (Lilly can help you with this): The repository is here https://github.com/frictionlessdata/fellows

The blog content can be found within the following folder:

fellows -> content -> blog -> [your-blog-folder-name] -> contents.lr

Step 1:, Pull down the main branch so you have the most recent version of the website code on your local machine. Do this before you make your edits. Type 'git pull origin main'

Step 2: Create a new branch: in the terminal, write 'git checkout -b your-branch-name' (replace with your branch's name, which can be anything) make sure you don't edit the main branch You can check with 'git status'

Step 3: Add your blog text to the 'contents.lr' file within the correct blog folder. Each blog has it's own folder. Add your text as Markdown, and remember to keep the title and body keywords.

Step 4: Add and commit your changes: Once you finish editing the file, in your terminal, type: git status make sure everything looks OK git add content/blog/blog-folder-name/contents.lr git commit -m "adds your-name's blog"

Step 5: Push your changes to your branch and open a Pull Request git push origin your-branch-name in GitHub, open a pull request (PR) + tag @lwinfree for review Lilly will merge your PR ask Lilly or each other if you need help!