Skip to content

100-Days-of-Coding/Coding-for-100-days

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

83 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Coding-for-100-days

Thanks for choosing to take this 100Days of flutter with us

i must say it is not an easy decision to take so if you decided to take it then Congrates

Objectives

By the end of this 100 Days of Flutter, you should be able to

  • Learn and implement Dart Data structure
  • Understand and Implemented Darts Object Oriented nature
  • Write and Deploy you flutter Apps
  • Learn to connect your App to Firestore (firebase)

Description of the 100Days of FLutter

  • This is going to be an interactive period, your resources are available here and that is the curriculum we will be using. find it here here
  • It will take self discipline to go throughm we are an open community, so feel free to ask when you are stock, and advice! GOOGLE IS YOUR BEST FRIEND
  • Following the course material above, your progress is tracked based on your pull request, just for accountability purpose.

Getting Started

Enough of talking, lets get you start,

  • firstly navigate to https://github.com/100-Days-of-Coding/Coding-for-100-days and fork the repo
  • next, clone the repository with the following command git clone -repoLink
  • next study the repository structure, TiPs, everyone's work is inside a given directory inside the root directory,
  • create your own folder at the same level with everyones directory bearing your name, you can do so with the command mkdir Coding-for-100-days/<you-name>
  • excellent if you are up to this level, go ahead and do you first task by opening the directory with your prefered text editor, so some changes.
  • are you done, next check your changes with git status
  • stage your changes with git add /fileChanged
  • commit with git commit -m "commit message"
  • Awesome, we are all set, your default branch maybe main or master, if you feel you want to use this branch, then ignore the next two steps and run git push
  • Else, create a branch and switch to it with git checkout -b contrib_branc_name
  • now push to the upstream of your branch with git push --set-upstream branch_name
  • Congrats, your changes should be on github now, just create a pull request to the main repository of the organization

|Author: @andrew21-mch

Resources

So, working together, we will use the following resources

we will continue with the folders created, recording our work in our respective folders. A new folder for projects has been created where will create our folders and record or submit the individual projects at the end of the modules

Author: @PetraAG

Releases

No releases published

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •  

Languages