Mi voto para esta funcionalidad!
Todos los diseñadores necesitamos simplificar y unificar funcionalidades dentro de un mismo programa.
Por favor Xd team, hacerlo posible cuanto antes mejor :)

I'd like to add a comment here with an example. I always start a website development process out with some sort of outline. The ability to start in XD at an outline level would make it the very first tool I would open, and I'd be able to work with XD through the entire design process. Part of my process after the outline includes sharing overview sites maps - the current drawing board view just does not work as a site map showing connections etc. I put together a rough idea using three screen shot elements of tools I've used on projects. If you can get this under one roof you will have truly accomplished something! http://3.1m.yt/9GrtZ2W.jpg

This idea would be so helpful and would effectively collapse a few things I have to do as a designer into one app.

It would be really great to be able to export the whole app as a single PDF containing all visual links between each artboard, similar to what storyboards look like. The PDF contains a large canvas with all screens connected to each other, ordered hierarchically.
Additionally, each "connexion" can be labelled with custom text to provide more context about what should happen (animations, timing, etc...).
An example is attached to this feature request.

Quite agree with you. // This feature would be helpful to we explain to the client the entire project. We really need it.

http://www.sketchappsources.com/free-source/attachment-1638-flowchart-wireframe-kit-sketch-freebie-resource-img1.html

Thanks Peter, I went down a rabbit hole of links haha (since it seems you've threaded together these multiple subjects).

Automagic and simplified interaction connections seem awesome and I'd love to see this in the future. With that said, I'm still skeptical on if that would solve for more simpler sitemap and IA needs (that sitemap/flow programs would otherwise solve).

See also https://adobexd.uservoice.com/forums/353007/suggestions/12957801-simplified-view-of-artboard-interaction-links-overview-of-flow, which is more about an *automatically* generated site map view based on the artboard interaction connections you have created.

Besides the Design and Prototype tabs, it would be nice to have an Information Architecture tab where users could create site maps and flow charts with tools or stencils that are specifically made for the job. Auto-layouts for diagraming would also be a nice sub-feature under this tab.

I really want to this feature, but i want to export to PNG (not pdf because Windows is not friendly with pdf).

See also https://adobexd.uservoice.com/forums/353007/suggestions/12957801-simplified-view-of-artboard-links-overview-of-flow

I love this idea! :-)

Agree, and i love to see each art board on its own page as well. Balsamiq has this/similar feature, that would be awesome to see in XD. Export to PDF has +1 vote for me! :-)

Some of the other ideas are really amazing, but a simple export to PDF pages in the same exact order that pages are currently saved to share online would be amazing. Reason:

While the share online feature is great, we need to save "versions" of our work that we can use to reference at a later time, and single consolidated PDFs fit in with workflows in JIRA and Pivotal Tracker better at the moment.

Keep up the great work and very active development!

Yes, as Emanuele commented, please allow an export feature that saves each artboard as its own PDF page within a multi-page PDF document.

Definitely needed. You should be able to select screens, and export only the flow includes the selected screens, thus avoiding the clutter of the whole flow. It can also be nice to be able to break an app into groups of screens as a more generic feature - in a way that will enabling focusing and working on each group separately.

PDF Export Options
- Export all art boards with labels to one doc.
- allow placement of project name , id and logo ( although this can be achieved in its own art board)
- Show all user flow lines and arrows
- Do not shade or gray out as you do with selected now.
- Add labels/ titles to the path displayed along path.
- Allow of user specified color of workflow Lines from specific art boards. ( Set an outgoing color connection for an art board)
- Colorize the "Home tag" on the art board to match this specified color.

I was trying to do this in a backwards sort of way and gave up. I took web shot snaps of each of my sites existing pages and imported those pngs into XD. I wanted to then draw in the user flow paths and add some labels along the path. The goal was to print this on a large plotter. In the end I just imported all those pngs into one art board, exported as a png and then printed that at 44in wide and 16 feet long. We then proceeded to mark it up and work for there. It would have been *Amazing* if we could have done this in XD and presented to the client, instead the client never got a copy. :(

Not only the map, but also every single artboard as a single page of a PDF document of many pages, preserving prototype interactivity saving links as PDF internal page links invisible rectangles. So that in this way the prototype can be navigated in the PDF file like on a web page (transitions excluded of course).

I also want this. Clients ask us to send a PDF of the entire user flow. And always have to go to illustrator and paste the images and do the tedious task of doing all the linkage again.

Please add the feature to export entire map User Journer to a single PDF file and share the entire map online. Otherwise, love Adobe XD.

What would be great is if we could define an exportable area (e.g., I have 45 artboards, I need to share just a subset of those to explain the flow—artboards 30-36). If I could define the area with a tool, similar to the old print selection features in some apps, this would allow me to only export the flow I need as a pdf, jpg, png, whatever. Being able to redefine the background color for export would also be a plus.

The reason why this is helpful is because when we document we have to share specific parts of the flows so that the developers can understand that flow better.