career path guidance - john ong

Introduction to Meeting Context

• Informal check-in, discussing personal workload and training.
• Reference to organizational meetings planned for the afternoon.

General Background

• Discussion revolves around the Career Path Framework and its administrative components.
• The speaker is seeking input and ideas from another colleague, aiming for collaborative idea-sharing rather than direct questioning.

Admin Panel for Career Path Framework

• Objective: To create an admin panel that allows non-technical personnel to manage and edit the Career Path Framework website, including modifying objectives and frameworks.
• Reference to a related initiative called "pv two" which suggests similarity and consistency across projects.

Admin Panel Specifications

• Desired ability for non-technical users to interact with the framework.
• Exploratory ideas about reusing methods or structures being used in pv two for uniformity.

Conceptual Discussion

• The development of the admin panel may involve considerations regarding user-friendliness and functionality for all versions of the framework.
• Discussion of potential challenges in reusing current features due to the experimental nature of recent updates.

Technical Details of Existing Systems

• The existing admin console is going through tests; the new system should integrate smoothly.
• The integration of new themes and user changes possible via the admin panel:
  • Users can edit colors and preview changes. Transformation caused by modifications to themes is a focal point of the admin function.

Components of User Experience

• Specific parts of the framework considered include design tokens, header and footer components.
• The importance of functionality alongside aesthetics for user experience design (accessibility) emphasized.

UI Kit and its Role

Definition and Functionality of UI Kit

• Described as a component library designed for consistent functional design across applications.
• Serves as a headless component library separating visual styling from functionality, maintaining functional integrity while allowing for aesthetic changes.

Customization and Functionality

• Users may utilize local copies of UI and functional libraries rather than a centralized codebase to minimize dependency issues.
• Need for structured dependencies and understanding of the impact of changes across multiple applications is stressed.

Admin Panel Structure

• Two Approaches Suggested:
  • Creating a separate admin application for Career Path Framework with controlled access; could allow direct changes without affecting a broader suite of applications.
  • Adding an admin route to the existing application for editing functionalities—makes initial development easier.

Permissions and Authentication

• Authentication methods discussed, including consideration of Basic Auth vs. Cognito for internal applications.
• Emphasis on internal use of the admin panel means basic security measures may suffice.

Project Management and Development Timeline

• Speaker aims to work on updates to the Career Path Framework and wants to be able to show results within two weeks.
• Internal deadlines appreciated for visibility to upper management regarding progress.

Structure and Functionality Clarification

• The necessity of defining a clear data model for user input, emphasizing a data-driven design approach, and managing changes effectively through user-friendly interfaces.
• Internal discussions suggested need for cohesive collaboration between teams to define specifications that uphold functionality while also serving aesthetic requirements.

Recommendations on Project Development

• Focus initially on functionality and structure rather than aesthetics, suggesting that the design can evolve later once the main functionality is refined.
• Recommend collaborating with colleagues to ensure clarity and gather insights on both the technical and design aspects.

Conclusion

• Continuous iteration and improvement on development plans suggested, along with periodic reviews to align with evolving goals and standards set during meetings.
• Expectation of future discussions to share progress and clarify the approach towards integrating user feedback and requirements into final development.