Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
docs: new option direction (horizontal, vertical and papyrus) #883
Comments
|
Maybe I will have some doubts, but I would like to take it. |
|
Awesome! Thank you for your help @DaniAcu Yeah I know it is not that clear but it is something brand new which even live yet in our editor but, I just updated all our kits with it so you can easily give it a try. You should be able to create a new presentation locally with After you have started your presentation locally (
=> you can swipe the presentation
=> you can swipe the presentation
=> you can scroll the presentation Let me know if it is clearer like this? Of course happy to help, ping me anytime! Note: if you are participating to Hacktoberfest, note that the issue can of course wait for October so you can count it. |
|
@DaniAcu are you working on that one or should I un-assign you the issue? |
Documentation
The presentations used to be swipable horizontally but we recently enhanced this. We are going to introduce the ability to swipe vertically and also developed a new mode we called papyrus which basically transform a presentation into a "landing page".
These options can be set on the
deckgo-deckmain component with the propertiesdirectionanddirectionMobile(respectivellydirection-mobileif used as HTML attribute).Both option can be set as
horizontal,verticalorpapyrus.Direction default is
horizontal.Direction-mobile default is
papyrus.These options are not yet documented and therefore a new dedicated page should be added to our docs.
https://docs.deckdeckgo.com/deck/direction
What do do
To add a new page, the transition, renamed in master as "animation" documentation example can be followed.
Add a new TSX component
app-direction(see app-animation source as example). Therendercontent does not matter as it will be parsed at build time aka will be overwrite later with the related markdown file.Add a new route in app-root
Create the documentation in markdown. The animation example can be followed.
Note that there is no live reload to parse the mardkow to JSX.
Get starter
Get Started
If you need help to get started with this feature, I'll be happy to help.
Ping me: @peterpeterparker | twitter | email | slack