Hey Aaron. Using core components as a model is a smart way of working.

I noticed an oversight in your example.json. It currently references the Text component: "_component": "text". You'll want to change this to the name of your component: "_component": "pageJumper".

I'd like to call to your attention this line in the pageJumper.hbs:
<divclass="text-inner component-inner"role="region"aria-label="{{_globals._components._text.ariaRegion}}"> It still references the Text component in two places. Because you have conceived this as a Text component with a button, the appearance and behavior of the component is probably consistent with your expectations. But the class "text-inner" is typically formed by concatenating the component name with "-inner", yielding a class of "pageJumper-inner". There are a number of class names that are formed this way. Keep this in mind when independent CSS styling is warranted. Likewise, _text.ariaRegion can become _pageJumper.ariaRegion , but in practice you'll have to add a new section to the _globals in course.json. It might look something like this:
"_pageJumper": {
    "ariaRegion": "This component displays text with an accompanying button. Use the button to navigate to a section of content."
},

The content of the ariaRegion will be specific to the functionality of your component; some components might not even require it. But just wanted to be sure that you (and others reading this) make the connection between the ariaRegions found in the hbs and the _globals section. It's important for accessibility.

Aaron, if this is your first component, good job!. Hope this is the first of many. 
And hope this was helpful.
- Chuck

hi all.

the component has been updated to make it easy to position the button. just choose left (default), center, or right with the dropdown in the properties. the readme also shows how to position the instruction text.

cheers!

Aaron, this is great. I have a noob question. I'm more an I.D. than coder. How do I find the I.D. of an element?

Thanks

Chris