Publishing to Axure Share is a handy way to share the HTML output of your Axure RP prototypes with your teammates and stakeholders. You click the “Share” button in Axure RP, hit “Publish”, and get back a shareable link to the prototype. Bing, bang, boom!

But did you know that you can publish the same RP file to multiple Axure Share project IDs? This can be helpful when you need to maintain different versions of a prototype for different audiences, such as your design team, your developers, and your stakeholders. For example:

  • If you’re working on a team project, its HTML output on Axure Share is updated every time you check in. If you don’t want your stakeholders to see any unfinished pages or edits-in-progress, you can publish a standalone version of the prototype to a separate Axure Share ID and only include the prototype’s finished pages.
  • You can publish your prototype to a new Axure Share ID after each sprint in order to keep a live version history of corresponding changes for development, testing, and future reference.

Creating Multiple Axure Share IDs

Screenshot of the Axure RP UI's "Publish to Axure Share" dialog with the "Create a new project" option selected

Creating multiple Axure Share IDs for a prototype is as easy as re-publishing the RP file from Axure RP using the “Create a new project” option:

  1. Open your prototype in Axure RP and click the “Share” icon in the top toolbar.
  2. At the top of the Publish to Axure Share dialog, select the HTML generator settings you want Axure Share to use. These settings include options like which pages get published, and we’ll go over them in the next section.
  3. In the “Name” field, enter the project’s name along with something to indicate which audience you’re publishing for. For example, “Mobile App Redesign (Stakeholder Copy)”.
  4. Add a password, if you’d like, and choose which Axure Share workspace to publish the project in.

    Tip: It can be helpful to set up different workspaces for your various projects and/or clients. You can learn more about Axure Share workspaces in our Axure Share Basics reference guide.
  5. Click “Publish” to publish the project. When the upload is complete, make a note of the project ID and which audience it’s associated with.

When you’re ready to update a particular audience’s version of the prototype, just publish to the associated project ID. You can do that by manually entering the ID under “Update and existing project”, or you can search for the project by its name in the ellipsis menu to the right.

Customizing the HTML Output

Screenshot of Axure RP's "Generator Configurations" dialog

To customize each published version of the prototype, you’ll use Axure RP’s HTML generator settings. If you’ll be publishing to each of these projects regularly, I would suggest saving a separate set of generator settings for each audience in the RP file. To do this:

  1. In Axure RP, go to “Publish > More Generators and Configurations”.
  2. Click the “Add” dropdown at the top-left of the dialog and select “HTML”.
  3. Name the new generator in the table below.

    Tip: Try naming the generator after the target audience and the Axure Share ID for that audience’s version of the prototype. For example, “Stakeholder Copy ABC123”. This makes it easier to find the correct generator in the Publish to Axure Share dialog (Step 2 in the previous section).
  4. Double-click the generator’s name to configure its settings.

Now that you’ve got the HTML generator dialog open, it’s time to start customizing.

Pages – On the Pages tab of the HTML generator settings, you can decide which prototype pages get published and which don’t. For example, you may decide to only publish finished pages for your customers and other external stakeholders.

Page and Widget Notes – On these tabs, you can decide which of your note fields in Axure RP get published and included in the prototype sidebar. For example, if you have note fields with information intended specifically for your developers, you may want to uncheck these when publishing for your customers.

The Console – The console tab of the prototype sidebar is a tool that’s primarily useful for Axure RP users building prototype interactions. As such, you may want to turn it off when publishing for other audiences. You can do this on the Interactions tab.

Using Axure Share’s Project Settings

Once a project is published, you can also take advantage of Axure Share’s project settings to further customize each version of your prototype.

DiscussionsAxure Share discussions allow your team to comment on each page of the prototype, including onscreen comments. By maintaining separate projects for each audience, you’re also ensuring that each audience sees only the discussions relevant to them.

PluginsAxure Share plugins allow you to include different HTML, CSS, and JavaScript snippets for each version of the prototype. For example, you could include a heatmap plugin on a version of the project that you use for user testing.

– – –

Did you find this workflow useful? Let us know in the form below. We’d also love to hear how you and your team currently handle audience-targeted output for your prototypes.

Fill out my online form.

Share this: