This repository was archived by the owner on May 4, 2022. It is now read-only.
Slide deck design updates. #1
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi Jackie,
As a small step to help smooth your on-boarding with GitPitch I have created this little PR for you. The purpose of this PR is to show you how with a small number of changes to the
PITCHME.mdfor your Day01 presentation you can deliver some nice updates to your slide designs.My main goal here is to share some syntax features/tricks that can be used to help you get the most out of GitPitch...by getting the most out of the space on your slides. You can view my updated version of your slide deck right here:
https://gitpitch.com/gitpitch/TechReady2019?p=Day01
You can look over the file changes for this PR to see the exact set of changes that I have made to your deck. These changes are primarily taking advantage of (1) snap-layouts, (2) externalized and reusable source code, and (3) built-in list syntax and list style features.
This is a real PR so you are more than welcome to merge if you like the direction these changes are taking your deck. But if not, no problem. If nothing else, I hope the PR will give you some ideas that you can adopt for future decks. And if you have any questions about any of this, just let me know.
Cheers, David.