When setting up and/or editing an activity, it is possible to move the cursor about inside the "Summary" filed but not in the "Meeting Place and Time" and "Required Equipment" fields. As a result, it is very frustrating to enter or correct information in the online activity form.

In other words, when pressing the ⬅️➡️⬆️or ⬇️ keys on my keyboard, the cursor will move accordingly inside the text field "Summary" as one would expect with a normal word processing function.

But in the "Meeting Place and Time" and "Required Equipment" fields, pressing these same ⬅️➡️⬆️or ⬇️ keyboard cursor control keys causes the cursor to immediatly leave the field and fly to the bottom of the web form.

It seems that some attribute of the "Summary" field allows for normal cursor operation within the field. That same attribute seems to be missing from the "Meeting Place and Time" and "Required Equipment" fields, such that a cursor key press causes the cursor to fly to the bottom of the web form.

The Branch landing page presents a newsfeed (blog) over which the branch has little control and does not make a very useful "home' or "welcoming" page for branch.

Ideally,branches should be able to design/manage landing pages to their liking, but that's another story.

Short of that, I request a better way to prioritize the blogs that appear on that page. As it stands, the page intermixes blogs submitted by the branch with blogs submitted by staff and others. The problem is that the volume of blogs originating from others overwhelms those originating from the branch, causing them to scroll off the page too quickly. The result is that most of the time the preponderance of blog entries have little branch relevance, while the ones that the Branch wants there have scrolled off.

A couple of ideas come to mind. First, procedurally, staff could stop using the branch tags except for unusually important cases. The blogs so-affected do appear on the Mountaineers home page, after all (and it's sort of branch-diminishing to also usurp the branch blog with that stuff).

A more sophisticated approach would be to programmatically give branch-originated blogs priority, at least until their expiration dates.

Some benefits to using skill badges as prerequisites for activities include:
--Lessening bureaucracy and improving course administration. For example, Basic Climbing Admins would be able to track student progress online, rather than manually in booklets, and it can ensure that Basic Climbing students cannot register for glacier climbs until they've successfully completed glacier skills training.
--Allowing course leaders to specify leader prerequisites for skills conditioners, allowing people to grow into leadership, broadening the leadership funnel.
--Encouraging leaders who are reluctant to take students they don’t know on climbs to open them up, because they will be able to see more clearly what types of experiences students have.
--Making tracking and program cross-pollination easier.
--Increasing entry points to our organization.
--Helping leaders have increased confidence in the skills of their participants.