When at smallest breakpoints and header is presented at bottom of the page it can overlay content. The styles/structure need to be tweaked to avoid this.

** noticed on evolving detail results page with simple output

When using small window sizes where the menu moves to the bottom we need to alter or suppress the handling of the footer. For not it could be suppressed but eventually there will be navigation there that should most likely move to a hamburger style menu.

The footer currently stays where it was on the initial render when the page is scrolled.

To Reproduce

1. navigate to service detail locally

Expected behavior
when scrolling the page the footer should remain at the bottom 😄

Screenshots

Additional context
Occurs in both Chrome and Safari in testing.

Currently there is no way as a user of the system, without access to the server logs, to view activity in the system. I would like to eventually see the ability to "watch" a specific Service exposed. This could be implemented as a WebSocket subscriber or similar technology but will need the cooperation of the Core.

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

When first accessing the system I would like to see a list of the test-cases I've most-recently viewed and be able to navigate to the detail pages for them. Seeing a full list of anything I may have created over time is less than ideal.

To implement in an ideal fashion this would require core support but could be implemented as a simple list where each item is retrieved independently for display. With a tweak to the core the data could be retrieved in one query.

This task will be used for the basic testing of the interaction between mockiato-ux and the core implementation. It will include a few simple functions and screens to proof the interaction between the UX and the core before we start building any polished pages.

Currently there is no way to see or navigate directly to a request-response pair in the Browse function. Ideally a synopsis of the named pairs will be available, such as count, which could be expanded into a full list providing navigation into the detail screen with that pair selected for viewing.

• Enable CORS -- Optum/mockiato#150 (comment)
• Add rr-pair name property -- Optum/mockiato#136 (comment)

Current implementation on small mobile devices is missing the Mock menu. Need to adjust the strategy to ensure all relevant navigation is present.

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

UX needs and authentication layer which will be capable of being extended to varies authentication stores including external providers such as GitHub.