Achieving this required the use of an A/B Activity in Adobe Target for each variation of the concept to determine which concept had the best result in meeting the conversion goal and would ultimately be selected for component development as a permanent library asset. Utilized HTML, CSS, Javascript and JQuery to develop three design concepts, supplied by marketing through Figma collaboration files, into fully functional and responsive prototypes, that used a combination of new logic functionality, responsive styling, and existing libraries with dynamic features to handle analytics and pricing.

Once A/B testing was done and the winning concept was determined, I started the component development planning process. The requirement for this was to create a component structure that could be edited by both authors and developers, at the same time if necessary, to keep up with the rapid demand for changes as the tax season progressed. To accomplish this I created a baseline AEM component structure, which used a Sightly custom HTML template to house the functional logic, responsive styling and analytics, which are the areas of the component intended to be editable by developers. Between the custom HTML field calls I placed experience fragment calls to product assets housed on the AEM cloud development, staging and production environments. This allows authors to edit live content on the page through the experience fragments, without impacting any of the functionality or styling features of the component.

Developed for an A/B Activity in Adobe Target to determine if the concept met the conversion goal and would be selected for component development as a permanent library asset. Used HTML, CSS and Javascript to develop the concept, supplied by marketing through Figma collaboration files, into fully functional and responsive prototype, that used a combination of new logic functionality, responsive styling, and existing libraries with dynamic features to handle analytics and pricing.

Partnered with Business Analyst's who determined the assessment ranges based on predetermined variables, which were given a score. A low, moderate or significant result is based on this score, which determines the tools feedback to the user.

I used HTML and CSS to develop the responsive layout supplied by marketing, used Javascript to create the interface navigation flow.

A combination of Javascript and Jquery was utilized to create the logic to calculate the users total score based on their selections and used the ranges given by the staticians as a guide to determine the result screen, giving the user their review assesment.

I collaborated with a senior developer to create a contact form capable of collecting, validating and submitting the form data to a database.

Partnered with marketing staticians who used data from a TIS survey to create a 5 variable model to predict tax identity theft risk. From that TIS model a CHAID decision tree algorithm determined the low, medium and high risk factors which were put into classifications and scoring range scenerios. Determining the tools feedback to the user is based on these scoring range scenerios.

I used HTML and CSS to develop the responsive layout supplied by marketing, used Javascript to create the interface navigation flow.

A combination of Javascript and Jquery was utilized to create the conditional logic to classify the appropriate scenerio with the relative score, based on the users selections, to determine the result screen the user would be given.

I collaborated with a senior developer to create a contact form capable of collecting, validating and submitting the form data to a database.

Developed with the OpenText CMS approach. The layout was developed in HTML, CSS and Javascript, then separated into pods which were dynamically loaded into the H&R Block Velocity housing template system, which contained all global assets utilized by the site. The CSS files were minified with a Node script and synced with the repo through SVN.