Archive for the ‘Uncategorized’ Category

How to Upgrade to Reverb 2.0

Posted on: July 17th, 2018 No Comments
Have you ever tried to upgrade from PDF, WWH5 or Reverb 1.0 to a more advanced user-friendly output? We know it might seem difficult for a multitude of reasons. Perhaps you have inherited a project and you are not sure where to start or maybe you have several customizations in your output that make upgrading seem impossible.
With the release of ePublisher 2018.1, many ePubilsher customers have quickly and easily upgraded to Reverb 2.0. By utilizing the information in this article, this post will help get you started on the path to a Reverb 2.0 HTML5 advanced document set.

Here are a few reasons  why it is a good idea to upgrade to Reverb 2.0

  • Improved Customer Satisfaction
  • Increased Product Value
  • Measured Customer Engagement

Reverb 2.0 was designed to help you, the Content Creator, get the most relevant information to the customer in the least amount of time while maintaining an intuitive feel to your document sets. If you are looking to increase the value documentation brings to your organization Reverb 2.0 is a big step in that direction.

Process for upgrading

Find the Right Reverb 2.0 Skin

To view the Reverb 2.0 skins, we recommend adding a target to your existing ePublisher Designer project. This is so you can see what your source documents look like in the new skin and identify which customizations are going to automatically transfer over and which ones will need to be manually transferred. You always have the option of creating a new Designer project to see what the default output will look like.

How to add a target

  1. Click on the Project Tab in the menu bar and select Manage Targets
  2. In the Manage Targets window, you will select Add to create a new target
  3. Pick a target name and enter it in the Target Name box
  4. In Format Type, click on the drop-down arrow and select WebWorks Reverb 2.0
  5. Click OK
  6. Verify that the new target name appears in the Manage Targets window.
  7. Click Close

Once the new target has been added, it will now appear in your active target window. To view the new format simply select the target and generate all. Feel free to experiment with each new target, once you find the right Reverb 2.0 skin you can delete the other targets.

Choosing the Right Customizations

Once you have selected a skin the next step is to choose the right customizations. It is a simple process:

  1. Compare customizations from the old target
  2. Pick which new features to customize in Reverb 2.0
  3. Regenerate your output.

When comparing customizations (for more about ePublisher customizations click here) we recommend starting with the Style Designer. Any customizations in the Properties or Options tab will be automatically carried over to Reverb 2.0. Only review bolded items on the Target Properties or Target Options tab because they are not automatically carried over because they are Target specific.

After you have reviewed the old customizations you can add new ones. All new features available in this area will be listed in the Properties and Options tab. If you see a feature you would like to customize only for the selected target, look for the feature listed in the Target Properties or Target Options and make the changes.

Once you’re finished working in the Style Designer compare customization in the Target Settings window.

Hint: create an excel sheet with the categories in Target Settings that have been customized.

If a category carries over to Reverb 2.0, the name will be the same in the Target Settings window. For example, Company Information is the same category name in the Target Settings of WebWorks Help, Reverb 1.0 and Reverb 2.0. 

With the excel spreadsheet created you can compare target settings in Reverb 2.0 and determine which settings should be transferred.  After transferring the target settings you can scroll through the categories and determine which new features to customize. After all the customizations have been made, generate the new target. If the output meets all the requirements, we would recommend moving to the section “Putting on the Final Touches” If not, you will need to compare the Advanced tab customizations.

We recommended you have the person who created the Advanced tab customizations compare them. If that person is not available, you can create a support ticket to get help with the transfer. If you would like to learn more about the Advanced tab customizations there are several options available to you. We have ePublisher 201 training that covers Advance tab customization in detail. We also have Study Hall in which you could bring in a project and have someone help you determine the best way to customize a project. The optimal path is to take ePublisher 201 training for a solid overall understanding of the Advanced tab features and then Study Hall or a support ticket for one-offs.

Putting on the final touches

The final step of the process is to put on the final touches to your Reverb 2.0 output. Reverb 2.0 was developed with Sass technology to make it easier to customize colors, logo placement, and icons.

To change the color, logo placement or icon of your Reverb 2.0 output, navigate to the proper file under the Advanced tab (to learn more about Advance tab customizations click here.) Once you have selected either target or format customizations navigate to the Sass folder and make the necessary customizations in the correct file.

_colors.scss is the file to change the color scheme of your Reverb 2.0 output. This file is written so you can design a nice output with as few as three colors. You just enter the hex color code in the proper location as indicated in the picture below.

_sizes.scss is the file where you can control the dimensions of sections within the Reverb 2.0 layout. Sections include areas like menu, toolbar, and toolbar logo. The file is well noted and easy to navigate. Just find the right section and make the necessary changes.

These are just a few examples of the Sass system we are using to help you customize Reverb 2.0. For a full list of the Sass files and their descriptions, you can go here.

We at WebWorks have designed our newest output with your customers in mind. Reverb 2.0 has new and improved features to help you guide your customers to the information they need. We’ve made upgrading easy for you by decreasing the amount of time needed to do so and by helping make sure you hold on to the customizations you’ve added. When making the move to Reverb 2.0 feel free to reach out if you have any questions.

Product Update: ePublisher 2017.1 build 2333 now available

Posted on: November 1st, 2017 No Comments

After releasing 2017.1, we made some minor enhancements that we wanted to make available before the next major release.

For users who have already installed ePublisher 2017.1 build 2306: The update to build 2033 takes only a few minutes and does not require a prior uninstall. At the setup prompt, just select the Update option.

With build 2333, you will be able to incorporate the following summarized enhancements:

  • Reverb Search Index Relevance handling now supports fractional values smaller than 1. By default ePublisher styles are scored with a relevance of 1, however with this improvement, baggage files and external links that get indexed will default to a small percentage of 1, making sure that they do not get artificially inflated due to document size.
  • Reverb Search Indexing of external links ignores duplicate links to URLs different only by the ‘#’ at the end. This prevents indexing the same document mulitiple times just because it was linked multiple times with a different ‘#’ target.
  • Reverb Search baggage info file can now be located relative to the first source document in the project. This is useful for CloudDrafts publishing and when maintaining different Express projects that use the same stationery but have different baggage files and external links.
  • AutoMap now supports new command line options for scanning to find new variables, conditions, and styles. This allows for scripts to detect variables and conditions that have not been configured in the Statinoery or Express project.

For more information, please consult the release page and online documentation.

STC Summit

Posted on: June 10th, 2014

WebWorks is an Austin-based company. We have been here for over 20 years. I am a native Texan. I have lived here all my life. I was in Dallas during the heat wave of 1980—a 42-day string of high temperatures over 100 degrees. You could literally fry an egg on the sidewalk for breakfast. So let me tell you, when I got off the plane in Phoenix and said, “Damn, it’s pretty hot,” it was hot.
It was hot and beautiful, and the perfect setting for STC Summit 2014. I took all the precautions with my crew. “Drink plenty of water,” I told them. In heat like that, water is evaporated right out of your skin. It doesn’t hurt to mix a little Scotch in with that water. I am a Gin man myself, but we were talking survival here. Lucky for us, the conference was going to be another huge success.

I think for me, this conference started off better than any other had before. We were staying at the Hyatt Regency in downtown Phoenix, and inside the hotel, there is a restaurant named Networks. Doug Pocius is the beverage manager there—go in and say hi if you get a chance—and the food is fantastic. Networks with KentI met Kent on the first day, and we started talking normal hotel restaurant talk, like, “Hey, what you doing in town?” “Where are you from?” “No sir, it is not that kind of hotel.” Just the typical small talk. Kent was telling me what he does outside of working at the hotel, and we had a very interesting conversation. He told me about his band and the different sound equipment he uses while they are performing. I asked him if he ever used the manual on any of those, and he said, “The manuals just aren’t convenient for me, so I just pretty much figure it out on my own.” He explained what was convenient for him was forums and just word of mouth. He said, “You know, the manuals probably have all that information, but it is not easy to find. I mean, use the terms I am familiar with, or put it on my phone. It is easier for me to look stuff up on my phone.” I told him that was great feedback, and I was heading into a building where a lot of smart people were going to figure out how to give him exactly what he wants. Kent seemed to appreciate that, and really that is what it is all about: making our audience happy.

So, with Kent’s feedback in mind, I hit the conference.   Convention Center FrontThe first day was fast for me and the team. Jack and Lauren headed to the exhibition floor with our channel partner, Georg Eck from SQUIDDS. Georg’s team has developed tools and a workflow for the most advanced mobile delivery system I have ever seen, but I will have to get to that later. The Phoenix Convention Center is just a fun place to be. It looks modern, bright, and new. Walking in just got my blood pumping and made me glad I came.

I gave my first presentation at 9:45. It was titled “How to Get What You Want, When You Need It.” I have been on the presentation circuit for a while, and I have seen some fantastic presentations. We all talk about building the importance of documentation and how we can improve workflows, systems, and content to increase value. It had dawned on me that we really have not spent a lot of time teaching technical communicators how to pitch these fantastic ideas so they can get upper management approval, or as I like to call it, “buy in.” So I went through a five-step process on how to position those ideas to give the best opportunity for buy in. Before you ask, no there are no slides for that presentation. One of the skills you need to pitch your ideas is that of listening. You also have to be the one to start the conversation, so for my presentation, I told the audience they would not have any slides and would have to practice their listening skills while we were going through the presentation. I also stated, “Without any references, you are going to have to ask questions in the presentation. Let’s get you talking, because this is a conversation you are going to have to start.” I think it went well.
My second presentation was with Bernard Aschwanden from Publishing Smarter. We talked about having a revenue-generating mindset when developing content. Bernard has been in the business for a while, and as a consultant has helped a lot of companies look at their content with that mindset. The two of us on stage offered a lot of useful information, and a lot of entertainment. I really like presenting with Bernard; we have similar styles, and even though we get detoured, the trip is well worth it.

Monday night was karaoke night. That is pretty much all I remember about Monday night, and I have been told all pictures have been destroyed. This is just one of those reasons why it benefits people to actually attend STC.

Booth pic   Tuesday started off with as much energy as Monday. That is one of my favorite things about STC Summit. Everyone is excited to be there. There were a lot of first timers, and tons of them came by the booth to see Jack and Lauren. We are launching a new product this year, CloudDrafts, and we were giving sneak previews at the booth—another benefit to attending in person. CloudDrafts is a collaborative management system. We understand there are a lot of collaborative tools out there, but none of them are really designed for technical communication workflows or have the management features needed to run projects with a team.

The next presentation we attended was Jack Molisani’s “Monetizing Your Content.” Jack presentationGood, good presentation with some charts that will blow your mind. If you didn’t go, I would recommend getting on the STC website and getting a pass for those presentations:

The last conference presentation for me was with Georg Eck, our German Channel Partner. Georg was presenting his case study with Bihler. The case study solved a multi-device publishing problem Bihler was having. Bihler makes these huge stamping machines. They range anywhere from 500 to 2 mil Euros. Georg PresentationOn all of these machines is a touch screen used to control and adjust the machine itself. It is also used to display the help manuals when requested. Like my friend Kent, the technicians that were working on these machines did not find it convenient to switch back and forth from a control panel and PDF on the same display. It was actually very unproductive. Georg and his team came up with a workflow that could deliver the manuals to a mobile device that the technicians carry with them—any device the technician prefers. All the technician has to do is walk up to the machine that needs service. On the machine are individual QR codes. The technician scans the QR code with his/her mobile device, and the correct manual for service loads. Bihler loved the results. They showed the workflow off at a conference, and they increased new sales by 2%. Next year, they are outfitting their entire sales team with iPads so they can show the workflow in their demos. What a way to end a conference, with a case study that showed just how important and revenue centric documentation can be. I didn’t think it could get any better, but I had forgotten about the awards show that night.
The last night of the conference always includes the awards show. Deserving recipients collect awards for achievements they earned throughout the year. The Society of Technical Communication recognizes exemplary performance on the national as well as the local level. It is a well-deserved banquet, and yes everyone cuts loose and has some fun. Here is a quick video: 2014 STC Summit Awards
It was an awesome Summit, and again, I am glad we were there as presenters, exhibitors, and attendees. If you have any questions or want to know more about where we are going next, just email me at

WebWorks at CMS/DITA North America

Posted on: May 9th, 2014

DITA North America this year was held in the sunny city of Seattle. Now I know that sounds a little funny at first, especially if you are familiar with Seattle, but the weather was fantastic. I had been to Seattle once before to visit Boeing. If you have never been, you can see when first arriving that Seattle is a true industrial harbor.

Big Orange Giraffes thirsty for work

Warehouses and cranes edge up right to the water line just thirsty for work. Every time I see the cranes for moving goods on and off the ships, they remind me of large metal orange giraffes—moving slowly but gracefully, never stopping until the job is done. That view with the mountains in the backdrop just really makes Seattle one of the most unique places to fly in to.

Another thing that made DITA North America special for me this year was having Bernard Aschwanden in the WebWorks booth. I think the message is finally getting out that if you use the Open Tool Kit to generate output, you need to be looking at ePublisher. That generated a lot of traffic to the booth, and even though we are the experts when it comes to generating output from DITA, Bernard is a guru when it comes to transitioning to DITA or improving your current DITA process. I thought it would be good for attendees to have someone to talk to about their situation and offer help when needed. It was a huge hit for the attendees, although Bernard and I almost didn’t make it to the conference.

Bernard’s flight was delayed, so I called the hotel to let them know we were checking in a little late. Suzanne from Vasont Systems, a good friend and awesome partner with WebWorks, was kind enough to wait with me in the airport. I was telling Suzanne that every phone call I’d had with The Westin about our reservations had seemed a little odd, starting when I called back in March to book our rooms. She said, “Give me an example.” I told her we asked for a suite with two king beds, and they replied that they could put the request in the notes, but they couldn’t guarantee it so far out. I thought that was a little odd since we were only a month away. When I called from the airport, I asked about the room, and they had the same non-committal attitude. I was a little concerned.

Bernard finally hit Tecoma International, and we headed to The Westin. Upon our arrival, they could not find our reservation. I was ready, because of my sense of impending doom, and I threw down our confirmation number. Type, Type, Type on the keyboard and AHA! He found us. Unfortunately, the reservation was made for April 27th of 2015. I just said no. The front desk attendant looked at me with a blank face, not understanding. He was still smiling, but the word “no” seemed out of place to him, as though he were not sure how to interpret my use of it.

I then said, “Who calls in a hotel reservation and gives the year? You say, I would like to make a reservation for April the 27th, or May the 21st, but never Tuesday, March 22nd of 2024. It just doesn’t make any sense.” What did make sense to me finally were all the previous conversations: “We can’t guarantee that, sir, this far in advance.” Never did it dawn on me that they assumed we were making a reservation for next year. After presenting my argument, the front desk agreed, and this is where customer service and customer experience has made me a loyal Westin traveler. They hooked us up with the best possible room.

Panoramic view of Westin room 3650
Panoramic view of Westin room 3650

The view overlooked the harbor I love, and Bernard and I could not believe our favor.

View from my room at the Westin looking over the Seattle Harbor

I often say that content can be the most pivotal asset to a company’s continued success. The informed consumer demands information before they make a purchase. The reason is they understand the benefits of being informed. Companies understand that retaining customers is what generates revenue. Let me put those fragmented thoughts together. Upsets come from two things: miscommunications, or expectations that were not realized. Both are what caused my upset at the front desk.

At that point, the staff had to exceed my expectations to deliver a positive customer experience. They don’t always have the ability to do that. If that suite had not been available, or if a room were not available, then I would have left and never returned. As a business, you don’t want to have to scramble at that moment to “fix” things. Informed consumers want to make sure they do not experience an upset, so they do their research before making a purchase. They want to look at content and have a full understanding of what is available and how solutions will be able to deliver to their needs. If they do not get the information, they will not even consider the solution for purchase. This has increased the value of documentation, good documentation, and increased the importance of access before the purchase. Every technical communicator should be aware of this and build strategies around it.

On to the conference. We did an unofficial survey of the presentations. Basically, we went into the rooms and counted the number of attendees. The big winner happened on the first day: An Overview of DITA 1.3, by Kristen James Eberlein.

Overview of DITA 1.3 won the day.
Overview of DITA 1.3 won the day.

It had by far the largest attendance, and a really good presentation by Kris showing the new items in the DITA 1.3 standard. You can find the bullet points and short description of the presentation here:

One thing to keep in mind: JoAnn Hakos has been running this conference for a while. She has been involved with the DITA movement from the beginning. This conference has a lot of high-level presentations. There are some really smart people out there talking about DITA and where it should go as a standard. If you are new to the idea of DITA, you can catch yourself up here: This is one of the groups that keep tabs on the standard, and you can get updates from the OASIS site.   Now if you do a search on DITA, do not get confused if your search results come up with an attractive woman who looks a little like this:

American burlesque dancer, NOT Darwin Information Typing Architecture
American burlesque dancer, NOT Darwin Information Typing Architecture

This is actually Dita Vonteese, who is an American burlesque dancer, model, costume designer, entrepreneur, and just about anything else you can imagine. She is also more famous than Darwin Information Typing Architecture, and due to the nature of her profession, some photos are NSFW. So be careful when doing your research. She is a nice lady, and I actually met her at DITA Europe.

Sitting next to Dita Vonteese at DITA Europe (not really her)
Sitting next to Dita Vonteese at DITA Europe (not really her)

If you are wondering about the beard, it was Movember.

Ok, where was I? Yes, so if you are looking to get up to speed on DITA, follow some of those links and be cautious when searching. There are a lot of benefits to DITA, and it deserves a look. I think the biggest obstacle for people is knowing where to start. You don’t have to figure it out on your own. Conferences like DITA North America and organizations like The Center for Information-Development Management are great places to gather some information. Consultants like Bernard Aschwanden over at Publishing Smarter can actually come in and help you get started, or refine your process. WebWorks can provide the systems you need to implement the content strategies you decide are best for your environment. ePublisher is by far the best tool to convert DITA source into value output for your audience. CloudDrafts is a collaboration management system that helps you control the chaos of team projects and still allows you to pick the tools that best fit your needs. If you want more information on our systems or any of these resources, just contact us.

– Christopher

A few spots left in training.

Posted on: March 6th, 2014

Tomorrow I am doing ePublisher 101 again, and while the registration ends 2 days, you can still sign up by contacting Jack Newman about purchasing this. This training is ideal for people just getting into ePublisher, but also for experienced users who don’t really understand why you should use ePublsher Express, as well as other questions such as: Why the heck do you need the Reports? Why is there a .base folder in my Stationery directory? Who is the best audience for Stationery? Come find out tomorrow! The training comes with a manual and exercises, but is also informal enough to allow for questions, if you have any. Hope to see you there!

Can’t make it tomorrow? You can still sign up through our Eventbrite page to register for the session on the 31st

I am doing ePublisher 101 training this Friday!

Posted on: February 3rd, 2014

I will be taking over the training for the introductory ePublisher classes. You can find out  more information here:

This course is ideal for those who are just starting out with ePublisher and want to get into the ins and outs of using the Designer interface. I will go over our workflow as well as reasons to use Express and Stationery. Registration is limited to 15 participants so be sure to sign up before the class gets filled!  Hope to “see” you Friday. 🙂


ePublisher for Newbies – Adding Company Information

Posted on: November 19th, 2013

One of the easiest things in ePublisher to modify is the company information. In fact, you can do it with just four steps in Reverb:

  1. Go to the the Reverb target that you have created and then go to Target -> Target Settings
  2. Expand the Company Information pane and then click the in the Value column to add the values* you want
  3. Once you are satisfied with the information, click OK to go back to the ePublisher UI
  4. Click the three gears to generate the output and then you will see the changes

If you are working with WebWorks Help 5.0 for example, and you want to specify further the top or bottom alignment, we can do this by using the Style Designer’s Page Styles

  1. Navigate to the Style Designer by clicking the icon or using the Menu bar and then navigate to the Page Styles in the middle column
  2. Click on the Default in the list and then click on the Options Pane toward the right
  3. Let’s choose a Top/Right alignment, so select Enabled for Company info displayed at top and Right for Company info top alignment for the options
  4. Click the triple gears to generate all and notice then notice changes from clicking the output Output Explorer**

There you go, easy as pie. Please comment if there are any specific topics you would like to be simplified in the Newbies series.

*If you want to add a logo, you will need to have it placed in the Files directory. Go to View -> User Files to have it placed in the Windows Explorer so it can be easily accessed by our generation process

**You may have it already configured to view the output automatically, and that is cool, too!

ePublisher Tips and Tricks – Reverb URL Search

Posted on: October 23rd, 2013

I am taking a break from my Newbies series this week to present a cool feature of which you may or may not be aware. Drumroll please: using the URL bar to search Reverb. It is simple, you type in your URL, in this case, I am going to to use our own help to do this, and we are going to search for the term “othermeta” for our DITA friends:

To search this term, you can type in the following:

When you hit return, it will bring up the Google search results. (If you are using the Client-side search or IIS, it will show those results). For testing on your own help that you have generated, please keep in mind that this will need to be deployed to a web server or using IIS to work. If you do not have your http://localhost yet set up, you can actually use our “View Output” button to display a preview in your browser that will let you view the URL:


and from there you can use the #search/yoursearch term feature as addressed above to search the help in this manner. Let me know in the comments what your experiences using this functionality have been.

ePublisher for Newbies – Setting TOC levels

Posted on: October 14th, 2013

Part of any great help system is a Table of Contents (TOC) to help the user navigate through the topics. In this exercise we are going to use the project that we created from the last lesson, but add some navigability to the Reverb output by adding levels to our output. Let’s begin!

1.  Open up the WEP project that you previously created by using the Windows Explorer when you go to File -> Open, or by using the Recent Projects panel in the Start Page

2. Click on the first FM file again, right click and then click Display Preview

3. Click on the very first heading in the preview window and then the Style Designer will appear in the bottom as shown:Table_of_contents_level4. You will see that the level is automatically set to Auto-TOC* but for the purposes of this demonstration we are setting the Table of Contents level to 1

5. Notice again that when when change something in the Options pane, that this also makes the paragraph style bold to indicate that a change has been made

6. Repeat the steps to give Heading 1 a level of 2 and Heading 2 a level of 3

7. Save the project and click the generate all 3 gears located on the toolbar

8. Now your output should look something like this:


9. It looks good except that because this is a web output we don’t really need to have the chapter numbering. Never fear, ePublisher has a way to fix that as well.

10. Going back to the Options panel for each of the Paragraph Styles in the Style Designer locate the Keep paragraph numbering and the Keep paragraph numbering in TOC dropdowns


11. We are going to set both of those to Disabled and we are going to repeat this for all 3 paragraph styles we modified

12. Save and generate and now the output should look like this:


As you work more with your documents, you will need to do the Display preview less as you will already know what you have set in the documents, and then you can construct your Designer projects and then base the stationery on that.  Following lessons will include different aspects of generating online help that will be useful for you in getting all that you can out of ePublisher.  Feel free to make suggestions via the comments on anything as a new user that would be helpful to learn and I will take them into consideration in creating the next tutorial. Please note that advanced customization topics such as XSL or Javascript will be best handled through the Study Hall sessions. We also have introductory topics with our Show Me sessions.

*If you are wanting more in-depth coverage of what the Auto-TOC entails, please refer to the documentation link or join one of our training sessions

ePublisher for Newbies – Starting from Scratch

Posted on: October 3rd, 2013

Our documentation provides a lot of good information for those of you who have been working with ePublisher and want to get specific information about a topic, but admittedly it can be a bit overwhelming, so I thought I would try to distill this information for a quick-start guide in using ePublisher. By no means is this a comprehensive guide, for that we offer training.

Lesson 1 – Creating and Modifying a Designer Project

1. Go to File -> New. This will bring up the following window:


2. You can chose whatever name you want for the Project and the Target (covered more in depth by training). This window also lets you choose what kind of Format you want to use, for the purposes of this demonstration, we are going to use WebWorks Reverb (which, by the way is the output that our documentation uses). Click Next

3. Click Add put source files for this document. For the purposes of this demonstration, we are going to use FrameMaker:


3. In the next window, we are going to navigate to the following directory:


C:Users[yourusername]DocumentsePublisher Express ProjectsSourceAdobe Framemaker


4. We are going to add the book file located in this folder. Click the Open button to add this file, and then you are going to click the Finish button on the next screen.


5. Now you will see something like this in the Document Manager:


6. With the first document selected, as you see in the above image,  Go to Project -> Display Preview and you will select the “Heading_1” style by clicking “About the Sample Exploring ePublisher Source Documents (FrameMaker)” paragraph style. Again more in depth coverage of this is done in training:


7. We are going to change the color of this heading by going to Text -> Color in the Style Designer pictured below Notice that now the Text heading is bolded, this indicates that we have made a change to something in the Style Designer:


8. You can actually see the changes by clicking the green Refresh Preview button on the top corner:

Refresh Preview

9. For the purposes of this small demonstration, we are going to generate with just heading 1’s changed, Go to the 3 blue gears in the toolbar to do a generation:

Generate All

10. Once you click this, you will see logs that will indicate that you are generating and then you may get a message like this, go ahead and click Yes, and you can also select this message not to come up again as pictured below


11. Once you click yes you should be able to view the output and it will look like this when you click the right navigation button on the top.


12. Click File -> Save to save your project for the next lesson

So, this was a  very basic example of output that is possible from our sample source files. Right now we have navigation in our Reverb output, but we do not have a table of contents, breadcrumbs or any other bells and whistles that Reverb offers. In the following lessons, I will go over how to get cool features and settings in the output, but for now I hope this gives you a good starting point.