Welcome to my OP2 Skillflex on the Transformative Path - emergence and the ripple effect. The Core report (1.0-1.4) of this document is a broad perspective of the overall project. The outline of every page is found on 1.0 Specification and abstract, the header of each page also outlines its contents. Navigate through the pages either by the tabs at the top of the page, or the navigation menu at the bottom.

The core report has citations that are actively linked to bring you to the bottom of the page where the source is identified with its external link. There are other links in the text which are html anchor links. The text of these anchor links will tell you what it's linked to and where it goes. After visiting these links (which brings you to another page within this report) press the back button to continue where you left off.

These links give greater detail on the report but are not essential to understand the project. This report has a lot of content. I suggest you click on the items that spark the most interest and come back to others as your time and curiosity allows. All external links will open in a new window.

This report is comprised of two main layers. The first layer (micro-projects) is skill-flexing, and the second is an exploration of my design process (which I call emergent-design flow) and their impacts (the ripple effect). I made navigating both of these layers very easy, by incorporating the html anchor links. Remember when you are finished exploring one of these anchor links, hit the back button to continue where you left off.

Referring back to my Life and Career Review, I continue to follow Charles advice to balance the media I am using in my core report by using a supporting evidence page. I have expanded my supporting evidence capacity through my commentary and journal excerpts.

I waited until working on this report to go back and address my advisors critiques of my LIPD. Having had the fresh experience of addressing the issues in my LIPD while working on my OP2, helped me to apply the points she made, for this report.

Most of the critiques are based on lack of context and connectivity. This was a great project to challenge myself on this front. It was challenging in this report because of its layered content. In an attempt to make this report more navigable I embedded html anchor-links from text in the core report (discussed above) to their corresponding element, else where in the report (supporting evidence and commentary).

On the subject of connectivity I focused on bridging topics and connecting dots. On the topics of context, I articulate from patterns to detail for all the individual processes of this project. I posted a document of the main points made in my LIPD review with text telling what I did to address each issue, see 2.1 Pathway reflection.

I edited this report after my peer review see 2.4 Participation records Right column.

I reduced my word count from over 6000 to 4300 on my initial edit. After my peer reviewer said I went way over, I edited more and moved several things into commentary and supporting evidence. This reduced my core report down to 3222, including the page outline in Specification and abstract it is 3662.

Here is a journal entry reflecting on my difficulty to conform my learning pathway to the OP format, see 2.2 Thinking in use.

The Page Layout is 2 columns the right more narrow,  I created the text on Mac TextEdit  saved as a plain text uploaded it to Mahara for resilient documentation.