Aspiring to become new standard of teaching &
learning software development skills
With its clean design, great speed and flexibility, Nerdbord unlocks your learning materials full
potential. It is the tool of choice for teams, mentors and schools to grow faster and better.
Centralised content base
This is a place where all of your content live. You can add it here and reuse as wish. Nerdbord content is stuctured in a way that encourages you to put practise first. Projects consists of lessons that consists of tasks.
Projects
Base content container
Each project consists of lessons and tasks. For each project you can add extensive description that will be visible to your users. You can choose from 2 different projects types: Default and Gitflow.
Each project:
Can contain extensive description made in WYSIWYG editor
Have its own color theme
Can be published or unpublished – more about that in a program
Can be archived to pack all of the content that you’ve created in Nerdbord and downloaded it into a zip file with task descriptions as markdowns
Default Projects
Full content flexibility
Default projects do not require any external anthorisation. It’s the simplest form of projects that enables you to add all kinds of tasks.
Project specifics:
You can add any type of task in this project except for Github ones.
Gitflow Project
Connect GitHub repository directly to a project
Connected repository gets duplicated to your students repositories when they start working on it. Each task can have different GitHub related completion requirements.
Teach your students additional skills:
Real software development workflows
Working with GitHub repositories, pull requests, code reviews
Iterative process of professional coding flows
Initial GitHub authorisation requirements:
Install Nerdbord on your GitHub organisation in Settings / General
Users will be asked to authorise Nerdbord on their GitHub accounts while activating GitHub projects
Lessons
Grouping tasks together
Each project consists of lessons that consist of tasks. Lesson can have its own description and users activate them to display tasks on boards.
Tasks types
Theory task
This is the most basic task. You simply add a description to it and it has no completion requiements.
Completion requirements:
None
Users can:
Move it right to “Done” column
Text editor task
In this task you open the window between you and your users with text editor input where users can place their answer.
Completion requirements:
Review available Users will be able to request review but it will not be obligatory to complete the task
Manual approve Users will not be able to move this task to “Done” without your review acceptance
Users can:
Place their answer in text editor inside the task
Complete task according to completion requirements
Additionally:
You can also write in the text input and override users answers or write additional comment to help them out!
Code editor task
In this task you open the window between you and your users with code editor input where users can place their code answers.
Create in-app code challenges using cloud code compiler. We currently support 8 languages (Typescript, Javascript, Java, Python, PHP, C++, Ruby, Rust)
Completion requirements:
Review available Users will be able to request review but it will not be obligatory to complete the task
Manual approve Users will not be able to move this task to “Done” without your review acceptance
Users can:
Place their answer in text editor inside the task
Complete task according to completion requirements
Run their code cloud based code compilator
Additionally:
You can also write in the code input and override users answers or write additional comment to help them out!
Gitflow task
This task shows only in Gitflow projects and is directly connected to project repository connected to the project. Choose completion requirements for each task separately.
Completion requirements:
Connect Pull Request User has to create pull request in GitHub repository and connect it to this task
Request code review User has to request code review from assigned mentor. Code reviews happens in GitHub repository.
Get manual approval User solution has to get manual code approval in GitHub repository.
Merge code User has to merge code in GItHub to complete this task.
Users can:
Work in GitHub on a task and use task description to follow instructions
Complete task according to completion requirements
Learning by practise
Practise is proven to be the best possible way of learning any skills. That’s why in Learning Lab you’re able to create users groups and assign practical projects to each group individually and keep an eye on users progress.
User groups
Create programs for each group
User groups consists of invited users. Each of individual user receives own link and own kanban board. All progress that users make, meaning their all tasks progress, tasks previews is for you to monitor.
Program
Users will see on their kanban boards only the projects that you will assign in the group from Project Library. You can change it and update it anytime.
Important
Users will not get invitation until you will activate the group
Users will have access to your content until group deactivation / removal
Deleted / Unpublished content from library will not be visible to the users and they will get the notification about it
Updated content needs to be manually updated in group’s program to be visible to users
Reviews
Feedback is a gift
Each task that you will mark as “Review available” will enable users to send you review request. All review requests are visible in Learning Lab. After making any review decision users will have to change the task placement from “in review” to different column.
Accept
When you accept the task, users will know that they did a good job and they can move the task to “Done” column.
Submit
When you submit the task, users will know that you’ve reviewed it and problably added some comments. It’s up to a user to move to a task back to “in progress” or to “done” column.
Reject
When you reject the task, users will know that they need to work on a task some more. The only thing that they can do after you reject the task is to move the task back to “in progress” column.
Important
Users can get as many reviews as they want. We’re working on making reviews limits. See out changelog to see future options and suggest your own!
You can change your review status anytime as long as users have task in “In review” column.
Even if user doesn’t click “Request review” button you can still review it by clicking user name on users list.
Your users perspective
Each user gets their own kanban board with content that you’ assign in a group program. It has two views: Program and Board.
User board
Private kanban board
Activated projects and lessons will be visible on kanban board. Users can move the tasks around according to their task completion requirements.
Progress bar
Main program objective is to move all of the tasks from Backlog to Done column. Progress bar displays progress accordingly.
Task statuses
Each task has information about project and lesson that it’s in as well as completion requirements set by you in Project Library.
Task in review
Tasks that are “in review” column have their inputs blocked. If user wants to edit their answer they must move task back to ‘In progress” column.
Important
Users can create their own programs too by logging to Nerdbord.io!
Users can switch between differenet user groups in the top menu dropdown
Users can switch between board and learning lab by clicking on their profile picture
Program
List of assigned projects
Each project assigned to user program needs to be activated first. Then all lessons will be visible. Lessons need to be activated in order to be visible on users kanban boards.
Default projects
Project activation by clicking “Activate project”.
Gitflow projects
After clicking “Activate project” user will be asked to authorise Nerdbord on their GitHub account in order to copy connected repository to their personal repositories.
Important
Lessons have to be activated to be visible on the board
Lessons can be hidden from board by the user for their view comfort
