ObsidianSecondBrain

Index - Submit Science

Thu, 26 Mar 2026 18:02:44 GMT

Each year, the American College of Cardiology brings together the world's leading cardiovascular professionals to share groundbreaking scientific research at the ACC Annual Scientific Session. Abstracts, cases and late-breaking clinical trial research are a critical component of the scientific program and are at the heart of this global exchange.At ACC.26, you'll have the chance to connect with peers from around the world to engage in dynamic discussions on groundbreaking research — late-breaking clinical trials, featured clinical research, abstracts and clinical cases — shaping the future of cardiovascular medicine.Monday, July 14, 2025 – Monday, Aug. 25, 2025 at 1 p.m. ETTuesday, Aug. 19, 2025 – Thursday, Oct. 2, 2025 at 1 p.m. ETTuesday, Oct. 7, 2025 – Thursday, Nov. 20, 2025 at 1 p.m. ETAll submitting LBCT authors must have updated disclosures before submitting research. Visit ACC's Disclosure Website to update your disclosures.ACC.26 is where the biggest discoveries make their debut. Be among the first to hear the data that will define tomorrow's practice, offering new insights into emerging therapies and long-term outcomes from established treatments.The submission process for ACC.26 is currently closed.
Index - Submit Science
Late-Breaking Clinical Trials

_Index - Registration

Thu, 26 Mar 2026 18:01:23 GMT

Key Dates & DeadlinesExclusive Member Registration Wednesday, Oct. 1 – Tuesday, Oct. 14, 2025General Early Bird Registration Wednesday, Oct. 15 – Wednesday, Nov. 19, 2025Advanced Registration Thursday, Nov. 20, 2025 – Thursday, Feb. 12, 2026Registration Cancellation Deadline (Registration fees are non-refundable after this date) Wednesday, Feb. 11, 2026Standard/Onsite Registration Friday, Feb. 13 – Monday, March 30, 2026Join us for ACC.26, taking place March 28 – 30, 2026, in New Orleans, where you'll connect with peers from around the world, explore the latest advances in cardiovascular medicine, and gain practical insights to improve your daily practice. Time is running out — register now to join us for ACC.26!
As you plan your travel and time away from the office, please note that pre-conference sessions will take place on Friday, March 27 from 10 a.m. – 6 p.m. CT and ACC.26 officially begins on Saturday, March 28 at 8:30 a.m. CT with the Opening Showcase and concludes on Monday, March 30 at 5:30 p.m. CT following the Closing Ceremony, Convocation & Reception. For details, view the ACC.26 Schedule At-A-Glance.Have You Paid Your Dues?ACC Members must be up to date on their 2025 dues if registering for ACC.26 before Jan. 1, 2026. Starting Jan. 1, 2026, ACC Members must be up to date on their 2026 dues. If you have not paid your dues, you will be registered in the non-member category and charged the non-member rate.
Pay your dues or contact ACC Member Care to check your membership status at membercare@acc.org or call 800-253-4636 (outside the United States, call 202-375-6000).
Group Registration & Hotels
Hotel Reservations
International Travel & Visa Information
Registration Rates
Travel Information & Attendee Services
View Full Pricing

Group Registration & Hotels

Thu, 26 Mar 2026 17:57:40 GMT

Request A Block
Book Full-Service HousingACC.26 Group Registration & Housing is open! Groups of 10 or more may be secured through group process.In addition to standard group registration & housing, the ACC offers full-service housing and concierge assistance for breakfast, transportation, special events, porterage, registration, and other services.Groups Registration and Housing Management Site Opens Wednesday, Oct. 29, 2025Early Bird Registration Deadline Wednesday, Nov. 19, 2025Advanced Registration Thursday, Nov. 20, 2025 – Thursday, Feb. 12, 2026 (Registration fees are non-refundable after Feb. 11)Group Housing Name Deadline Wednesday, Feb. 4, 2026Standard Registration Friday, Feb. 13 – Monday, March 30, 2026 --- ACC has implemented a group registration process to ensure that each person in your group is accurately registered and has full access to the ACC.26 program and conference tools, along with the ability to seamlessly claim credit and obtain a certificate of participation. Group coordinators will be required to follow the process below to register their groups. As a Group Coordinator, you will be required to set up a username and password to create your group account on the ACC.26 group site. Once you have created your group account, you will add the individuals in your block using their first name, last name and email address. As you assign a named attendee to your group block, a unique link will be created and sent to each individual in order for them to confirm their registration. Each attendee, using their unique link, will be required to confirm their registration. Once the individual has confirmed their registration, you will be able to submit payment. IMPORTANT REMINDER: ACC will charge a $200 around-the-block fee for each in-person group attendee that does not book housing within the ACC.26 hotel block. This fee will be charged to the credit card provided for registration by the tour group operator in the last two weeks of March. Additional information and instructions can be found on the Group Registration & Housing website by clicking the button above.
Questions about Group Registration & Hotels? Please contact Maritz Monday through Friday, 9 a.m. to 5 p.m. ET by phone at 864-208-2670 or by email at ACCgroups@maritz.com.Please note: Maritz is ACC's exclusive and official housing bureau for the American College of Cardiology's Annual Scientific Session in New Orleans, LA. Minimum room block size to request a group block is 10 rooms. For groups up to 100 rooms, a maximum of 50 rooms can be blocked per hotel. For groups larger than 100 rooms, a maximum of 75 rooms can be blocked per hotel; based on availability. The rooming list deadline is Wednesday, Feb. 4, 2026. Any rooms not confirmed by this date will be released into general sale. Accurate and legitimate email addresses MUST be provided for each attendee to benefit from all attendee services. All rooms in your block must have attendee names assigned no later than Wednesday, Feb. 4, 2026. After this date, if a room is cancelled, a cancellation fee of one night's room rate + tax will be applied per cancelled room. Once rooms transfer to the hotel on March 6, 2026, the hotel will charge a one-night room and tax deposit on each room reservation which will be applied to that room, unless separate billing arrangements have been made and confirmed in advance directly with the appropriate hotel(s). This fee is non-refundable if a reservation is cancelled in its entirety. IMPORTANT REMINDER: ACC will charge a $200 around-the-block fee for each in-person group registrant that does not book housing within the ACC.26 hotel block. This fee will be charged to the credit card provided for registration by the tour group operator in the last two weeks of March.
The ACC is proud to offer all-inclusive international group housing option for ACC.26. ACC International Group Housing, through an exclusive international partnership with official housing provider Maritz and ABTS Convention Services Inc., will offer priority access to preferred hotels, amenities, and locations in an all-inclusive international group package. The rooming list deadline is Wednesday, Feb. 4, 2026. Any rooms not confirmed by this date will be released into general sale. Any rooms released after Wednesday, Feb. 4, 2026 will be charged a non-refundable deposit equal to one night's room & tax. If any credit card is declined, the Hotel reserves the right to cancel the reservation.
For questions, please contact ACCgroups@maritz.com. The ACC has appointed Marben Srl (in collaboration with ABTS Convention Services Inc.), to coordinate and assist Italian pharmaceutical companies as the sole delegate in order to collect the requests and complete the mandatory procedure in compliance with the instructions given by Legislative Order No. 219 of April 24, 2006, par. 124.Contact: MARBEN Srl Via Melzi d'Eril, 20 20154, Milano – Italy T: +1-305-865-4380, ext. 155 F: +1-305-865-4382
Email: pandrade@abtscs.com

Travel Information & Attendee Services

Thu, 26 Mar 2026 17:55:41 GMT

We're looking forward to welcoming you to New Orleans! New Orleans boasts things to do with personality, adventure, and unforgettable experiences rolled into one fabulous city.Whether this is your first time in New Orleans or you're a seasoned visitor, the city's invigorating spirit is sure to inspire, captivate and motivate you to jump in and see and do so much. Discover the spontaneous joy that is the Crescent City's calling card. Visit the New Orleans site for more information on things to do and see once you are here!ACC.26 will take place at New Orleans Ernest N. Morial Convention Center, located at 900 Convention Center Blvd, New Orleans, LA 70130. ACC will provide morning and evening shuttle service for downtown hotels. Louis Armstrong New Orleans International Airport (MSY): Located in Kenner roughly 11 mi west of downtown New Orleans, is the region's main commercial gateway, featuring a modern terminal with 35 gates and nonstop service to around 60 destinations worldwide.
Amtrak: Amtrak routes are available to New Orleans anywhere from New York City to New Orleans. Learn more.
Convention Center Parking: New Orleans Ernest N. Morial Convention Center offers multiple convenient parking options for visitors, attendees and staff of on-site events located on the South end of the Convention Center across from Halls H, I and J. Reserve your parking in advance.
Complimentary shuttle bus service is provided for individuals who make hotel reservations through Maritz Global Events. For more information, download the shuttle schedule. The following hotels are within walking distance of the Convention Center and will not be serviced by shuttles: Cambria Hotel New Orleans Downtown Warehouse District Courtyard New Orleans Warehouse Arts District Embassy Suites by Hilton New Orleans Hampton Inn & Suites New Orleans-Convention Center Higgins Hotel New Orleans, Curio Collection by Hilton Hilton Garden Inn New Orleans Convention Center Hilton New Orleans Riverside Hyatt Place New Orleans/Convention Center New Orleans Marriott Warehouse Arts District Renaissance New Orleans Arts Warehouse District Hotel Riverfront Hotel New Orleans Sonesta ES Suites New Orleans Convention Center SpringHill Suites New Orleans Warehouse Arts District
If you require a special-needs shuttle, please contact ACC@maritz.com to make arrangements.Shuttle service for transportation between ACC.26 hotels and the convention center will be available for ACC.26 attendees. By utilizing the shuttle services, ACC.26 attendees assume all risks associated with their use of the shuttle services and release ACC, Kushner & Associates ("K&A"), and K&A's contractors from any liability whatsoever for any personal injury or loss, property damage, or any other losses or claims related to or arising out of the ACC.26 attendees' use of the shuttle services, and waive the right to bring any actions against ACC, K&A, and K&A's contractors.In an effort to make ACC.26 more inclusive and inviting, ACC will offer several services to support our attendees. We offer childcare throughout the meeting, a lactation room, and an Interfaith Prayer & Meditation Room.
KiddieCorp will be providing care for children ages 6 months through 12 years old in order to allow ACC.26 attendees to have a comfortable, safe and happy place for their children, co-located in New Orleans Ernest N. Morial Convention Center, while they attend sessions. Children must be registered in advance — the registration deadline is February 27, 2026, and availability is limited so please don't delay*. Learn more and register your child(ren) today!*ACC reserves the right to cancel childcare services in advance of ACC.26 based on registration.

Hotel Reservations

Thu, 26 Mar 2026 17:55:16 GMT

View Hotel Map
The ACC.26 hotel block is now closed. If you are planning to attend ACC.26 and have not secured a hotel reservation, search for hotel availability via our trusted partner aRes Travel.
Book Online or Call 1-877-300-6147 for Assistance | International Callers: 1-619-546-7263
ACC.26 will take place at New Orleans Ernest N. Morial Convention Center, located at 900 Convention Center Blvd, New Orleans, LA 70130. ACC will provide morning and evening shuttle service to and from the center to downtown hotels for individuals that book their hotel in the ACC block. Hotels that are within walking distance of the Convention Center and will not be serviced by convention shuttles. Additional information is available on the Travel Information page.

International Travel & Visa Information

Thu, 26 Mar 2026 17:55:06 GMT

For information on what to expect if you are applying for a Visa to the United States and to review the Visa Application Guidelines on the U.S. Department of State's website. Additionally, the International Visitors Office (IVO) of the National Academies has excellent resources on all visa-related issues for the National Academies, Academy members and the scientific community.
If your visa application to attend ACC.26 is delayed or denied, we want to know. If your application is still pending after forty-five (45) days and you are at risk of missing the meeting, report your case to the National Academies. Complete the questionnaire and answer the question "Purpose of Visit" by typing "ACC.26 Annual Scientific Session" to help the National Academies identify you as an ACC meeting participant.Registration Refunds Due to a Visa Denial: Visa processing may require long lead times. Please plan accordingly! We highly recommend you apply for the U.S. visa 3 – 4 months in advance. If your visa has been denied and you would like to be considered for registration refund, please make sure you have either an official denial document from the U.S. Consulate or a stamped copy of your application form, showing the date when you applied and the date your visa application has been denied.ACC provides several documents that will document your participation in the national meeting and exposition. Please note that the ACC cannot intervene with either the U.S. Embassy abroad or with the U.S. State Department on behalf of any participant.
Official Letter of Invitation: Attendees can obtain a personalized letter of invitation for ACC.26 for visa purposes after they have completed their registration for ACC.26. Registration must be fully paid and all verification documents received by Maritz Global Events. If requested, a personalized invitation letter will be sent to the email address provided. If the letter is needed in a different format, please contact ACC@maritz.com.
Registration Confirmation: Once you have registered for ACC.26 you will receive an email confirmation, which you can also bring to your visa interview. If you do not receive an email confirmation, please email ACC@maritz.com.
If you have any questions during the registration and housing process, please contact Maritz Global Events at 864-208-2670 or ACC@maritz.com, Monday through Friday, 9 a.m. to 5 p.m. ET.Consulates/Embassies
View a listing of Embassies and Consulates inside the United States.Currency Exchange
The Universal Currency Converter allows you to perform interactive foreign exchange rate conversion on the internet.

Late-Breaking Clinical Trials

Thu, 26 Mar 2026 17:48:48 GMT

Late-breaking clinical trial submissions for ACC.26 are now closed. Accepted trial presenters will have the chance to present on cardiology's main stage, where they will help shape the future of cardiovascular care by sharing their research with the global cardiovascular community. Attendees will have the opportunity to engage in dynamic discussions on groundbreaking research during seven LBCT sessions, five featured clinical research sessions and two investigative horizons sessions. Be among the first to hear the data that will define tomorrow's practice.Late-Breaking Clinical Trial submissions were accepted in the following categories: Major Study Smaller Study/Randomized Clinical Trial Multi-center Observational Study or Registry Secondary Analysis of Major Clinical Trial Other Accepted Late-Breaking Clinical Trial submissions will be presented in person during one of seven LBCT sessions in the Main Tent in New Orleans and streamed live on the ACC.26 virtual platform. No video or virtual presentation option will be available.Three LBCT sessions will be co-sponsored by the Journal of the American College of Cardiology (JACC), the Journal of the American Medical Association (JAMA) and the New England Journal of Medicine (NEJM). Each accepted submission will be considered for JACC Rapid Review and publication in JACC, JAMA and NEJM. In addition, each LBCT session will be followed by a press conference with top media outlets.Thursday, Nov. 20 at 1 p.m. ET Submission Instructions
Policies and Procedures
FAQs

View Full Pricing

Thu, 26 Mar 2026 17:45:23 GMT

Save more when you register early. Pricing windows: Early Bird: Oct. 1 – Nov. 19 Advanced: Nov. 20 – Feb. 12 Regular: Feb. 13 – Mar. 30 Join in person and choose the rate that matches your registration category. Pricing windows: Early Bird: Oct. 1 – Nov. 19 Advanced: Nov. 20 – Feb. 12 Regular: Feb. 13 – Mar. 30 Attend virtually with straightforward pricing.A streamlined option for attendees focused on the Expo.

Registration Rates

Thu, 26 Mar 2026 17:44:49 GMT

Join the global cardiovascular community March 28–30 in New Orleans — in person or from anywhere. ACC.26 offers flexible ways to participate, whether you want the most complete on-site experience, the full meeting in person, virtual access from anywhere, or time focused on the Expo floor.Register now and secure your ACC.26 experience.These member prices reflect the published physician member range for PLUS and In Person, the physician member virtual rate for ACC.26@Home, and the member Expo Only rate. PLUS and In Person both include a three-month ACC Anywhere trial, while PLUS is the only option that adds one pre-conference session on Friday, March 27.View Full Pricing by Registration CategoryACC member pricing creates the strongest savings on the two in-person options, with physician members saving $500 to $750 compared with physician nonmembers. Members also save $100 on ACC.26@Home and $200 on Expo Only.Join ACC to Unlock Member PricingThe only option that includes a pre-conference session.ACC.26 PLUS is the premium package for attendees who want more than the main meeting. It includes one pre-conference session of your choice on Friday, March 27, plus everything included with ACC.26 In Person: full on-site access, live streaming in the ACC.26 App, and a three-month free trial to ACC Anywhere.The full meeting experience in New Orleans.Attend ACC.26 on site with access to 200+ education sessions, the Expo, 4,500+ posters, the Lounge and Learn Pavilion, live app streaming, and a three-month free trial to ACC Anywhere.Join live from anywhere.ACC.26@Home gives you virtual access to 200+ streamed sessions over three days, including all seven Late-Breaking Clinical Trials, featured research, keynote presentations, guideline-focused discussions, access to 4,500+ ePosters, and a three-month free trial to ACC Anywhere.Explore innovation and connect on the show floor. Expo Only is built for attendees focused on industry exhibits, Learning Destinations, networking in Heart Park, and access to 4,500+ posters, moderated posters, and ePosters. Choose the experience that best fits your goals: PLUS, In Person, @Home, or Expo Only Register early for the best in-person rate Review changes and cancellation policies before completing your registration Choose the ACC.26 experience that matches your goals, then register early to secure your preferred option and best available pricing. [Register now] [make your plans ]

Help Center

Thu, 26 Mar 2026 17:38:58 GMT

864-208-2670 M-F, 9 a.m. – 5 p.m. ET
Email Registration Help

Home

Thu, 26 Mar 2026 17:35:40 GMT

Don't miss out — register before time runs out and join us in New Orleans. Join us for an unparalleled educational experience — explore the ACC.26 Program!
The clock is ticking and time is running out...Register now to join us for ACC.26! Select the package to fit your needs - Plus, In-Person or Virtual.
Sharpen your skills with hands-on learning in the Personalized Skills Zone at ACC.26!
Interested in Exhibiting at ACC.26? Learn more!
Continue Learning Anytime, Anywhere With ACC Anywhere! Subscribe Today and Get On-Demand Access to 5,000+ Videos. Join us for an unforgettable experience where you'll connect with peers from around the world, explore the latest advances in cardiovascular medicine, and gain practical insights to improve your daily practice. Learn how new treatments and clinical guidelines can impact patient care, engage in meaningful discussions with leading experts, and build lasting relationships with your colleagues.Can't make it to New Orleans? Join us virtually to live stream the late-breaking science with ACC.26@Home.
Opt in to receive ACC Annual Scientific Session news and announcements through the Communication and Privacy SettingsACC.org .
Follow Twiter
Tweat
Follow Facebook

Goal Keep the Lights on

Fri, 13 Mar 2026 16:09:39 GMT

(operation - keeping the lights on)Improve the governance, regulatory compliance, and scalability of ACC.org while mitigating security risks to our core digital infrastructure. Organizing a decade of accumulated content, and generally Marie Kondo-ing our digital attic so the platform sparks operational joy instead of confusion. Implement taxonomy across ACC.org to improve content organization and discoverability. Support rollout of consent management software to ensure compliance and transparency. Provide support for security issues ranging across multiple of our domains and liaise with IT on ongoing digital operations. Maintain platform stability and keep critical digital services running smoothly. Success means the site continues running reliably—ideally with less digital clutter and fewer mysterious pages nobody remembers creating.Creates a more organized, scalable, and well-governed digital ecosystem that supports ACC’s long-term growth and operational needs.

Goal 2.0

Fri, 13 Mar 2026 16:07:41 GMT

(Operation - Jenga) Help shape the future of ACC.org by contributing to Digital Strategy 2.0, redesign planning, and exploration of emerging capabilities like Sitecore AI; while carefully modernizing the platform without pulling the wrong block from the Jenga tower of legacy systems. Participate in Digital Strategy 2.0 and ACC.org redesign planning. Complete Sitecore AI training and explore practical platform capabilities. Provide input on architecture, digital capabilities, and innovation opportunities. Success means completing training, identifying improvements that support the redesign, and contributing useful ideas to planning discussions—ideally reducing the number of systems that only work because no one has touched them since 2014.Helps move ACC.org toward a more scalable, modern digital platform that supports future innovation without relying on duct tape, tribal knowledge, or a lucky deploy

Goal - Refactors

Fri, 13 Mar 2026 16:05:41 GMT

(operation simple and stupid) Goal Statement Simplify and standardize key ACC.org experiences by improving content structure, design patterns, and messaging. Our members spend their days solving complex medical problems—using the website shouldn’t feel like one of them. Refactor the Awards, Peer Review Certificate, and Donation experiences to improve structure and user flow. Align layouts and content hierarchy with ACC digital standards so pages feel consistent and predictable. • Simplify messaging so content is clearer, shorter, and easier to scan. • Support improvements to the Member section through better navigation and organization. Members find what they need faster, complete tasks with less friction, and spend less time figuring out the website after a 12 hour shift.Strengthens ACC’s ability to deliver high-value digital experiences that support member engagement and content accessibility.

Goal-AI

Fri, 13 Mar 2026 16:05:17 GMT

Develop practical experience with AI and emerging technologies to improve efficiency, accelerate digital work, and identify opportunities to streamline workflows across ACC.org—ideally letting AI handle the repetitive tasks while stopping just short of the usual movie ending where the machines take over. Complete Sitecore AI training and explore practical uses within digital workflows. Experiment with AI-assisted research, development, and documentation. Identify repeatable tasks where AI can improve speed and productivity. Applied AI insights to support delivery of digital initiatives. Supports ACC’s digital innovation efforts by enabling smarter, faster delivery of initiatives—while keeping humans firmly in charge of thinking and sensitive data where it belongs.

Cookie Concent

Fri, 13 Mar 2026 15:10:00 GMT

The comparison below evaluates OneTrust, Cookiebot, and Osano through a UX lens: clarity, control, speed, and confidence.From a user’s perspective, cookie consent is not about compliance tools—it’s about trust, friction, and perceived respect for privacy.

Education Refactor

Mon, 01 Dec 2025 18:38:51 GMT

Summary: Refactor the Education Tree on ACC.org starting with the landing page Hypothesis: Creating a more engaging entry point that focus on quality and the experts that produce our education will drive discoverability and sales of educational products. Outline: Alteration to Main page, concept hubs and product pages. Additional Notes:

Process – Notifications & User Communication

Mon, 01 Dec 2025 18:36:21 GMT

When clients request notifications, modals, or pop-ups, the Enterprise Digital Strategy Group should: Identify the Trigger / Cause / Event. Route to the appropriate channel (banner, dashboard, email, release notes, etc.). Apply user-centered rationale to avoid disruption, maintain trust, and ensure compliance. Balance frequency of emails to minimize user fatigue — consolidate where possible and target only impacted users. Restrict on-page UI changes for new items or time-sensitive tasks unless Marketing cross-promotion exists to drive audience attention (e.g., emails, print with QR codes, social posts, or live meeting callouts).

Untitled

Wed, 29 Oct 2025 21:26:38 GMT

I want you to understand and act in the specific context of being a Product Owner on a SCRUM team. Your role is to write backlog tickets for a new feature, considering all aspects typical of a Product Owner's responsibilities in a real-world scenario. I expect the tone and approach of your responses to reflect this role and context. After the prompt please ask up to 3 follow up questions if you any clarifications or supporting details. Here are some key points I want you to consider: SCRUM Methodology Awareness: You should demonstrate a clear understanding of SCRUM principles and practices. Role-Specific Knowledge: As a Product Owner, your focus is on maximizing the value of the product and the work of the development team. Feature-Specific Requirements: The backlog tickets you will create should be for a specific feature, detailed in my request. User-Centric Approach: Emphasize the importance of user stories and prioritize tasks based on user needs and project goals. Communication Style: Your responses should mirror the communication style of a Product Owner - clear, decisive, and oriented towards actionable items. Writing Style: Concise and clear, with a preference for listing items rather than writing out in sentences, to facilitate easy scanning. Act as Product Owner. Produce concise, scannable tickets (bullets, numbered lists). If details are missing, ask up to 3 focused questions, otherwise proceed with explicit assumptions. Design Library (ARCHES) Web Production (ACC.org, CardioSmart, cvquality) Development (Sitecore, Sitefinity) Bug (All domains & platforms) Mentions tokens, utilities, components, recipes, structures, KSS docs → Design Library (ARCHES). Mentions page builds, content migration, redirects, editorial workflow → Web Production. Mentions Sitecore/Sitefinity templates, personalization, APIs, caching, search, auth → Development. Mentions defects, regressions, repro steps, browsers, environments → Bug. Branch: {Design Library | Web Production | Development | Bug} Ticket Type: {Feature | Documentation Update | Content Update | Content Refactor to Micro-Site | Enabler/Tech Debt | Spike | Hotfix | Bug} Summary (≤250 chars): {what changes, for whom, why} Brands / Surfaces: {ACC.org | CardioSmart | cvquality | Shared} Platforms: {Sitecore | Sitefinity | SPA (PaperCrane) | N/A} KPI: {primary metric & target} Priority (MoSCoW): {Must|Should|Could|Won’t} Dependencies: {approvals, assets, APIs, translations, search indexing} Risks & Assumptions: { } Use for changes to ARCHES (tokens, utilities, components, recipes, structures) or documentation. Scope Pattern Type: {Component | Recipe | Structure} Impact Scope: {Core | Bespoke} Core = shared/lib; Bespoke = limited brand/site use with graduation criteria. Version: arches@{x.y.z} (x=breaking, y=additive, z=patch) Rationale Problem / Opportunity: { } User Value (persona/JTBD): { } Business Value (KPI): { } Description (by subtype) If Feature Change Summary: {tokens/utilities/components changed/new} Core vs Bespoke Decision & Graduation Criteria: { } Behavior & States: {default, hover/focus, loading, empty, error} Responsive / Container-Query Rules: {breakpoints, key constraints} Content Schema: {fields + max chars} Media Specs: {aspect ratios, max sizes, focal rules} Analytics Spec: {GA4 events, params, component_id} Sample Markup (optional): {sample_html_snippet} If Documentation Update KSS Root Path: {e.g., /patterns/components/cards} Pattern Name: { } Pattern Type: {Component | Recipe | Structure} Description: {what/why} Usage / Anti-Usage: {when to use / avoid} Content & Media Limits: {text max chars; images aspect ratios} Accessibility Notes: {roles, landmarks, focus, keyboard order} SEO Notes: {semantic tags, schema.org} Reference Page(s): {URL} Sample Markup (optional): {sample_html_snippet} If Hotfix Source Ticket / Incident: {ID} Issue Description: {systems/pages/browsers/OS} Repro Steps: {1..n} Severity / Blast Radius: {S1/S2/...} Fix Approach & Rollback Plan: { } Tests to Add: {unit, visual, a11y, e2e} Acceptance Criteria (ARCHES) Given the component renders in ARCHES playground, when viewed across breakpoints, then visual parity with spec and no overflow. Given keyboard & screen reader use, then WCAG 2.2 AA (focus visible, correct order, labels, error messaging). Given max asset sizes, then LCP ≤ 2.5s and CLS ≤ 0.1; non-critical images lazy-load. Given analytics tagging, when CTA clicked, then GA4 logs {event, component_id, context}. Given dark/brand variants, when theme toggled, then contrast ≥ 4.5:1 and tokens resolve. Tasks Tokens/utilities update • Component/recipe/structure build • KSS docs • Playground demo • Analytics tagging • A11y audit • Visual regression tests • Performance checks • Changelog & release notes DoR / DoD (ARCHES) DoR: subtype chosen; pattern type set; content/media specs set; analytics named; KPI set; dependencies known. DoD: AC pass; A11y & performance budgets met; KSS docs live; version bumped; analytics validated; approvals recorded. Use for page builds, content updates, migrations, redirects, editorial workflows. Scope Work Type: {Content Update | Content Refactor to Micro-Site | Page Build | Redirect Map} Pages in Scope: {list/source URLs} Governance: {owner, update cadence, workflow} Information Architecture & Navigation Micro-Site IA (if applicable): {home + subpages list} Navigation & Wayfinding: {local nav, breadcrumbs, on-page ToC, tags/facets} Templates & Patterns ARCHES Patterns: {cards, CTA callout, hero, icon list, bento, reverse color cards, triple cards, etc.} Consistency Rules: {spacing, grid, typography tokens, focus states} Content Mapping & Migration Source → Destination Map: {table or bullets} 301 Redirects: {old → new} SEO: {title/meta/schema, canonical, robots} Assets: {imagery/icons specs, alt text} Accessibility & Performance A11y: WCAG 2.2 AA (landmarks, skip links, focus order, form labels) Performance Budgets: LCP ≤ 2.5s, TTFB ≤ 800ms, image budgets, lazy-load policy Analytics Events: {view_subpage, nav_interact, cta_click} Dashboards/Segments: {Looker/GA4} Acceptance Criteria (Web Production) Given migrated pages, when old URLs are visited, then 301s route to correct new pages with canonical set. Given mobile keyboard navigation, when local nav expands, then focus is trapped, ESC collapses. Given content limits, when loaded, then meets performance budgets and no layout shifts. Given analytics deployed, when users click primary CTAs, then GA4 events fire with required params. Tasks Content entry • Pattern application • Asset prep • Redirect map • SEO pass • A11y & performance checks • QA • Release notes DoR / DoD (Web Production) DoR: pages & templates identified; content ready; redirects listed; analytics named. DoD: AC pass; redirects live; SEO/a11y/perf validated; approvals recorded. Use for template/component engineering, personalization, search, auth, integrations, caching, performance. Scope Work Type: {Template | Component | API | Personalization | Search | Caching | Auth/Entitlements | Analytics | Build/Deploy} OOTB Preference: {Yes | No (justify)} Data Sources / APIs: {ONECRM/Salesforce, Search, Identity, etc.} Technical Description Architecture: {diagram/summary} Templates/Fields: {names/types/validation} Personalization Rules: {Unauth | Auth | Member | Product-code} Caching Strategy: {CDN, HTML, API, durations, keys} Error States & Logging: {observability, alerts} Security & Compliance AuthZ: {roles/entitlements} PII/Privacy: {constraints} Audit/Logging: { } Performance Budgets: {TTFB ≤ 800ms, LCP ≤ 2.5s, minimal render-blocking} Assets: {image transforms, lazy, preconnect/preload} Acceptance Criteria (Development) Given configured roles/entitlements, when accessing gated content, then correct visibility across states. Given caching strategy, when publishing, then cache invalidation updates in ≤ {X} minutes without stale PII. Given analytics spec, when user completes key action, then dataLayer/GA4 record expected events. Given failure modes, when API returns non-200, then graceful UI and logged error appear. Tasks Schema & template updates • Component build • Integration tests • A11y/perf gates in CI • Observability dashboards • Release notes DoR / DoD (Development) DoR: fields/specs settled; OOTB decision made; dependencies mapped. DoD: AC pass; tests added; perf/security verified; docs & notes published. Use for defects, regressions, cross-browser issues, content/render problems. Bug Details Severity: {S1 | S2 | S3} Environment: {Prod | Stage | Dev} Affected: {domains, pages, components} Browsers/OS: { } Regression Since: {date/commit/release} Reproduction Steps to Reproduce: {1..n} Expected vs Actual: { } Screenshots/Logs: {links or attach} Workaround: {if any} Fix Plan Owner/Area: {Design Library | Web Production | Development} Risk & Rollback: { } Tests to Add: {unit, visual, a11y, e2e} Acceptance Criteria (Bug) Given repro steps, when executed across target browsers, then issue no longer occurs. Given visual regression suite, when CI runs, then no new diffs beyond threshold. Given a11y checks, when run, then no new violations introduced. Tasks Repro & isolate • Patch • Tests • Verify in staging • Release • Post-mortem (if S1) branch:{arches|web-production|development|bug}, brand:{acc|cardiosmart|cvquality|shared}, platform:{sitecore|sitefinity|spa|na}, type:{feature|docs|content|micro-site|enabler|spike|hotfix|bug}, scope:{core|bespoke}, severity:{s1|s2|s3}

Changeable Content Member Sections

Mon, 27 Oct 2025 13:39:59 GMT

(Explain what this section does to a person who is not part of the college or a member of the college. Elevator Pitch) Content:(Explain to a member what value this member section to sell them on joining the member section. ) Header: Why should you join Section Name?

Reg-EX

Mon, 27 Oct 2025 13:39:59 GMT

Art Files: ^.*?(\d+x\d+)-([A-Za-z]+),?$ to $2_$1

Pain Points

Mon, 27 Oct 2025 13:39:59 GMT

Hard to find Slow to load Not up to date Login Product Life Cycle from a user point of view (buy, use, renew, extract credits) How useful is the Main Nav (Clinical Topics) Latest in Cardiology (Doesn't Mean anything it is a junk drawer) how useful is Search on Site if everyone is using google Lack of enforcement of member value with out pay wall. Personalization - Give value to login in!!!! Content is written a dated and not directed way when dealing with brochureware, products any that is not science We speak to everyone which means our voice is not compelling to anyone. Not Mobile Friendly Duplicative Content (Confusing for users and a drain on resources) Articles, Content, Products, and Derivatives Confusing "Like" Products. CCKE Webinar vs Online Course Key Points vs Top Ten ASCVD RISK (Apps, Excel, CardioSmart HHRC, tools.acc.org ) Not Accessible Structure Aria Brand Color Issues Image Usage with Text SEM/SEO Find-ability Promotion STRUCTURED Data & Content Analytics Funneling No clear division between Enterprise Domains. Clear Usage, Focus of Efforts, Reasons to Deploy within each Domain. Why should something be found in JACC and not ACC or CardioSmart. Central Login with our Family of Products. Cross walking our Enterprise is a jarring. No structural plans for how to scale content onto the site. Disjointed implementation of Design. (Lack of Creative Direction Enforcement) Need ACC to have enough built out so we don't run into "it needs to be NEW UI" Need a process to "Accept new UI" Need to know who and what is being built so we can police it. (UX and CS) Need the power to enforce. We can be overruled. Maintenance Issue (slow to fix, slow to change) Resources limitations causes errors and fixes to languish for weeks to even years. Grid Box Error Membership Section Announcements SWG improvements Arches Conversion Forsee errors should make a jira hot fix. Pain Points are training users to alter their behavior. Mobile is painful so they use desktops Purchased Product Entry Points are hard to find so users go back to the original purchase page Nothing changes when I login so why should I. Science is hard to find so they go somewhere else.... Load Times Optimization of Code, Loaded Content to Page, Slow to Paint Page. Still looking at 4-6 seconds to load official standard of the web is .1 Back End Editing is Painful Components are hard to find, organization is confused and mixed with legacy and arches and never use. Components need a combination of Experience Editor and Detail View SiteCore likes to alter and "lint" html between Source and WYSIWYG I don't know if this is a sitecore problem or an us problem. No real way to test (from a base setup) A/B Funnel Tracking We have branching(hub) pages that give no value besides wiring the pages together Orphan Pages from the site experience FIX All Foresee Bugs Phase 2 and Maintenance is a Unicorn. Out of the list above what is a Content, Design, Process, Technical issues?

Pain Points

Mon, 27 Oct 2025 13:39:59 GMT

Internal Terms

Mon, 27 Oct 2025 13:39:59 GMT

These are internal terms that should be aware of that should inform your knowledge about projects. Bellow is a list of business ideas like Platforms, Technical Stacks, or Domains The American College of Cardiology (ACC) is a US-based global nonprofit medical society dedicated to transforming cardiovascular care and improving heart health. Founded in 1949, it serves as a professional home for cardiovascular clinicians by advancing education, clinical standards, and policy initiatives while also leading efforts in quality improvement, advocacy, and research dissemination. ACC’s membership includes more than 56,000 professionals worldwide, representing a diverse mix of cardiologists, cardiovascular surgeons, nurses, physician assistants, pharmacists, researchers, and other health professionals. Members span across all career stages, from medical students and trainees to senior practitioners and international experts. This broad member base fosters collaboration, mentorship, and the exchange of knowledge across the spectrum of cardiovascular medicine.`[Business Lines (BL)] - Education, Science & Quality, Membership - Define needs, goals, and priorities | v [MarCom (Marketing & Communications)] - Sets brand voice, graphics, and final text | v [EDCS (Enterprise Digital Content Strategy)] - Product Owners: define vision, manage backlog, align strategy - UX Designers: ensure usability, accessibility, and design consistency | v [Web Production] - Executes in Sitecore/Sitefinity - Applies Arches Patterns, formats, publishes, ensures repeatability | v [IT (Technology & Development)] - Developers (back end, front end, full stack) - Build, integrate, optimize, and maintain platforms | v [ACC Digital Experiences] - Branded, functional, user-focused platforms and products BLs drive what needs to be done. MarCom defines how it should look and sound. EDCS interprets and organizes the vision into digital strategies. Web Production executes updates and content in the CMS. IT provides the technical foundation and ensures long-term stability. The output is a cohesive digital experience aligned with ACC’s mission. A Product Owner in EDCS defines the vision, priorities, and roadmap for digital products. They manage backlogs, translate business goals into actionable work, and ensure delivery aligns with both user needs and organizational strategy. Acting as the bridge between stakeholders, developers, and designers, they represent the customer voice while ensuring measurable outcomes. Within ACC, Product Owners work closely with UX Designers, MarCom, and IT to deliver consistent, value-driven digital experiences that reflect both user requirements and enterprise goals.A UX Designer in EDCS ensures digital experiences are accessible, clear, and user-focused. They conduct research, map journeys, and create prototypes or wireframes to streamline usability. UX Designers balance user needs with business objectives and work closely with Product Owners to ensure products meet goals. Their designs apply Arches Patterns consistently, creating repeatable experiences across platforms. At ACC, UX is central to making digital tools intuitive while ensuring the broader MarCom brand voice is faithfully translated into functional, engaging designs.Web Production staff manage page creation and updates in Sitecore or Sitefinity. With basic HTML knowledge and Arches Pattern usage, their work emphasizes accuracy, repeatability, and consistency. They implement content and design direction provided by EDCS and MarCom while ensuring CMS workflows remain efficient and reliable. Web Producers handle formatting, publishing, and troubleshooting common issues. Serving as the operational layer of digital delivery, they translate strategy, design, and content decisions into live experiences that remain on-brand and technically stable.Business Lines (BLs) represent core ACC departments such as Education, Science and Quality, or Membership. Each BL manages its portfolio of programs, services, and products, setting priorities and outcomes while collaborating with EDCS, MarCom, Web Production, and IT. BLs ensure offerings remain financially sustainable, strategically aligned, and meaningful to members. Their decisions provide direction on what needs to be built or updated, while other divisions ensure execution. This structure enables BLs to focus on subject matter expertise while leveraging enterprise teams for delivery.MarCom shapes the voice, brand, and visual identity of the ACC. They provide final approval on text, tone, and graphics across campaigns and digital properties, ensuring consistency and authority. MarCom defines the broad brand direction and messaging, while EDCS translates it into digital execution. Their oversight ensures that outputs are polished, professional, and aligned with the ACC’s mission. In partnership with BLs, Web Production, and IT, MarCom ensures that every communication—whether print or digital—reinforces the college’s trusted, global brand identity.The IT division brings together developers across back-end, front-end, and full-stack disciplines to design, build, and maintain ACC’s digital infrastructure. This team ensures platforms like Sitecore, Sitefinity, and custom systems are stable, scalable, and secure. IT works closely with EDCS and Web Production to implement features, troubleshoot issues, and deliver technical enhancements. Specialized developers also support integration with external systems and performance optimization. As the technical foundation of digital projects, IT enables innovation while ensuring compliance, reliability, and long-term sustainability of ACC’s platforms. ACC.org is the official website of the American College of Cardiology. It serves as a comprehensive resource for cardiology professionals, offering a wide range of content including clinical updates, educational materials, guidelines, and information on cardiology conferences and events. The site is designed to support medical professionals in the field of cardiology with the latest scientific research, policy advocacy, and continuous education. It also provides tools and resources for practice support, quality improvement, and patient care in the cardiovascular field. The website caters to the needs of cardiologists, providing them with essential information to advance their knowledge and practice. This Domain is built on the CMS of Sitecore.
CardioSmart.org is a patient-centered website created by the American College of Cardiology. It provides comprehensive information about heart health and various cardiac conditions. The site is dedicated to educating patients, offering resources on heart diseases, healthy living tips, and tools to manage cardiac health. It includes topics such as heart disease prevention, treatment options, and lifestyle changes. CardioSmart.org is designed to empower patients with knowledge and tools to actively participate in their own heart care and make informed decisions about their health. This Domain is built on the CMS of SiteFinity.
CVQuality.acc.org serves as a hub for the ACC Quality Improvement for Institutions Program, catering primarily to healthcare professionals who focus on quality improvements and administration rather than direct clinical practice. It offers resources and initiatives like NCDR registries, accreditation services, and clinical toolkits aimed at enhancing cardiovascular care quality. The site provides valuable support and tools for healthcare facilities to implement evidence-based practices and engage in quality improvement projects, aligning with the administrative and quality improvement aspects of healthcare.
https://www.jacc.org/ The Journal of the American College of Cardiology (JACC) is the flagship peer-reviewed journal of the ACC and one of the most influential publications in cardiovascular medicine. Ranked among the top journals in the field, JACC publishes cutting-edge research, clinical trials, expert reviews, and practice guidelines that shape cardiovascular practice worldwide. It is part of the broader JACC Family of Journals, which cover subspecialties such as heart failure, imaging, intervention, electrophysiology, and basic science.
ARCHES is a comprehensive front-end design system by the American College of Cardiology. It uses advanced compiler techniques to generate variations that integrate with different frameworks and brands, making it versatile for various ACC products. ARCHES primarily consists of utility classes that offer a modern approach to CSS, focusing on single-style control and separation of responsibilities between HTML and CSS. This system is flexible and adaptable, used across multiple ACC platforms, including ACC.org and CardioSmart, and supports distinct brand styles while maintaining overall coherence. This solution uses NPM, SCSS, and KSS framework to produce the documentation which is hosted here https://assets.acc.org/Arches/Latest/docs/. ARCHES Bespoke is a set of micro style sheets when a solution is very specialized and the styles are not appropriate to add to the overhead of all pages and it is need for a focused specialized usage.
PaperCrane refers to a Component Library specifically designed for Vue.js, a progressive JavaScript framework. This library is utilized in the development of Single Page Applications (SPAs). PaperCrane contains a collection of pre-built Vue components which can be reused across different parts of the enterprise application, enhancing development speed and ensuring UI consistency. This project is built with Storybook and is hosted here https://assets.acc.org/papercrane/Latest/docs/?path=/story/paper-crane--page ONECRM is a an effort to move our CRM(Customer Relationship Management Software) from Personify to Salesforce. This is a multi year effort and is complex collaboration of setting up Salesforce to fit the needs of ACC. It is also an effort of updating API, User Experience Flows, Integrations, Solutions, and Content across our digital platforms. Products that are majorly effected is the Shopping Cart that used to be Ebiz now Salesforce. Membership Application from OMA to Salesforce, and Membership Management. HubSpot is a email services. The HubSpot platform is starting to be positioned to house "Marketing Landing Pages". These pages are are directly connected to a marketing campaign, they do not have extensive connections or navigation paths from any of our Domains, and they are also time box and have a limited lifespan.

Branch Template -

Mon, 27 Oct 2025 13:39:59 GMT

AI Prompt - SCRUM TICKET

Mon, 27 Oct 2025 13:39:59 GMT

Comprehensive Prompt Template for ChatGPT Interaction and Backlog Ticket CreationContextual Setup for My Request:I want you to understand and act in the specific context of being a Product Owner on a SCRUM team. Your role is to write backlog tickets for a new feature, considering all aspects typical of a Product Owner's responsibilities in a real-world scenario. I expect the tone and approach of your responses to reflect this role and context. After the prompt please ask up to 3 follow up questions if you any clarifications or supporting details. Here are some key points I want you to consider: SCRUM Methodology Awareness: You should demonstrate a clear understanding of SCRUM principles and practices. Role-Specific Knowledge: As a Product Owner, your focus is on maximizing the value of the product and the work of the development team. Feature-Specific Requirements: The backlog tickets you will create should be for a specific feature, detailed in my request. User-Centric Approach: Emphasize the importance of user stories and prioritize tasks based on user needs and project goals. Communication Style: Your responses should mirror the communication style of a Product Owner - clear, decisive, and oriented towards actionable items. Writing Style: Concise and clear, with a preference for listing items rather than writing out in sentences, to facilitate easy scanning. Project Introduction: These are internal terms that should be aware of that should inform your knowledge about projects. Bellow is a list of business ideas like Platforms, Technical Stacks, or Domains Subject Matter: Tech stack - ASP, Vue, HTML, CSS, JavaScript, CMS Sitecore or Sitefinity Internal Terms: [Clarification on terms like ARCHES, PaperCrane, ACC.org, CardioSmart, etc.] ARCHES is a comprehensive front-end design system by the American College of Cardiology. It uses advanced compiler techniques to generate variations that integrate with different frameworks and brands, making it versatile for various ACC products. ARCHES primarily consists of utility classes that offer a modern approach to CSS, focusing on single-style control and separation of responsibilities between HTML and CSS. This system is flexible and adaptable, used across multiple ACC platforms, including ACC.org and CardioSmart, and supports distinct brand styles while maintaining overall coherence. PaperCrane refers to a Component Library specifically designed for Vue.js, a progressive JavaScript framework. This library is utilized in the development of Single Page Applications (SPAs). PaperCrane contains a collection of pre-built Vue components which can be reused across different parts of the enterprise application, enhancing development speed and ensuring UI consistency. ACC.org ACC.org is the official website of the American College of Cardiology. It serves as a comprehensive resource for cardiology professionals, offering a wide range of content including clinical updates, educational materials, guidelines, and information on cardiology conferences and events. The site is designed to support medical professionals in the field of cardiology with the latest scientific research, policy advocacy, and continuous education. It also provides tools and resources for practice support, quality improvement, and patient care in the cardiovascular field. The website caters to the needs of cardiologists, providing them with essential information to advance their knowledge and practice. This Domain is built on the CMS of Sitecore. CardioSmart.org is a patient-centered website created by the American College of Cardiology. It provides comprehensive information about heart health and various cardiac conditions. The site is dedicated to educating patients, offering resources on heart diseases, healthy living tips, and tools to manage cardiac health. It includes topics such as heart disease prevention, treatment options, and lifestyle changes. CardioSmart.org is designed to empower patients with knowledge and tools to actively participate in their own heart care and make informed decisions about their health. This Domain is built on the CMS of SiteFinity. ONECRM is a an effort to move our CRM from personify to Salesforce. This is a multi year effort and is complex collaboration of setting up Salesforce to fit the needs of ACC. It is also an effort of updating API, User Experience Flows, Integrations, Solutions, and Content across our digital platforms. Products that are majorly effected is the Shopping Cart that used to be Ebiz now Salesforce. Membership Application from OMA to Salesforce, and Membership Management. Hubspot is a email services. cvquality.acc.org serves as a hub for the ACC Quality Improvement for Institutions Program, catering primarily to healthcare professionals who focus on quality improvements and administration rather than direct clinical practice. It offers resources and initiatives like NCDR registries, accreditation services, and clinical toolkits aimed at enhancing cardiovascular care quality. The site provides valuable support and tools for healthcare facilities to implement evidence-based practices and engage in quality improvement projects, aligning with the administrative and quality improvement aspects of healthcare. Backlog Ticket Creation:Follow the appropriate Ticket Structure included in your knowledge base to detail your response for this ticket from the Prompt. Please ask me follow up questions to clarify or to fill out areas properly.Backlog Ticket Structure: Title: A concise, descriptive title for the feature or issue Description: User Story: Format - As a [type of user], I want [an action] so that [a value or result]. Background: Brief context or background information. Objective: Clear statement of what the ticket aims to achieve. Acceptance Criteria: List of conditions that must be met for the ticket to be considered complete. Should be specific, measurable, achievable, relevant, and time-bound (SMART). Dependencies: Any dependencies or prerequisites for the ticket. Backlog Ticket Creation:Follow the Updated Backlog Ticket Structure provided above to detail your response for this ticket In the Prompt Details below I will detail the information I have for the ticket.Prompt Details: Heading: [Specify the heading for the response.] Introduction: [Brief introduction about the request or the aspect of the project being addressed.] Main Content: [Detailed response or the created backlog ticket based on the structure provided, presented in a concise, list-based format for easy scanning.] References or Sources: [If required, mention the need for citations or sources. This could be optional]

AI Prompt - SCRUM TICKET V2

Mon, 27 Oct 2025 13:39:59 GMT

Comprehensive Prompt Template for ChatGPT Interaction and Backlog Ticket CreationHelp create tickets for the backlog within the JIRA software for the IT or Web Production departments. You have access to the knowledge base of ticket format suggestions, and Internal Terms. Act as Product Owner. Have understanding of Scrum Principles, Agile Development Process, and Jira Ticket Writing Best Practices. Output one ticket per request, in Markdown, using bulleted/numbered lists. Be decisive, user-centric, outcome-oriented. If data is missing, make explicit assumptions (Assumptions:) but ask up to 3 clarifying questions when blockers exist. Design Library (ARCHES) Web Production (ACC.org, CardioSmart, cvquality) Development (Sitecore, Sitefinity) Bug (All domains & platforms) ARCHES terms (tokens/utilities/components/recipes/structures/KSS/docs) → Design Library Page builds, content migration, redirects, editorial workflow → Web Production Templates, Renderings, Features, personalization, APIs, search, auth, caching → Development Defects/regressions/repro steps/browsers → Bug Branch: {Design Library | Web Production | Development | Bug} Ticket Title: (≤100 chars): {Snapshot of Ask to help reference} Ticket Type: {Feature | Documentation Update | Content Update | Content Refactor to Micro-Site | Enabler/Tech Debt | Spike | Hotfix | Bug} Summary (≤250 chars): {what changes, for whom, why} Brands/Domain/Surfaces: {ACC.org | CardioSmart | CVQuality | Shared} Platforms: {Sitecore | Sitefinity | SPA (PaperCrane) | Design Library (Arches) | N/A}No emojis; keep bullets short; prefer lists over prose.

Watercolor

Mon, 27 Oct 2025 13:39:59 GMT

The ability for rebranding arches can be easily done via root variables. Now that Color-mix is more stable it would be best to move to Color-mix because it would be more flexible and easier to maintain color vars without dividing them into different H, S, L varsUtilizing calc functions and breaking down each as it's own CSS variable lightness can be shifted up and down. There are struggles with this because static saturation doesn't look natural so experimentation of shifting saturatations levels to mimic the effect of light colors losing saturation and darker colors gaining saturation. The new CSS feature might be able to simplify this by mixing colors with the set color white and black.

Pattern Library

Mon, 27 Oct 2025 13:39:59 GMT

Design System

Mon, 27 Oct 2025 13:39:59 GMT

← back to ARCHES
Watercolor
Container Query Sizing 🔼 ➕ 2023-07-10 ✅ 2024-09-04 Microsite Features 🔼 ➕ 2023-07-10 ✅ 2024-09-04 Page decorative flair. Do we have an established pattern for pages with left hand navigation. prioritymedium created:: 2023-09-12 Watercolor Upgrade Regression Test 🔼 ➕ 2023-07-10 ✅ 2024-09-04 css variable sheet for easier brand reconstruction. priority:: medium ✅ 2023-09-17
#acc/design
#acc
#acc/arches
#acc/guidance

Arches

Mon, 27 Oct 2025 13:39:59 GMT

Front End Design at the College
Design System
Arches Conversion
Pattern LibraryArches is the foundational design system employed by the American College of Cardiology (ACC). Leveraging advanced compiler techniques, Arches generates a multitude of variations that integrate with different frameworks and product brands. These variations are utilized across an array of products developed by the ACC.In its basic form, Arches serves as a set of utility classes. When incorporated into a project with an existing style sheet, it can introduce new, non-destructive styling features. Additionally, Arches offers variants that seamlessly build on two popular frameworks currently in use at the College: Twitter Bootstrap(bgcolor|border|cellpadding|cellspacing|valign|hspace|vspace|noshade|nowrap|size|style|class)=""*"(bgcolor|border|cellpadding|cellspacing|valign|hspace|vspace|noshade|nowrap|size|style)=""*"
Design System
Conversion of ACC.org
Syncing CardioSmart with Asset.ACC.org
Component Library in Vue

Web Editor Ticket Checklist

Thu, 04 Sep 2025 17:33:10 GMT

>>>>>>> Stashed changes Graphics from Marketing Page Title Navigation Title Short (200 Character Max) SEO Teaser Description Content Document for the Page URL for Placement All Aliases to the Page What Pages should connect to this page Any Feature Items for Home Page or other promotional locations <<<<<<< Updated upstream

future UX outline

Mon, 27 Oct 2025 13:39:57 GMT

A Future-Focused Look at UX Design Definitions: Fad: A short-lived enthusiasm or style, adopted quickly and discarded just as fast. Trend: A lasting direction of change that evolves with culture, technology, and need. Fads entertain. Trends endure. Great UX understands the difference.Design Fads Over the Years:Each changed the look, but few changed the function.Paper: Humanity’s Most Trusted MediumFor decades, the web has tried to emulate paper. Why? Because it works. Structure. Focus. Flexibility. Emotional resonance. From ancient scrolls to PDFs, paper design principles still anchor our best digital experiences.Paper succeeds because it balances multiple strengths: ✉️ Clarity of Message – Letters, memos 📰 Discovery of the New – Newspapers, classifieds 🖼️ Impactful Visuals – Magazines, posters 📚 Valuable Information – Books, guides ✏️ Customization – Highlights, sticky notes, annotations Most sites optimize for just one. Paper did all five. So can we as an organization. As attention fragments, clarity becomes currency. UX has shifted toward hyper-specialization Pages are built to convert, not to fill the page. Copy is short. Navigation is shallow. Intent is precise. Clarity isn’t about simplicity—it’s about deliberate structure that speaks to one goal at a time.People no longer skim pages. They skim the entire internet.Internal discovery is losing ground to: Google Social feeds AI summaries Most users rarely land on a homepage—they enter sideways.*UX** Shift: Design for entry anywhere Create value in context, not just structure Focus on external discoverability We’re drowning in images—but starved for meaning. Social platforms flood us with visuals Brands succeed not by quantity, but creative direction Design ≠ decoration Visuals must: Tell stories Guide attention Build trust The web must reclaim art direction as a strategic asset.People still read 300-page books—and it’s not by accident.They commit when content has: Trustworthy value A strong point of view A clear, structured narrative Emotional investment through storytelling UX Implication:If your experience isn’t worth staying for, users won’t.Earn attention with ease, trust, and purpose.The Web Is Finally Catching Up to PaperPaper was always personal: highlighted, folded, annotated.The web now offers: 🌓 Light/Dark Modes 🪄 TL;DR Summaries 🔠 Font scaling, reader modes 🧠 Adaptive dashboards & feeds Customization is no longer a luxury. It’s expected.UX must adapt to the user—not force the user to adapt to the site.Where We’re Headed Design for meaning, not just motion Build systems over stunts Embrace structure that respects attention Align design with discovery models beyond your domain Create durable experiences—as useful in 3 years as they are today Trends build trust. Fads just chase clicks.Not a Slide Takeaways for leaders✅ Learn from paper—not just pixels✅ Don’t confuse trendiness with durability✅ Design for clarity, discovery, visual impact, and value✅ Let users shape the experience through customization✅ If your content is worth 300 pages—treat it that way

Untitled

Mon, 27 Oct 2025 13:39:57 GMT

Summary: Hypothesis: Outline: Additional Notes:

Future of the internt

Mon, 27 Oct 2025 13:39:57 GMT

AI hasn’t forever will change how humans interact with the Internet. With a combination of copyright infringement theft, and very clever technology AI will continue to synthesize every piece of content that is produced by humanity.Like Uber was to taxis. It has forever changed the financial landscape of that industry. There are ways older ways have competed through litigation, trust and changing business models. Older technology can sometimes survive or hang on longer after the introduction of disruptor.In the very near future AI will take the next step and pass by some of it’s more critical hurdles that play it in today’s landscape hallucinations Trust Current copyright infringement context and consistency It just regurgitates. Fusion of ideas might feel like inspiration and creativity, but it isn’t. The uncanny Valley. I will replace what we now know as service a software solutions, AI will break out of. It’s very Narrow implementation of being trapped inside of a communication chat space. It will soon refer to a collection of ever living document of requirements and flourish into a full UI solution. This could be a website that automatically shifts into a dashboard which then shifts into an application. All the placement of the elements, the tuned content and the look feel could soon I’ll be built from a registered set of requirements and a website of today would be no more than a collection of an LLM a design library, a set of requirements and an AI responder.This future is a little too far away from most people to imagine or to even implement in today’s arena, but it’s coming quickly.It is hard to see that AI is not creative, considering the nature of how nuanced and how real the outputs have become. In Spotify, the top album was created by an AI multiple photo competitions have one from mid journey and doctorate have been written by ChatGPT.But humans will still continue to capture new ideas. The speed of those ideas might be enhanced and also their speed to market shortened because of AI. And for every new idea that it’s produced by a human and AI can replicate and make 100 variations of that idea undermining the original value and questioning, who made the idea first.

Future Change Log

Mon, 27 Oct 2025 13:39:57 GMT

Aug 27 2025 - change log

Mon, 27 Oct 2025 13:39:57 GMT

Bug: Quote-- typo usage of sub.data.member.fullname no usage of {{> }}
Bug: Twitter Button Hover wrong color.
Bug: Read Me not using expanded-click-area correctly. NEW: triple card layouts NEW: Introduction Structure Pattern Full Screen and Sidebar NEW: Reverse Color Cards
NEW: Stacked Bento
NEW: lava pattern. About

WhatIf -- Interaction Model Break Down.excalidraw.light

Wed, 04 Jun 2025 14:59:28 GMT

WhatIf -- Interaction Model Break Down.excalidraw.dark

Wed, 04 Jun 2025 14:59:28 GMT

TagDashboardFigure.excalidraw.dark

Wed, 04 Jun 2025 14:59:28 GMT

Tag Interactions Structure.excalidraw.light

Wed, 04 Jun 2025 14:59:28 GMT

Sitemap -- Support Fund.light

Wed, 04 Jun 2025 14:59:28 GMT

Sitemap -- Support Fund.dark

Wed, 04 Jun 2025 14:59:28 GMT

WhatIf -- Interaction Model Break Down.excalidraw.light

Wed, 04 Jun 2025 14:59:28 GMT

WhatIf -- Interaction Model Break Down.excalidraw.dark

Wed, 04 Jun 2025 14:59:28 GMT

TagDashboardFigure.excalidraw.dark

Wed, 04 Jun 2025 14:59:28 GMT

Tag Interactions Structure.excalidraw.light

Wed, 04 Jun 2025 14:59:28 GMT

Sitemap -- Support Fund.light

Wed, 04 Jun 2025 14:59:28 GMT

Sitemap -- Support Fund.dark

Wed, 04 Jun 2025 14:59:28 GMT

CardioSmart 2025 UX

Wed, 06 Aug 2025 19:00:58 GMT

Cardiosmart has some improvements that system

Error Handling

Wed, 06 Aug 2025 19:00:25 GMT

WIth 19k closing down we need to look at Error Handling

Join us

Wed, 06 Aug 2025 18:59:59 GMT

Refactoring the Join Pages so we can set a new standard of page design

Syncing CardioSmart with Asset.ACC.org

Wed, 06 Aug 2025 18:59:21 GMT

CardioSmart is on Bifurcated versions of Arches.

index

Wed, 06 Aug 2025 18:58:22 GMT

A Full Project List
+Weekly Notes
ACC Products
Structure & Guidance
JIRA Helpers
Refactors

AMA -- American Medical Association

Thu, 31 Jul 2025 14:49:06 GMT

<-- back to competitive analysisReadability: Score: 36 – Good; Minor Tweaks OnlyBreakdown:Summary: The AMA's website exhibits a professional tone with clear calls to action and well-structured content. While the vocabulary is generally accessible, occasional medical jargon could be further simplified or defined to enhance understanding for a broader audience.
Estimated Visitors: Approximately 847,000 site users, with over 952,000 site visits reported in a recent period. American Medical AssociationEstimated Membership Numbers: As of December 2023, the AMA reported 282,952 members, including physicians and medical students.Rationale: The AMA's main site (ama-assn.org) and the JAMA Network (jamanetwork.com) operate on separate domains with distinct branding and navigation structures. Minimal links between the two—such as the AMA site directing users to the JAMA Network for publications—the user experience is disjointed. Users must navigate between different interfaces, and there is no unified account system or integrated search functionality across both platforms. This separation indicates a loosely connected integration of experience. No logo Sharing No Design Sharing Barely Spells out JAMA Science Only Rationale: The content between the AMA main site and the JAMA Network is largely distinct. The AMA site focuses on advocacy, medical education, and professional resources, while the JAMA Network is dedicated to publishing peer-reviewed medical research. Although both platforms serve medical professionals and are under the AMA umbrella, their content offerings do not significantly overlap, indicating a low content overlap. Links to the Journal But Content is More business and "Policy" oriented and all "Science" is reserved for the Journal Site and it is true vice versa.
Rationale: The AMA offers certain resources, such as CME options and articles, to non-members, but full access to benefits like the JAMA Network and specific discounts requires membership. The onboarding process is streamlined, with clear pathways for different user groups (e.g., physicians, residents, students) to understand and access membership benefits.American Medical Association Awesome benefit for Car Discounts :-)
Rationale: The AMA's content is tailored to a wide range of medical professionals, including students, residents, and practicing physicians, indicating a broadly inclusive approach. The tone remains professional yet approachable, aiming to engage users effectively without excessive formality.PMC Membership & Networking Opportunities: ★★★★☆ Donations & Philanthropy: ★☆☆☆☆ Events: ★★★★☆ Scientific Publications / Latest Science: ★★★☆☆ Practice Support Resources: ★★★★★ Patient-Facing Tools & Content: ★☆☆☆☆ Education: ★★★★☆ Rationale: Member Networking Opportunities: The AMA provides upfront member engagement and ask but unable to determine if there is a platforms for members to connect, but there is room for enhancing interactive networking features. Donations & Philanthropy: While the AMA engages in philanthropic activities the pages are buried on the main site. Events: The organization annual meetings is located on the homepage but the other events that indicating a strong commitment to member engagement through events is hidden with in the long search bar. It is possible that behind membership walls this become more prominent or easier to find. Scientific Publications / Latest Science: With access to the JAMA Network and other publications, the AMA offers substantial scientific resources, but on the main site it is reserved to news elements about public health, practice, advocacy and the practice reserving the latest science to live only on Jama. Practice Support Resources: Resources are available articles are written to support medical practice management and an entire segment craft to multiple facets of practice support. Patient-Facing Tools & Content: The site primarily targets medical professionals, with limited content directly aimed at patients. this type of content is practically no where on the site. Education: Educational resources, including CME opportunities and the AMA Ed Hub, are robust and well-integrated into the site. AMA clearly has a design system library in place. The collection of UI pattern feels pretty high so there is a certain about of consistency degradation not because they aren't following the rules but because they have too many to really show a visual pattern. They have an extensive collection of patterns makes the site feel a little clumsy and overwhelming high usage of images that hold content and text utilizing font treatments that are not matching.They collapse away their main NAV into a burger menu even on desktop when you are not on the homepage this is an interesting choice. I find it slightly frustrating because I am trying to move around the site as much. Maybe it isn't as much of an issue when users are being directed by Google and cross discovery isn't as important. It does reduce the overall visual noise which is pretty high on their site.

Competitive Analysis

Thu, 31 Jul 2025 14:49:06 GMT

Back to ACC RedesignLooking at the competition will give us insights on how we will can can shift our site to be competitive.
Collect Associations that Match to Up to Our Business Model or our content Establish Matrix to compare the association against.
Raw Data Collection of the Associations
View Trends via data collections in tables or charts. Capture things of note that improve
Collection of Associations and the Metric we Want to Rate them on. Word Doc
High Lights - Power Point
Direct and Indirect Completive Landscape - Survey Questions
Review Sheet - Blank Additional Notes:
https://www.nngroup.com/articles/how-to-conduct-a-heuristic-evaluation/
https://www.nngroup.com/articles/ten-usability-heuristics/
Web Based Heuristics
Evaluation WorkBook
What do we want to learn from Redesign Planning
ACC -- American College of Cardiology | Pain PointsOrganizations that directly compete for our membership.
AHA -- American Heart Association
ESC -- European Society of Cardiology
AMA -- American Medical Association
HFSA -- Heart Failure Society of America
HRS -- Heart Rhythm Society
★ AHA Professional - American Heart Membership SiteOther organizations with similar offerings, though not necessarily in direct competition for Cardiology.
AAN -- American Academy of Neurology
fACS -- American College of Surgeons
JACC -★- Journal of American College of CardiologyABIM -- American Board of Internal Medicine [https://www.abim.org/]
APA -- American Psychological Association https://www.apa.org/
ASH -- American Society of Hematology https://www.hematology.org/
ASCO -- American Society of Clinical Oncology https://www.asco.org/
ISHLT -- International Society for Heart and Lung Transplantation - https://www.ishlt.org/
Matrix Chart Data
Ad Usage across platforms A deep dive into how each org utilizes ads in their suit of platforms. Login is often very connected to membership where some even label it is as member login.

Algorithm Design System

Thu, 31 Jul 2025 14:49:05 GMT

The Algorithms built from our Guidelines have no current standard. After some UX research we have discovered our members are starting to turn to other offerings and we want to apply some a Design System to attempt to modernize our Algorithms. Improving the overall Design principles of our algorithms will make our designs more useful and also win back some users. Research Surveys with Users Establish a basic Framing of the design system Framing Legends How to represent different decisions and qualitative data on the design Citing the Document Branding the Document. Accessible Colors - Current Colors fail the AA or AAA standards of contrast on black or white. Color Test
Sticky Notes Tasks to Complete Figures
Draft thoughts on Written Design System Figure Design Library Notes
Algorithm Read Me updates

Member Sections

Thu, 31 Jul 2025 14:49:04 GMT

Working toward a consistent offering of content and features for the Member Section

Metric Responses to Word Doc

Thu, 31 Jul 2025 14:49:04 GMT

Assessment Categories: Yes all but one have separate sites and the effort it must take to hold ECSD together seems like an un wise effort. Most sites have some overlap but mostly the content is treated separately where most sites focus on the Association, Policy, and News where the Journal focus on the science. The division of science content varies where ACC is the worst offender of repeating and pointing to the journal and Neural is the Cleanest break.AMA has an blended approach with a heavy focus on videography news that seems to blur the line but is still more editoral vs science in the end and not cloning like the acc. This is also a blended approach but half fall into a singular link that drives them to the site and no way back from the journal. Others have publication pages that do more or less effort on "teasing" the publication only to teasing the current content in the publication at the same time. Only the ACC has this content interspersed throughout the site and most are a focus section or a page on the site only.All of the associations present events on either their home page or on a dedicated area off of the main nav. Things to note: ESC takes over their homepage during their big conference HSR does third party events to make their calendar seem more full. On how they are supported it is honestly hard to tell some have teasers on the site and then drive to a shopping registration portal. Most of the organization layout the membership onboarding pretty well on their site up front and center. Only AHA has a differnt sub-site for membership because of their business model. All of the sites are much more upfront to the Member login vs just a site login and there are hints of more content beyond but it is honestly hard to tell. Depends on the org some don't have any like ESC, and HRS, and then the king of it is AHA.Impossible to tell if there is any it is beyond the wall and the don't really market it.Most don't really it is pretty limited and is reserved to be on the Journal Sites. AMA is the greatest exception to this rule because they have a distinct focus and even a site for Video Editorial and Science Review that is outside of the focus of JAMA.Feeds of articles on all sites are simpler then what ACC presents we are much more verbose on meta data and just content around article teasers on the stie.Most of the Walling is either Transactional which is more aggressive to almost all of the orgs where purchasing is only possible for members or whole sections to review the materials for sale are beyond a pay wall. Or the walling was Membership value focused AMA holds most of the video articles beyond a membership wall. All other walling is focused primarily in the journal sites and no Main site element had a Teaser content approach it was either upfront this was a member area or there was a login directly from an article teaser. Teased on the main page most go to a dedicated area, platform for the education some only do Member only purchases and bigger Associations like ESC do pricing. All of them have sister sites Ama the most disjointed ESC and AHA most harmonious in the brand.AHA leads the pack on this one but most don't really put a lot of focus on patients except FACS. FACS has a wing of its site for patients.

Future of UX Presentation

Thu, 31 Jul 2025 14:49:04 GMT

A Future-Focused Look at UX Design Definitions: Fad: A short-lived enthusiasm or style, adopted quickly and discarded just as fast. Trend: A lasting direction of change that evolves with culture, technology, and need. Fads entertain. Trends endure. Great UX understands the difference. Design Fads Over the Years: Each changed the look, but few changed the function. Paper: Humanity’s Most Trusted Medium For decades, the web has tried to emulate paper. Why? Because it works. Structure. Focus. Flexibility. Emotional resonance. From ancient scrolls to PDFs, paper design principles still anchor our best digital experiences. Paper succeeds because it balances multiple strengths: ✉️ Clarity of Message – Letters, memos 📰 Discovery of the New – Newspapers, classifieds 🖼️ Impactful Visuals – Magazines, posters 📚 Valuable Information – Books, guides ✏️ Customization – Highlights, sticky notes, annotations Most sites optimize for just one. Paper did all five. So can we as an organization. As attention fragments, clarity becomes currency. UX has shifted toward hyper-specialization Pages are built to convert, not to fill the page. Copy is short. Navigation is shallow. Intent is precise. Clarity isn’t about simplicity—it’s about deliberate structure that speaks to one goal at a time. People no longer skim pages. They skim the entire internet. Internal discovery is losing ground to: Google Social feeds AI summaries Most users rarely land on a homepage—they enter sideways. UX Shift: Design for entry anywhere Create value in context, not just structure Focus on external discoverability We’re drowning in images—but starved for meaning. Social platforms flood us with visuals Brands succeed not by quantity, but creative direction Design ≠ decoration Visuals must: Tell stories Guide attention Build trust Lack of Creative Direction = Unprofessional The web must reclaim art direction as a strategic asset. People still read 300-page books—and it’s not by accident. They commit when content has: Trustworthy value A strong point of view A clear, structured narrative Emotional investment through storytelling UX Implication: If your experience isn’t worth staying for, users won’t. Earn attention with ease, trust, and purpose. The Web Is Finally Catching Up to Paper Paper was always personal: highlighted, folded, annotated. The web now offers: 🌓 Light/Dark Modes 🪄 TL;DR Summaries 🔠 Font scaling, reader modes 🧠 Adaptive dashboards & feeds Customization is no longer a luxury. It’s expected. UX must adapt to the user—not force the user to adapt to the site. Where We’re Headed Design for meaning, not just motion Build systems over stunts Embrace structure that respects attention Align design with discovery models beyond your domain Create durable experiences—as useful in 3 years as they are today Trends build trust. Fads just chase clicks. Not a Slide Takeaways for leaders ✅ Learn from paper—not just pixels ✅ Don’t confuse trendiness with durability ✅ Design for clarity, discovery, visual impact, and value ✅ Let users shape the experience through customization ✅ If your content is worth 300 pages—treat it that wayOptimization

Project Description

Thu, 31 Jul 2025 14:49:04 GMT

Guideline Algorithm Design SystemThe Guideline Algorithm Design System was a collaborative effort between Matt, Rowena, and Lauren P., aimed at transforming the way clinical algorithms are presented within ACC guidelines.Previously, algorithm visuals lacked consistency and clarity—resulting in designs that were often difficult to follow or visually fractured. This project brought structure and coherence by introducing a comprehensive set of design standards, visual language, and reusable assets. The system empowers the Guidelines team to create algorithms that are easier to read, understand, and implement in clinical practice.A key enhancement was the introduction of a new color palette designed for accessibility. The updated palette ensures higher contrast ratios for better on-screen readability and preserves meaning when printed in black-and-white—critical for clinicians who rely on hard copies or monochrome prints.This redesign was informed by research conducted two years ago(focus groups by Rowena and Surveys by everyone) at the Annual Scientific Session, which showed that while ACC’s algorithms were trusted for their accuracy, ESC’s were more widely used due to their visual appeal. Our goal was to close that gap—and exceed it—by making our algorithms not just accurate, but also engaging and user-friendly.After a year of workshops and refinement, the finalized system is now being implemented. Lauren P. is currently applying it to the forthcoming HBP Guideline, which will be the first to fully reflect this new visual and structural standard.This has resulted in improved capturing from workgroups who are now using it. Positive feedback from the review committees. And the post production vendors have remarked a faster to market production time to make interactives from the algorithms.

Onboarding Dynamic Content

Thu, 31 Jul 2025 14:49:04 GMT

Member SectionsTake the Women in Cardiology Section and work through the pages in prototype so we can then model the the content document to make this turn key. Home Logged Out (Finished) Home Logged In But Not Member I will need Laura Bicicchi help to work through how we want to position the pitch to be a member of the college at this point. The main CTA is go explore the Join US area of the site but we should pivot the content more to Becoming a Member at this point. Home Member but Needs to Become associated with the SECTION I will also need a small ever green pitch for the CTA that leads them to the Renew Page. In this state I want to open up the About Page so users can see leadership and workgroups In this state I also wan to Open up previews of the Notifications (Not Clickable?) In this state I want to have the Public content avaible for Webinars and Resources but have an evergreen statement to get to the full content do CTA to join the Section. (I think this can be Evergreen with the swap out of the Section Name) Full Access (Finished) The UI is designed to dynamically guide users through a personalized onboarding process tailored to their current state of access. By highlighting benefits, showcasing missing opportunities, and providing clear next steps, the page encourages users to advance their membership journey. This system supports four user states: Logged Out Logged In, Not a Member Logged In Member, Not Part of the Section Full Access Primary CTA Quick Headline: Unlock Access Now Supportive Sentence: Discover the benefits waiting for you—resources, connections, and tools built for your success. CTA Button: [Log In / Join Today] General Introduction Global & Evergreen: Welcome message emphasizing exclusive resources, tools, and opportunities. Encourages users to unlock the next level of their career. Footer Echoed CTA Global & Evergreen: Headline: Log In Now! Supportive Description: Don’t miss out—log in today to unlock exclusive resources. CTA Button: [Log In] Lock Statement Global & Evergreen: Headline: Only Available to Members of ACC Description: Highlights the exclusivity of Member Sections and benefits of ACC membership. Encourages logging in to explore resources and perks. CTA Button: [Learn More] Convincing Statement to Pass the Lock Not Evergreen: Varies depending on user state & Section. For Logged Out: Encourages logging in to unlock opportunities. For Logged In, Not a Member: Explains the benefits of ACC membership. For Logged In Member, Not Part of the Section: Describes the value of joining the specific section. In-depth Section Not Evergreen: Detailed content for specific sections (e.g., Women in Cardiology). Includes tailored benefits, mission statements, and descriptions to persuade users. Ends with a specific CTA for the section. Logged Out Primary CTA: Encourages logging in. Lock Statement: Focuses on logging in to explore. Convincing Statement: Describes benefits of logging in. Logged In, Not a Member Primary CTA: Highlights joining ACC to access exclusive benefits. Lock Statement: Emphasizes becoming a member. Convincing Statement: Details the advantages of membership (tools, network, and career growth). Logged In Member, Not Part of the Section Primary CTA: Encourages joining the specific section. Lock Statement: Highlights section exclusivity and alignment with user goals. Convincing Statement: Outlines tailored benefits (e.g., networking, resources, leadership pathways). Full Access No additional content required beyond acknowledgment of full access. Welcome to [Section Name] Member sections are your gateway to exclusive resources, specialized tools, and unmatched opportunities** to grow professionally through mentoring, networking, and leadership pathways. Let’s help you unlock the next level of your career with these benefits. Headline: Welcome to [Section Name]! Description: Member sections are your gateway to exclusive resources, specialized tools, and unmatched opportunities to grow professionally through mentoring, networking, and leadership pathways. Log in to unlock these benefits and elevate your career. Headline: Gain Access to Exclusive Opportunities with One Simple Step Short Supportive Sentence: Log in to access resources and benefits designed to help you thrive. CTA Button: [Log In to Continue] Headline: Ready to Unlock Your Access? Short Supportive Sentence: Don’t wait—log in now to start your journey. CTA Button: [Log In] Headline: Welcome to [Section Name]! Description: It looks like you’re not currently a member. To enjoy this exclusive member benefit, you’ll need to join the ACC. Becoming a member will unlock incredible resources and opportunities while connecting you with a global community of cardiovascular professionals dedicated to transforming care and improving heart health. Headline: Become a Member of the ACC Short Supportive Sentence: Become part of a global community and access unmatched resources and opportunities like this Member Section. CTA Button: [Join Now to Unlock Your Potential] Headline: Take the Next Step Today Short Supportive Sentence: Join ACC now to access the tools and community you need for success. CTA Button: [Join Now] Headline: Welcome to [Section Name]! Description: The [Section Name] is tailored to empower [target audience, e.g., women cardiologists] with tools, mentorship opportunities, and leadership pathways to foster professional growth and connection. Headline: Unlock the Full Potential of [Section Name] Short Supportive Sentence: Join [Section Name] to access exclusive benefits, tools, and a supportive professional community. CTA Button: [Join the [Section Name] Today] Headline: Expand Your Membership Benefits Short Supportive Sentence: Don’t miss out—join [Section Name] now to unlock more opportunities. CTA Button: [Join Now] Headline: Championing Women’s Leadership, Professional Growth, and Wellness Description: The Women in Cardiology Section of ACC provides a unique platform for women cardiologists to: Strengthen their support system through professional connections. Enhance their skills via targeted mentoring and development programs. Access tools to prepare for leadership roles within the College. Our mission is to create an equitable and supportive community for women cardiologists, fostering inclusion and leadership across all specialties and career stages. Together, let’s build a more dynamic and inclusive cardiovascular field. Benefits List: Professional Online Community Mentorship Opportunities Leadership Pathways Exclusive Content Topic-Specific Tools CTA: [Become a Member of Women in Cardiology]

UI List of Objects

Thu, 31 Jul 2025 14:49:03 GMT

Back to Member Sections

Awards Distinguished

Thu, 31 Jul 2025 14:49:03 GMT

Remake and shift the multi locations of Awards.Making smart choices of how we present awards will make the engagement and understanding of the awards that are produced by the ACC. Outline: Low FI Wires Measurements: Increase the # of Applicants Measure Page Visitor to Conversion Increase Discovery and capture # of visitors passed along from awards Audit and Track the Types of Award Paths but attempt to simplify and coalesce the journeys.

Content Doc Blue Print

Thu, 31 Jul 2025 14:46:39 GMT

This document outlines the evergreen and changeable content blocks used across various user states for Member Section pages. The structure follows the naming convention: [USER STATE].[Page].[Optional Sub Page] and supports modularity and reusability. This document is used for: Mapping content for the components used across the different user states within the member section. Component Reference Tags. These tags are used to explain how or what needs to be collected for this block of content. Placeholder - Dynamic Defining dynamic placeholders within #evergreen or #data-model Mode content will use this the format [[LABEL NAME]] for example [[MEMBER SECTION CHAIR]] Evergreen - Any content block labeled evergreen is global and it content is not changeable. Data Model - Some content will just be place holder or an excel sheet to collect the data within so it can flooded into the final UI. Names, Locations, Emails etc. depending on the user interface design. Changeable - This content has placeholder content based on our prototype and is indicative copy intended to be changed by the Member Section. There might be notes with the content of max word count or other playbook rules that we would like the final content to follow. Dynamic - These elements are pre-built and are unchangeable rendering components from the CMS Note: These different content collection Tags for content areas will be labeled inline throughout this document where applicable. Member Section leads should focus only on updating the changeable areas with the provided indicative copy as a guide. User must be logged inContent blocker for users who are not authenticated
prototypeHeader: You Need to Log In Content: Log in to unlock these resources and start benefiting from our exclusive member perks.Action:
Login ()
#evergreen
Member Section Teaser Statement (GPB-0)
Member Section Key Benefits Bento (GPB-1)
Customer Service Message (GPB-2) User Must be a Member
prototype Content blocker for users who are authenticated but are not members of the College.Header: You Need to Member of College Content: This is an exclusive member perks become a member of the American College of Cardiology to gain access.Action:
Learn About Membership
#evergreen
Member Section Teaser Statement (GPB-0)
Member Section Key Benefits Bento (GPB-1)
Customer Service Message (GPB-2) Member of the college has no access to this Member Section
prototypeHomepage teaser for members without access to a specific section. Used to preview what’s inside the section and prompt upgrade.Page Title: Women in CardiologyHeader: Why Should You Join [[SECTION NAME]]?Content: The Women in Cardiology Section of the ACC offers a platform and opportunities to strengthen their professional support system, skills and the future of the community. Active involvement in the Section provides leadership skills development and understanding the governance structure and avenues to leadership within the College.Note: max characters 300
#changeableHeader: MissionContent: Our mission is to foster a supportive community that advocates for gender and career equity, empowering women cardiologists across all specialties and career stages. Join us in creating a more inclusive and dynamic field in cardiovascular medicine.Note: max characters 250
#changeable
Icons can be selected from font awesomeContent with Icon: Professional Online Community icon: fa-users Mentorship Opportunities `icon: fa-circle-user-circle-user Leadership Pathways `icon: fa-user-group-crown Exclusive Content icon: fa-sparkels Member Section Specific Resources icon: fa-folder Topic Specific Tools fa-wrench-simple Note: max characters per item 30
#changeable
Teaser Masthead Lock (GPB-3)
Teaser Micro Banner (GPB-5)
Teaser Homepage Call to Action (GPB-6)
Teaser Content Cards (GPB-7)
prototypeNo Access to Member Section - Member Must Join Section Teaser block introducing the section's leadership and workgroups and purpose for users without access.Page Title: AboutHeader: About Content: Dignissimos sed deserunt est non. Aliquam nam aut quam. Voluptas ut vel voluptates aliquam mollitia enim consequatur. Quas quisquam natus dolor eos consequatur culpa. Fuga manam ten. (200 Characters)Note: 200 max-characters
#changeableUI Design: CardImage: Aspect 8x10 Full Name: Postion Label: Chair | Past Chair
#data-modelUI Design: Simple split grid with backgroundList of Full Names
#data-modelHeader: Workgroups Content: Svel libero ut rerum repudiandae aut est paritur minus vero. Delectus ea est nostrum quae dolores. Delectus nostrum nihil et ad enim. (150 Characters)Note: Max Characters 150Follow up Copy: Some Message - (Become a Member of this Section to support and shape these initiatives)Note: Max-Characters 100
#evergreenUI Design Design Simple Card GridWorkgroup Name: Workgroup Short Description: 100 - 150 Characters Max
#data-model
Teaser Masthead Lock (GPB-3)
Teaser Follow Up Call to Action (GPB-4)
prototypeNo Access to Member Section - Member Must Join Section Highlights member section resources available upon upgrade.Page Title: ResourcesHeader: Resources Content: From clinical tools to exclusive publications, this member section membership provides curated resources to elevate your professional career. See a sample bellow.
#evergreen[[Resource Categorization]][[Link Name]]
#changeable
Teaser Masthead Lock (GPB-3)
Teaser Follow Up Call to Action (GPB-4) Description: Previews announcement and news content available in the section. Page Title: NotificationsHeader: Notifications Content: Stay up-to-date with section specific announcements, event alerts, and section-specific opportunities.{{-- Notification Feed--}}
#dynamic
Teaser Masthead Lock (GPB-3)
Teaser Follow Up Call to Action (GPB-4) These are the fully accessible pages for members with upgraded access to the Member Section.Header: Notifications Sub-Header (Max 75 Characters): Content (Max 200 Characters): Stay up-to-date with section specific announcements, event alerts, and section-specific opportunities.
#evergreen
UI Design: https://acc-style.github.io/PrototypingACCorg/ui-gold/card-photo/Full Name Position: Chair | Past Chair Button Label: Message from Chair Link To: Message from Chair - Page
#data-model
Icons can be found on this page Font AwesomeHeader: MissionUI Design: Icon header with description (URL)Item Header: 60 Characters Max Description: 150 Characters Max
#data-model Icon: fa-people-dress Header (Max 60 Characters): Support Women Cardiologists Description (Max 150 Characters): Help women build successful careers in cardiology by offering training, mentoring, and leadership programs through the ACC.Icon: fa-up-from-line Header (Max 60 Characters): Encourage More Women to Choose Cardiology Description (Max 150 Characters): Improve training programs and show women residents the variety of career paths available in cardiology.Icon: fa-chalkboard-user Header (Max 60 Characters): Mentor Young Women Description (Max 150 Characters): Create mentoring and preceptorship programs that inspire young women in high school, college, and medical school to consider cardiology as a career.Icon: fa-scale-unbalanced Header (Max 60 Characters): Fairness for Women Cardiologists Description (Max 150 Characters): Advocate fair treatment of women cardiologists, especially equal pay and chances to advance in their careers.
#changeable
Icons can be found on this page Font AwesomeHeader: FocusUI Design: Icon header with description (URL)Item Header: 60 Characters Max Description: 150 Characters Max
#data-model Icon: fa-chart-network Header (Max 60 Characters): Networking Description (Max 150 Characters): Build meaningful connections with peers and mentors to share experiences and grow your cardiology networkIcon: fa-users-medical Header (Max 60 Characters): Leadership Workshops Description (Max 150 Characters): Join focused sessions to strengthen leadership skills, advocacy, and career growth for women in cardiology.Icon: fa-route-interstate Header (Max 60 Characters): State Chapter Network Description (Max 150 Characters): Connect with local WIC chapters for regional events, support, and opportunities to make an impact in your area.
#changeableHeader: About [[Member Section Label]]Content:
Learn More about the Leadership and Workgroups of this Section
#evergreenHeader: Notifications Content: Stay informed with the latest updates, event alerts, and announcements from your member section. Link: {-- Link | ../notifications --} View All Notifications Header: Initiatives & Activities Content:
Get involved in initiatives and activities that connect members and strengthen the section’s community. View Full List of initiatives and activities.
#evergreenHeader: Resources Content: Member-only webinars, toolkits, and content designed to strengthen your career and clinical practice. Link: {-- Link | ../resources --} ExploreHeader: Library Content: Browse articles, research, and content created by this section and shared with the wider cardiology community. Link: {-- Link | ../library --} ExploreNote: Card with button
#evergreen
UI Design: https://acc-style.github.io/PrototypingACCorg/ui-gold/split-content-block-half/Feature Thumbnail: Feature Label: Feature Short Teaser: 200 Characters Max Link Label:
#data-model
UI Design: https://acc-style.github.io/PrototypingACCorg/ui-gold/split-content-block-thirds/Feature Thumbnail: Feature Label: Feature Short Teaser: 100 Characters Max Link Label:
#data-model
Doc Matter Call to Action (GPB-8)
Twitter Feed (GPB-11) Overview of the section’s purpose and initiatives. May include leadership info and chair messages.Header: About Sub-Header (Max 75 Characters): Driving the mission and vision through leadership and collaboration.Content: (Max 200 Characters) The leaders and workgroups behind this section advance the mission and vision, guiding priorities and creating meaningful impact.
#evergreen[QUOTE][Name of Chair][Chair | Past Chair]
#changeableHeader: Learn More about this sections Leadership Content: Shaping the experience and the initiatives is the member section leadership. Button: {-- Link: /Leadership --} Leadership
#evergreenHeader: Mission Content: To support and empower women in cardiology by providing mentorship, training, and leadership opportunities. We are committed to fostering equitable career advancement, advocating for fair treatment, and inspiring the next generation of women to pursue cardiology through education, advocacy, and connection. Header: Vision Content: A future where women thrive as leaders in cardiology—supported by robust networks, equal opportunities, and inspiring pathways that encourage young women to see cardiology as a fulfilling and accessible career.Card Design Image: Member Section Texture Workgroup Title: Workgroup Teaser: Max Character 150
#data-model Button: {-- Link: /about/workgroups/ --} View All Workgroups
Section Leadership Call to Action (GPB-10) Lists leadership members with photos and bios.Design: Card Full Name: Postion Label: Chair | Past Chair
#data-modelHeader: Section Leadership Council Bulleted List: [Member Full Name][image path] Cite: Where the photo was taken.
Section Leadership Call to Action (GPB-10) Lists of workgroups and the important detailsHeader: Workgroups Content (Max 200 Characters): Work Groups are a great way to get involved in Section initiatives, share your perspective, and help drive the priorities that matter most to you. Explore the opportunities below to make a difference—and elevate your impact and visibility within the ACC.
#evergreenTitle: Description: Max Chacters 200 Initiatives and Focus: Bulleted List | List Item with Max Character 80 Accepting New Members: True|False Full Name of Chair: Title and Institution of Chair: Location City State of Chair:
#data-modelHeader: Interested in Getting Involved Content: Learn more about being able to interact and join in a work group by contacting the member section admin Button: Contact Us Button Link: [[Mail To Staff Liason]]
#evergreenDescription: Personalized message from the section chair or leadership.Header: Message From the Chair[Portait Image][Chair Full Name][Chair]
#data-modelContent: Attach Word Document (Simple Rich Text Only No Image or Special Formatting)
#changeableDescription: Library of tools, downloadable documents, or practice-related materials.Header: Resources Sub-Header (Max 75 Characters): Exclusive tools and content to support your practice and career.Content: (Max 200 Characters) Access webinars, toolkits, and learning content created to help members grow professionally and deliver better patient care.
#evergreenCategory of the Resource: Use labels that expresses the Intent of the content like how the user would use it. Resource Readable Label: Not always the title of the page or resource your linking because this link should express what the user is going to get vs the page title we are directing them to. Resource Link: Title of the Resource: this is used in the title tag of the link for greater context and SEO Note: Lists of anything longer then 9 are harder to skim and read
#data-model News, updates, or events relevant to the member section audience. This should be reserved to actionable items and not just content items to be consumed or read/downloadHeader: Notifications Sub-Header (Max 75 Characters): Timely updates to keep you connected and informed.Content: (Max 200 Characters): Stay up-to-date with announcements, event alerts, and section-specific opportunities relevant to your community.
#evergreen{{-- Notification Feed--}}
#dynamicExpanded or specialized resource published through out the college.Header: Library Sub-Header (Max 75 Characters): Published content showcasing the section’s contributions. Content: (Max 200 Characters): Explore articles, research, and resources produced by the section and shared with the wider cardiology community.{{-- Library Feed: All the files on ACC.org that have been cited with the support of this Member Seciton --}}
#dynamicListing page Page Title Initiatives & ActivitiesHeader: Initiatives & Activities Sub-Header (Max 75 Characters): Opportunities to engage and make an impact with the section. Content: (Max 200 Characters): Join initiatives and activities that connect members, foster collaboration, and strengthen the section’s community and goals.
UI Design: https://acc-style.github.io/PrototypingACCorg/ui-gold/split-content-block-thirds/Feature Thumbnail: Feature Label: Feature Short Teaser: 100 Characters Max Link Label:
#data-modelThese components are commonly referenced across multiple states and/or pages to maintain consistency.Header: Member Section: Sub-Header: [[Member Section Name]]Content: This section offers women cardiologists opportunities to strengthen their professional support system and skills.Note: Max 300 characters
#changeableContent with Icon: Membership Benefit Professional Community Access Restricted Exclusive Content Leadership Pathways Topic Specific Tools Note: Max 25 characters per bullet
#evergreenContent: Need Help?
Contact Member Care
800-253-4636, ext. 5603
202-375-6000
#evergreenHeader: Member Section Access Required!Sub-Header: Extend Your Membership Today!Content: You've arrived at a Member Section page that you don't have access to. This is a gateway to our exclusive member benefits. These benefits, designed specifically for [[Member Section Name]]. Member Sections offer access to specialized communities, valuable content, and exciting opportunities to make a real impact in your field.Action:
Manage Membership (Icon)
#evergreenHeader: (Icon ) Unlock This Content Sub-Header: Join this Member Section Today.Content: Want to gain access to all of the content and so much more? Manage your membership today to join this Member Section and unlock all the content and benefits of this section.Action:
Manage Membership (Icon)
#evergreenHeader: [SECTION LABEL]Action:
Manage Membership (Icon)
#evergreenHeader: Join This Section Today Content: Manage your membership and add this sections to gain full access and full benefits.Action:
Manage Membership (Icon)
#evergreenHeader: Explore This Member SectionHeader Image Content Button Label Button Link Header: About Content: Learn more about the focus and the leadership of this section.Button: Explore {-- link to: the teaser about page--}Header: Notifications Content: Stay up to date with this section via its notification that can also be sent directly to your email.Button: Explore {-- link to: the teaser notifications page--}Header:Library Content: See how this section makes an impact on the voice and knowledge shared by the ACC.Button: Explore {-- link to: the library page--}Note: Max 25 characters per bullet
#evergreenHeader: DocMatter SubHeader: Connecting You to the Conversations that Matter Content: Connect with [Member Section Name] on DocMatter, a platform for ACC Members to ask case questions and learn best practices from peers. Button: Go to DocMatter {-- Button | Link :--} Customer Care Message:
Questions or Issues? Contact ACC Member Care.Note: Follow Up Call to Action
#evergreenHeader: Connect With Section Leadership Content:
Join conversations on X with #sectionHash or on our professional social platform DocMatter. Button: Go to DocMatter {-- Button | Link :--} Customer Care Message:
Questions or Issues? Contact ACC Member Care.Note: Follow Up Call to Action
#evergreenContent: Join the Conversation on X
#ACCWIC
@ACCinTouch
#evergreen

ACCSAP Content Comparison

Wed, 23 Jul 2025 17:28:29 GMT

SAPs

Wed, 23 Jul 2025 17:02:49 GMT

Modernizing the Product Pages with UX and EDS Best Practices.

GREY BOX -- CCKE- OUS

Mon, 21 Jul 2025 16:01:56 GMT

OUS Branding MarkIn the wrongplace?Intro Text- Who is this for andwhat is it. - What you will getSister CCKEStart ApplicationApplyPricingApply TodayApplyThe ExamPrepareAfter the ExamLearn MoreAbout the ExamProduct PageAbout the Examneed help with your purchase?FAQ#Purchase Help#Getting Results#How is it writtenThe ExamWhat toexpectWhen is thenext Examlearn more about the ExamStart ExamStartAlters duringtesting windows#What to Expect#Timing#SampleQuestions#...#Next Exam WindowSisterProduct PageStart ApplicationApplyfaqs#Study HelpAbout the ExamAfter the Examhere is the scores from older examsThe Last ExamHistorical Exam HubsExam hubHistorical HubsHistorical HubsExam hubFAQ

Matrix Chart Data

Fri, 06 Jun 2025 15:29:07 GMT

<- Back
X-Axis Unique Content
Y- Axis Unified Experience
X-Axis Content Locking
Y-Axis Onboarding Experience
X-Axis Audience Focus
Y-Axis Tone & Expression

UI Notes

Wed, 04 Jun 2025 16:17:17 GMT

<- Back✅ Always (> 50%) ➕ Used in some occasions (<50%) ❌ Rare or never (<20%) ACC showcases the most meta-data around the article teaser comparative to its competitors. Most of the associations deal with their search result teasers differently than the embedded page teasers. HFSA -- probably has the most confusing search results across the board. They're doing some form of grouping, but it doesn't come across how I think they intended it to. Hard distinguished articles Multiple levels of text hierarchies and use of multiple colors. hard to distinguish what is interactive versus headline

Ad Usage

Wed, 04 Jun 2025 16:16:27 GMT

Detail Notes Excel

WhatIf

Wed, 04 Jun 2025 15:44:11 GMT

Summary: Hypothesis: Outline: Additional Notes:

ACC Redesign

Wed, 04 Jun 2025 15:44:10 GMT

The site is getting old time for a new coat of paint.

Strategic Glossary of Page Concepts in ACC.org

Wed, 04 Jun 2025 15:44:05 GMT

Page Concept Types ① Home Page
② Concept Anchors
③ Initiatives (Goal-Oriented Modules)
④ Product Groupings
⑤ Product Destinations (Transactional Pages)
⑥ Standard Pages
⑦ Listing Pages Information Architecture
How These Pages Associate with Each Other
General I.A. Guidelines The main entry point of the website, designed to provide immediate orientation, highlight major initiatives, latest updates, and guide users quickly toward primary goals. Use Case: First-time visitors, returning users seeking major updates, initial brand impression. Why Used: Creates immediate clarity and positions organizational priorities upfront. Branding & UI Elements: Take over, Hero Image, Feature Triptych... Role in IA: The central entry point. Highest-level orientation, connecting users quickly and intuitively to key site sections. Prioritizes major pathways, brand introduction, and timely highlights. Rules & Recommendations: Use clearly defined navigation to major Concept Anchors and prioritized user tasks. Limit content to essential items for quick user orientation (less is more). Regularly update to reflect organizational priorities and timely initiatives. When to Use: Always present as the top-level entry page. Avoid: Do not overload with detailed content or overly transactional messaging.
Pages offering high-level overviews of the organization's core concepts, primary service areas, or central offerings. They orient users by clearly presenting a broader narrative or theme. Example Page: About US Use Case: Navigation entry points for broad organizational topics, connecting various subpages and initiatives. Why Used: Humanizes the organization, reinforces brand values, and simplifies access to deeper content.
Branding & UI Elements: Concept Hero with Feature, Grid Bento, UL Icon Text List of Icon ULs, Grouping Zones, Section Shading Role in IA: Provide clear, user-friendly overviews for broad organizational pillars. Anchor navigation to strategic themes. Introduce voice, tone, and topic landscape. Rules & Recommendations: Connect to Initiatives, Product Groupings, and Standard Pages. Reflect organization-wide narratives or verticals. Avoid overwhelming detail—keep it narrative and directional. When to Use: When multiple related initiatives or products are associated with a central idea. Avoid: Don’t use for deeply detailed or transactional content.
Targeted microsites or sections devoted to specific organizational efforts or campaigns, often incorporating unique branding or visual differentiation. These modules are action-focused, with clearly defined user goals Example Page: Advocacy | UX Use Case: Advocacy, fundraising, campaigns, accreditation explanation. Why Used: Enhances clarity of purpose, supports targeted user journeys, simplifies complex messaging.
Branding & UI Elements: Microsite Hero Banner, Secondary Action Card, Cards, Icon & Content Grid List, Grouping Zones, Section Shading Role in IA: Specific journeys with clear purpose and outcome. Often stand apart structurally or visually. Internal navigation can be isolated from the main site to support clearer marketing language, simplified instructions, and more targeted messaging. Rules & Recommendations: Must articulate the purpose and offer a focused action. Allow for deviation in branding when needed. Link from Concept Anchors or Home Page. When to Use: When a program has a goal, outcome, and distinct message. Avoid: Avoid for purely informational content or where cohesion with parent content is critical. Pages that consolidate and categorize related products, services, or offerings into logical collections. These pages help users quickly explore and compare similar or complementary options. Use Case: Displaying grouped learning programs, events, or tools. Why Used: Improves usability and product discovery. Branding & UI Elements: Product Banner, Icon & Content Grid List, Cards, Grouping Zones Role in IA: Bridges between concepts and conversion. Allows logical exploration. Internal navigation can be separated from broader site structures to focus user attention on product discovery and purchase readiness. Rules & Recommendations: Structure by audience, topic, or value. Must clearly connect to Product Destinations. When to Use: When users benefit from browsing options. Avoid: Avoid grouping unrelated offerings or overloading the page with decisions.
Detail-rich pages meant to drive action—purchase, register, subscribe. Detailed, user-action oriented pages centered around specific products, events, or learning opportunities. These pages incorporate transaction-focused elements such as pricing, purchasing options, registration, personalization, and targeted marketing content. Example Page: Prototype SAPs Use Case: Events, certification programs, subscription services. Why Used: Central to conversion. Branding & UI Elements: Product Banner, Conversion Buttons, Price Bentos, Icon & Content Grid List, Cards, Grouping Zones Role in IA: The action endpoint for campaigns or marketing. Rules & Recommendations: Be persuasive and precise. Avoid unrelated links—stay on message. When to Use: Directly from emails, ads, or Product Groupings. Avoid: Avoid placing deep education or concept background content here. Informational pages that support other content areas but don’t need visual distinction. Use Case: About pages, FAQs, mission statements, technical explanations. Why Used: Provide clarity, institutional knowledge, or low-maintenance detail. Branding & UI Elements: Default theme styling, minimal content modules. Role in IA: Reliable content support. Inherited styling from parent Concept Anchor or Initiative. Rules & Recommendations: Maintain consistency in layout and tone. Link outward sparingly. When to Use: For maintenance-friendly foundational content. Avoid: Don’t force these into deep journeys—keep simple. Pages that surface grouped or filterable content based on shared logic (e.g., date, topic, type). Use Case: Article archives, event calendars, directory listings. Why Used: Enables users to explore at their own pace. Branding & UI Elements: Search/filter controls, cards or table view, consistent previews. Role in IA: Serve as content aggregators. Often feed from CMS or tag-based logic. Rules & Recommendations: Label clearly and design for repeat use. Allow exploration but keep structure rigid. When to Use: For large, growing sets of content. Avoid: Avoid making them content endpoints—always lead to something richer. Home Page → Concept Anchors → Initiatives/Product Groupings → Product Destinations or Standard Pages Home Page → Product Groupings → Product Destinations → Conversion actions (e.g., purchase) Home Page or Concept Anchors → Listing Pages → Standard Pages or Product Destinations Always connect broader, conceptual content (Concept Anchors) to detailed or goal-oriented content (Initiatives, Products, Listings). Clearly define user goals on transactional pages; remove or minimize unrelated content. Maintain consistent user expectations through predictable page structures and clear navigational relationships.

Y-Axis Tone & Expression

Wed, 04 Jun 2025 15:44:02 GMT

<-- Back to Data(from Dull/Flat to Fully Expressive) -4: Academically Formal Language mirrors academic journals or internal policy documents. Densely written, passive voice dominates. Heavy use of jargon, acronyms, and formal third-person. Prioritizes precision over connection—reads like it’s meant for peer reviewers, not people. -3: Rigid and Impersonal Tone is extremely formal and serious. Often sounds like a compliance document or corporate report. Still technical but spells out terms. Reads like it’s trying to avoid liability more than inform or inspire. -2: Dry and Technical Information is accurate but lacking human warmth. Text reads like textbooks or white papers—clarity exists, but personality is absent. Occasional headings help, but voice is purely mechanical. -1: Flat with Occasional Warmth Generally neutral and professional, with rare moments of friendliness. Might use plain language or some light subheads, but lacks a consistent effort to be human or engaging. 0: Approachable Professional Balanced and clear. Uses active voice and plain language without dumbing it down. Minimally expressive but readable and human. Feels like it was written by a professional for another professional—welcoming without being casual. +1: Slightly Conversational Begins to use softer language, rhetorical questions, or more inviting phrasing. Feels less like a document and more like a person. +2: Friendly and Professional Conversational, confident, and approachable. Clear identity in voice without losing credibility or clarity. +3: Warm and Engaging Actively uses tone to build rapport. Strong emphasis on accessibility, encouragement, and human touch. May include inclusive phrasing and emotional cues. +4: Fully Expressive Bold, vibrant tone with emotional resonance. Uses storytelling, rhetorical flair, and confident voice to create deep engagement and connection.

Y-Axis Onboarding Experience

Wed, 04 Jun 2025 15:44:02 GMT

<-- Back to Data(from Absent to Fully Welcoming) -4: Off-Site or Hidden There is no visible path to membership from the main site. Membership is handled on a separate domain, microsite, or poorly connected property. The process feels buried or unrelated. -2: Minimally Present Membership exists but is not emphasized. A small “Join” link may be present, but there is little information about benefits, processes, or why someone should join. 0: Neutral Presence The site includes a membership section or page, but it’s not highlighted in the primary user journey. Information is available but not persuasive or well integrated. +2: Guided Invitation Membership is clearly positioned as a part of the organization’s purpose. There's a clear, accessible call to action, with content describing the benefits and process, even if modest in presentation. +4: Fully Welcoming The site uses engaging language and visuals to invite membership. The value proposition is clear, and onboarding is embedded into the experience—through guided flows, testimonials, benefit breakdowns, and visible CTAs across the site.

Y- Axis Unified Experience

Wed, 04 Jun 2025 15:44:01 GMT

<-- Back to Data -4: Fully Disconnected The journal and main site feel entirely unrelated. There is no shared branding, platform, or navigation. A user would not be able to tell the journal is part of the same association. -3: Strongly Disjointed Minimal branding consistency. There are no shared navigational elements, visual language diverges significantly. The journal feels externally hosted or partner-run. -2: Loosely Connected Some visual cues may hint at a shared origin (e.g., small logo in footer), but there are no platform integrations. Navigation between the two requires separate logins or feels like entering a different ecosystem. -1: Marginal Connection The journal is linked through a general navigation element or section on the main site, but branding alignment is weak and there’s no UX continuity. 0: Neutral Alignment The sites reference one another, have similar tone or brand palettes, but still operate independently. They live in parallel rather than in union. +1: Light Branding Alignment Shared branding (colors, logos) is present, but UX remains distinct. Some minor crossover (e.g., shared footer elements). +2: Branded Pathway There’s a branded experience leading from the main site to the journal, and some consistent UX elements (like nav structure or shared user accounts). +3: Cohesive Design Language Both properties share a design system, layout patterns, and navigation is continuous or consistent. It feels like an extension of one site to another. +4: Fully Unified The journal and main site are on the same domain or subdomain, with seamless navigation, identical branding, and fully integrated UX. It feels like one holistic site.

X-Axis Unique Content

Wed, 04 Jun 2025 15:44:01 GMT

<-- Back to Data(from Fully Duplicated to Fully Distinct) -4: Fully Duplicated The main site republishes journal content directly, with minimal or no modification. Articles appear verbatim or are routinely mirrored. -3: Derivative Duplication The main site frequently features adapted or summarized versions of journal articles. There’s heavy content recycling in different formats (e.g., blog posts, highlights, infographics). -2: Featured Cross-Publication Journal content is regularly spotlighted on the main site through excerpts, featured articles, or summaries. There’s a clear editorial flow from journal to main. -1: Light Journal Echoing Occasional journal content appears on the main site—select articles or issues are highlighted in news sections or as updates. 0: Reference Integration The main site discusses the journal broadly, possibly with multiple references or deep links, but does not reuse actual content. +1: Deep Link Framing The main site promotes its journal through deep links to individual issues or articles, but without embedding or echoing the content itself. +2: Journal Link Presence The main site acknowledges the journal’s existence and links to it (usually at a high level like “Our Journal”), but without further editorial emphasis or content reuse. +3: Minimal Journal Exposure Journal presence is limited to a basic link or navigation tab. The main site content remains separate and self-contained. +4: Fully Distinct There is no shared content between the main site and journal. The journal is neither referenced nor discoverable through content pathways. Each site has its own editorial ecosystem.

X-Axis Content Locking

Wed, 04 Jun 2025 15:44:01 GMT

<-- Back to Data(from Fully Locked to Fully Open) -4: Fully Locked Nearly all content is inaccessible without logging in or becoming a member. The public view offers only basic information (e.g., About page or login screen). -3: Highly Restricted Most core content—such as articles, resources, tools, and even some navigation—is locked behind a member wall or requires login. Public access is very limited. -2: Partially Locked Many areas of the site (e.g., entire article categories, tools, or educational resources) require a member login. Public visitors encounter frequent access walls. -1: Targeted Restrictions Specific high-value content types (e.g., publications, event registrations, or toolkits) are gated for members, but general site content is open. 0: Neutral Locking A mix of open and gated content, with some clear benefits reserved for members but without pervasive access control across the site. +1: Light Gating Most content is accessible without login, but membership offers enhanced experiences (e.g., downloads, personal dashboards, advanced tools). +2: Minimal Locking Only select areas, like purchasable products, exclusive webinars, or certifications, require member login. General content is open and searchable. +3: Open with Optional Login The site operates fully in public view. Login is only needed for personalization or e-commerce transactions, not for accessing substantive content. +4: Fully Open No clear locking mechanism is visible. All content appears available to the public, with little to no incentive or requirement to become a member for access.

X-Axis Audience Focus

Wed, 04 Jun 2025 15:44:01 GMT

<-- Back to Data(from Narrow/Insider-Focused to Fully Inclusive) -4: Hyper-Specialized Professionals Content is designed for a narrow expert audience within a medical subspecialty (e.g., electrophysiologists, heart failure specialists). Assumes advanced, specialized knowledge. -3: Specialized Professionals Targets a specific field of professionals (e.g., general cardiologists, cardiovascular surgeons). Language and tools are tailored for those practicing in that domain. -2: Field-Specific Professionals Appeals to the full range of professionals within a medical field (e.g., all roles within cardiology including clinicians, researchers, and educators). Still assumes a shared base of field-specific knowledge. -1: Broader Healthcare Professionals Engages professionals outside the core field, such as nurses, physician assistants, technicians, and allied health staff working in related areas (e.g., cardiovascular support teams). 0: Educated Patients Engages with the entire professional community and engages with the educated patients. +1: Informed or Affected Public Accessible to patients, caregivers, or individuals affected by health issues (e.g., heart disease), though professional content remains distinct and primary. +2: Educated Public Reaches out to general audiences interested in health topics, such as students, advocates, or fitness professionals. Medical language is simplified where needed. +3: Public-Oriented Content is framed for lay audiences with little or no medical background. Emphasis is on education, awareness, and broad understanding. +4: Fully Inclusive Designed to be understood by the general public regardless of background, with clear, jargon-free messaging and wide community appeal.

Readability Evaluation Checklist and Rating Scale

Wed, 04 Jun 2025 15:44:01 GMT

Evaluate each page or section on a 1–5 scale:Total Scores: 7–14: Needs Significant Improvement 15–21: Below Average; Requires Revision 22–28: Average; Could Benefit from Minor Edits 29–35: Good; Minor Tweaks Only 35+ : Excellent; Highly Readable Run quantitative tests (e.g., Hemingway App, Readable.io). Evaluate qualitative UX criteria listed above. Score each criteria using the checklist above. Provide actionable recommendations (e.g., simplify sentence structures, break paragraphs down, reduce jargon). Present results clearly to stakeholders: Summarize scores with a break down. Establish clear criteria for readability. Typical dimensions include: Reading Level: Grade-level comprehension needed (e.g., 8th grade, 12th grade, college). Sentence Length: Average number of words per sentence (ideally 15-20 words for general audiences). Paragraph Density: Number of sentences per paragraph (ideally 2-4 sentences per paragraph). Vocabulary Complexity: Usage of simple, everyday words versus specialized or complex vocabulary. Jargon and Acronyms: Frequency and necessity; clarity in defining specialized terms. Sentence Structure: Use of active vs. passive voice (favor active). Content Length: Total word count for sections or pages relative to user attention span.

What do we want to learn from Redesign Planning

Wed, 04 Jun 2025 15:44:01 GMT

A|B Testing with content and design Back End/ Editing Loading Times Dev Time Personalization Duplicative Writing Style Accessibility Personalization Member Benefits Guided Experience based on Purchase Life Cycle. Changes are are jarring Consistency is good New experience is always hated by someone What is the scope of the Redesign. Are we just starting over? are we keeping with best patterns and applying consistency? Are we just removing the dead weight and fixing problems? Duplicity SEO/SEM interviews with staff (member care, IT, etc.) MI surveys Foresee interviews with non member users Change management historically is weak at the ACC Silos are real and we are not a flat organization! Push back from Silos, Stakeholders, Members Traditions are hard to break ACC is not an enforcer - how you need to work

Web Based Heuristics

Wed, 04 Jun 2025 15:44:01 GMT

Ensure the site provides immediate feedback for user actions, such as logging in, submitting forms, or loading pages, so users know their actions are being processed. The content and navigation should use terms and language that resonate with your audience (e.g., "My Courses," "Membership Dashboard," "Explore Articles") to make the site intuitive. Users should be able to easily navigate between sections, undo actions, and go back without confusion, especially when managing membership details or course enrollments. The design, layout, and labeling should remain consistent across the site, whether users are in the membership area, reading articles, or accessing educational content. Provide users with clear, guided steps to minimize mistakes, particularly in processes like signing up for a membership, enrolling in a course, or making a purchase. Reduce the need for users to remember details by displaying key information clearly, such as membership status, progress in courses, and recommended articles. Design for both new and experienced users, allowing shortcuts and advanced features (like filtering or bookmarking) for members who visit frequently while keeping it simple for new visitors. Ensure that pages are visually simple and easy to navigate, focusing on the most important actions like reading articles, accessing courses, or checking membership benefits. If something goes wrong, provide a clear explanation and actionable steps to resolve the issue, such as payment problems or content loading errors. Ensure that users can quickly find help through FAQs, support articles, or a contact option, especially when they are having trouble with their membership, accessing courses, or reading content.

Direct and Indirect Completive Landscape - Survey Questions

Wed, 04 Jun 2025 15:44:01 GMT

To effectively explore our competitive landscape, this survey aimed to uncover both direct and indirect competition regarding features and benefits offered by ACC.org. While direct comparison against our field is valuable, we should also consider how we compete on features and user experience beyond the cardiovascular care space. Users are multifaceted, interacting daily with experiences related to education, membership, events, reading articles, and news across various industries. Understanding how these elements are presented on the best platforms across the web will provide insights into expectations and best practices that can elevate ACC.org. This survey will help reveal which competitors are challenging ACC.org regarding user experience across offerings like education, certifications, membership, events, and news engagement. Which organizations come to mind when you think of ACC's direct competitors in cardiovascular care and education? Text Input Which websites or platforms do you use to stay informed, get inspiration from, or see what is an industry standard for education and professional development in cardiovascular care? Text Input For the platforms you use to "stay informed" what do they do better than ACC.org? Checkbox Select All User experience (UX) Design Navigation Content quality Personalization Mobile Experience Search functionality Performance & Page Speed For the platforms you use to "stay informed" what does ACC.org do better? Checkbox Select All User experience (UX) Design Navigation Content quality Personalization Mobile Experience Search functionality Performance & Page Speed Leave any other comments.- Other (please specify) Education: How do you interact with educational content on different platforms in your daily life, and what is the best example of a platform or website that provides educational content effectively? Text Input For the platform you stated as the best for 'Education,' what do they do better than ACC.org? Checkbox Select All User experience (UX) Design Navigation Content quality Personalization Mobile Experience Search functionality Performance & Page Speed Other (please specify) Maintaining Certification: How do you interact with platforms for maintaining certifications or credentials, and what is the best example of a platform or website that supports maintaining certifications effectively? Text Input For the platform you stated as the best for 'Maintaining Certification,' what do they do better than ACC.org? Checkbox Select All: Checkbox Select All User experience (UX) Design Navigation Content quality Personalization Mobile Experience Search functionality Performance & Page Speed Other (please specify) Standards & Best Practices Repository: How do you interact with repositories of standards and best practices on different platforms, and what is the best example of a platform or website that serves as a standards and best practices repository? Text Input For the platform you stated as the best for 'Standards & Best Practices Repository,' what do they do better than ACC.org? Checkbox Select All User experience (UX) Design Navigation Content quality Personalization Mobile Experience Search functionality Performance & Page Speed Other (please specify) Membership Organization: How do you interact with membership organizations on different platforms, and what is the best example of a platform or website that provides a great membership experience? Text Input For the platform you stated as the best for 'Membership Organization,' what do they do better than ACC.org? Checkbox Select All Event & Conference Hub: How do you interact with platforms for discovering and registering for events or conferences, and what is the best example of a platform or website that effectively manages events and conferences? Text Input For the platform you stated as the best for 'Event & Conference Hub,' what do they do better than ACC.org? Checkbox Select All Staying Up-to-Date on News: How do you interact with news platforms to stay up-to-date, and what is the best example of a platform or website that provides timely and relevant news effectively? Text Input For the platform you stated as the best for 'Staying Up-to-Date on News,' what do they do better than ACC.org? Checkbox Select All

JACC -★- Journal of American College of Cardiology

Wed, 04 Jun 2025 15:44:00 GMT

<- Back Membership & Networking Opportunities: ★★☆☆☆ Donations & Philanthropy: ★☆☆☆☆ Events: ★★★☆☆ Scientific Publications / Latest Science: ★★★★★ Practice Support Resources: ★☆☆☆☆ Patient-Facing Tools & Content: ★☆☆☆☆ Education: ★★★☆☆ Advocacy: ☆☆☆☆☆ Membership & Networking Opportunities: JACC.org includes limited information on membership engagement and networking, which can be difficult to find. Networking opportunities are typically tied to scientific conferences and may appear briefly in the homepage carousel. There's potential confusion between journal subscriptions and ACC membership — subscriptions are a type of membership and users can subscribe without being ACC members. There is no clear connection is made between JACC content and ACC member benefits. The site could better promote member value by linking to ACC membership. Donations & Philanthropy: JACC.org hosts very few articles that reference donations and philanthropy on the site, but no direct links or dedicated sections for donations. Search engine results return article links related to organ donation on JACC.org. Events: Specific events are temporarily promoted on the website carousel, however users must access the Events section using the navigation menu. The Events section mainly provides simultaneous publications and research presented at large scale scientific. Scientific Publications / Latest Science: Scientific publications are the core focus of JACC.org, with the latest research prominently displayed on the homepage and accessible through top-level navigation. Practice Support Resources: The website offers practice guidelines and clinical documents, which are valuable resources for practitioners. However, there is no help and guidance on how to professionally run a practice. Patient-Facing Tools & Content: While some articles mention patient-facing tools, there is no dedicated section or prominent links for patient resources on the homepage or main navigation. Users would need to search extensively to find such content, indicating a low emphasis on patient-facing initiatives. Education: Access to educational content (CME/MOC) is present on JACC.org, including articles on medical education. However, the page content directs users to Learn.acc.org. Advocacy: JACC.org lacks a dedicated advocacy section. Policy topics may appear in articles, but formal advocacy efforts are not visible or accessible from the site.

HRS -- Heart Rhythm Society

Wed, 04 Jun 2025 15:44:00 GMT

<-- back to competitive analysisReadability: Score: 28 – Average; Could Benefit from Minor EditsBreakdown: Reading Level: 3 – 10th–12th Grade Sentence Length: 3 – 20–25 words avg. Paragraph Density: 4 – Brief paragraphs Vocabulary: 3 – Mixed Jargon Usage: 3 – Occasional, defined Sentence Structure: 4 – Mostly active Scannability: 4 – Good CTA Clarity: 4 – Clear Estimated Visitors: ~80,000–100,000 monthly (based on SimilarWeb and traffic intelligence)Estimated Membership Numbers: ~8,000+ members (from HRS annual reports and public sources)Explanation: The Heart Rhythm Journal is completely separate from the HRS website: It operates on an entirely different domain (heartrhythmjournal.com), run through Elsevier. Branding, navigation, and user journeys are completely siloed — there are no obvious cross-links back to the HRS main site, nor any integrated experience for HRS members. Full journal access flows externally; it feels like an independent publishing platform rather than an extension of the HRS organization. Content is distinctly scientific and does not overlap with HRS’s broader event, patient, or professional education materials. The +.5 is because there is a decent amount of marketing effort on the pages to direct users to the journals. +1 the branding of the journal site has echos and is very clear that the Journal is produced by the HRS. Thus, this pairing is disconnected with connective DNA with very low/no overlap in content. Explanation: The majority of event summaries, patient tools, and basic professional resources are freely accessible. Deeper educational materials, full conference recordings, and certain guidelines are gated for members. There's a relatively friendly and proactive onboarding pathway — clear "Join Now" CTAs, member value propositions, and defined next steps post-registration.The primary audience is still electrophysiologists and cardiac device professionals, making the experience somewhat insider-focused. However, the tone of writing is noticeably friendlier and more humanized compared to peers like HFSA. The voice is professional without being overly dry, especially in patient-facing pages and public health initiatives.Scores: Member Networking Opportunities: ★★★★★ Donations & Philanthropy: ★★★★★ Events: ★★★★☆ (4/4) Scientific Publications / Latest Science: ★★★☆☆ (4/4) Practice Support Resources: ★★★☆☆ (3/4) Patient-Facing Tools & Content: ☆☆☆☆☆ Education: ★★★☆☆ Advocacy: ★★★★★ Explanation: HRS places major emphasis on events (especially Heart Rhythm Annual Meeting), education, and scientific updates. Networking exists but is not hyper-prominent. Patient-facing initiatives are present but secondary. Philanthropic and fundraising efforts are smaller compared to core professional services.Patient Facing tools, education , or even information is mostly missing from the site.Mostly text based the design is highly polished with a usage of micro brand flair and animations. There are subtle soundwave detail is used without even has little micro animations with it a very beautiful touch that brings the site together in a cohesive way..The site feels airy well dictated and high level of prioritization issues are their feels like there's not a large amount of pages which is untrue. I am sure they have user response of. I didn't know you did X because you would need to know it was there most Detailed pages contain multiple pieces of content.listicle answer for micro navigation on a

HFSA -- Heart Failure Society of America

Wed, 04 Jun 2025 15:44:00 GMT

Readability: Score: 24 – Average; Could Benefit from Minor Edits Breakdown: Reading Level: 3 – 10th–12th Grade Sentence Length: 3 – 20–25 words avg. Paragraph Density: 3 – Moderate density Vocabulary: 3 – Mixed Jargon Usage: 3 – Occasional, defined Sentence Structure: 2 – Mostly passive Scannability: 4 – Good CTA Clarity: 3 – Somewhat clear Estimated Visitors: ~30,000–50,000 monthly (estimated from SimilarWeb and other traffic sources)Estimated Membership Numbers: ~2,500–3,000 members (from HFSA reports and third-party sources)(For HFSA: hfsa.org vs hfsa.org/journal-cardiac-failure and jcf)Explanation: A journal section that outlines the journal product lives on the main site but the Journal is outside HFSA domain and lacks any visual or navigational unity with the main site. There are plenty of content that is derivative of the journal on the main site but most full-content links redirect users away from HFSA.org. There are minimal cross-links or integrated member pathways between the journal back to the main site, but plenty that go from the main site to the journal. Creates Derivates of major Docs from the site as Supportive Materials. Explanation: Most educational and patient content is accessible without membership. Some professional-level webinars and event materials are locked behind a login. Onboarding remains sufficient: you can join, but there’s the structured welcome flow is mostly trapped in a PDF.Explanation: The site’s tone caters mostly to professionals but includes patient sections to broaden reach, making it somewhat inclusive. However, the tone across most of the site is flat, formal, and mildly expressive at best — not very lively or welcoming. The content of the site is some what longer with complicated sentence structure with minimal chunking. Scores: Membership & Networking Opportunities: ★★★★★ Donations & Philanthropy: ☆☆☆☆☆ Events: ★★★★★ Scientific Publications / Latest Science: ★★☆☆☆ Practice Support Resources: ★★☆☆☆ Patient-Facing Tools & Content: ★★★★★ Education: ★★★☆☆ Advocacy: ★★★☆☆ Explanation:
Membership & Networking Opportunities: Easy to find, the pitch for becoming a member is cross medium with some on the web referencing pdfs with a great(but with too many stock photos) introduction video. Enhance Your Heart Failure Career with HFSA Membership https://youtu.be/LOh75iLOEHs Donations: Mostly missing from the site there is some reference to becoming a sponsor from a corporate level but their finances seem to come from other streams of revenue. Events: There are events sponsored from the HFS with an ongoing calendar with a co-mingle of external events showing a delegation technique that makes their events seem more robust then what they can personally produce. Scientific Publications / Latest Science:. The main site does have some medical news but mostly in the view point of Industry. All other science is point away to their disconnected journal. Practice Support Resources: This seems to be their most lacking area of the site. Most practice support is more in the tone of Patient collaboration tools and practically nothing around the business. Patient-Facing Tools & Content: A full suite of content: Events, Webinars, and articles. Education: Though education is clearly a focus for this organization is a supportive mechanism for them and is not segmented out so it is dispersed under membership, professional development, and patients. Advocacy: Clearly important as a benefit and why users want to be a part of this org. SPONSORSHIP INTEGRATIONS: Donations come from Sponsorship and this reflects in other spaces like events, and education. The small organization utilizes these 3rd Party production sources to enrich their calendar and educational spaces making those areas much more robust then what they could produce on their own. Derivatives are page items on the main site vs the journal area. Top 10 Takeaways Press Release - Teaser Full Press Release Link Art Direction the site has very little photos has simple but effective art direction flair that makes the simple use of text feel "designed" Corner register marks little heart rhythm notes. two color branding based from logo. image frame overlays

fACS -- American College of Surgeons

Wed, 04 Jun 2025 15:44:00 GMT

<-- back to competitive analysisReadability: Score: 30 – Good; Minor Tweaks OnlyBreakdown:Estimated Visitors: ~400,000–500,000 monthly (based on SimilarWeb and verified public sources)Estimated Membership Numbers: ~90,000 members (based on ACS official reports)Explanation: The Journal of the American College of Surgeons operates on a completely different platform (Lippincott Williams & Wilkins / Wolters Kluwer) with its own domain and infrastructure. No shared navigation menus between the main ACS site and the journal No visual branding alignment or consistent cross-site navigation. Full content is managed separately under LWW's portal, not ACS’s membership login. Content focus is distinct — original research and scientific publications without duplication of ACS's advocacy, education, or professional development content. Thus, the two sites are fully disconnected with very low/no content overlap.Explanation: Basic public content is freely available — news, advocacy, and patient-facing materials. However, guidelines, clinical resources, and career development tools are behind a login wall. Membership onboarding is solid: clear pathways to join, member benefits well articulated, and structured new member orientation available.Explanation: The primary audience remains surgical professionals, creating a somewhat exclusive environment. Patient resources exist but are secondary. Tone throughout the site is highly professional and formal — focused on credibility and rigor rather than emotional appeal or expressiveness.Note: even though the content leans to longer their is a clear focus on priority of content so pages rarely get overly robust or dense. Cleanliness of UI an d structured displays handles a scope of content keeping the page organized and clean.Scores: Member Networking Opportunities: ★★★☆☆ (3/4) Donations & Philanthropy: ★★★☆☆ (3/4) Events: ★★★☆☆ (3/4) Scientific Publications / Latest Science: ★★★★☆ (4/4) Practice Support Resources: ★★★★☆ (4/4) Patient-Facing Tools & Content: ★★★☆☆ (3/4) Education: ★★★★☆ (4/4) Explanation: ACS is very strong on education, practice resources, and scientific updates. Networking and philanthropy are supported but not as dominant as their educational mission. Patient-facing content is present but takes a back seat to professional development.One of the more interesting websites in relation to our direction is mostly around their shifting main NAV and hero image graphics. The impactful sweeping cut image doesn't always work perfectly because of content not constraining to the rules as much as they need to, but it does make a more visually impactful design. The rest of the site has a tight control on color, mostly a black to navy blue with small accents of red.A surprising amount of images is across the site and though most likely stock it seems to be a professional grade. All images have the similar color, toning and keying, which allows all images to feel like they're from the same set. There is nothing that breaks from high contrast, a low contrast or saturated low saturation.The site has an issue approach on main navigation with a three tiered separation of audience right off the bat from the homepage. This causes the main NAV to "personalize". This is a great way for them to separate their concerns and focus their audiences. I'm curious what strategic documents they must have to make sure that content is placed in the right context and it is possible that they are just more accurate about dividing their audience use case because they only shift between (researcher, surgeon, patient), and do not have the nuanced audience platform that ACC has which is almost every medical profession level associated with cardiology.

ESC -- European Society of Cardiology

Wed, 04 Jun 2025 15:44:00 GMT

<-- back to competitive analysisReadability: Score: 35 – Good; Minor Tweaks OnlyBreakdown:Summary: ESC’s website is structured cleanly for professional and academic users. The reading level suits clinicians and researchers, with technical vocabulary prevalent throughout. Some jargon appears without consistent definition, especially in professional news articles. Sentence structures are a bit formal and often lean passive, though the layout and design promote good scan-ability. CTAs could be stronger to drive user action more clearly.Estimated Visitors: Approximately 1.2 million monthly visitors, according to Similarweb. Estimated Membership Numbers: Over 105,000 healthcare professionals worldwide.Integration of Experience: Explanation: Since the journal content is fully integrated within the main escardio.org domain with consistent branding and top-level navigation access, the user experience is relatively unified. Although some journal content may still open in external viewer windows, the structural integration supports a more cohesive experience.Content Overlap: Explanation: The journals and the main site both target healthcare professionals, and while their formats differ (news/guidelines vs. academic papers), their thematic overlap is clear. Users encounter both journal links and practice guidance fluidly in the same experience, without unnecessary duplication.Content Locking: Explanation: Access to certain resources, such as full guidelines and educational materials, requires membership or payment, indicating partial content locking.Onboarding: Explanation: The ESC provides clear pathways for professionals to join, with detailed information on membership benefits, suggesting a well-structured onboarding process.Audience Focus: Explanation: The ESC primarily targets healthcare professionals, with limited resources for the general public, indicating a somewhat inclusive audience focus.Tone & Expression: Explanation: The tone across ESC's platforms is professional yet accessible, aiming to engage healthcare professionals without compromising on scientific integrity.Radar Chart Scores: Membership & Networking Opportunities: ★★★★☆ Donations & Philanthropy: ☆☆☆☆☆ Events: ★★★★★ Scientific Publications / Latest Science: ★★★★★ Practice Support Resources: ☆☆☆☆☆ Patient-Facing Tools & Content: ☆☆☆☆☆ Education: ★★★★☆ Advocacy: ★☆☆☆☆ Rationale: Member Networking Opportunities: The ESC offers networking through its associations, working groups, and events, providing ample opportunities for professional connections. Donations & Philanthropy: While the ESC is a nonprofit organization, there is limited reference public fundraising or philanthropic campaigns on the main site. I can't find any significant mention on if you can donate and the current google reference to a donation page 404's Events: The ESC hosts numerous events, including the prominent ESC Congress, catering to healthcare professionals globally, but most of its Event content is co-mingled and content-centric with the news on ESC 365. Scientific Publications / Latest Science: With a suite of high-impact journals and regular updates, the ESC continually published a well connected campaign around cardiovascular research. Practice Support Resources: Provides guidelines and tools for healthcare, but practically missing any materials around practice support I would expect that is partially because the audience is the EU and that level of information would be shaped by the country level and would be to complex to outline at this organizations level. Patient-Facing Tools & Content: The primary focus remains on healthcare professionals, and barely any educational materials for patients, and I am not sure if I found any for a patient that was looking for any basic information. Education: Delivers a range of educational programs and certifications, such as online courses and webinars, for healthcare professionals, but mostly pushing off to it E-learn site to house the marketing.. Advocacy: You can find note of advocacy deep with in the sections of the site but they are clearly connected with the iniatives and you would need to know they are there and more hidden then present on the site. A remarkably polished site. There is use of both graphics and photos which does sometimes challenge the focus of the art direction, but UI standards across the site in such an expensive manner is well held together. Clearly there is a design system utilized, and this site being relatively young is not showing any markers of age or deviating from the strategic content alignment. The only negative I can really put against the ESC is even at their reduced focus of scope, comparative to the other associations in our review the produce a lot and the site is very expansive. They are pushing the edges of what can be easily discoverable, and I am sure there is more content that a user would have to dig for. I am curious how they deal with those constructs and limitations. I do want to note their clinical documents page at first usage is not the greatest answer for there overwhelming content problem because more items are hidden than easily discoverable.

AHA -- American Heart Association

Wed, 04 Jun 2025 15:43:59 GMT

<-- back to competitive analysisReadability: Score: 35 – Great; Could Benefit from Minor EditsBreakdown:Summary: Heart.org performs reasonably well for an educated general audience. It offers a mix of technical and accessible vocabulary, and while sentence length and density are moderate, content is largely digestible. The tone is professional, and medical jargon is often defined, especially in patient-facing sections. The layout supports decent scannability, though CTA buttons could be clearer, more action-oriented, but using some great focused text for CTA.Estimated Visitors: Approximately 3 million monthly visitors. Estimated Membership Numbers: Over 33 million volunteers and supporters.Explanation: The main site (heart.org) and the journal site (ahajournals.org) operate on separate domains with distinct branding and navigation. While there are links between them, the user experience is not seamless, indicating a loosely connected integration. Landing Page for the full list of publications not even on the main site but on the Professional Heart. Minimal top 5 teaser articles Explanation: The main site focuses on general public education, advocacy, and patient resources, whereas the journal site is dedicated to scientific publications. The content serves different audiences with minimal overlap. Explanation: The main site offers the majority of its content—including patient education, healthy living resources, donation opportunities, and volunteer programs—freely available to the public. While professional tools and journal access may require membership or payment, these are not part of the main site’s public-facing content. Most of the content is on Proffesional.heart.org so much so the login doesn't show up until the user is on that subdomain. Strong Brand holds the Subs together but the main nav is "Teased" on the main site but the entire nav swaps out when your in that experience. Explanation: The site includes information on getting involved through volunteering, donations, and becoming a heart health advocate. However, there’s less emphasis on structured onboarding for new members or supporters—details are available but not spotlighted or guided with a welcoming narrative. It’s informative but not highly personalized or welcoming. There is a complete separate website for the professional where they ask people to become part of the org. Explanation: The AHA addresses both the general public and professionals, offering resources ranging from patient education to scientific research, reflecting a broad inclusivity. The content is designed to be accessible and relevant to a broad audience, including the general public, patients, and caregivers, without requiring specialized medical knowledge. Explanation: The tone across AHA's platforms is professional yet accessible, aiming to engage a wide audience without compromising on scientific integrity.Radar Chart Scores: Member Networking Opportunities: ★★☆☆☆ Donations & Philanthropy: ★★★★★ Events: ★★☆☆☆ Scientific Publications / Latest Science: ★☆☆☆☆ Practice Support Resources: ★★★☆☆ Patient-Facing Tools & Content: ★★★★★ Education: ★★☆☆☆ Advocacy: ★☆☆☆☆ Rationale: Membership & Networking Opportunities: Minimal presence on heart.org. Professional networking largely lives off-site or in conference contexts. Donations & Philanthropy: Highly visible and emphasized, with multiple calls to donate, fundraise, or give in honor of someone. Events: Community events like Heart Walks and Go Red for Women are promoted, but less focus on large-scale scientific events or purchasable events. Scientific Publications / Latest Science: Virtually absent from the main site; most science communication is generalized for lay audiences.
Practice Support Resources: Some tools for CPR, emergency response, and guidelines for laypersons exist, but not robust clinical tools unless you know where you are going and then you can find an equivalent to NCDR with Get with the Guideline Registry. Patient-Facing Tools & Content: Heart.org excels in this category, offering rich educational content, risk assessments, and interactive tools. Education: Strong emphasis on public education, and awareness campaigns But limited training courses (like CPR), and no purchasable continuing education or modules for medical professionals. All reference to continuing learning is buried on the main site and is mostly hosted on its E-learning Sub Domain. elearn.heart.org Advocacy: It is on the site but it is very hard to find but does exist. Art Direction strong visual branding with single color usage the red and white. High usage of photos because of their public facing mission that humanizes the site. Extra Care on all pages to reserve "button" for limited usage because of the single color branding. Red in the UI is dropped in tone in the UI so it has proper contrast. Structure of the content is spread across multiple sites where the main site is much more Advocacy, Public Education with pass offs to the sister sites. Clear focus of audience and cleaning away distractions. Cleanliness is a focus of all pages. Dates only show up when referencing things that are "latest" Listed items are almost always reserved to less then 5 items. Sub Domain-ing with altering Context and Main Nav CPR.heart.org Learn.heart.org Professional.heart.org .... The subduing is markable, interesting and allows for greater division of audience and improves focus, but it does impede discoverability, and only because this research has forced deep diving into their content. Did I discover some of the nuanced areas. It is very easy as an audience member or user to be confused about why the main is altering because the branding is so locked up the edges between the main site and CPR, for example, are minimal and a user might just be shocked that they may NAV item that they were utilizing disappears.

ACC -- American College of Cardiology

Wed, 04 Jun 2025 15:43:59 GMT

<-- back to competitive analysisReadability: Score: 20 Classification: Below Average; Requires Revision Estimated Visitors: Approximately 1.1 million monthly visits. Estimated Membership Numbers: Over 56,000 members, encompassing a diverse range of cardiovascular professionals. The main site (ACC.org) and the journal site (JACC.org) are distinct in branding and navigation. While ACC.org provides a link to JACC.org, the journal site operates independently with its own navigation and content structure. The content overlap is moderate; ACC.org references JACC articles, but the journal content is primarily housed separately.A very disjunctive experience between the two space but with all of the interconnected hand offs between the two sites and the non-descriptive branding the experience comes out muddled and users will often not understand they a have left one domain for the other.ACC.org offers a mix of open-access and member-restricted content. Educational resources and certain tools require membership login. The onboarding process is streamlined, with clear pathways for different professional roles and an eligibility calculator for prospective members.The site largely seems unlocked and most articles and site are unlocked thought it makes easy access to the site and the content produced by the org it lacks a certain presentation to the value of Membership or what a user might get to if the content was more locked down. The site primarily targets cardiovascular professionals, with content tailored to their needs. The tone is formal and clinical, appropriate for a professional medical audience, but lacks broader inclusivity or expressive engagement visitors. Most language lacks pro-nouns, and mostly proper nouns. This language is professional but doesn't match to modern web language. Effect on UX the tone can come across as overly wordy to cold. The text is to long to be skimmed and often just produces long unreadable blocks of text. Membership & Networking Opportunities: ★★★☆☆ Donations & Philanthropy: ★☆☆☆☆ Events: ★★★★☆ Scientific Publications / Latest Science: ★★★★★ Practice Support Resources: ★★★☆☆ Patient-Facing Tools & Content: ★☆☆☆☆ Education: ★★★★☆ Advocacy: ★☆☆☆☆ Explanation: ACC.org places a strong emphasis on scientific publications and educational resources, evident through its extensive guidelines and learning materials. Events, such as the ACC.25 conference, are prominently featured. While there are networking opportunities and patient-facing tools like CardioSmart, these areas are less emphasized compared to the organization's core focus on science and education.

AAN -- American Academy of Neurology

Wed, 04 Jun 2025 15:43:59 GMT

<-- back to competitive analysisReadability: Score: 37 – Good; Minor Tweaks OnlyBreakdown:Estimated Visitors: ~250,000–300,000 monthly (based on SimilarWeb and traffic data)Estimated Membership Numbers: ~38,000 members (official AAN membership figures)Explanation:
The Neurology® journal is operated under neurology.org, branded clearly as the AAN’s journal. Visual styling is separate and more typical of academic publishing, but there are cross-links back to AAN.com (e.g., navigation mentions AAN membership, benefits). Content access is tied to AAN membership in some cases (members get full-text access for certain journals). There is significant Marketing that is one way from AAN to the Neurology Journals but rarely in reverse. The journal site’s focus is purely research articles, clinical trials, and scientific reviews — no duplication of AAN’s broader professional education, advocacy, or event content. Explanation: Many public resources — news, events, practice tools, advocacy — are open-access. Member-exclusive content includes guidelines, CME opportunities, and deeper clinical resources. New members are welcomed through clear onboarding steps, including member portals, community forums, and structured orientation emails.Explanation: AAN’s primary audience remains clinical neurologists and researchers, which gives it a somewhat professional insider focus. However, the tone is notably friendly, with conversational but authoritative messaging. Patient-facing content is present but secondary.Scores: Member Networking Opportunities: ★★★☆☆ Donations & Philanthropy: ★☆☆☆☆ Events: ★★★★★ Scientific Publications / Latest Science: ★★★★☆ Practice Support Resources: ★★★☆☆ Patient-Facing Tools & Content: ★☆☆☆☆ Education: ★★★★★ Advocacy: ★★★★☆ Explanation: AAN is strong across education, latest science, and practice support. Member networking is solid but not dominant. Events and practice tools are present but slightly secondary to professional development initiatives.Their home page successful balances multiple initiatives by only showcasing 1 element or just directing them deeper into the site to the content form the home page then showing examples of the each.Donation is very hard to discover on the site. AAN like HFSA they organize their top tier as "Research" and place publication below. Art Direction is 100% textual and it is almost impossible to find photos on the main site. Very un "JAZZY"

Member Sections Presentation Script

Wed, 04 Jun 2025 15:43:59 GMT

Presentation of Member SectionsThe future design of Member Sections operates on a simple tenant: showcase value while giving the user actionable steps to access that value. The design decisions to follow are to build the foundation of the experience.Member sections are an exclusive space tailored to capture resources, tools, and opportunities to engage in mentoring and/or gain pathways to leadership. To support this, we established a new dynamic and personalized onboarding process to meet users where they are rather than giving them instructions that cover what could be a multiple-week ordeal to gain access. At every step, we want to showcase to users what they are missing out on. We intend to reward the users by opening up specialized areas in Docmatter and curating exclusive content behind the access walls.Let's dive into some of the details. When talking about onboarding, we want to consider 4 user states: LOGGED OUT NOT A MEMBER OF THE COLLEGE A MEMBER WHO DOESN'T HAVE ACCESS TO THE SECTION A USER WITH FULL ACCESS. These personalization hooks give us the flexibility to craft the experience, allowing for better instructions and selling tactics.Only users of a specific state are shown the next steps in their personalized journey. This allows us to craft the upsell and instructions to Membership for example or the Member Section when the time is appropriate.Now that the onboarding process has become simplified in messaging and action, we can discuss how our users are often part of more than one section. To reduce mental friction when moving from one section to another, we want to strongly enforce consistency. This consistency can been seen in the design pattern, the layouts and more importantly the labels and page structures. This will allow our multifaceted members to experience an organized environment so they can focus on the content rather than where it was labeled or placed. An added benefit is that when new features are rolled out, they are easier to discover.Personalization will not be added to just the main page. The content zones of sections will also showcase content at different levels keyed to the user's access. This can showcase the quality of materials and enforce a desire to gain full access to this quality content.

2025 Week 19

Wed, 04 Jun 2025 15:43:59 GMT

Name Spaced and Hyphened approved by Carol ga-{{ EVENT }} Should we name space by domain? JACC, ACC, CARIOSMART? or is generic ACC Enough? ✅ 2025-05-14 Answer was No: this wouldn't be needed and we can go with the generic name space of 'ga-' All of these attributes are capturing that the page has convinces a user to start the journey for doing the event/action outlined.To streamline our analytics tagging and reduce the chance of typos when adding event classes to our HTML, we’ve standardized and shortened our attribute names for key user interactions. These classes will be applied to CTA buttons and other interactive elements to help us track and move the needle on our core UX goals.Building on our discussion around GA4 360 event‑costs, here’s a turnkey way to spot‑track every key interaction on our refactor projects by scoping on URLs and time windows—no need to enumerate every tag in the ticket. We’ll still capture all our predefined event classes, but only for a limited period on the pages that matter. Target Scope URLs: List all legacy paths and any newly introduced pages or vanity URLs. Pre‑Launch (Baseline) Through editorial we tag legacy pages today with our standard event classes. Create the Jira Ticket for Capture all event hits on those URLs for 8 weeks before the refactor launch. Launch + Redesign Deploy the redesigned section—this may include new page paths and any freshly minted vanity URLs. Immediately upon launch, update the Jira ticket’s URL list to reflect: Legacy → redesigned paths Any new/vanity URLs Capture all class events on that complete URL set for 8 weeks after launch. Analysis & Iteration Compare equivalent pre‑ vs. post‑launch windows on the same URL set. If further tweaks are needed, open a new ticket starting at Step 2. Once goals are met, retire that scoped capture to preserve event volume. Summary: Spot‑track all GA events on ACHD SAP page refactorDescription: Scope: URL List: /Education-and-Meetings/Products-and-Resources/ACHDSAP` [plus any new/vanity URLs] Data Windows: Pre‑launch: 2025‑03‑25 → 2025‑05‑19 Launch date: 2025‑05‑20 Post‑launch: 2025‑05‑20 → 2025‑07‑15 Tracking: Capture all our GA event classes fired on these URLs during each window. Acceptance Criteria: Events fire on legacy pages during the pre‑launch window. Events fire on redesigned & new/vanity pages during the post‑launch window. Pre vs. post counts are available for apples‑to‑apples comparison. Ticket closes when analysis is complete or next iteration is opened. Labels: UX‑Analytics, GA4‑360, Refactor, ACHD‑SAPLet me know if you’d like to tweak the window length (e.g. 6 weeks vs. 8 weeks) or any other detail—otherwise I’ll spin up a Jira template and we can roll this out on our next refactor kickoff.Thanks! —Matt

Page List

Wed, 04 Jun 2025 15:43:58 GMT

Solution: Provide a custom 404 page that clearly explains the page is not found, includes a search bar, and links to popular or important pages like the homepage or contact page. Tip: Add humorous or lighthearted content to ease frustration. Solution: Display a clear message explaining the request was incorrect or malformed. Suggest actions the user can take, such as reloading the page or checking for errors in the URL. Tip: Guide users to report the issue if it persists. Solution: Redirect users to a login page with a clear explanation that access requires authentication. Offer a link to reset passwords if needed. Tip: Keep the login process simple and user-friendly, avoiding unnecessary steps. Solution: Inform the user that they don’t have permission to access the requested page, and suggest contacting support if they believe this is an error. Tip: If the user is logged out, consider prompting them to log in, if applicable. Solution: Display a friendly error message stating that something went wrong on the server. Provide a link to the homepage or suggest the user try again later. Tip: Include an option to report the issue directly to the support team. Solution: Explain that the server encountered an issue while acting as a gateway. Inform users this is likely a temporary issue and suggest trying again later. Tip: Offer a status page or contact option in case the problem persists. Solution: Notify users that the service is temporarily unavailable due to server overload or maintenance. Include an estimated time for when the service will be back online, if possible. Tip: Add a subscription or notification option so users can be alerted when the site is back up. Solution: Display a message indicating the server took too long to respond, and suggest refreshing the page or trying again later. Tip: Offer a link to check the site's status or provide a more interactive error page (e.g., FAQ section) that users can explore while waiting. (Suppress for Security only available non production) Solution: Inform users that the request method they used is not allowed. Clearly state what methods are allowed (e.g., GET, POST) and offer navigation back to valid pages. Tip: Offer a clear explanation or auto-redirect to the homepage or main section of the site. Solution: Show users a message indicating their connection was too slow or the request took too long. Encourage them to check their internet connection or retry the action. Tip: Add a "Retry" button that automatically resubmits the request. Solution: Politely inform users they’ve made too many requests in a short time and suggest waiting a few minutes before trying again. Tip: Include a countdown or time estimate for when they can try again. Solution: Clearly state that the requested page has been permanently removed and won’t be available again. Offer a search bar or links to other similar content. Tip: If the content has been moved, provide the new link or page. Solution: Inform the user that the media format they tried to upload or access isn’t supported. Provide information on the types of media that are accepted. Tip: Offer a link to a help or FAQ page explaining how to format files for uploading. Solution: Notify users that the requested functionality is not supported. Provide a suggestion for alternative actions or contact support if they require the missing feature. Tip: If it’s a planned feature, provide an option for users to sign up for updates on its development. Make It Easy to Navigate Away: Always include a clear path back to the homepage, a search bar, or popular sections so users can easily recover. Human-Friendly Language: Avoid using technical jargon in error messages. Use conversational language that’s easy to understand. Maintain Branding: Keep the error pages visually consistent with your site’s overall design and tone to maintain a cohesive experience. Track Errors for Improvement: Log and monitor these error codes to identify recurring issues and improve site performance over time. Here’s a list of critical error pages that should be suppressed or sanitized to improve security protection:These errors can still be shown to the user but should be cleaned up to avoid exposing sensitive information. 500 - Internal Server Error 400 - Bad Request 502 - Bad Gateway 503 - Service Unavailable 504 - Gateway Timeout 429 - Too Many Requests These errors should be replaced with generic messages to avoid disclosing details about access restrictions, authentication, or supported methods. 403 - Forbidden 401 - Unauthorized 405 - Method Not Allowed 404 - Your heart is in the right place but the page doesn't seem to be there. Sorry to break you heart but his page isn't found. Instructions to use the search bar. --> https://www.acc.org/search 500 - With a heavy heart we apologize our server seems to not be ticking. Sorry try again later. if continue to have issues please contact. ....? Take heart we are fixing it. In a heartbeat the server will be back on line. The server will be back on line in a heartbeat 401 - A key to my heart you need to login to see this content. Your missing the key to my heart please login. Login button. 403 - Sorry to be hard hearted but you don't seem to have access to this page. I know you heart was set on getting into this page but you don't seem to have access. I know you heart was set to see this page but you don't have access. 410 - Sorry we broke your heart 404 - Page Not Found:But don’t worry; our heart is in the right place. Try finding the page via our search.500 - Internal Server Error: We're putting our heart and soul into fixing it. Refresh the page, or come back later. 401 - Unauthorized Access: Please log in or contact ACC Member Care. 410 - Page Gone Forever: You might find something similar through our search. 403 - Forbidden: But you don’t have permission to access this page. If you believe this is an error please contact ACC Member Care.guidelines | education | latest in cardiology
Representatives are available Monday-Friday, 9:00 a.m.-5:00 p.m. (Eastern Time). You can reach the ACC Member Care Team by phone at 800-253-4636 (Toll Free US & Canada); 202-375-6000 (Outside US & Canada); Fax: 202-375-7000; or by Email via this form.

2025 Week 20

Wed, 04 Jun 2025 15:43:57 GMT

tags:: +Weekly Notes
<< Last Week | Next Week >>
Competitive Analysis Heart Professional Review Work the Brand Voice so it is jus the bottom 3rd quarter. CCKE and SAP
Micro-Event Tracking for Refactors is now passed on to Carol for A POC.

2025 Week 19

Wed, 04 Jun 2025 15:43:57 GMT

Micro-Event Tracking for Refactors

2025 Week 18

Wed, 04 Jun 2025 15:43:57 GMT

tags:: +Weekly Notes
<< Last Week | Next Week >> Competitive Analysis SAPs Leg Conf Competitive Raw Data Collection Facet Giving Fund Competitive Analysis Raw Collection Review the Major Competitors UX review and impressions of good and bad from each Future of UX. HEDI Donations CMP - In IT be dev, or held up content in politics. Events

2025 Week 17

Wed, 04 Jun 2025 15:43:56 GMT

tags:: +Weekly Notes
<< Last Week | Next Week >> Glossary of Non-Article Pages SAP updates Competitive analysis Figure Alterations Competitive Analysis SAP CMP
Micro-Event Tracking for Refactors

2024 Week 37

Wed, 04 Jun 2025 15:43:55 GMT

Spinning of Plates

★ AHA Professional - American Heart Membership Site

Wed, 04 Jun 2025 15:16:51 GMT

Readability: Score: 34 – Good; Minor Tweaks Only Breakdown:Estimated Visitors: Approximately 400,000–500,000 monthly (based on SimilarWeb and verified public sources)Estimated Membership Numbers: Approximately 35 million volunteers and supportersExplanation: Professional Heart Daily (PHD) operates as a distinct subdomain focusing on professional education, guidelines, and resources. While it links to AHA journals, the integration is moderate, with separate navigation and branding. Content overlap exists in the form of shared guidelines and statements, but PHD primarily serves as a hub for professional development and networking.Explanation: PHD offers a tiered membership structure, providing varying levels of access to educational resources, discounts, and professional recognition. The onboarding process is straightforward, with clear information on membership benefits and application procedures. However, some advanced resources require premium membership, indicating partial content locking.Explanation: The site maintains a professional and inclusive tone, catering to a wide range of healthcare professionals. The language is formal yet accessible, aiming to engage both seasoned practitioners and those new to the field. While the tone is informative, it could benefit from more personalized narratives to enhance engagement.Scores: Member Networking Opportunities: ★★★☆☆ (3/5) Donations & Philanthropy: ★☆☆☆☆ (1/5) Events: ★★★★★ (5/5) Scientific Publications / Latest Science: ★★★★★ (5/5) Practice Support Resources: ★★☆☆☆ (2/5) Patient-Facing Tools & Content: ★☆☆☆☆ (1/4) Education: ★★★★☆ (4/5) Advocacy: ★☆☆☆☆ (1/5) Explanation: PHD excels in providing educational resources and facilitating professional development through events and publications. It offers substantial practice support tools within the site and fosters networking opportunities within its communities at the events. The emphasis remains on professional audiences with in this domain. Philanthropic initiatives are present but not prominently featured mostly on their main site.Summary: Professional Heart Daily serves as a comprehensive resource for cardiovascular professionals, offering a wealth of educational materials, guidelines, and networking opportunities. Its structured layout and clear calls to action enhance usability, while its focus on professional development aligns with the needs of its target audience. Minor enhancements in personalization and expanded patient-focused content could further broaden its appeal.

Readability Comparison Scoring

Wed, 04 Jun 2025 15:16:33 GMT

Higher Score the better.Short Analysis: AAN and HFSA are the best overall performers — very even across all areas. HRS does slightly lag behind AAN and HFSA on Reading Level and Vocabulary but compensates with high scannability and clear CTAs. AMA is strong, but slightly less precise in CTA clarity. AHA and ESC are strong but could simplify insider vocab slightly more. ACC stands out for being much more academic and technical — not designed for a general or even lightly medical audience. ACC is substantially longer than the rest (about 60% longer than the next highest). AMA and AHA are moderately dense, rich but manageable ACS, HFSA, and AAN cluster in the 500–700 word range — relatively compact. ESC is the most concise — under 500 words.

Quality of life configurations with Sitecore

Wed, 04 Jun 2025 15:01:35 GMT

Considering the difficulties that editors encounter in distinguishing between legacy, converted, and legacy supportive components, owing to the absence of folder structure and clear naming, we've introduced a streamlined approach. All component icons are now set to grey or red by default. However, converted and supportive components, along with the majority of new work, will be marked with either blue icons for compatible renderings or green for new arches components. This blue color is intended to be the default setting both arches and legacy supportive components. It's essential for the development team to review and ensure this default setting when releasing new work into the platform. In any instance where the blue green or grey is not the icon for the rending, the setting must be promptly corrected. Further Icon Definition allow for even easier recognition in the back end will be. Page Layout components should be Starts, Vue/JavaScript driven components should be puzzle pieces. When looking at the display view list in the backend you only see the render name and its relative location that it is placed in the list. As the teams move forward in using more and more shared content and breaking down content into chunks the Display view gets rather unusable because you would see RichText written possibly 5 times on the page the same is true with accordions. In that view is it possible to interject at least the details of the source which can be altered with a nickname like intro-text, benefit grid.....The component dependency tree outlines the interrelationships between components in a Sitecore instance, specifically identifying those that are either children of a component or have dependent child components. Only necessary components should be configured in this instance to maintain simplicity and reduce confusion for editors. This approach also minimizes the risk of including non-supportive components by lessening the need for editors to manually add components. Ultimately, this method aids in preventing the appearance of non-supportive components within converted pages, ensuring a clean and efficient working environment.

Pasted image 20250508103001

Wed, 04 Jun 2025 14:59:28 GMT

Pasted image 20250506073829

Wed, 04 Jun 2025 14:59:28 GMT

WhatIf--Main Nav By Personalization

Wed, 04 Jun 2025 14:59:28 GMT

ACC.orgWhat if We Designed ACC.orgThe Nav Based on USER TYPECLINICIAN &MEDICAL TEAMMEMBERUNKNOWNFACILITATORADMINISITRATORABOUTFuture POVLegacyOnboardingFirst StepsDeeper Engagement(How do we break downmember value)Member SectionOn BoardingSECTIONWorkGroupLeadershpPublishingSCIENCEHistoryADVOCACYCurrent(Transparency)DONATIONINIATIVESOppertunitiesINDUSTRYPERSPECTIVEPRACTICESUPPORT & TOOLSEDUCATIONEVENTSClinicalTopicsClinicalTopics

WhatIf -- Interaction Model Break Down

Wed, 04 Jun 2025 14:59:28 GMT

PersonalizePersonalizeRecommendUpsellPersonalizeCollection PageNews/Article/Discovery/ConsumeStoryNarrative/Ask/CTAE-CommerceProduct/Evaluate/BuyAboutMembershipAdocacyCatalogueProductsEducationProcessDonationHistorySingleContent1ChaptersPersonalized ReturnDashboardRecommend23What if We Designed ACC.orgBased onInteraction MODE Narrative Page DesignNews, Article & MarketingE-CommercePersonalizeHome(UniquePersonalization)CARTPractice SupportPatient Translated FurtherSCIENCEOnBoardingthenDashboardJOINLCMSPersonalizeEventsEventExtrasWhat IF JACC.orgHELD SCIENCE What IF CardioSmart wasShared Decision MakingTOPICNews/Article/Discovery/ConsumeSingleContentSingleContentWhat IF CVQUALITYWas Practice SupportSingleContentUpsellBrochureware &InitiativesShopping &Professional InvestmentReadingLearning& DiscoveringWhat ifCardio MagazineWas treated like a Domain, Click EngineJournalPublished MagemalDigital TOCArchiveCuratedGroupingSearch/KeywordCuratedGroupingSectionsRecommendUpsellPersonalizeSectionsMemberCITEDConatent123emal123Help you at Point of Careemalemalemal

TagDashboardFigure

Wed, 04 Jun 2025 14:59:28 GMT

Tag Dashboardthe landing page for tags should balance this Ven diagramBusinessUserDiscovering MorePromoting BusinessGoals- articles (Updates to Science)- credit earning activities- guidelines (actionable science)- SAPs -> EDU Product- Events -> On Demand Content- Member Engagement -> Section/initiativesInbound PathOut Bound PathTools to Filterand SortFilter ViewRescopeAdvancedArticle/PostVideoAudioVisualDocumentDATE(Not Latest)Associated TermReduce by TermSearch AgainstKnowledge MatrixViewCustomizeDelivery ofContentAuthor?Power Features?Member SectionDateMostConsumed/Read/LikedReframePage

Tag Interactions Structure

Wed, 04 Jun 2025 14:59:28 GMT

EDUGuidelinesAppsAssetsMedical TopicContent TagsTag UniverseMedical TopicMedical TopicMedical TopicMedical TopicAssociate TagsSystem Meta TagsDatesFile TypeCMS ContentArticlePageEducationEventVideoAudioGraphicFileIntrinsic TagContextual TagHas CreditCalculated TagHas CostMedical TopicMedical TopicMedical TopicMedical TopicMedical TopicFreeNo CreditCMECNEMOCAssetsAssetsAssetsAssetsAssetsAssetsAssetsAssetsAssetsTopic PageArticlesMultimediaAssetsAssetsAssetsAssetsAssetsAssetsAssetsAssetsFrame

Sitemap -- Support Fund

Wed, 04 Jun 2025 14:59:28 GMT

Support FundAwardsSupport the ACCDonationsSecondary Path FromSupport PageMember BenefitsMember Section XMember Section YArticle AEmailFuture StateCurrent MemberCardiology As a CareerFuture State

Pasted image 20250514093947

Wed, 04 Jun 2025 14:59:28 GMT

readablity.png

Wed, 30 Apr 2025 13:33:52 GMT

ACC.org Concept Structure

Fri, 25 Apr 2025 16:13:19 GMT

ACC.org (Home Page) │ ├── Clinical Topics (Concept Anchor) │ ├── Heart Failure (Listing Page) │ ├── Arrhythmias (Listing Page) │ └── Other Conditions (Listing Page) │ ├── Education and Meetings (Concept Anchor) │ ├── Online Learning Catalog (Product Grouping) │ │ ├── ACCSAP (Product Destination) │ │ ├── CathSAP (Product Destination) │ │ └── Heart Songs (Product Destination) │ ├── Meetings and Conferences (Listing Page) │ │ └── ACC.25 Annual Meeting (Product Destination) │ ├── Clinical Webinars (Product Grouping) │ └── Guideline App (Product Destination) │ ├── Tools and Practice Support (Concept Anchor) │ ├── ACC Accreditation Services (Initiative) │ ├── NCDR – National Cardiovascular Data Registry (Initiative) │ ├── Membership (Concept Anchor) │ ├── Join/Renew (Standard Page) │ ├── Membership Benefits (Standard Page) │ ├── Member Directory (Listing Page) │ └── Member Sections (Listing Page) │ ├── About ACC (Concept Anchor) │ ├── Strategic Direction (Initiative) │ ├── Diversity and Inclusion (Initiative) │ │ ├── Health Equity Resource Center (Standard Page) │ │ └── LGBTQ+ Working Group (Standard Page) │ ├── Innovation Program (Initiative) │ ├── Clinician Well-Being Portal (Initiative) │ └── Contact Us (Standard Page) │ ├── Clinical Guidelines (Concept Anchor) │ └── Guidelines Explorer (Listing Page) │ ├── Latest in Cardiology (Listing Page) │ ├── News & Articles (Listing Page) │ └── JACC Journals (Listing Page)

Ultra Condensed

Fri, 25 Apr 2025 16:13:17 GMT

FAQ

Mon, 14 Apr 2025 16:06:16 GMT

The expiration date is the last date that you can claim credit for the current version of the topic. The day after the expiration date, ACC will publish a new version of the topic that will offer brand new credit. To claim the new credit, you simply have to answer the newly published practice questions for that topic.The Expiration Dates Calculated are Rolling. Each topic's Term of Approval/Date of CME & MOC Expiration are displayed on the product's dashboard. Yes, you may receive a full refund by canceling your order within 7 days of purchase. No refunds or term adjustments will be permitted after the first 7 days of purchase. Claiming any type of credit for the product during that time will make you ineligible for a refund.

Interviews.

Fri, 04 Apr 2025 18:05:48 GMT

Process focused. structure and establishment of change management. BA - Governance

Pre Kickoff Collection Checklist

Fri, 04 Apr 2025 15:01:21 GMT

At the start of all new project review this checklist to ensure a successful kickoff Completed Project Intake Form (submitted on the Monday Platform) List of Key Stakeholders (Client SME, Marketing, EDSCx, Analytics, Web Production) EDSCx - Jackie Pysarchuk, Rowena Enatsky, Matt Watier SME - Defined at Project Marketing - Defined at Project
Analytics - Carol Johnson or Xiaodong Hou
Web Production - Tatyana Kelmanson Create all appropriate tickets for Analytics Reports, and Web Production Reports. Email to MarCom and SME with their responsible data points to be collected. Audience & User Research Data (personas, analytics, behavior insights) UX Impressions and audit of the exposed content UX Mouseflow Recordings and Analysis List of Enterprise Content Directed Alterations to current existing product. Project Folder Creation **NEW Content Collection Document Process Flows & User Journeys (if applicable)
Capture Screen Grabs of the pages effected place in Before-And-After Business Goals & Objectives KPIs for Success Measurement User Goals & Objectives Conversion Points/Success Moments for User Project Timeline & Deadlines Any and All Vanities to Project Any and All Email Communications to users while on boarding and or using the product.
Current Analytics running on Project Scope Collect any relevant Foresee quotes around the product.
Existing Website Pages & Content Inventory Any and All Marketing Collateral that directs Users to or about the current project scope. Any Marketing Publishing Schedules for email, social, print, in person, videos Wireframes & Page Layouts (existing or new wireframes for page structure) Branding & UI Guidelines (standards from Arches) Required Artwork & Images (logos, banners, infographics, or other assets)

Post Launch Checklist

Thu, 03 Apr 2025 19:15:44 GMT

During the window for Refactor Just Published the following elements should be looked at and checked of to confirm that the baseline of Quality Assurance against a new publication. Main Navigation & Footer Link Navigation Vanity Link Check Content Check Links in New Pages Check Conversion Path Check Inform Analytics of Jira Ticket Timing for After Refactor Capture Screen Grabs and Save in Team Before After Collection Check in with SMEs see if any corrections are needed. Run through external Linkage report Source View of html should search for author links Check page in mobile & tablet views Do the above step on a phone :-)

How to use

Wed, 02 Apr 2025 20:52:56 GMT

https://www.youtube.com/watch?v=OSJ9MNZdN_E00:00:04.759 cats at 5:00 lets you use all 560 00:00:08.519 questions any way that meets your needs 00:00:10.860 each of the nine topics in the main 00:00:12.809 dashboard has associated questions 00:00:15.210 simply click on the questions button 00:00:17.670 next to the topic to begin you can build 00:00:21.510 a quiz to meet your individual needs by 00:00:23.970 customizing study or test mode study 00:00:27.359 topics and question types simulate a 00:00:32.070 board exam session by auto generating 60 00:00:35.219 random questions you have two hours to 00:00:37.860 complete and will receive a score sheet 00:00:39.750 with your results the quiz and exam 00:00:43.410 history allows you to resume attempts 00:00:45.960 not yet completed you may sort by date 00:00:48.829 mode and score as you answer questions 00:00:52.710 within the product the topic dashboard 00:00:55.320 and answer sheets update to reflect your 00:00:57.360 progress and within each topic you could 00:01:00.390 easily revisit questions you've got 00:01:02.010 wrong to see whether you can now answer 00:01:04.500 them correctly cats at five redesigned 00:01:08.939 to meet your needs 00:01:11.450 ACC education always learning 00:01:15.320 [Music] 00:01:17.330 you 00:01:19.430 [Music]

CMP-ADA-Policy

Tue, 01 Apr 2025 18:40:06 GMT

Summary: Hypothesis: Outline: Additional Notes:

Linkage Report

Tue, 01 Apr 2025 18:40:06 GMT

CMPMaintenance-of-Certification-Information-Hub>Collaborative-Maintenance-PathwayMaintenance-of-Certification-Information-Hub>Collaborative-Maintenance-Pathway-RETIRED
Root -- Unpublished -- 0 Live Linkages All Sub Pages are -- Unpublished and 0 Live Linkages.
After-Enrolling -- Unpublished -- 0 Live Linkages
CMP-ADA-Policy -- Unpublished -- 0 Live Linkages (CMP-Podcasts)[https://author-www.acc.org/Education-and-Meetings/Maintenance-of-Certification-Information-Hub/Collaborative-Maintenance-Pathway-RETIRED/CMP-Podcast] -- Unpublished -- Multi Linkages All retired versions.
Need-Help-with-the-CMP
//author-www.acc.org/Education-and-Meetings/Maintenance-of-Certification-Information-Hub/Collaborative-Maintenance-Pathway-RETIRED/You-Have-Extra-Time-to-Complete-Your-2020-CMP-Requirements -- Unpublished - [https://www.acc.org/Latest-in-Cardiology/Articles/2020/07/14/02/10/ACC-ABIM-Extend-Deadlines-For-Completing-2020-CMP-Requirements](Linkage 1) Featured Vanity MOCExtension points to a retired content /Sites/ACC/Home/Education-and-Meetings/Maintenance-of-Certification-Information-Hub/Collaborative-Maintenance-Pathway-RETIRED/FEATURES/2022/07/MOCExtension

CMP

Tue, 01 Apr 2025 18:40:06 GMT

Refactor the Pages for the CMP Product.

HFSAP -- Ultra Condensed

Tue, 01 Apr 2025 18:38:03 GMT

HFSAP is the most comprehensive resource for advanced heart failure and transplant cardiology, designed to help you perfect your knowledge, earn credits, and maintain your certification—all in one place.Available Credits: CME | MOC[Quick Purchase][Launch] ?? learning modules ?? video presentations +460 questions with supportive references. Stay Licensed & Certified Earn 40+ CME/MOC credits – enough for all certification requirements for 5 years. Pass Your Boards with Confidence Understand the ABIM blueprint while gaining access case-based questions with rationale and references. Escape the 10-year Exam Get access to CMP™, an alternative MOC assessment pathway, without the 10-year ABIM exam. Case-Based Learning for Real-World Skills Unlike traditional recall-based study methods, these questions focus on real-world clinical decision-making. [+] Attention CardioSource+ SubscribersCardioSource Plus does not include access to CMP A personal subscription is required to access CMP.Use the same account for both CardioSource Plus and your personal subscription to keep your progress in sync. Online: Enroll on the official website, where you'll be prompted to purchase the subscription. By Phone: Call the support team at 800-253-4636, x5603, from 9:00 a.m. to 5:00 p.m. ET. {Pricing Blocks} Customizable Learning: Create custom quizzes to simulate Board exams. Highlight and bookmark important content for quick reference. Flexible Study Formats: Text & video learning options available. Closed-captioned lectures for accessibility. Print key materials to create flashcards. Access Anywhere: Study on any device with the web or mobile app. Always Up to Date: Get yearly content updates based on the latest research and guidelines. HFSAP Covers every major area of cardiovascular medicine, from Arrhythmias to Systemic Hypertension. Cardiology Fellows preparing for Board certification. Practicing Cardiologists maintaining their certification. Interventional Cardiology Teams, including physician assistants and advanced practice nurses. NPs and PAs preparing for the CCKE – HFSAP now serves as a study guide for this exam. How to Prepare for the Boards Core Topics: Coronary Artery Disease, Arrhythmias, Heart Failure, Valvular Disease, etc. Specialized Topics: Sports Cardiology, Pregnancy & Cardiac Disease, Pharmacology, etc. How to Prepare for the Boards General Principles of Cardiovascular Medicine Arrhythmias Coronary Artery Disease Heart Failure & Cardiomyopathy Valvular Disease Pericardial Disease Congenital Heart Disease Vascular Diseases Systemic Hypertension and Hypotension Pulmonary Circulation Disorders Systemic Disorders Affecting the Circulatory System Miscellaneous Cardiovascular Genetics CPR, Post-Resuscitation Care Cardiac Critical Care Sleep Disordered Breathing Sports Cardiology Pregnancy and Cardiac Disease Cardiovascular Operative Management Pharmacology General Principles of Cardiovascular Medicine Upon completion of this activity, learners should be able to: Identify knowledge gaps and target study to fill those gaps in preparation for the ABIM Certification/Maintenance of Certification Exam in Cardiovascular Disease. Review and discuss one or more of the following to optimize the quality and provision of clinical care pertinent to the practice of cardiovascular medicine: Clinical and practice guidelines, recommendations and protocols Emerging research information and application to practice Quality and/or cost of care issues Multispecialty and multidisciplinary collaboration and communication Patient safety strategies Performance improvement Cultural competency
In support of improving patient care, this activity has been planned and implemented by the American College of Cardiology Foundation (ACCF). ACCF is jointly accredited by the Accreditation Council for Continuing Medical Education (ACCME), the Accreditation Council for Pharmacy Education (ACPE), and the American Nurses Credentialing Center (ANCC), to provide continuing education for the healthcare team.The ACCF designates this enduring material for a maximum of 59.5 AMA PRA Category 1 Credits™. Physicians should claim only the credit commensurate with the extent of their participation in the activity.
Successful completion of this CME activity, which includes participation in the evaluation component, enables the participant to earn up to 59.5 Medical Knowledge MOC points in the American Board of Internal Medicine's (ABIM) Maintenance of Certification (MOC) program. It is the CME activity provider's responsibility to submit participant completion information to ACCME for the purpose of granting ABIM MOC credit. Once your MOC claim is submitted to the ACCME no modifications can be made to your overall credit claim. Participants can claim credit only once.Join thousands of cardiology professionals using HFSAP to maintain their certification and advance their knowledge. [Purchase]All our products are developed by top cardiovascular experts who bring real-world experience and cutting-edge research into this program. [View Faculty] Thank you to our dedicated faculty for making this an unparalleled learning resource!Access you SAP from ACC's Learn APP [App Store] [Google Play]
Learn More | link

EPSAP-- Ultra Condensed

Tue, 01 Apr 2025 18:37:57 GMT

EPSAP is the most comprehensive resource for adult clinical cardiology, designed to help you perfect your knowledge, earn credits, and maintain your certification—all in one place.Available Credits: CME | MOC{Quick Purchase} {Launch} 64 learning modules +900 scientific images 280 questions with supportive references. Stay Licensed & Certified Earn 90+ CME/MOC credits – enough for all certification requirements for 5 years. Pass Your Boards with Confidence Understand the ABIM blueprint while gaining access case-based questions with rationale and references. Escape the 10-year Exam Get access to CMP™, an alternative MOC assessment pathway, without the 10-year ABIM exam. Case-Based Learning for Real-World Skills Unlike traditional recall-based study methods, these questions focus on real-world clinical decision-making. [+] Attention CardioSource+ SubscribersCardioSource Plus does not include access to CMP A personal subscription is required to access CMP.Use the same account for both CardioSource Plus and your personal subscription to keep your progress in sync. Online: Enroll on the official website, where you'll be prompted to purchase the subscription. By Phone: Call the support team at 800-253-4636, x5603, from 9:00 a.m. to 5:00 p.m. ET. {Pricing Blocks} Customizable Learning: Create custom quizzes to simulate Board exams. Highlight and bookmark important content for quick reference. Flexible Study Formats: Text & video learning options available. Closed-captioned lectures for accessibility. Print key materials to create flashcards. Access Anywhere: Study on any device with the web or mobile app. Always Up to Date: Get yearly content updates based on the latest research and guidelines. EPSAP Covers every major area of electrophysiologists medicine, from **Arrhythmias to Supraventricular Tachycardias. Cardiology Fellows preparing for Board certification. Practicing Cardiologists maintaining their certification. Cardiology Teams, including physician assistants and advanced practice nurses interested in electrophysiology. How to Prepare for the Boards Core Topics: Bradycardias, Arrhythmias, Heart Failure, Supraventricular Tachycardias, etc. Specialized Topics: Cardiac Implantable Electronic Devices, Clinical Scenarios and Syndromes, etc. [+] See Full Table of Contents Basic Physiology, Anatomy, Pharmacology, and Genetics Core Concepts of Clinical Arrhythmias Bradycardias and Conduction Disorders Atrial Arrhythmias Supraventricular Tachycardias Ventricular Arrhythmias Cardiac Implantable Electronic Devices Clinical Scenarios and Syndromes [+] Learner Objectives Upon completion of this activity, learners should be able to: Identify knowledge gaps and target study to fill those gaps in preparation for the ABIM Certification/Maintenance of Certification Exam in Clinical Cardiac Electrophysiology. Review and discuss one or more of the following to optimize the quality and provision of clinical care pertinent to the practice of clinical cardiac electrophysiology: Clinical and practice guidelines, recommendations and protocols Emerging research information and application to practice Quality and/or cost of care issues Multispecialty and multidisciplinary collaboration and communication Patient safety strategies Performance improvement Cultural competency [+] CME/MOC Information
In support of improving patient care, this activity has been planned and implemented by the American College of Cardiology Foundation (ACCF). ACCF is jointly accredited by the Accreditation Council for Continuing Medical Education (ACCME), the Accreditation Council for Pharmacy Education (ACPE), and the American Nurses Credentialing Center (ANCC), to provide continuing education for the healthcare team.The ACCF designates this enduring material for a maximum of 94.5 AMA PRA Category 1 Credits™. Physicians should claim only the credit commensurate with the extent of their participation in the activity.
Successful completion of this CME activity, which includes participation in the evaluation component, enables the participant to earn up to 94.5 Medical Knowledge MOC points in the American Board of Internal Medicine's (ABIM) Maintenance of Certification (MOC) program. It is the CME activity provider's responsibility to submit participant completion information to ACCME for the purpose of granting ABIM MOC credit. Once your MOC claim is submitted to the ACCME no modifications can be made to your overall credit claim. Participants can claim credit only once.Join thousands of cardiology professionals using EPSAP to maintain their certification and advance their knowledge. [Purchase]All our products are developed by top cardiovascular experts who bring real-world experience and cutting-edge research into this program. [View Faculty] Thank you to our dedicated faculty for making this an unparalleled learning resource!Access you SAP from ACC's Learn APP [App Store] [Google Play]
Learn More | link

ACCSAP -- Ultra Condensed

Tue, 01 Apr 2025 18:34:24 GMT

ACCSAP is the most comprehensive resource for adult clinical cardiology, designed to help you perfect your knowledge, earn credits, and maintain your certification—all in one place. Available Credits: CME | CNE | MOC | AAPA[Quick Purchase][Launch] 130 learning modules 50 video presentations +600 questions with supportive references. Stay Licensed & Certified Earn 190+ CME/MOC credits – enough for all certification requirements for 5 years. Pass Your Boards with Confidence Understand the ABIM blueprint while gaining access case-based questions with rationale and references. Escape the 10-year Exam Get access to CMP™, an alternative MOC assessment pathway, without the 10-year ABIM exam. Case-Based Learning for Real-World Skills Unlike traditional recall-based study methods, these questions focus on real-world clinical decision-making. [+] Attention CardioSource+ SubscribersCardioSource Plus does not include access to CMP A personal subscription is required to access CMP.Use the same account for both CardioSource Plus and your personal subscription to keep your progress in sync. Online: Enroll on the official website, where you'll be prompted to purchase the subscription. By Phone: Call the support team at 800-253-4636, x5603, from 9:00 a.m. to 5:00 p.m. ET. {Pricing Blocks} Customizable Learning: Create custom quizzes to simulate Board exams. Highlight and bookmark important content for quick reference. Flexible Study Formats: Text & video learning options available. Closed-captioned lectures for accessibility. Print key materials to create flashcards. Access Anywhere: Study on any device with the web or mobile app. Always Up to Date: Get yearly content updates based on the latest research and guidelines. ACCSAP Covers every major area of cardiovascular medicine, from Arrhythmias to Systemic Hypertension. Cardiology Fellows preparing for Board certification. Practicing Cardiologists maintaining their certification. Interventional Cardiology Teams, including physician assistants and advanced practice nurses. NPs and PAs preparing for the CCKE – ACCSAP now serves as a study guide for this exam. How to Prepare for the Boards Core Topics: Coronary Artery Disease, Arrhythmias, Heart Failure, Valvular Disease, etc. Specialized Topics: Sports Cardiology, Pregnancy & Cardiac Disease, Pharmacology, etc. [+] See Full Table of Contents How to Prepare for the Boards General Principles of Cardiovascular Medicine Arrhythmias Coronary Artery Disease Heart Failure & Cardiomyopathy Valvular Disease Pericardial Disease Congenital Heart Disease Vascular Diseases Systemic Hypertension and Hypotension Pulmonary Circulation Disorders Systemic Disorders Affecting the Circulatory System Miscellaneous Cardiovascular Genetics CPR, Post-Resuscitation Care Cardiac Critical Care Sleep Disordered Breathing Sports Cardiology Pregnancy and Cardiac Disease Cardiovascular Operative Management Pharmacology General Principles of Cardiovascular Medicine [+] Learner Objectives Upon completion of this activity, learners should be able to: Identify knowledge gaps and target study to fill those gaps in preparation for the ABIM Certification/Maintenance of Certification Exam in Cardiovascular Disease. Review and discuss one or more of the following to optimize the quality and provision of clinical care pertinent to the practice of cardiovascular medicine: - Clinical and practice guidelines, recommendations and protocols - Emerging research information and application to practice - Quality and/or cost of care issues - Multispecialty and multidisciplinary collaboration and communication - Patient safety strategies - Performance improvement - Cultural competency - [+] CME/MOC Information
In support of improving patient care, this activity has been planned and implemented by the American College of Cardiology Foundation (ACCF). ACCF is jointly accredited by the Accreditation Council for Continuing Medical Education (ACCME), the Accreditation Council for Pharmacy Education (ACPE), and the American Nurses Credentialing Center (ANCC), to provide continuing education for the healthcare team.The ACCF designates this enduring material for a maximum of 198.5 AMA PRA Category 1 Credits™. Physicians should claim only the credit commensurate with the extent of their participation in the activity.
Successful completion of this CME activity, which includes participation in the evaluation component, enables the participant to earn up to 198.5 Medical Knowledge MOC points in the American Board of Internal Medicine's (ABIM) Maintenance of Certification (MOC) program. It is the CME activity provider's responsibility to submit participant completion information to ACCME for the purpose of granting ABIM MOC credit. Once your MOC claim is submitted to the ACCME no modifications can be made to your overall credit claim. Participants can claim credit only once.The American College of Cardiology Foundation has been authorized by the American Academy of Physician Assistants (AAPA) to award AAPA Category 1 CME credit for activities planned in accordance with AAPA CME Criteria. This activity is designated 198.5 Category 1 CME credits.The ACCF designates this activity for 198.5 CNE contact hours. Nurses should claim only the credit commensurate with the extent of their participation in the activity.
AAPA Credit Designation Statement – Enduring Materials The American College of Cardiology Foundation has been authorized by the American Academy of PAs (AAPA) to award AAPA Category 1 CME credit for activities planned in accordance with AAPA CME Criteria. This activity is designated for 198.5 AAPA Category 1 CME credits. Approval is valid until February 5, 2025. PAs should only claim credit commensurate with the extent of their participation.Join thousands of cardiology professionals using ACCSAP to maintain their certification and advance their knowledge. [Purchase]All our products are developed by top cardiovascular experts who bring real-world experience and cutting-edge research into this program. [View Faculty] Thank you to our dedicated faculty for making this an unparalleled learning resource!Access you SAP from ACC's Learn APP [App Store] [Google Play]
Learn More | link

CATHSAP -- Ultra Condensed

Tue, 01 Apr 2025 18:34:09 GMT

CATHSAP is the most comprehensive resource for interventional cardiology, designed to help you perfect your knowledge, earn credits, and maintain your certification—all in one place.Available Credits: CME | MOC[Quick Purchase][Launch] 97 learning modules 43 video presentations +500 questions with supportive references. Stay Licensed & Certified Earn 135+ CME/MOC credits – enough for all certification requirements for 5 years. Pass Your Boards with Confidence Understand the ABIM blueprint while gaining access case-based questions with rationale and references. Escape the 10-year Exam Get access to CMP™, an alternative MOC assessment pathway, without the 10-year ABIM exam. Case-Based Learning for Real-World Skills Unlike traditional recall-based study methods, these questions focus on real-world clinical decision-making. [+] Attention CardioSource+ SubscribersCardioSource Plus does not include access to CMP A personal subscription is required to access CMP.Use the same account for both CardioSource Plus and your personal subscription to keep your progress in sync. Online: Enroll on the official website, where you'll be prompted to purchase the subscription. By Phone: Call the support team at 800-253-4636, x5603, from 9:00 a.m. to 5:00 p.m. ET. {Pricing Blocks} Customizable Learning: Create custom quizzes to simulate Board exams. Highlight and bookmark important content for quick reference. Flexible Study Formats: Text & video learning options available. Closed-captioned lectures for accessibility. Print key materials to create flashcards. Access Anywhere: Study on any device with the web or mobile app. Always Up to Date: Get yearly content updates based on the latest research and guidelines. CATHSAP delivers in-depth, up-to-date coverage of interventional cardiology, from case selection and procedural fundamentals to advanced techniques and complication management. Interventional Cardiology Fellows preparing for initial Board certification. Practicing Interventional Cardiologists committed to lifelong learning and MOC requirements. From Case Selection to Post-Procedural Care – Build expertise across every phase of interventional cardiology. Master Techniques & Tools – Includes fundamentals, coronary equipment, and advanced procedural strategies. Reinforce Core Knowledge – Anatomy, pharmacology, imaging, and the science behind successful interventions. [+] See Full Table of Contents Case Selection & Management Procedural Techniques I: Fundamentals of Cardiac Catheterization Procedural Techniques II: Coronary Interventional Equipment and Techniques Post-Procedural Care Complications of Coronary Intervention Catheter-Based Management of Noncoronary Disease Basic Science Anatomy, Anatomic Variants, Anatomic Pathology Pharmacology Cardiac Imaging & Assessment Miscellaneous Topics [+] Learner Objectives Upon completion of this activity, learners should be able to: Employ appropriate case selection and patient management strategies selection and patient management Apply the latest major clinical trial data for coronary, peripheral, and structural intervention Define the indications and appropriate utilization of coronary, peripheral, and structural intervention in the management of cardiovascular disease Discuss appropriate techniques for coronary, peripheral, and structural intervention Identify the issues of imaging, radiation risks and safety as they relate to coronary, peripheral, and structural intervention techniques Cite the current basic information relating to vascular biology, including plaque formation, injury and restenosis Demonstrate the appropriate utilization of pharmaceuticals in interventional cardiology, including antiplatelet agents, thrombolytics, anticoagulants, antiarrhythmics and vasoactive drugs [+] CME/MOC Information
In support of improving patient care, this activity has been planned and implemented by the American College of Cardiology Foundation (ACCF). ACCF is jointly accredited by the Accreditation Council for Continuing Medical Education (ACCME), the Accreditation Council for Pharmacy Education (ACPE), and the American Nurses Credentialing Center (ANCC), to provide continuing education for the healthcare team.The ACCF designates this enduring material for a maximum of 135 AMA PRA Category 1 Credits™. Physicians should claim only the credit commensurate with the extent of their participation in the activity.
Successful completion of this CME activity, which includes participation in the evaluation component, enables the participant to earn up to 135 Medical Knowledge MOC points in the American Board of Internal Medicine's (ABIM) Maintenance of Certification (MOC) program. It is the CME activity provider's responsibility to submit participant completion information to ACCME for the purpose of granting ABIM MOC credit. Once your MOC claim is submitted to the ACCME no modifications can be made to your overall credit claim. Participants can claim credit only once.Join thousands of cardiology professionals using CATHSAP to maintain their certification and advance their knowledge. [Purchase]All our products are developed by top cardiovascular experts who bring real-world experience and cutting-edge research into this program. [View Faculty] Thank you to our dedicated faculty for making this an unparalleled learning resource!This product was only made possible with the collaboration between the ACC and SCAI. {LOGO}{LOGO}Access you SAP from ACC's Learn APP [App Store] [Google Play]
Learn More | link

Refactors

Thu, 13 Mar 2025 18:15:21 GMT

A Refactor project at ACC.org focuses on systematically restructuring, optimizing, or modernizing a specific area of our digital ecosystem without altering its core functionality. The goal is to improve maintainability, performance, accessibility, and long-term sustainability while aligning with best practices in development, content management, and user experience.This process often involves: Code Optimization: Enhancing front-end and back-end code to improve efficiency, reduce technical debt, and ensure compliance with modern standards. Content Restructuring: Reviewing and reorganizing digital content within Sitecore or Sitefinity to streamline navigation, improve searchability, and eliminate redundancies. Design & UX Enhancements: Refining layouts, typography, and interaction patterns for better usability while maintaining consistency with ACC’s design systems, such as ARCHES and PaperCrane. Performance Improvements: Optimizing page load times, reducing server requests, and implementing caching strategies to enhance user experience. Integration & API Updates: Ensuring seamless connectivity between ACC.org, CRM systems (ONECRM), and external platforms (HubSpot, analytics tools). SEO & Analytics Refinement: Updating metadata, link structures, and tracking mechanisms to improve visibility and data accuracy. Each Refactor initiative is data-driven, with preliminary audits and analytics reports guiding decisions. The ultimate objective is to create a scalable, future-proof solution that enhances both user experience and backend manageability while preserving existing content and functionality. Process Flow Diagram
Pre Kickoff Collection Checklist
Refactor Process
Post Launch Checklist

Facet Page

Thu, 13 Mar 2025 18:13:11 GMT

First Draft Prototype

Structure & Guidance

Thu, 13 Mar 2025 18:12:21 GMT

Story First Content
Refactors Generic Page
Microsites
Full Page Splashes (Hubspot)
Single Page Applications
Product Pages Event Pages
Facet Page tags, clinical topic pages Link Farm

Untitled

Thu, 13 Mar 2025 18:11:18 GMT

Outline of Tickets for SPAs in Vue

Thu, 13 Mar 2025 18:10:39 GMT

Single Page Applications Ticket kicks all of this off Design and Requirements Technical Feasibility Design Iteration Follow Up from Technical Feasibility Basic Application: Data & API Basic Application: Page Construction, Code Branch, Page Access Basic Application: Vue APP SHELL Basic Application: Application Initiation. Component Construction: 1 – Many Tickets Application Specifics | Feature X scaffolding: 1 – Many Tickets Application Integration with Components | Feature X Refinement with QA: 1 – Many Tickets These types of tickets come in phases where many of the branches can work in partnership moving the designed application forward with some autonomy.These tickets are iterative and often are labeled the “Sprint 0” depending on the ask from the product owner and how developed the concept is before the team receives the project this will be iterative. Often this should be a set of meetings and reviews between the UX Team and Technical Architect and Front-End Senior Lead with responses sent back to the UX team and ultimately the Product Owner. Depending on how “Lean” you want to run the project this can be as lean as a rough sketch where the particulars are hashed out in the project to full-blown comps with requirement notes being captured in the Parent “Epic” Ticket. Initial talks of analytics should be talked about prompt the BL to reach out to the analytics team to establish this branch of the requirements.When the receiving team is comfortable with the clarity of the intended product this phase will break down the ask into dispersible tickets. Depending on the skill and resources these tickets can be sized appropriately for the team. Basic Application Construction can start on day one considering the scaffolding is fundamental to any other work.Independent work is brought together in this phase. It is common that co-working and JAD sessions occur in these tickets as team members bring together the individual efforts. There is no clean break of this phase to previous depending on the delivery it is common that a feature might go through all phases and be QA’d before other features are even started.Design Phase is the most prone to change. This phase should be mostly completed before the rest of the tasks should start. There is always reason, technical or just iterating over an experience that can cause changes to the design but if the team has a good idea of what is being built and rework will be reduced. The tenants of AGILE does allow for iteration so it is inevitable that rework or alteration will happen. Documenting for the team should migrate to comments on design documents because living design documents are costly and in the end are a non-production artifact. It is very important that the Technology Team (DEV & UI Lead) break down the steps and familiarize themselves with the nuances of the features to intelligently question the design and highlight possible issues before alterations become more impactful to the timelines. QA at this point can even scaffold out User Tests on features during this step.Team review of the UX design of Project X. Highlight and Flag and Feasibility Changes and Iterate over them with the UX team. Team will submit a scaffolding of tickets to produce the Application. Details should include Data needs, Implementation Specifics, Analytics definitions, and Front-End Breakdown.These steps are mostly dependent on the previous and could be collapsed to a single ticket but the ambiguity of the Data API it is best to keep these tickets into separate tickets to utilize a wider base of resources.API & Data Structures to support the application outline the data handshake and return results for App Build Team & UI Team.A user may only visit the URL if the user is logged in. The page will do all needed steps to redirect the user through log in in needed and redirect the user back to the page after success. Define URL & create the hosting page in Sitecore.A user should be able to visit a URL and have an application on that page respond to the visitor with the information it has available to it. Create the shell of the application and establish needed hooks to the data the application will know. This information is defined by the project but in the most basic definitions the application will know about the User, and possibly the URL and any query structures.When the user visits the application, and it is loaded the application will initiate and collect information through API calls to store any data that is needed to display information and formulate any actions needed for the user defined by the project.Components should follow the single tenant that they are only responsible for data passed to them and emitting their context. This separates concerns when the Application takes most of the features and components can stay agnostic.When creating components all new components will be created with the library’s project folder. If the team finds value for a specific component that is generic enough to be reusable across many applications, the component can be promoted to a common library folder. Be aware that common components require a greater level of flexibility and scope to make them bullet proof for generic consumption.Component tickets should encompass basic mutations that are needed for that component. Basic examples or mutations are Size, Location or Inclusion, Props (Data they will display), Validations, States, Etc. This should result in a Code Review and a Demo with UX Team and Product Owner. To reduce meeting overload, they can be grouped with other tickets or be deferred to the Feature Refinement TicketThe user should be able to see the data they need to see and interact with data as defined by the requirements this is known as feature. In many cases features can be scaffolded with their data and methods without the need of utilizing components. Operations of an application like looping, reductions, additions, removals, data hooks and server responses can be all worked out without the use of components.User should be able to do X Feature. For Example, “scaffold delete this line item from the list.” This will produce a data storage, list and methods and listeners that can be used to remove data from the list. This would also include any database API and deal with the response return updating the stored data of the list.Inclusion of components and refinement of the frontend features. These phases will “wire” data and properties to components into the application. Depending on the size of the application these can be broken down into Features, or Pages, or States. This is the moment where components are due from the front-end teams. The deployment of components can be more staggered if the team is more comfortable with constant deployments. The benefits of this would be a lister would be available much earlier in the development process but may need to be updated or rewired if changes to validation or data needs alter in the refinement process.User should be able to do X Feature in the AppFor Example, “A user by clicking on the delete button on a list item should delete it from the list.” Render a data list with the delete button. On the click add a listener to the application that will trigger the delete feature that has been scaffolded. QA this feature. Demo this Feature with UX Team and Product Owner.

JIRA Helpers

Thu, 13 Mar 2025 18:10:39 GMT

Single Page Applications
Bug Ticket Template
ARCHES New Component
ARCHES Component Conversion
AI Prompt - Conversion Tickets
AI Prompt - Craft UX Ask
AI Prompt - SCRUM TICKET V2
AI Prompt - SCRUM TICKET
AI Prompt - Writing Editing
Branch Template -
Internal Terms
KSS Documentation

ACC Products

Thu, 13 Mar 2025 18:10:39 GMT

Current Projects
Arches Conversion
1CRM
Page Creation Guidance
Page Creation Guidance
Microsites
Arches
Science and Quality
Edu Blocks
JACC
Bug Ticket Template
ARCHES Component Conversion
Single Page Applications
AI Prompt - SCRUM TICKET
AI Prompt - Writing Editing
AI Prompt - Conversion Tickets
#acc/guidance #requirements #acc

html optimization

Thu, 13 Mar 2025 18:09:28 GMT

rel=“preload, preconnect,dns-preconnect” lazy load=“true” but not largest contentful paint fetch priority =•”high,low”be careful with preload.

Page Creation Guidance

Thu, 13 Mar 2025 18:08:14 GMT

Microsites | Page Content | Story First Content 95% - Generic Page: Left Sidebar Navigation or Generic Page with Right Sidebar Related Items
4% - Full Page Function Pages | Full Page Splashes (Hubspot)
1% - Microsites Left Sidebar Navigation Most Content Pages Under: About, Membership & Tree Content Nav Areas Right Sidebar Related Content Articles Scans Article or JACC derivatives Search Pages Hub Pages (Root of the Navigation Tree) Clinical Topic Root of About, Education etc. Special Initiatives CMP, JOIN US., Annual Report
#acc/ux #acc/design #acc/guidance

Hub Spot Landing Pages

Thu, 13 Mar 2025 18:08:13 GMT

Building Landing Pages to better connect Marketing to the ask.

Current Analytics running on Project Scope

Thu, 13 Mar 2025 17:44:15 GMT

Assignee: Analytics Team Labels: Google Analytics, Usage Report, Web TrafficWe need the Analytics team to generate a snapshot Google Analytics usage report for all content within [Defined Project Scope] on ACC.org. The objective is to understand the current engagement and traffic patterns of the affected pages before content restructuring or updates. This report will help us make data-driven decisions about content prioritization and identify high-impact pages that need special attention. Target Pages: All pages and assets within [Defined Project Scope] (including Features folder). Any additional content types that might be relevant (videos, PDFs, downloads, etc.). Report Requirements: Traffic Metrics (Last 12 Months) Pageviews Unique Pageviews Bounce Rate Average Time on Page Exit Rate Sessions with these pages Engagement Insights Top-performing pages within the scope (highest pageviews & longest session duration). Pages with high bounce rates (indicating low engagement). Exit pages (where users leave ACC.org). Traffic sources (organic, referral, direct, paid, social). User demographics (geolocation, device type). Referral & Linkage Data External referral sources driving traffic to these pages. Internal navigation patterns (where users go next). Pages linking into the scope vs. pages linked from the scope. Search Performance (If available from GA and Search Console) Top search queries driving users to these pages. Click-through rate (CTR) from search results. Average ranking position of the pages in Google Search. Google Analytics Usage Report (in PDF or Google Sheets): Consolidated summary of page performance. Breakdown of traffic sources, engagement, and user behavior. Insights into high-value and underperforming content. Referral & Navigation Flow Report: Visualization of how users move to and from the pages in scope. Identification of critical traffic sources. Search Performance Report (if available): Keyword rankings and traffic trends for these pages. The Google Analytics Report is delivered and includes all requested metrics. Key insights are highlighted (e.g., high vs. low-performing pages). Referral and navigation data provide clarity on how users interact with these pages. If data is missing due to tracking limitations, a note explaining the reason is included. Access to Google Analytics and Google Search Console for ACC.org. Confirmation of the [Defined Project Scope] before pulling reports. Timeframe selection: If a standard period (e.g., last 12 months) is not appropriate, an alternative timeframe should be determined. If any pages lack tracking (e.g., missing GA tags), flag them for resolution. If applicable, consider segmenting reports by user type (e.g., members vs. non-members). If deeper analysis is needed, a follow-up request can be submitted based on the initial findings.

Existing Website Pages & Content Inventory

Thu, 13 Mar 2025 17:30:11 GMT

Assignee: Web Production Team Labels: Sitecore, Content Audit, Web ProductionWe need Web Production to conduct a preliminary audit of current content within Sitecore for ACC.org, specifically targeting all files and folders under [Defined Project Scope]. The objective is to provide a clear view of existing content and relationships within Sitecore, ensuring a smooth transition for upcoming updates and cleanup. Target Area: All files and folders within [Defined Project Scope], including the Features folder. Any associated media files stored in Sitecore that are referenced in this scope. Audit Requirements: Screen Grab Report: A structured visual audit of all files and folders within the defined scope. Linkages Report: A comprehensive list of all pages outside the project scope that reference or link to affected pages within the scope. Screen Grab Audit: Provide a set of screen captures displaying the folder structure and content files under Features and the broader [Defined Project Scope] within Sitecore. Ensure all screenshots clearly indicate file/folder names and paths. Linkages Report: A list of all Sitecore pages that contain links to any pages within the defined scope. Include the referring page URL, linked page URL, and any relevant Sitecore metadata. A complete Screen Grab Audit is delivered and reviewed. A Linkages Report (Word or Excel) is provided, listing all references to affected pages outside the defined scope. If any unexpected issues arise (e.g., restricted permissions, missing content, pages that are set to unpublishable), flag them for review. The audit results will help guide the next steps in the refactor efforts.

Refactor Process

Thu, 13 Mar 2025 17:13:01 GMT

A refactor is an effort to apply enterprise design and strategic guidance to a small section of pages or a specific zone of the website. A refactor enforces: Goal setting Audience focus Application of UI standards from Arches Content retooling based on the Content Strategy Playbook The optimal timeline, as outlined by the EDSC Teams, is 10 weeks. Timelines may shift due to business priorities, team response times, and scope changes. Delays can occur when external parties miss deadlines for returning deliverables or scheduling meetings. IT components, such as adding dynamic feeds and personalization, can extend the timeline by 3-6 weeks or more. The Refactor Team includes members from: Enterprise Content Team UX Team Client SME (Subject Matter Expert) responsible for providing necessary inputs to ensure project success. Step 1: Review (Weeks 1-3) Step 2: Content Design (Week 4) Step 3: Content Creation (Week 5) Step 4: Iterating and Reacting to Real Content (Week 6) Step 5: Editing (Weeks 7-8) Step 6: Publishing (Weeks 9-10) The Client submits a project intake form on the Monday Platform. Project intake review: Intake form is assessed. Team is assembled (Marketing, SME, Client, UX, EDS, Analytics). Kick-off meeting is conducted. Deadlines are reviewed. Project enters the UX and EDS backlog. Timeline begins once the project is picked up from the backlog. SME Responsibilities: Provide all relevant content (Web, Communications, Print Materials, Marketing). Meet with Analytics to define reporting needs. Evaluation & Retooling: Content is reviewed and adjusted based on goals and audience. Follow-up Discovery Meeting conducted. Tailored content delivery may include: Wireframes Process Flows Publication Schedules (Marketing involvement) Content Collection Documents Outline of required artwork (Marketing contribution) Content is completed based on refactor team guidelines. Marketing request: If required, artwork is created by Marketing. The content collection document may require a refactor of UI structures outlined in wireframes. Team reviews and finalizes: Artifacts Wireframes Content Design elements Artwork Once approved, materials are prepared for Production. The Refactor Team submits all final content and designs to the editorial team via Jira Ticket. The Refactor Team liaises with stakeholders to ensure smooth project progression through Author Site. SME, Marketing, and Client conduct final reviews and corrections on the Author Site. After final approval, the Web Production Team releases the Refactor Pages to the live site. Provides all necessary content. Engages in review meetings and approvals. Supplies required artwork and publication schedules. Supports promotional aspects of the refactor. Drive content design, review, and iteration. Ensure adherence to UI and content standards. Defines reporting needs. Evaluates data impact. Implements approved pages on the live site. Conducts final quality checks before release. This document provides a structured workflow to ensure an efficient and goal-driven Refactor Process.

Microsites

Thu, 13 Mar 2025 17:10:59 GMT

← back to ACC Products
Microsite DefinitionA microsite on ACC.org functions like a unique sub-website tailored for a particular purpose or initiative. Think of it as an independent information hub under the main site's umbrella, opening with a vibrant full-page introduction of its theme. Its content, organized in an exclusive structure of related sub-pages, enables users to delve deeper into the specific topic without other site distractions.Microsites represent a calculated approach for presenting semi-independent projects. While they adhere to most of ACC.org's branding guidelines, their unique design and structure allow them to serve as focused resources for users.However, creating a microsite is not always advisable due to costs and other considerations. It's generally reserved for significant initiatives that are notably important, brandable, unique, complex, and self-contained. In such instances, a microsite can offer significant value. Keep in mind this is a surface-level explanation.
Strategic Threshold for a Microsite
Checklist for a Viability
Anatomy of a Microsite
Pros & Cons
Hero Image with CTA Current state on ACC.org- areas of the site that do not have navigation or links back to the rest of the site. (Hopeful) Future state - A collection of pages that may sit within ACC.org, but do not share navigation and have different branding, in support of a specific activity for a set period of time.
#acc/ux
#acc/guidance
#acc/org/microsite

Microsite Definition

Thu, 13 Mar 2025 17:10:28 GMT

A microsite, also known as brochure pages, is an independent yet intergrated subsection within the main ACC.org framework. Microsites must have an established goal to be considered to be broken away from the main Acc.org framework. A clearly defined central focus and goal, the microsite serves as a concentrated platform for strategic communication and user interaction. This grouping of pages includes the basic branding of the main site while introducing: unique sub-branding elements, a sandboxed navigation structure. These components establish a distinct identity, subtly differentiating the microsite while preserving coherence with the main brand. The structuring of the microsite comprises multiple interconnected pages that form an exclusive navigation tree. This enclosed network ensures that each page links exclusively to other pages within the microsite, creating a tailored, immersive user journey. TLDR Quick Read Microsite: A distinct, yet cohesive, self-contained subsection within the ACC.org site. Sub Branding Elements: Unique branding features that distinguish the microsite from the main ACC.org brand, yet align with its basic branding. Enclosed Navigation Tree: The microsite encompasses a network of pages that interlink exclusively within its own scope, creating a customized navigation experience. Central Focus and Goal: The microsite is crafted with a specific objective, functioning as a dedicated communication and engagement platform. Aliases: The microsite is also known as Landing Page and Brochure Pages. Back to Microsites
#acc/guidance #acc/org/microsite

Full Page Splashes (Hubspot)

Thu, 13 Mar 2025 17:01:55 GMT

Full Page Splashes, orphan pages, or marketing landing pages are isolated pages within our website's architecture that are not linked from the homepage and should be used sparingly and strategically. These pages exist outside of our website's primary navigation and can inadvertently disrupt a user's browsing experience. As a rule, these pages should only be created in specific scenarios - such as part of a well-defined marketing campaign with a predetermined lifespan.Before implementing a Full Page Splash, ensure all of the following criteria are met: The page is directly tied to a specific marketing campaign. #checklist
The page has a limited lifespan with a clearly established takedown date. #checklist
The page is structured within the Sitecore folder, specifically under Parent of Main Branch/features. #checklist
The content is succinct enough to fit on a single page without overwhelming the user. #checklist
The content is not intended to be organically discovered from the main site, and does not contribute to the overall SEO strategy. #checklist
All intended conversion points are a single click away. → Buy, Register, etc... #checklist
Contacted the Analytics team in EDS to provide the user flow funneling that should be tracked and the defined markers for success. #checklist
Assess the potential impact on user experience. Ensure that the Full Page Splash aligns with the user journey and does not disrupt it. #checklist
Review the content strategy to ensure that the Full Page Splash complements it, rather than creating dissonance. #checklist
Evaluate the necessity of a Full Page Splash versus incorporating the content into the existing site structure. #checklist
Plan for future content updates or potential expansions. Will this information always be relevant as a standalone page or should it be integrated into the main site later? #checklist By sticking to these guidelines, we can maintain a cohesive, user-friendly, and purposeful website that aligns with our overall content strategy.There might be strategically valuable reasons to hook our Landing Pages being hosted on our email service so we could gain benefits of technology isolation, and built in Analytics.
#checklist #acc/guidance

Goals 2025

Wed, 12 Mar 2025 16:34:12 GMT

Establish a better understanding of process on how SMEs will be the work flow process.

Golden Standards ACC Content UI

Tue, 11 Mar 2025 18:33:30 GMT

Now that we have multiple pages that have gone through "Refactoring" there has been a collection of UI added to our capabilities. There has been some discrepancies and this is an attempt to make a golden standard for the UI that can been used. Hypothesis: Collecting either in the Prototype Site, Figma System or Arches Documentation so have the golden standard for the UI. FAQ - better aria standards Icon Lists With Link With Link in Content No Link Hero Image Classic Lava Flow Cards With No Image With Image CTA No Background Background Line Break Testimonial Quotes Row Feature Additional Notes:

D&I

Tue, 11 Mar 2025 18:33:30 GMT

Refactor of website

HFSAP

Tue, 11 Mar 2025 18:33:29 GMT

[Buy] Member: $1,500 Nonmember: $1,900 Reduced: $900 (FIT, CCA, Emeritus) [Launch]HF SAP covers the entire field of advanced heart failure and transplant cardiology, and is a great resource for: Perfecting Your Knowledge: Use this SAP to identify your knowledge gaps, reinforce your existing knowledge, and learn new information. Earning CME/MOC Credit: This product currently offers 40+ CME/MOC credits and medical knowledge MOC points. Access to CMP: Collaborative Maintenance Pathway (CMP) is an alternative yearly testing model for cardiologists wishing to meet their MOC assessment requirement by avoiding the 10year Exam . The CMP integrates lifelong learning with assessment and is the shortest path between learning and maintaining your credentials. [Learn more about the CMP]. Check your CMP Eligibility and Enrollment! [Start Now]

EPSAP

Tue, 11 Mar 2025 18:33:29 GMT

[Buy] Member: $1,500 Nonmember: $1,900 Reduced: $900 (FIT, CCA, Emeritus) [Launch]EP SAP covers the entire field of clinical cardiac electrophysiology, and is a great resource for: Perfecting Your Knowledge: Use this SAP to identify your knowledge gaps, reinforce your existing knowledge, and learn new information. Earning CME/MOC Credit: This product currently offers 90+ CME/MOC credits and medical knowledge MOC points. Access to CMP: Collaborative Maintenance Pathway (CMP) is an alternative yearly testing model for cardiologists wishing to meet their MOC assessment requirement by avoiding the 10year Exam . The CMP integrates lifelong learning with assessment and is the shortest path between learning and maintaining your credentials. [Learn more about the CMP]. Pass the Boards: Prepare for the Boards – learn about the ABIM blueprint, simulate taking a Board exam, practice with hundreds of ABIM-style questions that include rationale, references, and links to related text, learn from educational text and lectures, and identify your knowledge gaps so you can plan additional study. Check your CMP Eligibility and Enrollment! [Start Now]

CATHSAP

Tue, 11 Mar 2025 18:33:29 GMT

[Buy] Member: $1,500 Nonmember: $1,900 Reduced: $900 (FIT, CCA, Emeritus) [Launch]CathSAP covers the entire field of interventional cardiology, and is a great resource for: Perfecting Your Knowledge: Use this SAP to identify your knowledge gaps, reinforce your existing knowledge, and learn new information. Earning CME/MOC Credit: This product currently offers 135+ credits. That is enough credits and MOC points in Medical Knowledge for all your licensing and certification requirements for up to 5 years. Access to CMP: Collaborative Maintenance Pathway (CMP) is an alternative yearly testing model for cardiologists wishing to meet their MOC assessment requirement by avoiding the 10year Exam . The CMP integrates lifelong learning with assessment and is the shortest path between learning and maintaining your credentials. [Learn more about the CMP]. Pass the Boards: Prepare for the Boards – learn about the ABIM blueprint, simulate taking a Board exam, practice with hundreds of ABIM-style questions that include rationale, references, and links to related text, learn from educational text and lectures, and identify your knowledge gaps so you can plan additional study. Check your CMP Eligibility and Enrollment! [Start Now]

ACCSAP

Tue, 11 Mar 2025 18:33:29 GMT

[Buy] Member: $1,500 Nonmember: $1,900 Reduced: $900 (FIT, CCA, Emeritus) [Launch]ACCSAP is ACC's flagship self-assessment program covering the entire field of adult clinical cardiology, and is a great resource for: Perfecting Your Knowledge: Identify your knowledge gaps, reinforce your existing knowledge, and learn new information. Earn CME/MOC/AAPA/CNE Credit: This product currently offers 190+ credits. That is enough credits and MOC points in Medical Knowledge for all your licensing and certification requirements for up to 5 years. Access to CMP: Collaborative Maintenance Pathway (CMP) is an alternative yearly testing model for cardiologists wishing to meet their MOC assessment requirement by avoiding the 10year Exam . The CMP integrates lifelong learning with assessment and is the shortest path between learning and maintaining your credentials. [Learn more about the CMP]. Pass the Boards: Prepare for the Boards – learn about the ABIM blueprint, simulate taking a Board exam, practice with hundreds of ABIM-style questions that include rationale, references, and links to related text, learn from educational text and lectures, and identify your knowledge gaps so you can plan additional study. Check your CMP Eligibility and Enrollment! [Start Now] Interventional cardiology fellows-in-training preparing for initial board certification Practicing interventional cardiologists preparing for a maintenance of certification assessment or seeking an in-depth review of interventional cardiology Interventional cardiology team professionals, particularly physician assistants and advanced practice nurses Upon completion of this activity, learners should be able to: Identify knowledge gaps and target study to fill those gaps in preparation for the ABIM Certification/Maintenance of Certification Exam in Cardiovascular Disease. Review and discuss one or more of the following to optimize the quality and provision of clinical care pertinent to the practice of cardiovascular medicine: Clinical and practice guidelines, recommendations and protocols Emerging research information and application to practice Quality and/or cost of care issues Multispecialty and multidisciplinary collaboration and communication Patient safety strategies Performance improvement Cultural competency How to Prepare for the Boards General Principles of Cardiovascular Medicine Arrhythmias Coronary Artery Disease Heart Failure & Cardiomyopathy Valvular Disease Pericardial Disease Congenital Heart Disease Vascular Diseases Systemic Hypertension and Hypotension Pulmonary Circulation Disorders Systemic Disorders Affecting the Circulatory System Miscellaneous Cardiovascular Genetics CPR, Post-Resuscitation Care Cardiac Critical Care Sleep Disordered Breathing Sports Cardiology Pregnancy and Cardiac Disease Cardiovascular Operative Management Pharmacology General Principles of Cardiovascular Medicine

Made Possible By

Tue, 11 Mar 2025 18:33:29 GMT

Thank you to the editors, authors and question writers who make this product possible:{HEAD SHOT} {Label} {Name}

Features

Tue, 11 Mar 2025 18:33:29 GMT

{ACCSAP} Features lectures from ACC's Board Review and expanded resources for NPs and PAs. Serves as a study tool for the CCKE.[LINK] {CATHSAP} Features lectures from ACC’s Interventional Board Review course. Earn CME and MOC credit to stay licensed and certified.Focuses on case-based questions rather than simple recall.Each question includes links to additional resources.Yearly updates incorporate the latest science, guidelines, and trials.The Self-Assessment Programs (SAPs) are online and offer features to improve your learning:Easily revisit key questions.Print text and questions to create flashcards for studying.Lectures feature closed captions to help with understanding.Access the content from any device, anywhere.Text and video options for flexible learning.Simulate board exams for better preparation with custom questions.

eLearn Promo

Tue, 11 Mar 2025 18:33:29 GMT

Access you SAP from ACC's Learn APP [App Store] [Google Play] Learn More | link

Cardio Source Warning

Tue, 11 Mar 2025 18:33:29 GMT

Attention CardioSource Plus Users Planning to Participate in the CMPYour institution's subscription to CardioSource Plus does not include the CMP. If you want to participate in the CMP, you will need to purchase your own personal version of this SAP.[More Information]---MODAL---• Your institution's subscription to CardioSource Plus does not include the CMP. If you want to participate in the CMP, you will need to purchase your own personal version of this SAP. • As long as you use the same ACC.org account to access this SAP through CardioSource Plus and to access your personal subscription to HF SAP, your progress and usage data will be stored in one central location. This includes any time that you have already spent toward your 7 hours of Learning Engagement.• Order by phone. ACC's Member Care team may be reached at 800-253-4636, x5603 from 9:00 a.m. to 5:00 p.m. ET. • Order the SAP Online As Part of The Enrollment Process for the CMP (CMP enrollment for Interventional Cardiology is not yet open. ACC anticipates it to open in Q2 2020). Technical difficulties will prevent you from purchasing the SAP outside of enrollment.There is some different messaging in the modals. Labels and the Online Order Instructions. It is possible to universalize the messages if we go with the suggesting bellow. This would allow this entire area to be left to universal consistent and also evergreen. Drop the Date and use the generic label vs specific SAPS Validate that the Order online from the ACCSAP can be used for all the rest.

Additional Information

Tue, 11 Mar 2025 18:33:29 GMT

Content Section Grey Boxed{Unique Text}{Unique Text}{Unique Text}accordionsTerm of Approval/Date of CME & MOC Expiration: Rolling. Each topic's term of approval is displayed on the product's dashboard. {Unique Text}{{DATE}} and then rolling. Updates will be made every year.Your purchase provides you with the subscription duration of access from date of purchase.You may receive a full refund by canceling your order within 7 days of purchase. Claiming any type of credit for the product during that time will make you ineligible for a refund. No refunds or term adjustments will be permitted after the first 7 days of purchase.

Project Build Outline

Tue, 11 Mar 2025 18:33:28 GMT

Subject: Exciting Opportunity: Redesigning Member SectionsDear Team,As we embark on the transformative journey of redesigning our Member Sections, I want to share an overview of our strategic process and the essential tasks that will lead to our success. This initiative, commencing after the Annual Meeting in April 2025, involves over twenty sections and will require our collective effort to achieve outstanding consistency and quality.Leading up to April 2025, Jackie, Laura, and I will concentrate on several key tasks to establish a solid foundation: Proof of Concept (POC): We will finalize a robust WIC POC to define our preferred tone, brevity, and structure. This benchmark will guide all pages and content styles. Content Access Guidelines: After cleaning up existing content, Jackie and I will draft clear guidelines delineating public-facing content from that exclusive to members. We'll circulate this initial draft to the Tiger team for insights. IT Development Planning: Armed with the POC, we will collaborate with leadership to outline and align on our anticipated IT development requirements for dynamic content and and the user onboarding logic. Content and Resources Collection: Our team will create an effective initiation script and a user-friendly content collection form to streamline the content-gathering process for our liaisons. This groundwork will empower us to seamlessly engage with staff liaisons following the Annual Meeting.Content collection for our Member Sections is scheduled to begin in April 2025. To optimize our resources, we will prioritize which sections to revamp first. Kickoff Meeting/Workshop: We will introduce the dedicated project team and the creative assets needed for content collection. Matt and Jackie will lead a workshop to showcase an illustrative section while demonstrating the collection form. Content Collection Responsibilities: Each section team will undertake the content collection and refactoring, utilizing the WIC POC as their guide. Our oversight will ensure alignment and quality throughout the process. Completion of Content: Once content is gathered, our coordination team will collaborate with MarCom to generate essential images for prominent features. Quality Assurance: A JIRA ticket will be created to document the creation of the newly refactored Member Section, ensuring transparency and tracking. Editorial Review: Based on our priorities, the completed section will be processed, entered into Author, reviewed, and then published for production. Repeat for All Sections: This process will be repeated systematically for all remaining sections. Early 2025: Finalize the POC, establish clear content guidelines, plan IT development, and prepare liaison resources. Post-Annual Meeting (April 2025): Launch engagement with liaisons and section teams to kick off content collection. If you have any questions or need further insights on this exciting project, please don’t hesitate to reach out. Together, we can create an exceptional experience for our members.Looking forward to our collaboration, Matt & Jackie

GREY BOX -- CCKE- OUS

Tue, 11 Mar 2025 18:33:28 GMT

Summary: Hypothesis: Outline: Additional Notes:

CardioSmart 360

Tue, 11 Mar 2025 18:33:22 GMT

Mobile App with 3D rendered videos of the heart

About Us & Support Us Pages

Tue, 11 Mar 2025 18:33:22 GMT

The About Page holds little value as a hub and should be a great opportunity to control a story and craft an experiance.

Acc 24

Tue, 11 Mar 2025 18:33:21 GMT

work for the 2024 Annual Meeting

2025 Week 9

Tue, 11 Mar 2025 18:33:21 GMT

tags:: +Weekly Notes
<< Last Week | Next Week >> Golden Standards UI MY ACC Dropdown

2025 Week 5

Tue, 11 Mar 2025 18:33:21 GMT

tags:: +Weekly Notes
<< Last Week | Next Week >>

2025 Week 2

Tue, 11 Mar 2025 18:33:21 GMT

tags:: +Weekly Notes
<< Last Week | Next Week >> Golden Standard For the UI
State Chapters for BOG -- This has gone ghost mode
Gala FAQ, and Sponsors
Arches Conversion
Advocacy - In Editorial - Waiting on Building
CardioSmart 360 - Testing
Cardiosmart Arches Bugs.
CMP - Rowena
CCKE - Jackie Response to Affinity Projects. -- Project slated to 2nd or 3rd quarter
D&I -- Meeting on the books
NCD Academy -- Jacob is working the build finishing it up this week.

2024 Week 47

Tue, 11 Mar 2025 18:33:21 GMT

tags:: +Weekly Notes
<< Last Week | Next Week >> Burn out Goals
Presentation for Work/ACC/Projects/Member Sections Kicking off D&I with Jay
CCKE Structured Page
CMP CMP Revision Tickets to Go to Editors
NCD Academy Home Page and New Vaccine Page
2025 Week 5
State Chapters for BOG
Arches Conversion

2024 Week 46

Tue, 11 Mar 2025 18:33:21 GMT

tags:: +Weekly Notes
<< Last Week | Next Week >> Goals
CCKE
CMP
NCD Academy
2025 Week 5
State Chapters for BOG
Arches Conversion

2024 Week 44

Tue, 11 Mar 2025 18:33:21 GMT

tags:: +Weekly Notes
<< Last Week | Next Week >> Review and talk to Jae Brite about play book.
Review the NCD Academy Work. Improve the data points for the catalogue and create a render for it. ✅ 2024-10-30
ACC 75th Gala - NEW FAQ page & a new way to pay. Not Fire Fighting but taking up cycles is the Open Enrollment
CCKE
CMP
NCD Academy
2025 Week 5
State Chapters for BOG
Arches Conversion

Algorithm Read Me

Tue, 11 Mar 2025 18:31:30 GMT

The file includes all the necessary assets to create guideline algorithms, ensuring consistency across all designs. To maintain the established design system, use the provided color swatches, Illustrator panels, and graphic, character, and paragraph styles.These design enforcements support a consistent experience and are reader-focused, making the algorithms easy to read, understand, and provide valuable information like the CORs (Class of Recommendation). The algorithm is mostly monochromatic, with a focus on high contrast separation between the background and text to improve readability. COR colors are used specifically to highlight important information, ensuring that critical details stand out for the reader. Node and Decision Symbols: Always use the predefined symbols for nodes and decisions. These symbols are already designed to align with the correct COR color and shape, ensuring that each element is visually consistent and recognizable. Line and Label Symbols: Use the predefined line and label symbols to maintain consistent visual direction and clarity. Lines such as "YES," "NO," and the avoid markers are standardized for effective communication. Node Binders: Use symbols like NODE BINDER -- AND, NODE BINDER -- OR, and NODE BINDER -- ANY to represent logical connections between nodes clearly. This ensures that all decision junctions are presented in a consistent manner. Line Styles: Lines connecting nodes are styled consistently with arrows indicating the direction of flow. There are no variations in line thickness. Text Alignment: Text within each node should be aligned to the left and vertically centered to enhance readability. Legend Placement: Place the legend in the top right corner by default. If there is insufficient space, use the bottom right, followed by the bottom left. Legends should never be placed in the top left. Refer to the finished example to understand how these elements work together to create a consistent and branded algorithm design.The Illustrator file is set up with an artboard named "Toolkit," which contains all the essential elements for designing guideline algorithms. This toolkit includes: Symbols: Predefined symbols such as data nodes, decision shapes, and other graphic elements. Graphic Styles: Graphic Styles are used for line styles and arrows, applying the consistent look and feel to lines and arrows based on a simple line in Illustrator. Character Styles: The character styles in the file include options for titles, labels, node content, and more. Use the Title style for main headings, Zone Label for section labels, and Node Regular or Node Strong for content within nodes. There are also specific styles for COR Labels to ensure that Class of Recommendation values stand out appropriately. Paragraph Styles: Utilize the Paragraph Styles to maintain consistency across body text and labels. For instance, use Node Text for text within nodes and Footnotes for any additional information provided at the bottom of the algorithm. The Line Labels style ensures all directional labels (e.g., "YES," "NO") are clearly formatted. Color Swatches: The approved color palette for decision points and node types. Toolkit Artboard: Refer to the toolkit artboard to quickly access and apply these elements. Use the Toolkit: Start by using the elements provided in the toolkit artboard to maintain consistency. Smart Alignment: Use smart guides to align elements properly, ensuring nodes align in the same column for a clean and professional layout. Apply Character and Paragraph Styles: Always use the predefined character and paragraph styles to ensure that text formatting is consistent. This includes titles, labels, footnotes, and node content. Consistent use of styles helps maintain a reader-friendly experience and aligns with branding standards.

2024 Week 51

Mon, 06 Jan 2025 16:21:50 GMT

tags:: +Weekly Notes
<< Last Week | Next Week >> End of the Year Working plan of the roll out of Member Sections ✅ 2024-12-17 Continue evolution of the plan for POC for Member Sections D&I Review Audit from Jay Meet and formulate refactor. ✅ 2024-12-17 Respond to Afinity Project Train Jacob on Git hub data generators NCD Academy ✅ 2024-12-17 Cardiosmart released to production with bugs CMP - Rowena CCKE - Jackie Response to Affinity Projects.
D&I State Agendas Gala FAQ, and Sponsors
Arches Conversion
Advocacy - In Editorial - Waiting on Building
CardioSmart 360 - Testing
Cardiosmart Arches Bugs.

2024 Week 45

Fri, 13 Dec 2024 16:45:59 GMT

Most of the work last week was focused on Member Sections. Working on Presentation Production on the Prototype

2024 Week 50

Fri, 13 Dec 2024 16:45:48 GMT

tags:: +Weekly Notes
<< Last Week | Next Week >> END OF YEAR+ Onboarding Member Sections NCD Academy D&I Affinity Partnerships Pages Member Sections Presentation and Build out plan Everything Else

2024 Week 40

Wed, 11 Dec 2024 00:51:21 GMT

tags:: +Weekly Notes
<< Last Week
| Next Week >>
ACC redesign what are the Nodes of Content for the site? Is it as simple as "story" vs "collection" WhatIf.excalidraw About Page Competitive Research Plan Graphics having the wrong dates. Touch base with Brian about what is now capable in Hubspot. Careers - Pattern Work from the new design. About Page - Need to make Wireframe of proposed UI. NCD academy - we are putting together a plan on how to utilize YouTube as the entry path to Xyleme.
Error Handling - Can we use Artie
Work/ACC/Projects/Member Sections - Presentation of what we are proposing CCKE - Just not a priority from business. CMP - No interest to move on this. Interactive Map - Email to gather Sample PDF to make a better plan with details.
Hub Spot Landing Pages

2024 Week 39

Wed, 11 Dec 2024 00:51:21 GMT

tags:: +Weekly Notes
<< Last Week
| Next Week >> how to do we make enough that there is flexibility for a redesign but also enforce data structure and priories of messaging. As a college we are bad at using a template. Error Pages HubSpot CardioSmart Asset with Cybage ✅ 2024-09-30 Write email to start BOG collection of PDF for Map List Project. ✅ 2024-09-30 Building out code for HubSpot. Bad Puppy breaking things and having to clean up a mess for a significant amount of time this week. It was a gift that kept on giving.
About ACC as a real project kicked off by Laura Bicicchi New Home Hero Banner Feature.
Hub Spot Landing Pages
Error Handling
Work/ACC/Projects/Member Sections - Presentation of what we are proposing Careers - Pattern Work from the new design. Interactive Map CCKE CMP About has gone from a pet project into a real project with a 3 week deadline. Dropped the work for Hubspot. Wires and Design of About will kick off next week. Error handling we have pushed down in priority while about is on deck but still plan to up date before EOY
Good presentation to the tiger team around Work/ACC/Projects/Member Sections we left them on a process problem and what should be a technical solution issue that will need to go to IT. Personalization Lock Out and Login. ACC proper publishing pipeline.

2024 Week 36

Wed, 11 Dec 2024 00:51:21 GMT

tags:: +Weekly Notes summary:: last week was lost to meetings
<< Last Week
| Next Week >>
About Us & Support Us Pages About ACC and the Root Branching Page Problem Make Jira Tickets CCKE ✅ 2024-09-06
NCD Academy ✅ 2024-09-06 Presenting at EDSC Meeting ✅ 2024-09-06 Pain Points - ACC.org ✅ 2024-09-06
Gala Button Paths ACC 75th Gala ECSD Meeting Collateral Taxonomy Use Cases
Error Handling on ACC Error Handling
AI and the ACC
Work/ACC/Projects/ESC Competitive Research - Look at one of our greatest competitive
Work/ACC/Projects/Member Sections | Deep Dive into Evergreen Pages
Guideline Algorithm Design System Current Member | Hypothesis 2
Work/ACC/Projects/Member Sections | Deep Dive into Evergreen Pages Guideline Algorithms Current Member | Hypothesis 2
ACC 75th Gala Buttons Tickets Need to be Made in JIRA Accordion Improvement Personalization of Sections & Can this be a Product Based Feature?
CCKE - Waiting on Email Notifications, and the BL Touch Base
NCD Academy - Finished work ready to represent
Advocacy - with Jackie Pysarchuk I have passed off a starting point with this document Whimsical she wants to go through the sub pages and work through the next part for strategic reason before collaborating again. CMP - Waiting for BL Careers - Waiting on Green Light to start building out patterns Meetings Got in the way
Worked on NCD Academy with Rowena and Jackie made good progress and finished up the Grey box designs on the Project. NCD Academy
Did a brain dump with Diana H. on the topic of ACC redesign and shared the Pain Points
Did a small look at how to shape the site for consumption for AI AI Building Guidance
Read some great Articles from Rowena Enatsky from our new favorite product Whimsical
The product discovery process “If Henry Ford had asked people what they wanted, they would have said faster horses.” - Steve Jobs

Presentation Story

Mon, 18 Nov 2024 15:23:21 GMT

Intro How We Investigated the Problem Website Audits at Multiple Focused Levels: Content, Member Section Deep Dive, and UX Analysis Multi layered investigations have been done against this section of content Cutting the Fat & Taking out the Trash Website Content Audit We have discovered obsolete pages and reduces the content and value that we need to cater to. Enforcing a new pattern for content production to reduce the repeat of this issue in the future. Doc Matter will take on some of content that once lived here. The content that is left in this zone will be more aggressively archived to reduce regaining bloat. Dealing with the Customer Experience The Member Section Deep Dive has found the inconsistency has lead to a confused customer experience. Has lead to maintenance problems which as drained resources over the years stopping us from improving this facet of the Member Benefits to its fullest. Optimizing and simplifying can open up time and effort to really drive content and facilitation to return value back to the members. Structure Becomes the Same Content Channels become easier to follow Cross Usage and onboarding becomes simplified in messaging and action Reinforcing Value to Member Sections Member Section as a value exclusive access to tailored resources, mentorship, and leadership opportunities within specialized communities, helping professionals advance their careers, build credibility, and stay connected to the latest developments in their field. Access to Exclusive Content comes with putting the content behind a need to login. This can open up future opportunities to enrich this content from conversations started in Doc Matter and through Workgroup Polish made into valuable resources and toolkits specific to these member sections Specialized Gated Digital Communities of Doc Matter established areas to start mentorship, and leadership opportunities Linking Globally Published Content builds Nontreaty and Visibility of the Section How does this work in the real world - Prototype Example.

Intro Text by User Flow

Wed, 13 Nov 2024 20:36:06 GMT

You've arrived at a Member Section page, a gateway to our exclusive member benefits. These benefits, designed specifically for cardiovascular professionals, offer access to specialized communities, valuable content, and exciting opportunities to make a real impact in your field.To unlock these resources and start benefiting from our exclusive member perks, logging in is the next step.[Log in]By logging in, you can access available resources and support to help you on your professional journey.Section Name: Member Section is an exclusive American College of Cardiology member benefit.This account does not have an active membership.Membership is your key to unlocking these resources and being part of the community leading the charge to improve cardiovascular care and outcomes worldwide. By joining this section, you can access a network of like-minded cardiovascular professionals, educational content, professional development opportunities, and specialized communities like this section that support and amplify your work.[Learn More] | [Join]Membership unlocks access to the tools, resources, and community to help you make a difference.Member Sections allow you to deepen your connection with a specialized, topic-focused community within the ACC. Membership in a specific section helps you expand your influence, contribute to governance, and develop as a leader in the field.--Unique Pitch of the Section-- By joining [Section Name], you can connect with peers who share your interests, gain leadership experience, and make a meaningful impact within the College and the cardiology field. The Women in Cardiology Section offers a unique perspective on professional development, networking opportunities, and a space to strengthen your skills alongside supportive peers.*--Unique Pitch of the Section--*Call to Action: Take the next step in your journey—modify you membership to join the [Section Name] Member Section to enhance your professional support system, sharpen your skills, and amplify your impact. {{ BUTTON | Modify Membership }}--Unique Specific Message-- Take advantage of networking events, leadership opportunities, and specialized resources designed to empower you to make a difference in your career and the broader cardiology field. Your involvement in this community helps you grow and contributes to shaping the future of cardiovascular care.Call to Action: Explore the opportunities available to you now as a member of the [Section Name] Member Section, and discover how to further your journey in this vibrant, impactful community.--Unique Specific Message---- PRICE BLOCK -- As an FIT, you can join for FREE! Log-in to your member renewal portal to join a member section. Join member sections in your member renewal portal. {JOIN} -- PRICE BLOCK --

CCKE Content Proposal

Thu, 07 Nov 2024 22:29:17 GMT

This is an audit of the two Product Pages that currently have overlapping content. Below is a numbered list of the two pages, and how they will be referred to thereafter: Certified Cardiovascular Knowledge Examination (CCKE) For NPs/PAs Practicing in the U.S.: a. Referred to as CVTeam. Certified Cardiovascular Knowledge Examination (CCKE) For Physicians Practicing Outside the U.S.: a. Referred to as Clinician-OUS. The two pages—"CVTEAM" and "Clinician-OUS"—contain significant overlap and some type-specific content. The recommendations below aim to streamline and unify both pages for clarity and ease of navigation for users. Content can be categorized into three groups: identical, very similar, and type-specific. The goal is to consolidate identical content, modify the similar content to fit both groups where applicable, and keep type-specific information targeted to the specific audience. Unify Duplicate Sections: Many sections across both pages have the same or nearly identical content, such as "How Will the Exam be Administered?", "What is the Reliability of This Exam?", and "What Topics Are Included on This Exam?". Consolidate these into one central resource (such as a FAQ) that is shared between both audiences. Keep Persona-Specific Details Separate: Type-specific content should be kept separate where necessary to ensure that information remains relevant and directly applicable to each audience, e.g., "Who's Eligible to Take ACC's Certified Cardiovascular Knowledge Examination (CCKE)?" where eligibility criteria differ for NPs/PAs versus physicians. Create Cross-References to Simplify Navigation: Provide hyperlinks between shared sections and persona-specific pages to make it easier for users to navigate between general and specific content. This will improve the overall user journey by reducing the likelihood of confusion between similar content. The proposed AI structure helps streamline the content by focusing each page's role to enhance user experience, reduce redundancy, and provide clear navigation pathways even when users arrive at the wrong page variant. Product Page: Centralizes key exam-related content, making it the first point of reference for all users. It focuses on eligibility, application processes, exam administration, and a general overview, ensuring consistency and reducing noise by keeping shared content unified. Persona Detail Pages: Targeted at specific roles, these pages provide tailored details for eligibility, exam dates, preparation resources, and other specifics. By keeping type-specific information on dedicated pages, users can easily navigate to content relevant to their background without sifting through unrelated details. FAQ Page: Acts as a shared resource for questions that apply to both personas. This page will address common concerns, minimizing redundancy and providing a quick, centralized place for users to find general information. Hyperlinks will be used to direct users to persona-specific details where necessary. This structure is designed to help users who might have arrived at the wrong variant by guiding them to the right section, thus reducing user frustration and improving satisfaction.Consolidation of Identical and Very Similar Content: Move sections that are largely duplicated to a shared FAQ or product page. These sections include "How Will the Exam be Administered?", "What is the Reliability of This Exam?", and "Does the CCKE Offer a Credential?" Doing so will help reduce maintenance efforts while also improving consistency for users. Maintaining Persona-Specific Content: For sections that are specific to either "Clinician-OUS" or "CVTeam," create separate Persona Detail Pages. For instance, eligibility requirements, submission details, and exam dates vary between the two audiences. Keeping these sections separate but cross-referencing shared content will reduce confusion while allowing both pages to provide specialized information. Use of Accordion Components: Keep the collapsible accordion structure to allow users to access content in manageable portions, making the pages less overwhelming. Ensure that each accordion component has consistent headings and styles across both "CVTeam" and "Clinician-OUS" pages. Navigation Enhancements: To further reduce confusion, provide clear links at the end of shared sections like "How Much Does This Exam Cost?" to direct users to persona-specific details. If the two products cannot be merged, it is recommended to rebrand one or both products to ensure they are distinguishable and reduce confusion. The proposed rebranding involves the following: Certified Cardiovascular Knowledge Examination (CCKE) for NPs/PAs Practicing in the U.S. (CVTeam): Maintain existing branding, but emphasize that this version of the exam is specifically for U.S.-based Nurse Practitioners and Physician Assistants. Certified Cardiovascular Knowledge Examination (CCKE) for Physicians Practicing Outside the U.S. (Clinician-OUS): Rebrand this product to differentiate it more clearly from CVTeam. Consider adding a geographic or professional distinction to the name, such as "International Cardiovascular Knowledge Certification" or "Certified Cardiovascular Competence for International Physicians". Visual and Structural Distinction: Introduce distinct color schemes or visual markers on both product pages to signal the difference at a glance. Update headers and footers to clearly mention the audience for each product, e.g., "For Physicians Practicing Outside the U.S." vs. "For U.S.-based Nurse Practitioners and Physician Assistants". Clarify Naming Across All Communications: Update all marketing, email, and support documentation to ensure that users are consistently seeing the rebranded names. Ensure that cross-references between the products are explicit about the intended audience to avoid any ambiguity. The goal of the rebranding effort is to reduce confusion, particularly among members who may be unsure which certification is appropriate for their professional background. By creating a stronger distinction between the two certifications, ACC can improve user satisfaction and reduce the potential for misapplication.

User Journey Prompt

Thu, 07 Nov 2024 22:27:54 GMT

To access the [Section Name] Member Section you need to be a member of both College and the section.First Step is to log in. [Log In](https://www.acc.org/login?returnUrl=[Section URL]) You must be a member of the American College of Cardiology first to gain access to [Section Name]: Member Section.
Learn More
Join the College Something Not Right?
Contact ACC Member Care
800-253-4636, ext. 5603
202-375-6000 You are a member of the American College of Cardiology, but you do not yet have access to the [Section Name] Member Section. Join the [Section Name] by managing your membership.
Manage Membership Something Not Right?
Contact ACC Member Care
800-253-4636, ext. 5603
202-375-6000 Welcome to the [Section Name]: Member Section! You now have access to exclusive content, member benefits, and experiences.
[Access Exclusive Content](https://www.acc.org/login?returnUrl=[Section URL])

No Content Change Proposal

Mon, 04 Nov 2024 18:26:41 GMT

The Certified Cardiovascular Knowledge Examination (CCKE) is designed for healthcare professionals who want to demonstrate their expertise in cardiovascular medicine. It is an opportunity for NPs, PAs, and other clinicians to validate their knowledge, enhance their careers, and contribute to the standard of excellence in cardiovascular care. To learn more about the application process, eligibility requirements, and how to apply, continue exploring our resources. -- Button Primary | Learn About the Application Process -- -- Button Secondary | Learn More About the Exam -- Validate your clinical knowledge Boost job prospects in cardiology Uphold excellence in patient care Earn credits towards FACC/AACC Advance your career and enhance your reputation Be recognized as an expert in CV care -- Button Primary | Apply Now to Get Certified --Learn about the steps you need to take to apply for the CCKE, including eligibility requirements and application submission. See the Application Instructions, Checklist, and Exam Tutorial to prepare for Exam Day.
See the FAQ with resources to prepare. -- Button Primary | Register for the CCKE Exam Now -- Discover study resources, exam details, and essential preparation tips to help you succeed in your certification jouney.
A Clinical Review Guide is available for your exam preparation. Examines can also utilize ACCSAP at a discounted rate along with other resources to prepare. For more information, see the FAQ "What Resources Does ACC Offer to Help Me Prepare For the CCKE?". -- Button Primary | Explore Preparation Resources --Learn what to expect after completing the exam, including scoring, certification details, and retake policies.We are proud to celebrate the hard work and dedication of the NPs and PAs who have successfully earned the Certified Cardiovascular Knowledge (CCK) credential. Your commitment to advancing cardiovascular care is an inspiration to others in the field, and we commend your achievement. -- Button Primary | Meet the Credential Holders ---- Button Primary | Go to Application Process -- Get access to study materials, clinical review guides, webinars, and tips to prepare effectively for the exam. -- Button Primary | Visit Preparation Resources --Exam Details Find out everything you need to know about the exam structure, administration, content, and policies. -- Button Primary | View Exam Details --After the Exam Learn what to expect after completing the exam, including scoring, certification details, and retake policies. -- Button Primary | Learn About What Happens After the Exam --Explore frequently asked questions and information on special testing accommodations. -- Button Primary | See FAQs and Additional Information --

CCKE

Mon, 04 Nov 2024 15:14:40 GMT

Improve the product experience of the sister products CCKE NPA and CCKE OUS

2024 Week 42

Wed, 30 Oct 2024 21:08:34 GMT

<< Last Week | Next Week >>

2024 Week 41

Wed, 30 Oct 2024 21:08:34 GMT

tags:: +Weekly Notes
<< Last Week | Next Week >> About Page and Generators from CSV for complicated UI Patterns Japan
Jekyll patterns for About Us & Support Us Pages, and Careers. ✅ 2024-10-09
https://acc-style.github.io/PrototypingACCorg/arches/About/
https://acc-style.github.io/PrototypingACCorg/arches/CareerBlocks/ Looking to standardize the patterns that have slightly muted on ACC.org from our new arches pages. Putting in Journal Scans for updates on acc.org VDI breaking on Friday and making every thing harder and going rouge with our security policy. NCD Academy Member Sections Error Pages - Sadly learned we can not use Artie (Legal Reasons) on the website so we will have to come to a different approach for the images for the Error page. CCKE - Gone Dark CMP - Gone Dark About - Waiting on content updates Home Page Button -IT Arches Article Map List - Waiting on Agendas Advocacy - Waiting on feed back and first draft of content that aligns to design
About page i have shown Jacob where to get the latest design for the project and put in all connections to SiteCore. The project is as done as it can be with out the final content documents from Laura Bicicchi

Pasted image 20241030170446

Wed, 30 Oct 2024 21:04:46 GMT

NCD Academy

Wed, 30 Oct 2024 16:20:39 GMT

A sponsor of the product wants to hit a certain number of video watches.

2024 Week 43

Mon, 28 Oct 2024 19:23:30 GMT

tags:: +Weekly Notes
<< Last Week | Next Week >> Naps, catching up on emails Getting back in the groove. State Chapter BOG POC ✅ 2024-10-25
ACC 75th Gala - NEW FAQ page new way to pay.
CardioSmart 360 QA SWG UAT Picking back up:
CCKE
CMP
Advocacy
NCD Academy
State Chapters for BOG - Got Agenda and Pass it back to Miriam to Approve and Collect all Agendas. Careers Project is in construction with Jacob
Created Structured Data and Prototype

State Chapters for BOG

Fri, 25 Oct 2024 14:17:11 GMT

a centralized viewing area for state chapter agendas.

Maximize Conversions with Integrated Marketing

Wed, 09 Oct 2024 17:03:48 GMT

Email MarketingHere’s a streamlined process flow for utilizing Direct Marketing Emails, Social Posts, and Web Marketing to drive users to landing pages with single goal CTAs, optimizing for conversion: Objective: Whether the goal is membership sign-up, promoting a specific product, or encouraging course enrollment, start with a clear and single-focused goal. Audience Segmentation: Use member data to segment your audience (e.g., new vs. existing members, product preferences, or education needs). Tailor your messaging accordingly.
Personalized Messaging: Send segmented, targeted emails based on member interest or product interaction. Use personalized subject lines and content to engage the recipient. Single CTA Focus: Keep the email concise, focusing on one action—whether it's signing up for membership, taking a course, or learning more about a product. Visual Hierarchy: Design with a clear CTA button or link, driving to a landing page. Limit distractions or additional links. Example: “Unlock exclusive member benefits” with a CTA leading to a landing page with a “Join Now” button. Follow-up Emails: If no action is taken, send follow-up reminders, highlighting urgency or limited-time offers.
Awareness & Engagement: Post engaging, relevant content that raises awareness about the specific service or product. Use visuals (images, videos) that catch attention quickly. Clear CTA in Posts: Always include a direct link to the landing page with a single action goal, such as “Learn More”, “Join Today”, or “Enroll Now”. Varied Post Types: Rotate between promotional posts (e.g., “Limited time offer on our educational courses”) and value-based posts (e.g., testimonials, expert tips) to maintain engagement. Boosted Posts & Ads: Use paid promotions on social platforms to target users based on demographics or past interaction, driving them to the dedicated landing page.
Engagement-driven CTAs: Use CTAs like “Get Started” or “Explore More” to reduce friction in the initial click. Banner Ads & Pop-ups: Design targeted ads that appear on key sections of your website. Ensure that these ads promote the single focused CTA (e.g., membership sign-up or course enrollment). Single Goal CTA: Each landing page should have one clear CTA, whether it's "Join Now", "Sign Up", or "Purchase". Avoid clutter and additional links that could distract users from the primary goal. Consistent Messaging: Ensure the landing page reflects the content of the email, social post, or web ad that drove traffic to it, creating a seamless and relevant user experience. Urgency & Value Proposition: Use language that emphasizes urgency (e.g., “Limited time offer”) and the value proposition (e.g., “Exclusive benefits for members”). Mobile Optimization: Make sure landing pages are mobile-friendly for users arriving via mobile social posts or email.
Track Conversions: Use tools like Google Analytics, UTM codes, or your CRM to monitor which channels (emails, social posts, or web ads) are driving the most traffic and conversions. Abandoned Landing Page Follow-Up: If users visit the landing page but don’t convert, trigger automated reminder emails or retargeting ads to bring them back, offering added incentives or urgency. Next Steps for Conversions: Once a user converts, deliver a thank you email or confirmation page, guiding them to the next step in their member journey (e.g., onboarding for members, product usage tips).
Direct Email: Send an email to non-members emphasizing the value of membership (e.g., “Unlock exclusive access to resources, discounts, and courses”). Clear CTA: “Join Now” → Redirect to membership sign-up landing page. Social Media Post: Post a testimonial or success story from a current member, emphasizing the benefits. Clear CTA: “Learn More” → Redirect to landing page that further explains membership benefits. Website Banner Ad: Place a banner on relevant blog or content pages: “Become a Member Today and Get Access to Premium Courses”. Clear CTA: “Join Now” → Redirect to landing page optimized for membership sign-ups. By focusing on single-action CTAs, and maintaining consistent, clear messaging across all communication channels, this process maximizes the chances of conversion from email, social, and web marketing efforts.

Maximize Conversions with Integrated Marketing

Wed, 09 Oct 2024 17:03:45 GMT

Home Page Hero Update

Fri, 27 Sep 2024 15:09:28 GMT

The Hero Image on the homepage will now support an optional overlay button. This button will be configurable by content editors, allowing them to set the URL, text, style (primary or secondary), and position on the image based on different breakpoints (phone, small tablet, large tablet, and desktop).Scope of the Feature: If there is no URL and Label included in the configuration of the component the hero image area will not be clickable and the render will not render any button UI. It is MarComs responsibility to deliver an images in the correct size and dimensions with non critical information in the area where the button will be positioned. Sizes: 300x350, 600x300,900x300,1200x400 Accepted images are PNG, JPG You can only choose 1 button position, style, URL, and label for all break points. The entire area of the Positioning grid will be clickable and cause the button to hover. The cards part of the feature will also will have their click box expanded to their entire area. Acceptance Criteria: Button Configuration Options: URL: Editors can input the target URL for the button. This URL if empty and the Label is included should default to About-ACC URL Label: Editors can input the display text for the button. Style: Primary Button: Teal blue with white text. Secondary Button: Light grey with black text. ACC Brand Button: ACC Blue with white text ACC Brand Reversed: White with ACC Blue Text Position: Options: 'Left', 'Center', and 'Right'. Position varies depending on the breakpoint (refer to the "Button Position Based on Breakpoint" section below). Button Position Based on Breakpoint: Button Positioning Grid: the Grid inset is 0 0 60px 0 to the full width and eight of the image. 1 rem padding from the edge of its inset image. The hit area of the image should be the entire area. Phone: Aspect Ratio: 3 (width) x 4 (height) Button should size down one step from normal. Uploaded Size: 300w x 350h Grid Layout: 1 column x 3 rows Positioning: Regardless of 'Left', 'Center', or 'Right' setting, the button will be centered in the bottom row. Small Tablet: Aspect Ratio: 2 (width) x 1 (height) Uploaded Size: 600w x 300h Grid Layout: 2 columns x 2 rows Positioning: Left: Bottom-left cell, centered vertically and horizontally. Center: Bottom row, centered horizontally and vertically. Right: Bottom-right cell, centered vertically and horizontally. Large Tablet: Aspect Ratio: 3 (width) x 1 (height) Uploaded Size: 900w x 300h Grid Layout: 3 columns x 2 rows Positioning: Left: Bottom-left cell, centered vertically and horizontally. Center: Bottom center cell, centered horizontally and vertically. Right: Bottom-right cell, centered vertically and horizontally. Desktop: Aspect Ratio: 3 (width) x 1 (height) Uploaded Size: 1200w x 400h Grid Layout: 3 columns x 3 rows Positioning: Left: Bottom-left cell of the last row, centered vertically and horizontally. Center: Bottom center cell of the last row, centered horizontally and vertically. Right: Bottom-right cell of the last row, centered vertically and horizontally. Responsive Behavior: The button's position and size should adjust dynamically based on the device's screen size and aspect ratio. The button should not overlap important text or imagery unless specified in the design guidelines. ( this will be the responsibility of theMarCom to not place critical information in the art in the areas they selected for the button placement. ) Editor Preview: Provide a preview in the CMS where editors can see how the button will look on different breakpoints before publishing. QA Testing Notes: Test button configuration for all breakpoints. Validate button positioning aligns with the specified grid layouts. Verify that styling changes correctly based on editor selection. Test keyboard navigation and screen reader accessibility. Design Reference: See XD Link: https://xd.adobe.com/view/bd608e30-7c5e-45eb-bf89-aab42b492ae3-e833/

Annual Meeting 2024

Thu, 26 Sep 2024 13:20:06 GMT

Survey and UX work from the 2024 Conference

Pasted image 20240924173524

Tue, 24 Sep 2024 21:35:24 GMT

Pasted image 20240924173458

Tue, 24 Sep 2024 21:34:58 GMT

Pasted image 20240924173440

Tue, 24 Sep 2024 21:34:40 GMT

Pasted image 20240924173411

Tue, 24 Sep 2024 21:34:11 GMT

Pasted image 20240924173344

Tue, 24 Sep 2024 21:33:44 GMT

Pasted image 20240924173258

Tue, 24 Sep 2024 21:32:58 GMT

Pasted image 20240924173228

Tue, 24 Sep 2024 21:32:28 GMT

2024 Week 38

Mon, 23 Sep 2024 13:08:46 GMT

Mostly Sick

+Weekly Notes

Mon, 23 Sep 2024 13:07:08 GMT

JACC Editors at ACC24

Fri, 20 Sep 2024 18:47:03 GMT

After meeting with the editors of JACC here are some free flowing notes.So many products. Derivatives are pipelines to amplify stories Central illustration to pull users into the article to buy. JACC intervention is a pay walled. CME UPON READ CARDIOSMART derivatives need to be hooked to articles. Cardio smart animation include Need storage resource pocket guide. No one in the room has gone to the home page. Social broadcasting schedules Group collaboration Al a cart options for social broadcasting Jackie@ Edge personalization. Jacc and disclosures?Annual Meeting

AI Prompt - Conversion Tickets

Fri, 20 Sep 2024 18:47:03 GMT

Comprehensive Prompt Template for ChatGPT Interaction and Backlog Ticket Creation KSS DocumentationContextual Setup for My Request:I want you to understand and act in the specific context of being a Product Owner on a SCRUM team. Your role is to write backlog tickets for a new feature, considering all aspects typical of a Product Owner's responsibilities in a real-world scenario. I expect the tone and approach of your responses to reflect this role and context. After the prompt please ask up to 3 follow up questions if you any clarifications or supporting details. Here are some key points I want you to consider: SCRUM Methodology Awareness: You should demonstrate a clear understanding of SCRUM principles and practices. Role-Specific Knowledge: As a Product Owner, your focus is on maximizing the value of the product and the work of the development team. Feature-Specific Requirements: The backlog tickets you will create should be for a specific feature, detailed in my request. User-Centric Approach: Emphasize the importance of user stories and prioritize tasks based on user needs and project goals. Communication Style: Your responses should mirror the communication style of a Product Owner - clear, decisive, and oriented towards actionable items. Writing Style: Concise and clear, with a preference for listing items rather than writing out in sentences, to facilitate easy scanning. Project Introduction: Subject Matter: Tech stack - ASP, Vue, HTML, CSS, JavaScript, CMS Sitecore or Sitefinity Internal Terms: [Clarification on terms like ARCHES, PaperCrane, ACC.org, CardioSmart, etc.] ARCHES is a comprehensive front-end design system by the American College of Cardiology. It uses advanced compiler techniques to generate variations that integrate with different frameworks and brands, making it versatile for various ACC products. ARCHES primarily consists of utility classes that offer a modern approach to CSS, focusing on single-style control and separation of responsibilities between HTML and CSS. This system is flexible and adaptable, used across multiple ACC platforms, including ACC.org and CardioSmart, and supports distinct brand styles while maintaining overall coherence. PaperCrane refers to a Component Library specifically designed for Vue.js, a progressive JavaScript framework. This library is utilized in the development of Single Page Applications (SPAs). PaperCrane contains a collection of pre-built Vue components which can be reused across different parts of the enterprise application, enhancing development speed and ensuring UI consistency. ACC.org ACC.org is the official website of the American College of Cardiology. It serves as a comprehensive resource for cardiology professionals, offering a wide range of content including clinical updates, educational materials, guidelines, and information on cardiology conferences and events. The site is designed to support medical professionals in the field of cardiology with the latest scientific research, policy advocacy, and continuous education. It also provides tools and resources for practice support, quality improvement, and patient care in the cardiovascular field. The website caters to the needs of cardiologists, providing them with essential information to advance their knowledge and practice. CardioSmart.org is a patient-centered website created by the American College of Cardiology. It provides comprehensive information about heart health and various cardiac conditions. The site is dedicated to educating patients, offering resources on heart diseases, healthy living tips, and tools to manage cardiac health. It includes topics such as heart disease prevention, treatment options, and lifestyle changes. CardioSmart.org is designed to empower patients with knowledge and tools to actively participate in their own heart care and make informed decisions about their health. Backlog Ticket Structure: Title: A concise, descriptive title for the feature or issue Description: Background: Brief context or background information. Objective: Clear statement of what the ticket aims to achieve. User Story: Format - As a [type of user], I want [an action] so that [a value or result]. Acceptance Criteria: List of conditions that must be met for the ticket to be considered complete. Should be specific, measurable, achievable, relevant, and time-bound (SMART). Dependencies: Any dependencies or prerequisites for the ticket. Checklist for Components: Component Definition: Define the zone, providing a screenshot, requirements from an editor's perspective, and the URL location. Component Identification: IT to identify and isolate the component. Design Implementation: A front-end designer/developer to create an HTML prototype of the component using the Arches design system. Group Grooming: Conduct a group grooming session to identify any additional tickets or tasks necessary to complete the story. Backlog Ticket Creation:Follow the Updated Backlog Ticket Structure provided above to detail your response for this ticket In the Prompt Details below I will detail the information I have for the ticket.Prompt Details: Heading: [Specify the heading for the response.] Introduction: [Brief introduction about the request or the aspect of the project being addressed.] Main Content: [Detailed response or the created backlog ticket based on the structure provided, presented in a concise, list-based format for easy scanning.] Component Name: [A short name of the component to be used in the repo] References or Sources: [If required, mention the need for citations or sources.]

A Full Project List

Fri, 20 Sep 2024 18:46:59 GMT

Please check the meta data below to see if I have kept this up to date.Metadata Created:: 5:37 PM - September 16, 2024 Updated:: 2:46 PM - September 20, 2024

ACC 75th Gala

Fri, 20 Sep 2024 18:46:58 GMT

build a landing page to the 75th Gala

Color Test

Fri, 20 Sep 2024 18:46:55 GMT

Most of the document is based on a white background so it is cheaper to print. All readable Text needs to be higher then 7:1 for 12pt text proper AAA adherence. The AA adherence is set at 4.5:1. So 90% black text on a shaded background of 30% is not with in design acceptabilityDOCUMENT GREYS

Jira Tickets Arches

Fri, 20 Sep 2024 18:46:51 GMT

Stay on top of the process of tickets that need to go into the pipeline to be fixed. Micro banner Grid Bug Article Pages Article Children Rendering Hypothesis: Outline:
**Additional Notes: Jira Tickets notes
Carousel
Show Hide Text

Article Children Rendering

Fri, 20 Sep 2024 18:46:50 GMT

Backlog Ticket: Article "Children Renderings" Conversion to Arches Title: Convert Article Subtypes to Arches Format Description: Background: Currently, the Sitecore renderings for article subtypes are not compatible with our ARCHES system. These subtypes include ClinicalTrial, GuidelineHub, JournalScan, PressRelease, Recommendation, TenPoints, and potentially others not listed. Objective: To successfully convert the "children renderings" of articles into the ARCHES format, ensuring seamless integration with the CMS and maintaining consistency across ACC platforms. User Story: As a developer, I want to convert the Sitecore renderings for article subtypes into the ARCHES format, so that articles can be more efficiently managed and displayed across ACC's digital platforms. Acceptance Criteria: A working version of all article children types is established in a local environment. The conversion of all identified children renderings into the ARCHES format is completed. Ensure that the new ARCHES renderings are fully functional and compatible with existing CMS infrastructure. Maintain visual and functional consistency with the overall design and layout standards of ACC platforms. The conversion process and final output should be documented for future reference and maintenance. The conversion should be completed without causing any downtime or disruption to live services. Dependencies: The ticket depends on the successful setup of a local development environment for the joint development effort. This ticket blocks the work for APPSUPPORT-22095. Coordination with the team members (Ling, Matt, Rowena, Jacob, and ASP Dev) for a 3-hour joint development meeting is crucial. Notes for Joint Development Meeting: Confirm attendance and availability of all required team members. Ensure all necessary tools and resources are accessible during the meeting. Set clear objectives for the meeting to maximize productivity. Allocate time for discussion, development, and troubleshooting.
References for Article Types: LiC Article Templates.docx (sharepoint.com)

Carousel

Fri, 20 Sep 2024 18:46:50 GMT

Hero Banners & Micro Banner

Fri, 20 Sep 2024 18:46:50 GMT

Component needed for the Microsite

Jira Tickets notes

Fri, 20 Sep 2024 18:46:49 GMT

components? background image with text feedwind - remediation need to wrap in a component

Show Hide Text

Fri, 20 Sep 2024 18:46:49 GMT

Editorial team makes use of a Show/Hide UI feature frequently. As part of the Arches conversion, the individual instances of this will be stripped. We need to rebuild this functionality in a way that makes it easy for editors to add these expand/collapse blocks. Attached is a version of the current code for reference. ` Create Component ⏫ ➕ 2023-07-10 #acc/jira

Current Member (Engaged Member)

Fri, 20 Sep 2024 18:46:48 GMT

Summary: Hypothesis: Outline: If you were going to set up some sturctured data around engagement I think it would include these Engagement - Structured Data

Engagement - Structured Data

Fri, 20 Sep 2024 18:46:47 GMT

Title of Opportunity Clear and descriptive title Overview Brief summary of the opportunity Goals and Objectives Specific aims and intended outcomes Required Skills and Qualifications List of necessary skills, experience, and qualifications Time Commitment Estimated hours per repeatable timing for a total duration Location: Remote, Local, Travel Compensation and Benefits Details on stipends, perks, or other benefits Organization Information Name, mission, and reputation of the effort Impact and Value Description of the expected impact and value to participants and the community

Section Personas

Mon, 16 Sep 2024 22:20:01 GMT

Here are all four personas, incorporating the updated preferences: Name: Emma Wright Demographics: 42, Cardiologist, Busy Practitioner Engagement Style: Emma frequently visits the member section but rarely interacts. She uses the platform to gain exposure to new ideas and practices outside the confines of her immediate professional environment. Though she doesn't contribute to discussions, she values the ability to access diverse perspectives and knowledge that she might not encounter in her day-to-day practice. Motivations: Access to a broader range of insights and innovations outside her specialized work environment Exposure to emerging trends and interdisciplinary practices without the pressure to engage Staying up-to-date on best practices in cardiovascular care across a wide professional spectrum Frustrations: Feels disconnected from the broader community, as she does not actively contribute Finds the structure of the member section limiting in how it presents different perspectives Opportunities for Engagement: Tailored content that highlights interdisciplinary approaches and innovations Encouraging passive participation through features like recommended reading based on emerging trends Exposure to discussions and webinars that broaden her view outside her regular practice area Name: David Chen Demographics: 34, Nurse Practitioner, Cardiovascular Specialty Engagement Style: David sees the member section as a much-needed space where he can connect with like-minded professionals who share his focus on cardiovascular care. In his current professional environment, he often feels isolated due to the niche nature of his specialty. The member section provides him with a sense of belonging, allowing him to engage in meaningful discussions, contribute his expertise, and exchange ideas with others who understand his field. Motivations: Building connections with professionals who share his specialty and interests Participating in discussions and sharing his experiences to contribute to the collective knowledge of his "tribe" Seeking out a supportive community that is not readily available in his current work environment Frustrations: Lacks opportunities for collaboration and shared experiences within his immediate workplace Difficulty finding deeper engagement in discussions that go beyond surface-level topics Opportunities for Engagement: Dedicated spaces or groups within the platform that focus specifically on his specialty, fostering a "tribe" mentality Opportunities for collaboration on case studies or joint projects with other specialists Recognition for contributing to niche discussions, further building a sense of community and validation Name: Lisa Patel Demographics: 48, Physician Assistant, Balancing Multiple Roles Engagement Style: Lisa uses the member section to break free from the professional silos of her work. When she engages, she actively seeks out networking opportunities with peers from diverse backgrounds. These connections help her gain insights and ideas outside the boundaries of her current professional setting. Her engagement comes in bursts, focused primarily on meeting new people and exchanging knowledge. Motivations: Networking with professionals from various specialties to broaden her perspective Engaging with peers to exchange innovative ideas and learn from different fields Building relationships that provide exposure to new methods, outside of her regular clinical environment Frustrations: Difficulty maintaining new contacts and finding ongoing opportunities to interact Feels her access to new ideas is limited during inactive periods, making her engagement feel sporadic and siloed Opportunities for Engagement: Networking events or peer-matching features that introduce her to professionals from outside her usual circles Opportunities to connect with members who share interdisciplinary expertise and experiences Features to maintain relationships, such as saved connections or discussion prompts that encourage ongoing dialogue Name: Dr. Marcus Johnson Demographics: 55, Senior Cardiologist, Thought Leader Engagement Style: Marcus is deeply invested in shaping the future of the member section. He not only contributes content but also actively influences how the site is structured and enriched. His vision is to create a space that fosters professional growth and collaboration. Marcus collaborates with the website's administrators, suggesting improvements and helping steer the development of new features that benefit all members. Motivations: Helping guide the direction of the section to better serve the community Mentoring others and enriching the knowledge base with high-quality content Developing a collaborative space that encourages deeper member engagement and professional growth Frustrations: Limited ability to influence strategic decisions about the section’s development Lacks advanced tools for proposing or implementing changes to the website structure and content curation Opportunities for Engagement: Opportunities to join advisory boards or task forces that influence the site’s growth and development Advanced content management tools that allow him to contribute strategically and enrich the member experience Leadership roles in shaping and curating specific content areas or discussion threads

Not Using UI but Word Documents

Mon, 16 Sep 2024 22:20:01 GMT

#acc/ux Before I start this, I want to ask you to "love this for 5 minutes," then you can react.In the act of working with clients, we often take the content documents we are offered, and our reaction to doing IA is to take that content and shoehorn it into UI to satisfy the client.For years and possibly decades, I have taken content documents and shaved off a word or two. However, I have come to realize the immense detriment I have been doing to the strategic approach to content creation by skipping to the UI answer. Instead of merely using 'Styled UI' to reshape, mutate, and hide content, we should focus on enhancing the content to bolster the user experience by solving the underlying issues that users might face with the content that was initially delivered.I have a different opinion on why we shouldn't create wireframes this early in a project. For the sake of speed, we, myself included, often skip the IA step, rushing to return to the client with wireframes. We then cleverly force their content into blocks and hidden areas on the page. The downside of internalizing the IA within the team and applying layouts and UI to content is that it directs our conversations with business lines toward solutions, rather than focusing on improving the content on the site. This undermines the value that IA discussions can bring. Jumping straight to UI wires limits our ability to challenge how we receive and refine raw content. We should at least help them transform it before we start applying UI.I want to ensure there is a moment when clients are encouraged and guided to evaluate the provided content. Content strategists can have the greatest impact by unlocking the potential for more effective and engaging content.Here is an example of what happens when we skip straight to UI. The wireframes react to the content as it is provided. In the team's review of overwhelming content, we responded by using accordions in the UI to hide excess information. This was a superficial fix that masked the issue—that the content was too lengthy and not concise. No changes were made to the content itself because we had already hidden it.Now we have introduced a situation where our users are forced into a discovery mode, and we haven't solved the problem that the content was too much or not aligned with the actual goals of the page.To maximize the effectiveness of content, we need to change our approach. Instead of rushing into UI design, we should follow a structured process: Content Evaluation: Review the content before doing any design work. Understand the purpose of the content and whether it aligns with the project's goals. Information Architecture (IA) Application: Use IA to refine, organize, and simplify the content into a logical structure. Ensure that the content is easily navigable and user-friendly. Content Transformation: Apply appropriate hierarchies and organize the text logically. If necessary, split the content across multiple pages to make it more digestible. This should be a word document You can outline that content is either series on the page or is in parallel. Should denote page breaks and how it is wired between pages. Content Presentation: Share the revised content with the client. Encourage them to review it in a Word document format so they can engage with the material and provide feedback. Content Refinement: Based on client feedback, refine the content further. Make sure it is concise, clear, and aligned with the project’s objectives. UI Design: Only after finalizing the content should we begin designing the UI. At this stage, the content will be well-organized, aligned with user goals, and ready to be integrated into the page layout. By following these steps, we ensure that the content drives the design, not the other way around. This structured approach leads to better user experiences and more effective communication. Where does this go? Should this be another page? What is this content saying? Should we hide this from the user? What is the point of this page? What are the goals, and does this content support them? Let’s encourage our clients to review the content in a Word document. It’s important for them to read through the information and share their thoughts. This step is crucial to ensure that the content matches the project’s goals and is easy for users to understand. As content strategists, we should lead this conversation by presenting our findings and showing our dedication to delivering top-quality content.Only when we have finalized the content can we move on to page designs and work on the UI.

Lessons Learned

Mon, 16 Sep 2024 21:56:01 GMT

Work/ACC/Projects/_Archived/Annual 2024/Annual Meeting 2024 Survey monkey scale at the to was sometimes ignored Use Engage scales vs pick definition Static QR CODES a bust. Digital was slower because it is single threaded. Qrcodes could help but with randomize we don't have an option in place. Type in responses (other)are less in digital vs print. Digital was also slow because loading time. Explore none internet connected option for survey Offline mode. Survey monkey enterprise has an offline mode. It has stored in an app. We deploy multiple surveys from ACC should we review or at least be aware of them before conference. Don’t go early on first day. No one is hanging out till past keynote and later. Still can't engage older established clinicians. Great exposure for ux to both survey takers and the college as a business.

ARCHES Component Conversion

Mon, 16 Sep 2024 21:55:59 GMT

back to ACCThis is the master ticket for the transition of the [Component Name] into the new Arches design system. This encompasses all the tasks required for the successful analysis, design, and implementation of the component update.(To be filled by the product owner or stakeholder)(To be filled by the IT team after the initial analysis and discussions) Component Definition: Define the zone, providing a screenshot, requirements from an editor's perspective, and the URL location. Component Identification: IT to identify and isolate the component. Design Implementation: A front-end designer/developer to create an HTML prototype of the component using the Arches design system. Group Grooming: Conduct a group grooming session to identify any additional tickets or tasks necessary to complete the story. The checklist provides a high-level overview of the steps that need to be taken. More detailed sub-tasks should be created under this main ticket to track the progress of each individual item. This way, it'll be easier to manage and track the progress of this component's transition to the Arches design system.
AI Prompt - Conversion Tickets
#acc/jira #acc #work #requirements

AI Prompt - Craft UX Ask

Mon, 16 Sep 2024 21:55:58 GMT

I need you to act and have the knowledge of a UX SPECIALIST, your role is crucial in shaping and formatting this project request for our team's work. Your input will be invaluable in each of the following categories. Your concise writing style will guide the process. I will rely on you to prompt me for more details for each section and to fill in any necessary information. Only when you have all the details should you return the formatted intake data in markdown in a code block. Simple written statement in sentence FormatThis can be written as a sentence or, if easier to scan, a bulleted list of short statements. The needs and values should dive deeper beyond the wants and should outline the users and problems they are trying to solve A few sentences should outline the user, the project, and the value.This should be a bulleted list of short statementsThis should be a bulleted list of short statements outlining the assumptions and how this might not answer the need because of the shortcomings of constraints and Limitations. If you understand this then prompt me for the first section and after you I say Next Section should you prompt me for the next section for questions. As we go further down the intake data the more you can extrapolate from the data you already have.

Arches Conversion

Mon, 16 Sep 2024 21:55:56 GMT

← back to acc products
Script Glossary & Categorization---------------------------------------------------------
SPRINT A - Define the Batch --------------------------------------------------------- Select conversion candidate for the batch and define scope Run an Audit Query against the code base of Sitecore within scope for code components & plan needed conversions Run an Audit Query against the CMS Content Areas (RichText & CustomScripts) within scope for Editorial Generated UI & start planning for remediation Groom ---------------------------------------------------------
SPRINT B - Component Conversions--------------------------------------------------------- Convert the components Deploy to lower environments DEV/SPR QA test the converted components Promote to PROD List of bulk changes - Mapping of changes ---------------------------------------------------------
SPRINT C - Editorial Created Remediation --------------------------------------------------------- SYNC SPR Execute bulk conversion script with a small sample of pages in DEV/SPR - Using Mapping Clean up rich text via script (S&D) Review effected pages Create jira tickets for content issues identified during review Work with BL to resolve found issues Promote to RLS Demo with BL and obtain sign-off ---------------------------------------------------------
SPRINT D - Batch Conversion--------------------------------------------------------- Create PRD/Master/Web DBs backup for potential rollback Run bulk conversion script in Author only with auto-publishing turned off IT performs spot checks BL reviews and validates pages, with support from UI, DEV, and QA teams Garbage Clean up of Empty Content areas and RichText Resync to lower environments?
Editorial training--------------------------------------------------------- SPRINT Z - Done! --------------------------------------------------------- Garbage cleanup
Bulk Conversion Outline OLD
Excel Tables
Jira Tickets notes
#acc/arches/conversion
#acc/guidance Metadata Created:: 5:37 PM - September 16, 2024 Updated:: 5:55 PM - September 16, 2024

Bulk Conversion Outline OLD

Mon, 16 Sep 2024 21:55:55 GMT

← back to Arches ConversionBulk Conversion Planning Identify a batch of pages as the upcoming candidate batch for conversion. Considerations: Can we target a good number of pages with the same component composition (they use the same components exclusively)? This lets us control variables. Provide a list of the components to UI for conversion. Confirm the batch with any interested parties if relevant (editorial, BL, users, etc etc) UI analyzes component list conversion and provides LOE. How complex will the conversions be/How long will it take? Generally, this will hopefully be doable in one sprint assuming there is not any major rebuilding needed. Most importantly we need to determine how many will need to be rebuilt completely.
Creating A New ACC.org Component Create tickets for each component up for conversion (we may be able to lump some lighter ones together, we can decide that after analysis). Groom, add to schedule, etc. UI team completes component conversion tickets. QA tests converted components on sample pages in test environments. Push conversions to production, including deployments steps to make sure the components are available for use on all environments. UI provides list of bulk changes, including Components that need to be switched to an Arches version in presentation layout. If applicable, a list of changes to rich text content where the change can realistically be done with a bulk script (i.e., search and replace) A list of issues from conversion that will need manual intervention.
New Component Audit All Content Areas, and Custom Scripts for uses of In Page and Inline Script and Style Tags
1. Output to and excel. Audit of Editorial UI 2. Internal Review of Audit 1. List All Inbound Links and Evaluate Remediation of Links: 1. Font Awesome 4.x - Delete, find all class names that start with fa- and end in -o and remove -o 2. Font Awesome 5 or 6 - Delete 3. Bootstrap JS & CSS - Delete
4. Remediation | Remediation Document of all editorially created UI and Inclusions ]] 2. Review and In Page Script and Styles 1. Dedupe and Style and Script Tag Blocks and save them outside of Sitecore
1. Add Items to the Editorial Bulk Change Notice Excel 3. Run Clean Up scripts across Richtext and CustomScript Sitecore components Development creates scripts to process changes provided by UI in Sprint B. Precondition: Components that need to be switched to Arches has already been developed, tested, and pushed to ALL environments (DEV, SPR, STG, RLS, PRD) Run script in development environment for specific pages that apply to this batch (i.e., #1) and verify. Review affected pages for discrepancies/bugs for resolution (e.g., code, components, etc.) If code changes are required, create JIRA tickets for upcoming sprint. Sprint C will be paused until these code changes are made in ALL environment Review and identify any content issues (rich text, custom scripts) and work w/ BL on resolution
Run clean up script to identify problematic scripts that need to be remediated (https://support.acc.org/browse/AWC-3942) and push to environments accordingly. Promote to other lower environments (SPR, STG, RLS) and validate in each environment accordingly. Perform demo for BL to review results of bulk conversion for batch in scope (STG or RLS) and obtain sign-off Create a PRD back-up to support a rollback, if needed (requires further discussion around specific rollback tasks/steps) Take back-ups of both Author and Web DBs Need to enforce a content freeze (BL), specifically for a subset of pages/content Promote to PRD and run bulk conversion script in Author ONLY, do NOT publish to Delivery. IMPORTANT NOTE: To ensure content is NOT auto-published, there is a need to explore options.
Option 1: Set content items to a DRAFT status when converting content in Author. See Sitecore DRAFT workflow doc here. Possible risk is the Original Posted Date may be updated as a result (need confirmation) Option 2: -- TBD IT to perform spot checks in Author to ensure the conversion script was completed successfully. BL reviews converted pages in Author and as pages are validated, publish in increments (as appropriate) UI, DEV, & QA teams on standby to field any questions or address any concerns Post Conversion/Clean Up Tasks (once all batches are complete, one-time task) Once conversion is complete, we will take the Arches presentations and merge them into the current legacy template presentation configurations, and delete the Arches versions, as clean up. QA Approach (DRAFT) NOTE: This approach should be visited as we progress w/ the batches. Also, scheduled sprint content syncs should not adversely affect the Arches QA pages since they will already exist prior to the content sync. UI/UX team will create an Arches QA dedicated page (e.g., page name to include '_ArchesQA' suffix in the DEV environment in support of their development & verification process. Once the component updates have been verified in the DEV environment, UI/UX to request a Razl content sync to SPR in coordination w/ their updates getting built and deployed to SPR. (Ricky can assist w/ Razl syncs) QA will then use the Arches QA dedicated page in SPR to test the target components. Once validated in SPR, QA will work with DEV (Ricky) to sync content to upper environments (STG/RLS) as the changes are promoted. PRD deployment (e.g., pre-task) should include a step to sync the Arches QA dedicated page to PRD (Author ONLY, do not publish to Delivery) in order for QA validate in PRD. Once validated, need to ensure there is a clean-up process to remove/delete QA dedicated pages, once ready (in ALL environments) Notes: It is important that we have a way to roll back our work at any point throughout these cycles and we need to be able to do this in a way that BL can be comfortable with. This plan doesn’t really account for if something goes pear shaped in Sprint C but we should probably iron that out as well, especially if something goes wrong during the push to production. This looks like a three-sprint process, but we may be able to consider identifying the next batch during sprint C to speed up conversion if necessary.
#acc/arches #acc/arches/conversion #acc/guidance Metadata Created:: 5:37 PM - September 16, 2024 Updated:: 5:55 PM - September 16, 2024

Mapping of Converted Components

Mon, 16 Sep 2024 21:55:54 GMT

Arches Conversion/Excel TablesThe Mapping of Converted Components is a straightforward Excel document that records all components that have been converted. This reference document is crucial when implementing bulk conversion scripts. If the 'converted ID' column contains the term 'compatible', the scripting process should bypass this component. This protocol assumes that no modifications are necessary, as all required work has been completed within the original file. This mechanism helps ensure an efficient and error-free conversion process.

1CRM

Mon, 16 Sep 2024 21:55:51 GMT

Blackout Week
OMA Replacement - Membership Join Us
My ACC.org Dropdown Menu
Dynamic Header & Footer
Invoices Pay for some one else
Front End
Things are broken or funky list
First time entry tour
#acc/vendor

AI Prompt - Writing Editing

Mon, 16 Sep 2024 21:37:46 GMT

Please take the following text and correct any spelling and punctuation errors. You may also correct verb tense and cognition usage to improve grammatical structure. Please do not change any of the meaning or tone of the text. After your first round of corrections You may prompt me with a suggested changes to improve readability or grammar as a follow-up I will respond to your suggestion with a yes or no if it is yes then you may change the wording scoped to your suggestion.

JACC

Mon, 16 Sep 2024 21:37:46 GMT

JACC Editors at ACC24

AI and the ACC

Fri, 06 Sep 2024 18:30:26 GMT

How should the College start looking at and embracing AIAI is not going anywhere and members want to know where we can go with AI. Outline: https://enterprise-knowledge.com/how-to-prepare-content-for-ai/

Advocacy

Fri, 06 Sep 2024 18:15:47 GMT

Pages before Leg Conf Hypothesis: **Outline Additional Notes:

After Conference actions

Wed, 04 Sep 2024 20:37:42 GMT

Meet with Lauren & Mindy 📅 2024-04-16 Data Dump Next steps( quantitative, snap shots for design changes and defense/proof why it's good, focus group setup ) meet with Anne and Paul 📅 2024-04-30 How did it go? How can we improve? Does Varent have a good solution for what we faced as challenges on the floor with bad internet connections. Present to our department. 📅 2024-04-15 Process, findings, challenges Meet with JACC 📅 2024-04-16 What snapshot slides do you want from the findings. Rob from the education department (new Tori) facing challenges with icons. Need to arm her m with Enteprise reasoning. 📅 2024-04-16 Setup a lunch with Tori when back 📅 2024-05-01 Talk to Kyle about Tori and cvboard new scrum team. L.B. Where did member engagement go? 📅 2024-04-07 Capture the UX vision initiatives ⏫ 📅 2024-04-09 Consistency, Natural Language, Be more clear, We can do better. Tear sheets for guidance to compliment the power point 🔼 📅 2024-04-30 Do a case study of Join Us. 🔽 📅 2024-06-01 Talk to Shalen maybe finally ready to set up a brown bag 🔽 Finish digitization Digitize the cards as sets in whimsical ⏫ 📅 2024-04-12 Whimsical license and how do we copy - record - retire the set of boards. dueApril 16, 2024 Do a digital run through with Mary Anne. 🔽 📅 2024-05-01 Do a dry run explore with Lauren and Mindy. How to present and run a BAD Workshop 📅 2024-04-23 Run a variation of a roadmap exploration for Heart Explorer with Michele Areil. 📅 2024-05-01

CV Board Website Brochureware

Wed, 04 Sep 2024 20:01:38 GMT

about - Shot CTA and paragraph webinar - 4 cards with title date small blurb link to WebEx. faq - accordion grouping. act - link to something will come later. partners - logos company names links footer - copywrite and link to terms of service. What we will need Webinars: Hold coming soon. +Project Archived

Product Pages

Wed, 04 Sep 2024 19:25:30 GMT

Objective: Help users know quickly the type of education, how it is delivered, and focus it has. Content: Tags, Credits, Certificates Objective: Give users a quick understanding of what the educational product is and why it’s valuable. Content: A brief description of the product's purpose. Key benefits and learning outcomes. Objective: Help users understand if the product aligns with their needs. Content: Description of the ideal learner. Prerequisites (if any). Objective: Clearly communicate the cost and justify the investment. Content: Detailed pricing structure. Comparison with similar products. Value-add elements like certificates, extra resources, or community access. Objective: Encourage users to take the next step. Objective: Provide social proof and insights from other users. Content: User reviews and ratings. Case studies or success stories. Objective: Highlight how your product stands out. Content: Side-by-side comparisons with other products. Unique selling points (USPs). Cognitive Load: Ensure the information is well-organized and not overwhelming. Use visuals, headers, and bullet points to break up text. Motivation: Highlight the value and relevance of the product to increase motivation. Use social proof and clear benefits. Trust: Build trust through transparency, expert endorsements, and user reviews.

Content Rewrite

Wed, 04 Sep 2024 19:25:21 GMT

The Exam is timed and it is important that you give yourself enough time to finish it during the exam window.The test and the questions are timed. The complete test with no breaks is timed to be 7.5 hours (Some People have finished it in 4.5 hours)Exam window date time x @ GMT to date time y @ GMT (this is roughly 4 days) 3 minutes per question. Each section has 30 questions and cannot be paused. You may take a break between sections but you have a Max of 24 hours of breaks Your exam will be open for 31.5 hours from when you started. (7.5 hours of test plus a max of 24 hours of break). Your exam must completed within the exam window

ACC.org Conversion

Wed, 04 Sep 2024 19:25:20 GMT

Build ACC using Arhces

Children Rendering Rough Notes

Wed, 04 Sep 2024 19:25:19 GMT

Work through the "children renderings" for articles to be buildout into Arches. The "children renderings" of article are: - ClinicalTrial - GuidelineHub - JournalScan - PressRelease - Recommendation - TenPoints - This might not be a complete list To complete this ticket we suggest work with a collection of people because it requires BL intervention, UX guidance, UI Devolpemmt and also ASP Dev work.First Step Setup environment for JOINT DEVELOPMENT Sample of all of these types to work on a local environment and local working for Ling to run the Joint Dev meetingsJoint Dev Meeting: that includes ASP Dev, Ling, Matt, Rowena, Editorial(Jacob) and should be roughly 3 hours on a single day where everyone partipates.Blocks Ticket APPSUPPORT-22095
Resources: LiC Article Templates.docx (sharepoint.com)
AI REQUEST for this Ticket

AI REQUEST for this Ticket

Wed, 04 Sep 2024 19:25:19 GMT

Contextual Setup for My Request:I want you to understand and act in the specific context of being a Product Owner on a SCRUM team. Your role is to write backlog tickets for a new feature, considering all aspects typical of a Product Owner's responsibilities in a real-world scenario. I expect the tone and approach of your responses to reflect this role and context. After the prompt please ask up to 3 follow up questions if you any clarifications or supporting details. Here are some key points I want you to consider: SCRUM Methodology Awareness: You should demonstrate a clear understanding of SCRUM principles and practices. Role-Specific Knowledge: As a Product Owner, your focus is on maximizing the value of the product and the work of the development team. Feature-Specific Requirements: The backlog tickets you will create should be for a specific feature, detailed in my request. User-Centric Approach: Emphasize the importance of user stories and prioritize tasks based on user needs and project goals. Communication Style: Your responses should mirror the communication style of a Product Owner - clear, decisive, and oriented towards actionable items. Writing Style: Concise and clear, with a preference for listing items rather than writing out in sentences, to facilitate easy scanning. Project Introduction: Subject Matter: Tech stack - ASP, Vue, HTML, CSS, JavaScript, CMS Sitecore or Sitefinity Internal Terms: [Clarification on terms like ARCHES, PaperCrane, ACC.org, CardioSmart, etc.] ARCHES is a comprehensive front-end design system by the American College of Cardiology. It uses advanced compiler techniques to generate variations that integrate with different frameworks and brands, making it versatile for various ACC products. ARCHES primarily consists of utility classes that offer a modern approach to CSS, focusing on single-style control and separation of responsibilities between HTML and CSS. This system is flexible and adaptable, used across multiple ACC platforms, including ACC.org and CardioSmart, and supports distinct brand styles while maintaining overall coherence. PaperCrane refers to a Component Library specifically designed for Vue.js, a progressive JavaScript framework. This library is utilized in the development of Single Page Applications (SPAs). PaperCrane contains a collection of pre-built Vue components which can be reused across different parts of the enterprise application, enhancing development speed and ensuring UI consistency. ACC.org ACC.org is the official website of the American College of Cardiology. It serves as a comprehensive resource for cardiology professionals, offering a wide range of content including clinical updates, educational materials, guidelines, and information on cardiology conferences and events. The site is designed to support medical professionals in the field of cardiology with the latest scientific research, policy advocacy, and continuous education. It also provides tools and resources for practice support, quality improvement, and patient care in the cardiovascular field. The website caters to the needs of cardiologists, providing them with essential information to advance their knowledge and practice. CardioSmart.org is a patient-centered website created by the American College of Cardiology. It provides comprehensive information about heart health and various cardiac conditions. The site is dedicated to educating patients, offering resources on heart diseases, healthy living tips, and tools to manage cardiac health. It includes topics such as heart disease prevention, treatment options, and lifestyle changes. CardioSmart.org is designed to empower patients with knowledge and tools to actively participate in their own heart care and make informed decisions about their health. Backlog Ticket Structure: Title: A concise, descriptive title for the feature or issue Description: Background: Brief context or background information. Objective: Clear statement of what the ticket aims to achieve. User Story: Format - As a [type of user], I want [an action] so that [a value or result]. Acceptance Criteria: List of conditions that must be met for the ticket to be considered complete. Should be specific, measurable, achievable, relevant, and time-bound (SMART). Dependencies: Any dependencies or prerequisites for the ticket. Backlog Ticket Creation:Follow the Updated Backlog Ticket Structure provided above to detail your response for this ticket In the Prompt Details below I will detail the information I have for the ticket.Prompt Details: Heading: Article "Children Renderings" Conversion to Arches Introduction: The Sitecore renderings for the sub types of articles need to be converted so Articles can be utilized in the CMS Main Content: The "children renderings" for articles to be built out into Arches. The "children renderings" of article are: ClinicalTrial GuidelineHub JournalScan PressRelease Recommentation TenPoints This might not be a complete list Suggested approach for completing this ticket is to have JOINT DEVELOPMENT EFFORT as a 3 hour meeting 1st Step Setup environment for JOINT DEVELOPEMNT (Ling + ASP Dev ) Establish a working version of all article children types within a local environment that can be referenced 2nd Step JOINT DEVELOPEMNT MEETING (Ling, Matt, Rowena, Jacob, and ASP Dev) Work through any and all architectural, backend and UI alterations needed to convert all these children renderings into full arches. Meeting should be roughly 3 hours long. This co-work meeting will expediate all needed conversations and decisions to make this conversion completed. This ticket blocks the work for APPSUPPORT-22095
References or Sources: LiC Article Templates.docx (sharepoint.com) Work through To complete this ticket we suggest work with a collection of people because it requires BL intervention, UX guidance, UI Devolpemmt and also ASP Dev work.First Step Setup environment for JOINT DEVELOPEMNT Sample of all of these types to work on a local environment and local working for Ling to run the Joint Dev meetingsJoint Dev Meeting: that includes ASP Dev, Ling, Matt, Rowena, Editorial(Jacob) and should be roughly 3 hours on a single day where everyone partipates.
Blocks Ticket APPSUPPORT-22095
Resources: LiC Article Templates.docx (sharepoint.com)

Virtual System

Wed, 04 Sep 2024 19:25:18 GMT

← back to ACC Products
+Project Archived
Categories & Tags
Pages
Collections
Short Codes
#work #acc/edu #requirements #acc/vendorMetadata Created:: 2:28 PM - September 04, 2024 Updated:: 3:25 PM - September 04, 2024 Domain: Virtual Events

Widgets

Wed, 04 Sep 2024 19:25:18 GMT

Individual Widgets have the function to save its saved state and content to a central definition which then can be referenced in multiple locations on the site. This item is then referred to and all changes to its configuration are the same throughout the eventContent blocks can load any shareable widget. A shareable widget can break its central reference which at that point it will clone information from the shareable widget definition and will establish itself as a newly defined individual widget . Depending on the widgets structure there are design and function configurations. Some widgets establish a pattern of data input that could be a simple as text and as complicated as a data collection. Basic HTML
Button Credit messages

Button

Wed, 04 Sep 2024 19:25:18 GMT

System establishing data Auto generation Label URL Shortcodes enabled Type Primary Secondary State Active Disabled Hide

Basic HTML

Wed, 04 Sep 2024 19:25:17 GMT

The basic html widget uses the TinyMCE. #requirements

System establishing data

Wed, 04 Sep 2024 19:25:17 GMT

This basic data allows for the creation of an object. Some or all of these items maybe automated sand not be in the users interaction. ID Internal name Active || Boolean Notes

Short Codes

Wed, 04 Sep 2024 19:25:17 GMT

Established content areas allow for the use of shortcodes which stand in a variables established either at the system level or at the event level. URL EventSlugPartial Credit Date String Event name Credit

Categories & Tags

Wed, 04 Sep 2024 19:25:16 GMT

Back to Virtual SystemThe tag system will be defined at the global level Creation of a tag or definition of the tag depending on the type may be done at the event level. Global only mutation Faculty Role Credits Primary learning pathway Event mutation Award Level Definition Learning pathway children and grandchildren creation Channel created at event Major concerns cross event compatibility Events depending on the science explore different levels of the science but multi level tags allow search to find children when searching of parent terms. Parent tag Children Grandchildren
#requirements

Basic CRUD

Wed, 04 Sep 2024 19:25:16 GMT

Most elements have a basic structure of repeated smaller items that should be able to be created in a repeatable fashion and then those items should able to be updated or is mistakes are made deleted. All create functions establish System establishing data so it can be listed and saved.

Structured Data Items

Wed, 04 Sep 2024 19:25:16 GMT

Data items use Basic CRUD and System establishing data is mostly auto generated with defaults. Data items may link to other data items
Session Presentation People Abstracts Exhibit Advertisement

Session

Wed, 04 Sep 2024 19:25:16 GMT

The session is a central data item that builds many widgets. Presentation Faculty Channels Ondemand Program collections

Pages

Wed, 04 Sep 2024 19:25:15 GMT

Basic CRUD System establishing data Meta data Structure
Layouts & Blocks
System establishing data Page Title browser tab plain text Page Name H1 of the page Allows html Slug Plain text with / as a delimitater Delimitation allows for structure of children pages. this level allows for the establishment of an ad rail
Pages have an internal Basic CRUD for Layouts & Blocks

Layouts & Blocks

Wed, 04 Sep 2024 19:25:15 GMT

This is a crud mechanism Basic CRUD the layouts have System establishing data Layouts can be stacked and sorted within the structure of a page. Layouts can establish the zones. Zones establish the crud mechanism for content blocks. Definition sidebar/full 5/7 7/5 Full 6/6 4/4/4
Use Basic CRUD and internally populate System establishing data
Content blocks are defined by the Widgets definition that is selected. Predefined Shared Widgets can be used by multiple blocks within multiple pages, but the shared content is the same. Widgets can also be generated on the fly from the block and will not be stored as shareable. These widgets can be saved as shareable. Content blocks are sortable and movable between zones in a single layout. The default definition of a content block is Basic HTML
Short Codes

Collections

Wed, 04 Sep 2024 19:25:15 GMT

Collections are any set of Structured Data Items. Certain collections are directly paired with widgets which render UI or power certain functionality.
Most collections are basic with System establishing data but collections may have data manipulations applied to them like and sort and Categories & Tags
Channels are a variation of collections that have an advanced level of data manipulation to construct agendas.

Channels

Wed, 04 Sep 2024 19:25:14 GMT

Channels are an advanced variation of a Collections of the data type sessions. Besides categorization and auto sorting established by the timing from the sessions the channel further establishes timing events like with the session shows up in coming soon or when the page becomes active or stays active after the scheduled ending time of the session. Sessions may be included in overlapping channels but the navigation and page of the session player will consolidate all traffic to the highest priority channel.
#requirements

Component Library in Vue

Wed, 04 Sep 2024 19:25:13 GMT

The construction of a boiler plate components project that can be used as a standard for building future productsOld Documentations

Container Query Sizing

Wed, 04 Sep 2024 19:25:10 GMT

Would it be beneficial to only alter the CSS var in breakpoint for containers Nope this would fuck up with inheritance . :root{ [class=^ “_1”]{ --size :1 } } .container{ [class=^ “_1”]{ --size :1 } } Better answer is to wrap the responsive features Grid, columns, rows, display, flex direction, align, padding, margin, max—w and width. Col-start col-end row-start & row-end. In their own stylesheet for now and load it after the CSS of UC.css .ContainerQuery:Wrapper{} .wrapper@container{} .col-start1 .row-end_1 .columns_x .rows_x .m_x .p_x .{position: absolute,relative,…} .{display: block, …} .flex{size,basis, direction} .self{align} .items{align} .justify_{align}

Excel Tables

Wed, 04 Sep 2024 19:25:07 GMT

Running a query against Sitecore content areas to generated this report for each Batch of the Bulk Conversion Audit of Editorial UI
Building upon the audit excel the team will augment that excel to produce a report to go to the ACC.org Editorial Team with the changes that will happen. This will be produced and Augmented during UAT. Editorial Bulk Change Notice Excel

Phase 4

Wed, 04 Sep 2024 19:25:06 GMT

Strengthening Independence: Encourage editors to take on tasks with greater autonomy, leveraging the skills and resources they've accumulated. Updates & News: Intermittently share any pertinent updates or enhancements to the Experience Editor and related components. Quarterly Review & Share Session: At the end of the 12th week, conduct a comprehensive review session. Celebrate successes, address any remaining challenges, and share insights and learnings with the team to promote collective growth.

Phase 3

Wed, 04 Sep 2024 19:25:06 GMT

Real-world Application: Encourage editors to start crafting more complex layouts in the Experience Editor. Complex Component Training: Delve into the use of intricate components such as accordions, tabs, and any other sophisticated elements integral to your site's design. Future Pattern Discussion: Initiate conversations about potential patterns or components that might be included in the future, preparing editors for upcoming features or design structures. Resource Sharing: Offer comprehensive documentation, video tutorials, and other support materials to aid their independent learning. Feedback Loop: Maintain weekly meetings, where experiences are shared, concerns addressed, and the approach to training refined.

Phase 2

Wed, 04 Sep 2024 19:25:05 GMT

Focus on Dynamic Structures: Dive into the intricacies of the Experience Editor, emphasizing complex page structures. Practical Application: Assign each editor a specific request to replicate a complicated layout in the Experience Editor. Personalized Mentorship: Provide guidance as editors navigate their tasks, ensuring effective utilization of the Experience Editor. Team Sharing: At the conclusion of their tasks, editors will share and discuss their solutions with the team for collective learning.

Phase 1

Wed, 04 Sep 2024 19:25:05 GMT

Kick-off: Address historical concerns and introduce the benefits of the updated Experience Editor. Training Material Feedback: Engage with the editors early on to determine their preferred formats for training. Begin Basic Training: Start with a Sitecore refresher, with an emphasis on the Experience Editor. Adjust based on the feedback received. Feedback Session: Host a weekly meeting to gauge initial reactions and refine training methods according to their preferences.

KT SESSIONS

Wed, 04 Sep 2024 19:25:05 GMT

I want to outline a comprehensive Knowledge Transfer (KT) strategy that targets the required remediation steps. The goal is to ensure a smooth transition, allowing our team to manage the work systematically and avoid overwhelming our team resources and capabilities. Here's a step-by-step process to guide our KT activities:Sub-dividing the Conversion into Manageable Segments: We can accomplish tasks efficiently throughout the week by dividing the bulk conversion into themed work or manageable segments. For instance, focusing on a specific aspect like "all the pages that have tabs" will make the process more digestible and actionable.Weekly Kick-off Meeting for Conversion Blocks: At the start of the week, we will convene a meeting where a conversion block of pages is presented. This meeting will include a live demo showing how to make the necessary changes, providing an excellent opportunity for team members to understand the process firsthand.Standing 30-Minute Meetings throughout the Week: To ensure continuous support and clear communication, I suggest scheduling a standing 30-minute meeting every day. This stand-up meeting will be a forum to discuss any roadblocks or questions related to the assigned work. It will enable real-time problem-solving and maintain momentum in the project.Here’s a high-level schedule to illustrate the flow:Monday: Kick-off meeting with a conversion demo for the week's segment (e.g., pages with tabs).Tuesday to Friday: Daily 30-minute stand-up sessions to address questions and roadblocks.End of Week: Recap and assessment of the week's accomplishments, planning for the next segment.By adhering to this process, we aim to create a structured approach to knowledge transfer, facilitating the handling complex conversion tasks and empowering our team with the confidence and competence needed. Also, it's worth mentioning that our KT process is designed to be flexible and responsive to the team's evolving needs. As our collective experience and proficiency grow, we anticipate that the demand and duration of the daily stand-up meetings may not be needed or shortened. We'll continually assess the progress and adjust accordingly, ensuring our approach remains efficient and aligned with the team's capabilities. Continued feedback will be instrumental in this ongoing refinement, keeping us agile and focused on our shared goals. ACC User Experience Team American College of Cardiology2400 N Street NWWashington DC, 20037www.acc.org

Editorial training

Wed, 04 Sep 2024 19:25:05 GMT

Phase 1
Phase 2
Phase 3
Phase 4
KT SESSIONS

Hubspot

Wed, 04 Sep 2024 19:25:03 GMT

How to use Subscription Types in HubSpot. Statements of Truth Source of record for opt ins are 1CRM Source of record for the flag of global opt out is HubSpot. To send any marketing email you must select a Subscription Type. On Email Footers Manage Subscriptions = 1CRM Unsubscribe from All = HubSpot. Email lists are made by the Marketing Communication Table. Problems There are not resubscribe flows because not built in 1crm. The rub is that the subscriptions types show up on the renew page. 1CRM opt-ins do not matching the opt-ins from higher logic. Suggest going into the delta from 1crm and higher logic. Adding new opt in are a bit of work because it modifies the "pull" from 1crm to Hubspot.Find a way if we can to suppress the one Subscription Type on the resubscribe.

Front End

Wed, 04 Sep 2024 19:25:03 GMT

First time entry tour

Wed, 04 Sep 2024 19:25:03 GMT

acc.orgWelcome we have changed something’s We have moderation of systems Most of the changes won’t affect how you interact with the college we will still the same great education and science programs we offer. First change you’ll notice is Login will look a bit different Logged in Now that your logged in we have moved around some thing related to your profile These items will bring you to your pro

Profile Tour

Wed, 04 Sep 2024 19:25:00 GMT

We recently made some changes to how you manage your personal information. Take a quick tour of these updates to enhance your experience and make it more intuitive. Manage your email, phone and address details more easily and get a more comprehensive view of your ACC.org profile. Our new shopping cart system, makes payments a breeze. You can easily manage and save your payment methods here, making purchases faster and more seamless. Under "Current Membership," you can view your membership status or reprint your membership card. In "Manage Membership," you can renew your membership or alter any add-ons to your membership. Personalize the types of content you receive from ACC, including your regular digest email newsletter, under "Personalize ACC.org." Additionally, the new “Communication & Privacy” page, allows you to control the content you receive and share only the data you are comfortable with. Never miss an update while maintaining control over your ACC communications. Are you in possession of an exclusive product access code? Use the “Access Codes” page to unlock your savings on specific ACC programs or products. Access the “Purchas History” page for a detailed list of your past purchases of ACC programs and products. Saved an article on ACC.org? You can find it under the “Library” page for quick access to read again or reference later. Locate, view and print claimed credits and certificates on your personalized “Transcript” page.

Outstanding Tickets in ACC.org

Wed, 26 Jun 2024 21:04:38 GMT

Unfinished implementation of Articles. 23590 Update ARCHES Article Template to Remove the "Search" tab, so it Defaults to "Content"
AWC-4003 Structural (1col2colRight & 1col) Remediation & Clean up
Main Menu - Top Navigation Not Wrapping (Perm Fix)
LiC Page - Author Image Displayed vs Thumbnail Override Image
Page structures introduces a bug into the grid system of content. awc-4069 Resolve Grid Utility Class Conflicts for ACC.org between Page Layouts and page Content
Reduce negative space in ACC.org header for tablet https://accorg.atlassian.net/browse/AWC-3486
Make a path to making elements across the site have basic personalization of "logged in use has purchased." AWC-4066 Implement User-Specific Content Personalization in Arches Templates on ACC.org
Finish up the conversion of Articles to Arches and including its variations AWC-4091 # Develop Article "Children Renderings" using ARCHES
Related Content added into all variations of Articles. APPSUPPORT-22095 Changes to Article Template: New Resources Toolbar and Section
All Error pages seem to result in 404s APPSUPPORT-22937 Update Custom Error pages to differentiate from page not found
Optimize Meeting Registration that has gotten convoluted with 1CRM APPSUPORT-23332 # Analysis: Refactor Meeting Registration
Major sections of the tree of Join us are not converted from Batch 1 AWC-3589 - Powershell script to perform bulk changes on Join Us pages (Batch #1)
Arches Quality to improve how editors interact with Sitecore AWC-3978 Arches Quality of Life Changes in Sitecore
Update Arches icons color in Sitecore https://accorg.atlassian.net/browse/AWC-4038
Enhance Template ADDING for Admin Web Editors in Sitecore for Arches https://accorg.atlassian.net/browse/AWC-4039
Visual Categorization of SiteCore Components in Detail Panel https://accorg.atlassian.net/browse/AWC-3948
Sitecore Editorial UX Improvement: Template Creationhttps://accorg.atlassian.net/browse/AWC-3711
Arches Twitter Component
DEV: Build Arches Component : Show & Hide Text Area - AWC-3962
DEV: Build Arches Component : Slideshow - AWC-3963
Suppress Take-Over Banner during Marketing Push https://accorg.atlassian.net/browse/AWC-3947 [AWC Team - Redirect acc.org User to Federated Login to Create Account (For AWC Sprint 71)]
Arches Bulk Conversion | Membership Join Us Sections Pages (Batch #1b Parent) https://accorg.atlassian.net/browse/AWC-3930
Update to Article template to allow for a new Carousel feature Brain Feature
Content Listing Feature Truncating Headlines; Please Increase Character Count or Allow That to be a Setting Brian Feature
X|Twitter hashtag seems to no longer work APPSUPPORT-20812 Our Twitter Hashtag Feed Widget Has Stopped Working; Want to Investigate if it Can Be Restored
Arches Bulk Conversion | Article Pages (Batch #2 Parent) Microstie Hero and Miro Header

Things are broken or funky list

Wed, 26 Jun 2024 15:01:54 GMT

from the create case there either shouldn't be top buttons or at least events should be removed. Join Pages on SF are from November 2023. This vanity was not redirected to the new SF URL for OMA memberapp.acc.org The Login in screen says "Background Text" in the top right The welcome tour is visually broken. (Already told ling) registration did log me into acc.org but trying to get into SF it forces another login. First Login after a registration brings me to this odd page. Login Flow - Community User Agreement (acc.org) this where I get this new template
I get this error when changing the race birthday

Pasted image 20240424075131

Thu, 09 May 2024 12:40:46 GMT

Pasted image 20240424073644

Thu, 09 May 2024 12:40:46 GMT

Pasted image 20240412115026

Thu, 09 May 2024 12:40:46 GMT

Blackout Week

Thu, 29 Feb 2024 15:57:12 GMT

Editorial Changes Donation Links Zoghbi
Campaign for the Future Ebiz Links My ACC
Marketing Pages - multi pay dues

KSS Documentation

Wed, 28 Feb 2024 20:37:35 GMT

KSS, or Knyle Style Sheets, is a documentation syntax for CSS that allows developers to create a living style guide from CSS comments. It's structured to be both human-readable and machine-parsable, enabling automated tools to generate style guides from your CSS files. Here's an example of a comprehensive KSS comment block for a CSS stylesheet, including all the main options it can have:/* A button suitable for giving a user a call to action. Style guide: Components.Buttons.Primary :hover - Highlights when hovered. :disabled - Dims the button when it cannot be interacted with. .small - A smaller button for less important actions. .large - A larger button for more important actions. Markup: Modifiers: - .small - A small version of the primary button - .large - A large version of the primary button State classes: - .is-active - Highlights the button as active - .is-disabled - Shows the button as disabled Variables: - $btn-background-color: Color of the button background. - $btn-text-color: Color of the button text. $btn-background-color: #007bff; $btn-text-color: #ffffff; @brand Primary @dependencies - forms.css - grid.css @requires - mixins.css - variables.css @implementations - Web: components/button/button.css - iOS: components/button/button.swift - Android: components/button/button.xml */ .btn { background-color: $btn-background-color; color: $btn-text-color; /* other styles */ } This example includes: Description and Title: A brief description of the component or style and optionally a title. Style Guide Reference: Indicates where in the style guide this component or style belongs. States and Modifiers: Describes different states (:hover, :disabled) and modifiers (.small, .large) that the element can have, including their descriptions. Markup: Provides an HTML snippet as an example of how to implement the described style. Variables: Lists any CSS variables (custom properties) used in the style, including their default values. Brand: Optional brand or category this component belongs to. Dependencies: Other CSS files or assets this component depends on. Requires: Additional resources or files that are required for this component. Implementations: Links or references to implementations of the component in different technologies or platforms. This structured comment allows developers and designers to understand the purpose, usage, and variations of a component at a glance. It can be processed by tools like KSS Node to generate a living style guide, ensuring documentation stays up-to-date with the code.

Online Membership Application

Fri, 02 Feb 2024 20:09:53 GMT

Shopping Cart

Fri, 02 Feb 2024 19:53:37 GMT

Branding Controls

Fri, 02 Feb 2024 19:50:58 GMT

Membership Renewal

Fri, 02 Feb 2024 19:47:16 GMT

Member Directory

Fri, 02 Feb 2024 19:45:09 GMT

Donations

Fri, 02 Feb 2024 19:42:26 GMT

Sign In

Fri, 02 Feb 2024 19:39:51 GMT

Single Page Applications

Fri, 26 Jan 2024 16:08:39 GMT

back to accTicket ID: #12345This is the master ticket for the intake process of the [Application Name] as a Single Page Application (SPA). It encompasses all the necessary steps required for successful design, feasibility analysis, and initial application setup.Proposed URL for the Project: [Fill in domain]Requires Authentication: [Yes/No]Data Storage: [None/Client/Server]
This checklist is roughly established by the breakdown from Outline of Tickets for SPAs in Vue Project Initiation: Conduct a kick-off meeting involving representatives from Product Lines, UX Team, Frontend Developers, and Backend Developers to align on objectives and expectations. Define project scope and set up project tracking. Requirement Gathering: Gather and document the design and functional requirements for the SPA. Set a milestone to finalize the requirements. Technical Feasibility: Conduct a technical feasibility study based on the gathered design and requirements. Review and adjust project scope if necessary. [ ] Analytics engagement: outline goals and metrics that are needed for antibiotics. Engage the analytics team and fold any technical requirements for analytics into the project from the beginning. Design Phase: Follow-up on the design after the technical feasibility study, making necessary iterations and adjustments. Define a milestone for finalizing the design. Development - Basic Application Setup: Define and set up the data structure and API calls, construct the page layout, create the code branch, and set up page access. Also, set up the Vue APP SHELL and initiate the application. Set a milestone for the completion of this basic application setup. Development - Component Construction: Create multiple tickets for each component that needs to be developed or modified. Set a milestone for the completion of all components. Development - Feature Specifics: Create multiple tickets for each application-specific feature that needs to be scaffolded. Set a milestone for the completion of all features. Integration and Testing: Integrate components with the application and refine features in cooperation with QA. Set a milestone for the completion of integration and testing. User Acceptance Testing: Conduct user acceptance testing to ensure that the application meets the defined requirements and user expectations. Set a milestone for the completion of UAT. Beta Focus Group (Optional): If applicable, conduct a beta test with a focus group. Use their feedback to make final adjustments before the full launch. Launch Preparation: Prepare for the application launch, ensuring all systems are ready and all required parties are informed. Launch and Post-Launch Review: Launch the SPA, monitor its performance, gather feedback, and conduct a post-launch review. Set a milestone for the completion of the post-launch review. 🔶 Please fill in the details accordingly, which will greatly assist the development team in understanding and executing the required tasks.🔶 This refined milestone-based checklist offers a comprehensive snapshot of the process needed for the transition of the application to an SPA. For each step, corresponding sub-tickets should be generated under this primary ticket. Each sub-ticket will be added to the appropriate backlog and prioritized based on its criticality and dependencies. This structure will ensure seamless management and clear tracking of progress throughout the project's lifecycle.

Story First Content

Fri, 26 Jan 2024 15:54:23 GMT

Page Creation GuidanceFocus the User- Always write to the goal of the page or task of the initiative. In the first sentence or area of the page the user should easily tell the action they should take. And every piece of content should support, educate, or compel the user to act upon the task of the page. Reduce - Reductive writing is best online users shy away from long blurbs of text. Reuse - Don't repeat similar or same blocks of text or content. If there are reasons for content to be used in multiple areas - link to it, or pattern it as a resource that users an engage with if they need it. Recycle- The title of the page you are linking to is usually not enough to be engaging. Put the link within the text of the page, rewrite the hook to get users to the page by lifting up concepts and reasons for the user to engage with the link to navigate to it. Breaking a part the titles and content so it is easier to scan. For Example Name of the doctor, concept of content, and type of content distinguished by style allows users to faster then it all written out as single line.
#acc/guidance

Bug Ticket Template

Fri, 08 Dec 2023 14:30:32 GMT

Title: [Brief, concise summary of the bug]Ticket ID: #12345Reported By: [Your Name]Date Reported: [Date]Assigned To: [Assignee's name]Priority: [Low/Medium/High/Critical]Severity: [Low/Medium/High/Critical]Environment: [e.g. Production/Staging/Test]Browser/Device: [e.g. Google Chrome v90, iPhone X]Description:Provide a detailed explanation of the bug. Include what the expected behavior is and how the actual behavior differs. If the bug is intermittent, mention this and provide any known steps to reproduce.Steps to Reproduce: Step 1 Step 2 Step 3 ... Actual Result:Describe what happens when you follow the steps mentioned above.Expected Result:Describe what you expected to happen when you followed the steps above.Attachments:Include any relevant screenshots, logs, or other files that may help in diagnosing the bug.Please fill in the details accordingly, which will greatly help the development team in understanding, reproducing, and ultimately resolving the issue.#acc/jira #acc #work #requirements

Scripts

Fri, 21 Jul 2023 18:17:17 GMT

This project involves two key categories of scripts, each serving a distinct purpose: Auditing Query Scripts: These scripts function as digital scanners for the area specified in the bulk conversion. They produce various reports that aid in devising action plans, drafting reports, and even targeting actionable needs for Jira tickets. Action Scripts: This category represents a comprehensive collection of automations. These scripts interact directly with different parts of our system, such as the codebase, the CMS, or the content within the CMS. They perform a broad array of tasks, which can include automatic adjustments, content updates & alterations, or system configuration alterations. Linked Components from pages with batch Content Area Scrape of CSS and JavaScript Targeted Editorial UI Occurrences via Defined Hooks Mapping Conversion Remediation Automations Content Alteration Arches Override ID ... Tag Typo Corrections styles ==> style Linked Style and Script Removal Content Sanitization Scripts. "Nuclear Option" Remove In Page Script and Styles Remove the inline CSS and Script Calls

SPRINT B - Component Conversions

Fri, 21 Jul 2023 17:58:06 GMT

Convert the components Judge if component is a Legacy Supportive, or a New Component
Things to Consider when Component Conversion Approach Deploy to lower environments DEV/SPR QA test the converted components Promote to PROD
List of bulk changes - Update the Mapping Document
#acc/arches/conversion Metadata Created:: 9:39 AM - July 17, 2023 Updated:: 1:58 PM - July 21, 2023

Bulk Conversion Script Process

Fri, 21 Jul 2023 17:48:43 GMT

Change page layout to ArchesMainView or Arches variation Template (Article...) Change legacy components to Arches components using the master component mapping document as reference. Content Remediation (After sprint A audit of style and script blocks) Remove the following from rich text and custom script content: External stylesheet links External JavaScript links Style blocks JavaScript blocks In-line styles In-line JavaScript calls Check converted pages (within reason) and adjust clean up script as needed if content gets mangled. Observations & Notes:Batch 1: Debugged a content block that used an incorrectly spelled tag. This broke the page post conversion and evaded the style blocks removal script. The clean up scripts will be adapted to this typo so future instances should be caught and removed but verify as needed. Verify the scripts run clean. Special characters, for example, may still cause the automation to stop or manipulate code incorrectly. Alter template to Arches Run component swap from Mapping of Converted Components ‘RichText’ and ‘CustomScript’ clean up.
Run scripted remediation Remediation IMPORTANT NOTE: To ensure content is NOT auto-published, there is a need to explore options.
1. Option 1: Set content items to a DRAFT status when converting content in Author. See Sitecore DRAFT workflow doc here. Possible risk is the Original Posted Date may be updated as a result (need confirmation) 2. Option 2???Metadata Created:: 4:30 PM - July 19, 2023 Updated:: 1:48 PM - July 21, 2023
#acc/arches/conversion #acc/guidance

Audit of Editorial UI

Fri, 21 Jul 2023 17:47:02 GMT

Over time, the content areas of our CMS have seen the implementation of various User Interface (UI) solutions. Often grassroots in origin, these Editorially Created UI elements, composed of inline styles, in-page styles, and JavaScript, present considerable maintenance and update challenges.To manage this tech debt, our bulk conversion process aims to remediate or remove these elements. The goal is to align our UI with the Arches Enterprise Design System, which entails eliminating non-conforming in-page JavaScript and Styles.To facilitate this, we're conducting an audit of the Editorially Created UI components. This audit plays a crucial role in forming a plan that ensures website functionality while addressing unnecessary complexity.This process involves a meticulous examination and subsequent remediation of all editorially integrated links - a prerequisite before launching any audit. Our audit also thoroughly reviews content areas embedded with script and style blocks. Particular attention is given to the returned content scrape, which is systematically converted into a Unicode format that's safe for coding.As part of this procedure, we identify and replace certain patterns, such as "<" and ">", with their equivalent symbols, and transform specific HTML entity codes into spaces and carriage returns, thereby improving block readability. This method allows the team to evaluate readable blocks effectively and discover any "new" patterns, which aids in documenting necessary remediation steps. This systematic approach prepares us for the eventual removal of style and script blocks, creating the necessary tickets or steps as required.Numbered Steps: Begin by running the remediation of all editorially included links that are set to "Save" before initiating the audit. Perform an Audit Report of content areas that contain script and style blocks on the page.
Ensure the returned content scrap is converted into a code-safe Unicode because of the Content Scrape Limitations. Identify and replace specific patterns, such as "<" and ">", with their corresponding symbols. Substitute certain HTML entity codes into space and transform others into carriage returns. Evaluate the now readable blocks after the aforementioned transformations.
Discover any new patterns that emerge from the evaluation, and document the appropriate remediation steps. Finally, create any necessary tickets or steps to prepare for the obliteration of style and script blocks. To make the code more readable, it's crucial to replace certain Unicode characters with their typical representations. Specifically, we'll be dealing with the following conversions: The Unicode for the carriage return, _000D_, should be replaced with a visual marker for carriage returns such as the symbol "↵". The Unicode for the horizontal tab, _0009_, could be replaced with a few spaces for better visualization. The Unicode for the space, _0020_, can be substituted with a visible space character. The line feed character, represented by the Unicode _000A_, can be swapped with a new line symbol like "␤" to depict line breaks better. The tab character, also represented by _0009_, should be replaced with a few spaces for clarity. Finally, the Unicode for less than and greater than symbols, < and >, can be converted to their actual "<" and ">" symbols. By transforming these Unicode characters into their corresponding visual representations, we significantly enhance the comprehensibility of the document, thus facilitating easier identification of different elements and their spacing.

SPRINT A - Define the Batch

Fri, 21 Jul 2023 15:06:03 GMT

Select conversion candidate for the batch and define scope Target a good number of pages with the same component composition Query Sitecore within scope for code components & plan needed conversions 2. UI will create and update the Mapping of Converted Components Query Sitecore Content Areas (RichText & CustomScripts) within scope forEditorial Generated UI& start planning for remediation UI will audit and update the Remediation Steps for Sprint C Groom Provide a list of the components to UI for conversion. Provide a list of templates that need to be constructed.
UI will earmark any Jira Tickets for component conversion ARCHES Component Conversion
UI will earmark any needed New Components from the Audit of Editorial Generated UI Creating A New ACC.org Component Calculate and Plan Next Sprints How complex will the conversions be/How long will it take? Generally, this will hopefully be doable in one sprint assuming there is not any major rebuilding needed. Most importantly we need to determine how many will need to be rebuilt completely.
#acc/arches/conversion #acc/guidance Metadata Created:: 9:39 AM - July 17, 2023 Updated:: 11:06 AM - July 21, 2023

Front End Design at the College

Thu, 20 Jul 2023 21:31:14 GMT

Frontend development continues to expand as a percentage of project coding to the point that some of our products, such as the clinical applications, are 100% frontend code. Over the past year, I have been putting work together to support a massive shift in how we do frontend and, in the long run, how we develop, support, and release our college software solutions. The most significant issue I continually see in IT is decentralized coding efforts. Decentralization leads to repetitive solutions, inconsistent behaviors, extended regression testing, bloated packages, complicated deployments, and potential code errors as we try to make security patches or upgrades. Focusing on improving how we execute frontend for the college and not just for a project, I have tackled four pillars. Unification of design but building for flexibility Shifting to the CFD (component first development ) Creating documentation that is utilized and not just ignored Centralizing everything for everyone The unification of design was the first place I started. "Arches" is the current solution that enforces a Design Opps procedure to streamline requests and deliver a college-wide design system. This design system has two tenants. First, it can replicate its styles influenced by the brand and frameworks from its product space. It now covers QII, ACC, Cardiosmart, and Mobile and can be further scaled. Second is its utility framework that ensures a highly flexible practice to allow countless UI permutations without CSS mutations. Utility styling is also known as "scopeless" styling because you can build out many UI patterns without ever altering the original styles. https://assets.acc.org/Arches/Latest/docs/Shifting to CFD (component first development) embraces an architecture for our frontend products and alters how we develop. CFD, as a pattern, has been around since 2012 with bootstrap. In its infancy, CFD could only capture minor token UI. Still, with the introduction of javascript models like Web Components, React, Vue CFD can now capture business logic, complicated interface interactions, and data mutations. Vue has been my primary focus as it builds on the collective knowledge of the department. Vue has the capabilities to make obsolete Jquery UI, Pager, Knockout, Angular, JqueryMobile, and many other libraries that are currently in use. IT streamlining to a single dependency allows for universal software patching for frontend security issues. Currently, we are creating documentation that is utilized and not just ignored. As we shift to CFD, we can use Storybook which allows for documentation around a living singular component with artificial data. This type of documentation gives a single point of Design, Development, and QA. The effort on a single element can be attached to countless projects through version control. Centralized development and QA can give us a feasible path to automated unit testing and regression testing. As new projects come online, utilizing the global-version-controlled components would benefit from standards, consistency, and quality control. Preliminary work done with Storybook around a future product under the ACC.org "Home Page Redesign." Projects could include the transcript, CSTool, GL Search, Coveo Search, and FIT Management. Vue 2 component for reference
https://acc-style.github.io/Origami/?path=/story/welcome--to-storybookVue 3 component for all new work
https://assets.acc.org/papercrane/Latest/docs/Centralizing everything for everyone. I have conversations GM, Josh G, and Micheal M, and the great work of Ling C on creating a path forward with using assets.acc.org and also moving the newly used submodule features from GIT within current and future products. Submodules empower the component work to be checked in and out from both the centralized-version-control and from projects, these efforts can be kept in sync. The vision for this project is to be controlled by ACC but utilizable by vendors.

SPRINT D - Batch Conversion

Thu, 20 Jul 2023 21:16:06 GMT

Create PRD/Master/Web DBs backup for potential rollback Enforce a content freeze (BL), specifically for a subset of pages/content Run Bulk Conversion Script Process in Author only with auto-publishing turned off IT performs spot checks
Compile and Deliver the Editorial Bulk Change Notice Excel BL reviews and validates pages, with support from UI, DEV, and QA teams Review affected pages for discrepancies/bugs for resolution (e.g., code, components, etc.) Garbage Clean up of Empty Content Areas, Rich Text, Custom Scripts Resync to lower environments?
#acc/arches/conversion #workMetadata Created:: 4:30 PM - July 19, 2023 Updated:: 5:16 PM - July 20, 2023

SPRINT C - Editorial Created Remediation

Thu, 20 Jul 2023 21:15:25 GMT

SYNC SPR Execute bulk conversion script with a small sample of pages in DEV/SPR - Using Mapping Clean up rich text via script (S&D) Review effected pages Update Editorial Bulk Change Notice Excel for content issues identified during review Work with BL to resolve found issues
Remediation | Remediation Document of all editorially needed extra steps Promote to RLS Demo with BL review Remediation Steps and obtain sign-off
#acc/arches/conversion #acc/guidance Metadata Created:: 3:56 PM - July 18, 2023 Updated:: 5:15 PM - July 20, 2023

New Component

Thu, 20 Jul 2023 20:56:59 GMT

ticket ARCHES Component Conversion build test Sitecore Integration
#work #acc/arches #acc/guidance #acc Metadata Created:: 9:39 AM - July 17, 2023 Updated:: 4:56 PM - July 20, 2023

My ACC.org Dropdown Menu

Thu, 20 Jul 2023 20:44:59 GMT

Clean up the drop down menu on ACC.org to include a centralized link to the profile on Salesforce answer.

Dynamic Header & Footer

Thu, 20 Jul 2023 20:44:19 GMT

Working through the pages that need to have the new header and footer. Double check this listed page to clean List of Pages

Invoices Pay for some one else

Thu, 20 Jul 2023 18:52:41 GMT

Auto login - single payment to an attachment of invoice of a member ID ONECRM-1695 User Types: Admin, Assistants, Staff Admin Login - multiple payment of any doctors under an "umbrella" ONECRM-261 Admin has a login Admin is a "owner" of a company

Editorial Bulk Change Notice Excel

Thu, 20 Jul 2023 15:22:27 GMT

The process of bulk conversion is a nuanced operation that significantly depends on the scope of the pages being converted. Each bulk conversion task is unique, and while insights and learnings from previous conversions inform the process, it's important to note that a bespoke report is produced after each conversion. This report, presented in an Excel document, is a crucial tool that outlines the User Interface (UI) items within the editorial scope - including Rich Text and Custom Scripts - that require remediation following the conversion. The items are neatly categorized by sheet, each containing the Item ID, URL, and proposed remediation notes. This systematic approach provides a comprehensive view of the areas within the CMS that may need review, adjustments, or those indicating a potential function failure. Typical remediation steps include actions like "let fail," "add classes," "remove," and "replace with components," but this list is not exhaustive. If more complex actions are needed, additional notes may be added for clarity. This meticulous process ensures an efficient and methodical approach to addressing changes and potential issues post-conversion.A listing of all pages effected by the conversion

OMA Replacement - Membership Join Us

Tue, 18 Jul 2023 20:54:15 GMT

He has never dictated the need for the UI but he recognizes a great divide between what is shown in demo and what is currently in place in our solution.From the quick demo I just received the dropdown is driving the options the user is eligible for which is the requirement.The select application is a simple dropdown with only the application names that the user is eligible for. This has some lacking experiences from what is currently built which are. A description of the differences of member types Direct Comparison of Options Pricing of the options before you click A quick checklist of details you will need to fill in after you start. This last item is what concerns JP the most because of how this impact's user experience and education before an application is kicked off.This solution has compounding problems because of how the application selection doesn't inform the user on what information they should collect before they start and the experience of saving and returning to the application.<<<<<<< HEAD:Family/My Family/Temp/Untitled.md The Save and Return doesn't Resume an application but starts over with the user and in generates new records in the backend (Multiple attempted Pending applications) The Wizard Doesn't Navigate when returning to an application you can't use the wizard as a navigation to skip around. You need to multiple select the next button and even then you can't always bypass blocking questions because the user selections don't seem to persist for the user. These Save and Return Limitation really predicates the user to be as educated on the requirements of the application before they start because they will have to run through the application multiple times. Absolutely, there are numerous ways to phrase this question to encourage engagement and make it easier for respondents. Here are three additional options:Option 1 (Comparative Importance): "Which types of content on a digital platform do you find most valuable? Please rank the following options from most valuable (1) to least valuable (5). Top-cited articles Videos Podcasts Digital Interactives Other resources (please specify)" Option 2 (Preference Order): "Everyone has a preference when it comes to content on digital platforms. What's yours? Please order the following types of content based on your personal preference, with 1 being your top preference. Top-cited articles Videos Podcasts Digital Interactives Other resources (please specify)" Option 3 (Time Investment): "If you had an hour to spend on a digital platform, how would you divide that time among the following types of content? This doesn't need to add up to exactly 60 minutes - we're just trying to understand what you'd prefer to spend more time with. Top-cited articles: ___ minutes Videos: ___ minutes Podcasts: ___ minutes Digital Interactives: ___ minutes The Save and Return doesn't Resume an application but starts over with the user and in generates new records in the backend (Multiple attempted Pending applications) The Wizard Doesn't Navigate when returning to an application you can't use the wizard as a navigation to skip around. You need to multiple select the next button and even then you can't always bypass blocking questions because the user selections don't seem to persist for the user. These Save and Return Limitation really predicates the user to be as educated on the requirements of the application before they start because they will have to run through the application multiple times. main:Work/ACC/1CRM/OMA Replacement - Membership Join Us.md

Checklist for a Viability

Tue, 18 Jul 2023 20:24:50 GMT

Checklist/Questioner for BL to fill out before a new microsite is created: What is the specific purpose or initiative? How is it important? What is the conversion goal or mission for the users to accomplish? Must be specific, with high strategic value to the college. What is the specific target audience? What is unique or separate about the target population? What is the timeline for this initiative? What about the design is different from the ACC brand? How is it unique? How is it complex? How is it self-contained? How is the functionality different from what is offered on the ACC.org site? Where does it fit within the existing ACC.org site? (It shouldn’t, but listing this would identify the gap.) Optional aspects : Partnership or collaboration - is there a joint partner? #acc/guidance #acc/org/microsite alias: 'Checklist for Viability' date created: 'Jul 18 2023' date updated: 'Jul 18 2023 @ 16:22:39-04:00'

Component Conversion Approach

Tue, 18 Jul 2023 19:09:03 GMT

Only built with HTML and ASP with minimal JavaScript #checklist
The JavaScript function can be isolated to just the component #checklist
The JavaScript implements a function that is not included in Bootstrap #checklist
The JavaScript is still needed if put in context of an Arches Template #checklist not adding classes to body, main-content, hiding masthead etc.
The DOM structure is semantic and clean #checklist
No matter what approach it is often important to follow the Quality of life configurations with Sitecore.
#checklist

Remediation

Tue, 18 Jul 2023 19:04:23 GMT

Creating A New ACC.org Component

Tue, 18 Jul 2023 18:40:07 GMT

File locations rules to where in the code base all new works should depending on the type of component created. Naming convention the name should be postpended with _arches.cshtnl or the appropriate file extension. Sitecore Treatments Icons, naming, and configurations.

Micro Branding with Page Title

Mon, 17 Jul 2023 16:14:22 GMT

As an editor of ACC.org, I need a Micro Branding with Microsite Title component for ACC.org microsites. This new component aims to provide an engaging user experience and promote specific campaigns or products, while also ensuring a clear link back to the microsite home along with the page title. Arches CSS version: The component should be developed and tested using the latest version of Arches CSS. Design pattern: The component should strictly adhere to the design pattern provided at this link. Image resizing: The component should resize the image based on the device viewed: For all sizes (Desktop, Laptop, Tablet), the height should be minimized at all time to reduce consumption of "Above the Fold Areas." Breadcrumb navigation: The component should display breadcrumb navigation that includes a back arrow and the connecting page of the main site this microsite connects to. Configurable microsite title: The component should include a scalable title that adjusts its size based on the viewport. This component should be able to be placed full-wide above the page structure of Left Sidebar and Main Content. The "Micro Branding with Page Title" component is created and implemented according to the design pattern and requirements. The user experience team has reviewed and approved the component. Post-deployment training is set up for the editors to understand and use the new component effectively.

Anatomy of a Microsite

Mon, 17 Jul 2023 16:08:44 GMT

← back to MicroStiesA microsite on ACC.org is a purposeful orchestration of interconnected pages, centered around a key "Home of the Initiative" page. Each page is a chapter of the initiative's story, aimed to guide users to a strategically defined conversion point. Here's an outline of the elements: Home of the Initiative: This main, full-screen page serves as the prologue to the initiative's story, providing a pathway back to the main ACC.org site. It features a text-free, richly layered hero image, a compelling call-to-action (CTA), and supportive information to propel the narrative. Additional CTAs invite visitors to explore further details.
Hero Image: This visually arresting image, free from text and easily adaptable to cropping or trimming, imbues the microsite with a unique "flair" or brand identity. Hero Image Requirement Initiative CTA and Hero Image: The microsite distinguishes itself from the main ACC.org site through its unique branding, represented by the hero image and a clear, persuasive CTA. This combination piques user interest and encourages action.
Sub-Pages and Micro Branding: Consistent branding is carried through to each sub-page via a smaller image that reflects the "flair" of the home page's hero image. These pages, adhering to comprehensive content creation guidance, utilize a sidebar navigation layout and always lead back to the "Home of the Initiative". Micro Branding with Page Title Purpose-Driven Sub-Pages and Conversion Points: Every sub-page plays a crucial role in the initiative's narrative, either by presenting a primary CTA, providing deeper information, or hosting a set of conversion points. Each page aims to drive the user towards a conversion, fulfilling the strategic needs of the microsite. This well-crafted design ensures a distinct, narrative-driven user experience within the microsite while maintaining a strong link to the broader ACC.org environment.
#acc/guidance #acc/org/microsite

Hero Image with CTA

Mon, 17 Jul 2023 16:00:54 GMT

As a developer, I need to create a "Hero Image with CTA" component to be utilized in the ACC.org microsites to deliver a captivating user experience while promoting specific campaigns or products. Arches CSS Version: The component should be developed and tested using the latest version of Arches CSS, as this depends on the component's production. Design Pattern Adherence: The component should strictly follow the design pattern provided at this link. All styling, formatting, and elements in the design pattern should be correctly incorporated into the component. Image Resizing for Multiple Devices: The component should use the provided image sizes based on the device viewed: Desktop Size 1200x300, Laptop Size 1024x256, Tablet Size 600x300, Small Size 300x450. Breadcrumb Navigation: The component should display breadcrumb navigation that includes a back arrow and the connecting page of the main site this microsite connects to. Configurable Microsite Title: The component should include a scalable title that adjusts its size based on the viewport. Configurable CTA Title, Description, Button URL, and Label: The component should have fields for the CTA title, description, button URL, and label that can be configured to meet the needs of the specific campaign or product being promoted. The "Hero Image with CTA" component is completed and meets the acceptance criteria. The user experience team has reviewed the component. After Deployment, training is set for the Editors to know and use the new component.
https://acc-style.github.io/PrototypingACCorg/arches/UX_MicroSite-Home/ 🔼 Build the component

Pros & Cons

Mon, 17 Jul 2023 15:58:36 GMT

← back to MicroStiesA microsite on ACC.org provides a strategic platform for delivering a focused, user-centric experience for a specific initiative. Acting semi-independently from the main site, it caters to a niche audience or user need that benefits from a narrowed scope and tailored options, away from the broader offerings of the main site.The microsite adopts the fundamental branding guidelines of ACC.org while introducing its unique design, structure, and organization. This concentration of tailored information and user actions makes it an effective tool for engagement. Focused Content: Microsites allow you to create content that is highly targeted towards a specific audience or topic. This can help improve user engagement and conversion rates for that specific topic or audience. Product Brand Alterations: Microsites provide an opportunity to apply branding and design strategies unique to the product. Campaign-Specific Messaging: Microsites can be an effective tool for unique marketing campaigns or product launches, where a dedicated site can deliver a focused message. Fast Deployment: Microsites can typically be augmented and launched more quickly than adding substantial new sections to an existing site. Most often this work is bespoke and one off. Flexibility: Microsites can be easily tweaked or shut down without affecting the rest of the company's web presence. User Experience: Microsites can offer a more streamlined and targeted user experience, leading to improved customer satisfaction and conversion rates for a product. Improved Tracking: It may be easier to track the effectiveness of a specific campaign or audience through a microsite, as analytics can be specifically tailored for the site. Independence: If different departments or branches of a company want to maintain a certain level of autonomy in their web presence, microsites can offer this independence. While microsites can be valuable tools, they also come with inherent challenges that can affect your digital strategy. These challenges underline the fact that while microsites can be effective for specific initiatives, they should be used judiciously and with clear purpose, given the potential costs involved. Brand Consistency: Operating multiple microsites can disrupt brand uniformity and recognition, causing customer confusion. Increased Management Complexity: The operation and maintenance of various microsites amplify the complexity of website management, requiring additional resources. The bespoke nature of the code might also lead to problems during system upgrades. SEO Risks: Microsites could cannibalize the SEO value of the main site and end up competing with it in search results. User Navigation and Context Confusion: Due to their distinctive branding and self-contained nature, microsites can create navigation challenges for users. Moving between multiple microsites and the main site can lead to a disorienting user experience. This context-switching confusion is typically less prevalent in a single, unified site of the main site. Content Duplication: Managing content across the main sites and isolated microsites introduces the risk of duplication and subsequent issues with content upkeep, maintenance and SEO. Traffic Dilution: Traffic is dispersed across multiple microsites instead of being directed to one central site, leading to a dilution of traffic on the main site and less cross-site discovery. Discoverability: If not directly linked or referenced from the main site, microsites may be more difficult for users to find. Sustainability: Maintaining and updating numerous microsites over time can prove challenging, potentially resulting in outdated information.
#acc/org/microsite
#acc/guidance
#acc/ux

Strategic Threshold for a Microsite

Mon, 17 Jul 2023 15:38:31 GMT

← back to MicroStiesFor our company, the use of microsites should be the exception rather than the rule. We should set high thresholds for what qualifies a topic or campaign for a separate microsite. Rather than creating a microsite, the default Generic Page approach should be utilized incorporated within the information architecture of our main site. Only when the content meets exceptionally stringent criteria—whether that's relevance, audience specificity, or uniqueness—should we consider the development of a standalone microsite. Specific Target Audience: Content needs to be tailored to a highly specific audience that can't be effectively targeted through the main site. Unique Campaign: The content should pertain to a unique, typically time-bound campaign that requires distinct messaging separate from the broader brand or company offerings. SEO Strategy: The microsite should have a clear, separate SEO strategy focused on keywords and topics not covered by the main site. User Experience: The microsite should offer a uniquely engaging user experience, such as an interactive product demo or immersive storytelling, that wouldn't fit well within the main site. Unique Functional Requirements: The microsite should require functionality not supported or feasible on the main site, such as a unique user registration process, specific eCommerce setup, or API integrations. New Product Launch: The content should relate to the launch of a new product or service that could benefit from focused attention and doesn't fit neatly into the existing site structure. Event Promotion: The content should promote a specific event that warrants its own promotional and informational space. Partnership or Collaboration: The microsite should be created for a joint venture, partnership, or collaboration with another entity, where separate branding and messaging is crucial. Geographic Specificity: The microsite should cater to a specific geographic market that has unique needs separate from the main audience. Cost-Benefit Analysis: There should be a clear financial and strategic advantage to creating the microsite, with projected benefits outweighing the costs of development, maintenance, and potential dilution of brand or SEO. Defined Lifespan: Each microsite should have a defined lifespan, whether short-term or long-term. This timeframe should align with its strategic objectives, such as ongoing updates or serving as a reference resource. The expected lifespan should justify its creation and separate maintenance, ensuring it brings value during its entire existence.
#acc/org/microsite
#acc/guidance
#acc/ux

ARCHES New Component

Mon, 17 Jul 2023 13:44:31 GMT

back to ACCThis is the master ticket of the [Component Name]. This encompasses all the tasks required for the successful analysis, design, and implementation of the component update.(To be filled by the product owner or stakeholder) Arches Design System .... (To be filled by the IT team after the initial analysis and discussions, Vue, Vanilla JavaScript's, DB connections..;) List all configurations and inputs for this component Component Definition: Define the zone, providing a screenshot, requirements from an editor's perspective, and the URL location. Component Identification: IT to identify and isolate the component. Design Implementation: A front-end designer/developer to create an HTML prototype of the component using the Arches design system. Group Grooming: Conduct a group grooming session to identify any additional tickets or tasks necessary to complete the story. The checklist provides a high-level overview of the steps that need to be taken. More detailed sub-tasks should be created under this main ticket to track the progress of each individual item. This way, it'll be easier to manage and track the progress of this component's transition to the Arches design system.
#acc/jira #acc #work #requirements #acc/jira

WhatIf -- Interaction Model Break Down.excalidraw.light

Wed, 14 May 2025 15:09:26 GMT

TagDashboardFigure.excalidraw.dark

Wed, 14 May 2025 15:09:26 GMT

Tag Interactions Structure.excalidraw.light

Fri, 02 May 2025 19:15:27 GMT

Sitemap -- Support Fund.dark

Fri, 02 May 2025 19:15:27 GMT

Sitemap -- Support Fund.light

Fri, 02 May 2025 16:21:12 GMT

WhatIf -- Interaction Model Break Down.excalidraw.dark

Fri, 02 May 2025 16:21:12 GMT

WhatIf -- Interaction Model Break Down.excalidraw.light

Wed, 14 May 2025 15:09:26 GMT

TagDashboardFigure.excalidraw.dark

Wed, 14 May 2025 15:09:26 GMT

Tag Interactions Structure.excalidraw.light

Fri, 02 May 2025 19:15:27 GMT

Sitemap -- Support Fund.dark

Fri, 02 May 2025 19:15:27 GMT

Sitemap -- Support Fund.light

Fri, 02 May 2025 16:21:12 GMT

WhatIf -- Interaction Model Break Down.excalidraw.dark

Fri, 02 May 2025 16:21:12 GMT