Pushing further from the "app - website - training program" discussion in the previous blog, I would like to suggest a template that could be used across a large part of the project. This template would load into the website, but include an export pdf or jpg that would go into the app.
For many years i have utilised a strategy tool to facilitate the maintenance of focus in situations guaranteed to elevate blood pressure and challenge distractibility. It is termed a "Waiting Loop", and comes unashamedly from computer programming ("if-go to" loops). For example, national anthem ceremonies pre-games, waiting for a playing partner to hit his shot into the green in tournament play, or between deliveries as the quick is marching back to the top of their mark out near the car park.
The concept is to get the individual to loop through a sequence of shifting focus points / activities that combine cognitive, physical and/or psychophysiological components into a personalised technique / strategy / "system" (my preferred term) that is designed for their specific application need.
Typically these kinds of strategies come with a back story, such as the reason for developing them in the first place. This background / back story could include some explanation of the research material that had been checked by your team members. Clearly the nature of this input will depend on the topic.
Before detailing more of the template, let's put the topic in the larger context of the CF2 Project. I would put this system under the Composure Module, and specifically the CF2 subcomponents of 1.1, 1.2, 1.3, 2.1, 2.3, 2.5, and it could be argued 4.1 and 5.3.
You will see the references below to Title, Module Category & CF2 Category. Consider these "for office use only" as opposed to publication on the actual web page - save for the working title which may be modified in the context of our final "look and feel" discussions. Don't get too precious or possessive of titles at this time - unless they are tied to specific research lines or protocols. It is an interesting thought to consider a major selection criteria for what goes through to the app in our first iteration is the number of CF2 Categories an item covers. Clearly there will be other considerations.
This template example adds a space for a graphic or some kind of diagram. In a sample layout page, the diagram is balanced by a text box that would contain the back story / introduction to the topic.
Remember that webpages are completely free form, so treat this layout as recommended for this topic. Think powerpoint layout flexibility in shaping up these pages. Beyond a colouring protocol and font family i would not envisage trying to squeeze every topic into the same page format. You will find that the wix system greatly facilitates these fundamental design issues.
I envisage this as a scrolling page - you are seeing it split in 2 above.
The green box may take more space in reality, but once again the webpage format doesn't limit length or word count. I would think the writing principles would focus on brevity and plain english as far as possible. Remember that we will be developing a glossary section that will aid in adding definitions in these sections. This will be done by adding a hyper-link on the "technical word" that will take the reader to the glossary and the word in question. It is a very simple process to add these links.
The blue box adds the opportunity to cross reference other sections of the modules, sites from our partners and/or sources that we will identify in a similar section to the glossary. There is also the possibility in some applications for this to be done with the psychologist in a one-on-one meeting. We might as well build it in from the beginning.
It would also be possible to add another section here providing some of the athlete scenario examples we have begun to collect. Alternately, we could have a glossary style page that presents some athlete scenarios that we could hyperlink to at this stage to aid in making the issue more "real world".
The aim of our work is to encourage interactivity, homework, or full on training program involvement and adherence.
The yellow box is where this kind of thing would be set up, including any pdf file downloads relevant to the exercise. Here I am envisaging a "build your own loop" synthesiser done by clicking and dragging icons from a selection list into a space where a screen shot can be taken and exported to go into the athlete's Go Bag collection.
The computer bits behind what I just said can be quite simply "cludged" (computer term for worked around without spending $5m in programmer time). I will need to discuss some of these "how's" with you individually as you think about ways you may like to build interactivity in. When I lose the hospital restrictions i will bring you together for a workshop on developing assessment systems for drill work like this.
This topic was selected to best demonstrate a "template approach" to directing your research, creativity and writing. While there is a place for overall statement pages at the start of each module section, there is very much a place for "how tos" like this to add real flesh to the bones of the CF2 diagram. Just as completing a template base abstract submission for a conference comes complete with challenges such as "i don't really have a traditional methodology section". So here we have a simple rule - "fake it or change the heading".
I trust this will help the creative wheels to keep turning.
JC