kaitvan

Markdown Assignment Feedback

Don't bother making a header bold. If you bold a header, it won't make a difference, because headers automatically have bold formatting. The following two headers are both level 2 headers with double # in front, but the first is also bolded (**). You can't see the difference!

3 Tips to Improve Your Work

1. In numbered lists, you don't have to number them. Start everything with a 1. and it will automatically number them for you! 🤯 Click the raw version of this markdown file to see an example!
2. For fenced code blocks, you do need the three backtics to close the block. If you don't, anything you write after that will be included in the fenced code block.
3. Only use a single backtic on either side of the word or phrase to create an inline code block. A few people had two backtics on either side. GitHub seems to adjust it for you and render it the same, but not every space would recognize that as valid Markdown. Like Slack, for example!

kaitvan

Calendaring - CFU

To start this assignment:

1. Click the button in the upper right-hand corner that says Fork. This is now your copy of the document.
2. Click the Edit button when you're ready to start adding your answers.
3. To save your work, click the green button in the bottom right corner. You can always come back and edit your gist.
4. As you are working, you can use the Preview changes button to check your markdown formatting.

Exercises

kaitvan

Calendaring - CFU

To start this assignment:

1. Click the button in the upper right-hand corner that says Fork. This is now your copy of the document.
2. Click the Edit button when you're ready to start adding your answers.
3. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

Exercises

kaitvan

<!--- Provide a general summary of your changes in the Title above -->
<!--- DELETE ALL COMMENTS BEFORE CREATING PULL REQUEST -->

## Description
<!--- Describe your changes in detail -->

## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->

kaitvan

<!--- Provide a general summary of the issue in the Title above -->
<!--- DELETE ALL COMMENTS BEFORE CREATING ISSUE -->

# User Story
<!-- Write a description of what the user should see and experience based on THIS ticket -->

# Acceptance Criteria
<!-- The Acceptance Criteria of a User Story consists of a set of Test Scenarios that are to be met to confirm that the software is working as expected. The Acceptance Criteria illustrates the scope of the individual ticket and expectations from the team and client. -->

<!-- The Acceptance Criteria is applicable to specific User Story. Acceptance Criteria of each User Story will be different based on the requirements of that User Story. -->

kaitvan

### Tickets WITH Dependencies
Tickets are listed in the order they need to be developed. DO NOT start a ticket before ensuring the ticket before it is completed.
- [ ] TicketName(assigned Dev) IssueNumber
- [ ] TicketName(assigned Dev) IssueNumber
- [ ] TicketName(assigned Dev) IssueNumber
- [ ] TicketName(assigned Dev) IssueNumber

### Tickets WITHOUT Dependencies
The tickets below DO NOT have any dependecies and can be worked in any order. They are listed by importance. Start at the top and take the next ticket.
- [ ] TicketName(Assigned Dev) Issue Number