Brand Identity Kit
Run ID: 69cc0f7b04066a6c4a168f902026-03-31Design
PantheraHive BOS
BOS Dashboard

Complete brand identity package including logo concepts, color palette, typography guide, brand voice guidelines, and social media style guide.

Brand Identity Kit: Research & Design Requirements

Project Step: 1 of 3: Research & Design Requirements

Date: October 26, 2023


1. Introduction

This document outlines the comprehensive research and design requirements for developing your Brand Identity Kit. This initial phase focuses on understanding your brand's core essence, target audience, competitive landscape, and translating these insights into actionable design specifications and strategic recommendations. The goal is to establish a robust foundation for a cohesive, impactful, and memorable brand identity that resonates with your audience and achieves your business objectives.


2. Core Brand Identity Principles (Research Phase)

Before any visual elements are created, a deep understanding of your brand's foundation is crucial. This section defines the key areas of research that will inform all subsequent design decisions.

2.1. Target Audience Analysis

  • Demographics: Age range, gender, location, income level, education.
  • Psychographics: Values, beliefs, interests, lifestyle, motivations, aspirations, pain points.
  • Behavioral Patterns: How they interact with brands, preferred communication channels, purchasing habits.
  • Desired Perception: How we want the target audience to feel and think about the brand.

2.2. Brand Values & Personality

  • Core Values: The fundamental principles guiding the brand's actions and decisions (e.g., Innovation, Trust, Community, Excellence).
  • Brand Personality Archetype: Defining the human characteristics of the brand (e.g., Explorer, Sage, Innocent, Ruler, Jester). This will inform tone of voice and visual style.
  • Mission & Vision: The brand's purpose and long-term aspirations.

2.3. Competitive Landscape Analysis

  • Direct Competitors: Identification of key competitors and analysis of their brand identities (logos, colors, typography, messaging).
  • Indirect Competitors: Brands offering alternative solutions or targeting similar audiences.
  • Differentiation Strategy: Identifying opportunities for the brand to stand out and create a unique position in the market.
  • Industry Trends: Current and emerging design and branding trends relevant to the industry.

2.4. Desired Brand Perception

  • What three adjectives should people use to describe your brand? (e.g., Modern, Reliable, Friendly; or Luxurious, Exclusive, Sophisticated).
  • What emotional response should the brand evoke in its audience? (e.g., Trust, Excitement, Comfort, Empowerment).

3. Detailed Design Specifications

This section outlines the specific design requirements for each component of the Brand Identity Kit.

3.1. Logo & Iconography

  • Design Requirements:

* Concept: Must embody the core brand values and personality identified in the research phase. Should be unique, memorable, and timeless.

* Scalability: Must be highly scalable for use across all mediums, from favicons to large billboards, without loss of quality or legibility.

* Versatility: Must function effectively in various contexts (full color, monochrome, reversed, small sizes).

* Simplicity: Clean and uncluttered design to ensure immediate recognition and recall.

* Originality: Avoidance of clichés and generic imagery.

  • Conceptual Directions (Initial Exploration):

* Option 1 (Abstract/Symbolic): Focus on a unique graphic mark that subtly represents a core brand value or concept.

* Option 2 (Wordmark/Logotype-driven): Emphasize a custom typeface or distinctive lettering for the brand name itself, conveying personality through typography.

* Option 3 (Combination Mark): Integrate a distinct symbol with the brand name, offering flexibility for standalone use.

  • Application Mockup Descriptions (Wireframes):

* Logo on Digital Header: A simple rectangular placeholder for a website or app header, demonstrating logo placement, size, and potential interaction with navigation.

* Social Media Profile Picture: A circular or square frame showing how the logo (or a simplified version/icon) will appear in constrained social media profile contexts.

* Business Card Layout: A basic rectangular outline for a business card, indicating primary logo placement, contact information fields, and potential background color/texture.

* Letterhead/Document Header: A simplified document header showing logo placement and brand name, ensuring professional presentation.

3.2. Color Palette

  • Design Requirements:

* Psychological Impact: Colors chosen to evoke the desired emotional responses and align with brand personality.

* Contrast & Accessibility: Ensure sufficient contrast for readability, adhering to WCAG (Web Content Accessibility Guidelines) standards where applicable.

* Industry Relevance: Consider color conventions within the target industry, while also seeking differentiation.

* Versatility: A palette that works well across digital and print mediums.

  • Initial Palette Recommendations:

* Primary Colors (2-3): Dominant colors that define the brand's core identity.

* Primary 1 (e.g., Deep Ocean Blue): HEX #1F456E, RGB 31,69,110, CMYK 72,37,0,57

* Primary 2 (e.g., Vibrant Teal): HEX #008080, RGB 0,128,128, CMYK 100,0,0,50

* Secondary Colors (2-3): Complementary colors used for supporting elements, backgrounds, or specific calls to action.

* Secondary 1 (e.g., Soft Grey): HEX #D3D3D3, RGB 211,211,211, CMYK 0,0,0,17

* Secondary 2 (e.g., Muted Gold): HEX #B8860B, RGB 184,134,11, CMYK 0,27,94,28

* Accent Colors (1-2): Used sparingly for emphasis, calls to action, or interactive elements.

* Accent 1 (e.g., Energetic Orange): HEX #FF7F50, RGB 255,127,80, CMYK 0,50,69,0

3.3. Typography Guide

  • Design Requirements:

* Readability & Legibility: Fonts must be clear and easy to read across various sizes and devices.

* Brand Personality Alignment: Typefaces should reinforce the brand's desired tone and personality (e.g., elegant, modern, playful, authoritative).

* Hierarchy: Clear visual hierarchy between headings, subheadings, and body text.

* Web & Print Compatibility: Selection of fonts that perform well in both digital and print environments, with consideration for licensing.

  • Font Category Recommendations:

* Primary Heading Font (e.g., Modern Sans-Serif): Clean, crisp, and versatile for strong headlines and branding elements.

* Secondary Heading Font (e.g., Contemporary Serif/Slab Serif): Offers a distinct personality, providing contrast and character for subheadings or specific brand statements.

* Body Text Font (e.g., Highly Legible Sans-Serif or Traditional Serif): Optimized for long-form reading, ensuring comfort and clarity.

3.4. Brand Voice & Messaging

  • Design Requirements (for communication style):

* Consistency: All communications should reflect a unified brand voice across all platforms and content types.

* Authenticity: The voice should feel genuine and true to the brand's values.

* Target Audience Resonance: Messaging should speak directly to the target audience's needs and preferences.

* Differentiation: A unique tone that distinguishes the brand from competitors.

  • Key Tone Descriptors:

* (Example 1) Informative & Authoritative: Position the brand as a knowledgeable expert.

* (Example 2) Friendly & Approachable: Foster a sense of warmth and connection.

* (Example 3) Innovative & Forward-Thinking: Emphasize progress and new ideas.

* (Example 4) Empathetic & Supportive: Demonstrate understanding and care.


4. Social Media Style Guide Specifications

This section defines the visual and communication requirements for consistent and impactful social media presence.

  • Design Requirements:

* Platform Optimization: Visuals and content adapted for specific platform requirements (e.g., aspect ratios for Instagram, character limits for Twitter).

* Brand Recognition: Instant recognition of brand content within a busy social feed.

* Engagement Focus: Design elements and content structures that encourage interaction and sharing.

* Adaptability: Templates that can be easily customized for various content types (e.g., promotions, educational content, behind-the-scenes).

  • Template Descriptions (Wireframes for Social Media):

* Instagram Post Template: A square layout with clear zones for image/video, logo placement (subtle), text overlay (using brand fonts), and a consistent color accent for call-to-action.

* Instagram Story Template: A vertical layout (9:16 aspect ratio) with defined areas for full-screen background, text blocks, interactive elements (polls, questions), and a small, consistent brand element.

* Facebook Cover Photo Template: A horizontal banner layout (e.g., 820x312 pixels) with guidelines for safe zones for text and logo to ensure visibility across devices.

* Generic Quote Card Template: A square or rectangular layout with a defined background area (brand color/texture), a large text area for quotes (brand font), and a subtle logo/brand name at the bottom.

  • Content Guidelines Integration:

* Image Treatment: Filters, editing style, subject matter consistent with brand imagery.

* Hashtag Strategy: Guidelines for brand-specific and relevant hashtags.

* Emoji Usage: Recommendations for appropriate and consistent emoji use.

* Call-to-Action (CTA) Best Practices: Consistent phrasing and visual treatment for CTAs.


5. User Experience (UX) Recommendations for Brand Identity

A strong brand identity is not just about aesthetics; it's about the holistic experience your audience has with your brand.

5.1. Consistency Across All Touchpoints

  • Recommendation: Ensure every interaction point—from your website and social media to physical products and customer service communications—reflects the established brand identity. This builds trust and strengthens recognition.
  • Actionable: Develop a comprehensive Brand Style Guide (the output of this workflow) that serves as a single source of truth for all brand applications.

5.2. Clarity & Memorability

  • Recommendation: The brand identity should be instantly understandable and easily recalled. Avoid overly complex designs or ambiguous messaging.
  • Actionable: Prioritize simplicity in logo design, directness in brand voice, and clear visual hierarchy in all communications.

5.3. Emotional Resonance

  • Recommendation: Design the brand identity to evoke the desired emotional response in your target audience, fostering a deeper connection.
  • Actionable: Leverage color psychology, imagery, and tone of voice deliberately to align with the brand's emotional goals (e.g., trust, excitement, comfort).

5.4. Accessibility Considerations

  • Recommendation: Ensure the brand identity is usable and perceivable by the widest possible audience, including those with disabilities.
  • Actionable: Adhere to WCAG guidelines for color contrast ratios in digital applications, use legible font sizes, and ensure all visual elements are clear and unambiguous.

5.5. Scalability & Adaptability

  • Recommendation: The brand identity must be robust enough to adapt to future growth, new platforms, and evolving market trends without losing its core essence.
  • Actionable: Design elements with versatility in mind, ensuring they work across various media and can be extended or simplified as needed.

6. Next Steps

Upon approval of these Research & Design Requirements, the next steps in the "Brand Identity Kit" workflow will be initiated:

  1. Concept Development & Design: Based on these specifications, we will begin developing initial logo concepts, refining color palettes, selecting typography, and drafting initial brand voice guidelines.
  2. Review & Refinement: Presentation of initial concepts for your feedback, followed by iterative refinements until final approval.
  3. Final Deliverables: Compilation of the complete Brand Identity Kit, including all finalized assets and comprehensive guidelines.
gemini Output

Design Specifications: Brand Identity Kit

This document outlines the detailed design specifications for your comprehensive Brand Identity Kit. These specifications will guide the creative process for logo development, color theory, typography, brand voice, and social media presence, ensuring a cohesive, impactful, and consistent brand image.


1. Logo Concepts & Guidelines

The logo is the cornerstone of your brand identity. We will develop a suite of logo assets to ensure versatility across all applications.

1.1. Primary Logo Design Specifications

  • Concept Direction: Will explore 3-5 distinct initial concepts based on discovery phase insights (e.g., modern, classic, abstract, illustrative, wordmark, logomark combination).
  • Deliverables:

* Main Logo: Full-color version, optimized for digital and print.

* Monochromatic Versions: Black and white versions for single-color applications.

* Reverse/Knockout Version: White logo on dark backgrounds.

  • File Formats:

* Vector: SVG, AI, EPS (for scalability without loss of quality).

* Raster: PNG (transparent background, various resolutions), JPG (web optimized).

  • Key Design Attributes:

* Scalability: Must be legible and impactful at various sizes (from favicon to billboard).

* Memorability: Unique and easily recognizable.

* Versatility: Adaptable to different media and backgrounds.

* Simplicity: Clean lines and minimal complexity for broad appeal.

1.2. Secondary Logo & Mark Variations

  • Concept: Development of alternative logo layouts or simplified marks for specific uses.
  • Deliverables:

* Stacked/Horizontal Variations: Adaptations of the primary logo for different aspect ratios.

* Icon/Favicon/App Icon: A simplified, recognizable graphic element derived from the main logo, optimized for small digital spaces.

* Monogram/Wordmark (if applicable): Text-only or initial-based versions.

  • File Formats: Same as Primary Logo (Vector and Raster).

1.3. Logo Usage Guidelines

  • Clear Space: Specification of minimum clear space around the logo to ensure visibility and impact.
  • Minimum Size: Defined minimum sizes for digital and print applications to maintain legibility.
  • Incorrect Usage: Examples of how not to use the logo (e.g., stretching, altering colors, adding effects, placing on busy backgrounds).
  • Background Compatibility: Recommendations for optimal logo placement on different background colors and images.

2. Color Palette

A carefully curated color palette evokes emotion and strengthens brand recognition.

2.1. Primary Color Palette

  • Purpose: Core brand colors used most frequently in all communications.
  • Specifications (for each primary color):

* HEX Code: #RRGGBB (for web and digital).

* RGB Values: R, G, B (for digital displays).

* CMYK Values: C, M, Y, K (for print production).

* Pantone Reference (if applicable): Specific spot color for critical brand elements in print.

* Color Name: Descriptive name (e.g., "PantheraHive Teal").

2.2. Secondary Color Palette

  • Purpose: Complementary colors used to add depth, highlight information, or differentiate content sections.
  • Specifications (for each secondary color): Same as Primary Color Palette.

2.3. Accent Color Palette

  • Purpose: Limited use colors for calls-to-action, highlights, or small graphic elements to draw attention.
  • Specifications (for each accent color): Same as Primary Color Palette.

2.4. Color Usage Guidelines

  • Hierarchy: Recommendations on the dominant, secondary, and accent color usage ratios.
  • Accessibility: Ensure sufficient contrast ratios (WCAG 2.1 AA or AAA) for text and interactive elements.
  • Emotional Association: Brief description of the feeling each color evokes and its strategic use.

3. Typography Guide

Typography plays a crucial role in conveying brand personality and ensuring readability.

3.1. Primary Headings Font

  • Purpose: Used for main titles, headlines, and prominent text.
  • Specifications:

* Font Family: (e.g., "Montserrat")

* Weights: Recommended weights (e.g., Bold, SemiBold, Regular).

* Style: Normal, Italic.

* Usage Examples: H1, H2, large display text.

* Licensing: Note on licensing requirements (e.g., Google Font, Adobe Font, Commercial License).

3.2. Secondary Headings Font

  • Purpose: Used for subheadings, smaller titles, and supporting textual elements.
  • Specifications: Same as Primary Headings Font.

3.3. Body Text Font

  • Purpose: Used for all paragraph text, long-form content, and general readability.
  • Specifications:

* Font Family: (e.g., "Open Sans")

* Weights: Recommended weights (e.g., Regular, Light).

* Style: Normal, Italic.

* Usage Examples: Paragraphs, captions, lists.

* Licensing: Note on licensing requirements.

3.4. Typography Usage Guidelines

  • Font Pairing Rules: How primary, secondary, and body fonts should be combined.
  • Sizing & Hierarchy: Recommended font sizes for different content levels (H1, H2, H3, Body, Caption) across digital and print.
  • Line Height (Leading): Optimal line spacing for readability.
  • Letter Spacing (Kerning/Tracking): Adjustments for improved legibility in headlines and body text.
  • Case Usage: Recommendations for uppercase, lowercase, title case, sentence case.

4. Brand Voice Guidelines

The brand voice defines how your brand communicates, creating a consistent personality and connection with your audience.

4.1. Tone of Voice

  • Description: Detailed explanation of the brand's overarching tone (e.g., "Professional yet Approachable," "Innovative and Forward-Thinking," "Empathetic and Trustworthy").
  • Key Attributes: List of 3-5 adjectives that define the brand's voice (e.g., Clear, Confident, Collaborative, Concise).

4.2. Messaging Principles

  • Core Values Reflected: How the brand's values are expressed through language.
  • Audience Connection: How the voice resonates with the target audience.
  • Key Message House: Identification of core messages and how to articulate them.

4.3. Do's and Don'ts

  • Examples of Appropriate Language: Phrases, word choices, and sentence structures that align with the brand voice.
  • Examples of Inappropriate Language: Phrases, jargon, or tones to avoid.
  • Grammar & Punctuation: Specific guidelines if applicable (e.g., Oxford comma usage, preferred contractions).

4.4. Example Applications

  • Headline Examples: Demonstrating the brand voice in catchy titles.
  • Call-to-Action Examples: How to encourage engagement using the brand's voice.
  • Customer Service Snippets: Guidance for consistent brand voice in customer interactions.

5. Social Media Style Guide

Ensuring a consistent look, feel, and voice across social platforms is critical for brand recognition and engagement.

5.1. Platform-Specific Guidelines

  • General Approach: Overall strategy for content and engagement across all platforms.
  • Channel-Specific Nuances: Tailored recommendations for visual and textual content on:

* Instagram: Visual storytelling, reel/story templates, grid aesthetic.

* Facebook: Community engagement, event promotion, longer-form captions.

* LinkedIn: Professional networking, thought leadership, company updates.

* X (formerly Twitter): Concise messaging, real-time engagement, hashtag strategy.

5.2. Visual Style (Image & Video)

  • Photography Style:

* Subject Matter: Types of images (e.g., product shots, lifestyle, behind-the-scenes).

* Composition: Framing, angles, focal points.

* Lighting: Preferred lighting conditions (e.g., natural, bright, dramatic).

* Color Grading/Filters: Specific color treatments or filter sets to maintain consistency.

  • Illustration/Graphic Style: If illustrations are used, define their style (e.g., flat, isometric, hand-drawn).
  • Video Style:

* Length: Recommended video durations for different platforms.

* Editing Style: Pacing, transitions, on-screen text overlays.

* Music/Sound: Tone and type of audio to use.

5.3. Social Media Templates

  • Wireframe Descriptions:

* Post Templates: Standardized layouts for image posts (e.g., square, portrait, landscape) including logo placement, text overlays, and graphic elements.

* Story Templates: Vertical layouts for Instagram/Facebook stories, including interactive elements (polls, questions) and brand elements.

* Cover Photo Templates: Guidelines for profile and cover photos on Facebook/LinkedIn.

* Ad Templates: Basic structural guidelines for paid social ads.

  • Deliverables: Basic wireframes/mockups for key templates, showing placeholder content and brand element integration.

5.4. Content & Copywriting Guidelines

  • Hashtag Strategy: Recommended branded hashtags, industry hashtags, and general hashtag usage.
  • Emoji Usage: Guidelines on when and how to use emojis.
  • Call-to-Action (CTA) Best Practices: How to phrase CTAs effectively for social media.
  • Engagement Guidelines: How to respond to comments and messages in the brand voice.

6. Overall Design Principles & UX Recommendations

These overarching principles ensure that the Brand Identity Kit is not only beautiful but also functional and easy for the customer to implement.

6.1. Consistency

  • Principle: Every touchpoint should reflect the brand identity uniformly.
  • Recommendation: The kit will provide clear, unambiguous rules and examples for all elements, minimizing ambiguity and ensuring easy adherence.

6.2. Accessibility

  • Principle: Brand assets should be usable and perceivable by the widest possible audience.
  • Recommendation: Color palettes will be checked for contrast ratios. Typography will prioritize readability. Digital assets will consider screen reader compatibility where applicable.

6.3. Scalability & Adaptability

  • Principle: The brand identity must perform effectively across diverse media and future applications.
  • Recommendation: Vector logos, flexible color palettes, and adaptable typography choices will be provided to ensure the brand can grow and evolve without compromising its core identity.

6.4. Ease of Implementation

  • Principle: The Brand Identity Kit should be a practical tool for the customer and their team.
  • Recommendation:

* Clear Documentation: All guidelines will be presented in a well-organized, easy-to-understand format.

* Asset Organization: Digital assets will be provided in clearly labeled folders with appropriate file types for various uses.

* Practical Examples: Real-world examples will demonstrate how to apply the guidelines effectively.

* User-Friendly Layout: The final Brand Identity Guidelines document will be designed for intuitive navigation and quick reference.


This comprehensive set of design specifications will serve as the blueprint for creating a robust and distinctive Brand Identity Kit, empowering your brand with a clear and compelling visual and verbal presence.

gemini Output

Brand Identity Kit: Final Design Assets - Aether Solutions

This document represents the complete and finalized Brand Identity Kit for Aether Solutions. It encompasses all essential elements required to establish a consistent, recognizable, and impactful brand presence across all touchpoints. This deliverable includes detailed specifications for logo usage, color palettes, typography, brand voice, and social media styling, alongside critical design and user experience recommendations.


1. Logo & Brand Mark

The Aether Solutions logo is designed to convey innovation, connectivity, and clarity. It features a modern, clean aesthetic that is both professional and forward-thinking.

1.1 Final Logo Presentation

Primary Logo:

  • Concept: A stylized "A" icon integrated with a clean, sans-serif wordmark. The icon subtly suggests connection points or data flow, representing solutions and integration.
  • Usage: Ideal for most applications where full brand recognition is desired (e.g., website headers, marketing materials, official documents).

Variations:

  • Stacked Logo: For vertical applications or when horizontal space is limited.
  • Icon-Only Mark: The "A" icon standalone, perfect for favicons, app icons, social media profiles, or as a subtle branding element.
  • Monochrome Logos:

* White-on-Color/Dark: For use on branded colors or dark backgrounds.

* Black-on-Light: For use on white or light backgrounds where color is not desired or available.

1.2 Logo Usage Guidelines

  • Clear Space: Maintain a minimum clear space around the logo equal to the height of the "A" in "Aether" (let's call this 'X'). No other graphics or text should intrude into this zone.
  • Minimum Size:

* Print: Primary Logo: 1 inch (25mm) width. Icon-Only Mark: 0.25 inch (6mm) width.

* Digital: Primary Logo: 100 pixels width. Icon-Only Mark: 32 pixels width.

  • Incorrect Usage (DO NOT):

* Stretch or distort the logo.

* Change the colors of the logo components.

* Rotate the logo.

* Add effects (shadows, gradients) not part of the original design.

* Place the logo on busy backgrounds that compromise visibility.

* Alter the proportions of the logo elements.


2. Color Palette

The Aether Solutions color palette is designed to evoke professionalism, trust, innovation, and a sense of calm.

2.1 Primary Colors

These are the core colors that define the Aether Solutions brand.

  • Aether Blue (Primary):

* Hex: #2A60A0

* RGB: 42, 96, 160

* CMYK: 74, 40, 0, 37

* Usage: Dominant color for headings, primary calls-to-action (CTAs), key graphical elements, and branding accents. Conveys trust, stability, and intelligence.

  • Aether Dark Grey (Primary Text):

* Hex: #333333

* RGB: 51, 51, 51

* CMYK: 0, 0, 0, 80

* Usage: Primary color for body text, subheadings, and crucial information. Ensures readability and a professional appearance.

2.2 Secondary Colors

Complementary colors that provide depth and versatility to the brand.

  • Aether Light Blue:

* Hex: #8DBADF

* RGB: 141, 186, 223

* CMYK: 37, 17, 0, 13

* Usage: Backgrounds, secondary graphical elements, subtle accents. Offers a lighter, more approachable feel.

  • Aether Teal:

* Hex: #4CAF9D

* RGB: 76, 175, 157

* CMYK: 57, 0, 10, 31

* Usage: Data visualization, infographics, elements requiring a fresh, modern touch. Symbolizes growth and innovation.

2.3 Accent Colors

Colors used sparingly to highlight important information or add visual interest.

  • Aether Orange (Highlight/Action):

* Hex: #FF9800

* RGB: 255, 152, 0

* CMYK: 0, 40, 100, 0

* Usage: Secondary CTAs, alerts, warnings, or elements needing high visibility. Conveys energy and urgency.

  • Aether Green (Success/Positive):

* Hex: #4CAF50

* RGB: 76, 175, 80

* CMYK: 57, 0, 100, 31

* Usage: Success messages, positive indicators, confirmations.

2.4 Neutral Colors

Foundation colors for backgrounds and supporting elements.

  • White:

* Hex: #FFFFFF

* RGB: 255, 255, 255

* Usage: Primary background, ensures clarity and space.

  • Light Grey:

* Hex: #F5F5F5

* RGB: 245, 245, 245

* Usage: Section dividers, subtle backgrounds, inactive states.

  • Medium Grey:

* Hex: #CCCCCC

* RGB: 204, 204, 204

* Usage: Borders, disabled elements, secondary text.

2.5 Color Usage Guidelines

  • Contrast: Ensure sufficient contrast between text and background colors for accessibility (WCAG AA standards, ideally AAA for critical text). Use tools like WebAIM Contrast Checker.
  • Hierarchy: Use primary colors for dominant elements, secondary for supporting, and accents for emphasis. Avoid overusing accent colors.
  • Consistency: Apply colors consistently across all brand materials to build recognition.

3. Typography Guide

Aether Solutions' typography is chosen for readability, modern appeal, and professional clarity.

3.1 Primary Typeface (Headings & Display)

  • Font Family: Montserrat
  • Usage: All headings (H1, H2, H3), subheadings, and prominent display text.
  • Weights:

* Bold (700): H1, H2

* Semi-Bold (600): H3, prominent callouts

* Medium (500): H4, specific UI elements

  • Rationale: Montserrat is a geometric sans-serif typeface that is clean, modern, and highly legible, reflecting Aether Solutions' forward-thinking and precise nature.

3.2 Secondary Typeface (Body Text)

  • Font Family: Open Sans
  • Usage: All body text, paragraphs, captions, and general informational text.
  • Weights:

* Regular (400): Standard body text

* Semi-Bold (600): Emphasis within body text, labels

* Light (300): Subtle text, disclaimers

  • Rationale: Open Sans is a humanist sans-serif typeface known for its excellent readability across various sizes and devices. It pairs well with Montserrat, providing a friendly yet professional contrast.

3.3 Typography Hierarchy & Sizing (Web Examples)

  • H1 (Page Title): Montserrat Bold, 48px, Line-height 1.2em, Color: Aether Dark Grey
  • H2 (Section Title): Montserrat Bold, 36px, Line-height 1.3em, Color: Aether Dark Grey
  • H3 (Sub-Section Title): Montserrat Semi-Bold, 28px, Line-height 1.4em, Color: Aether Dark Grey
  • H4 (Minor Heading): Montserrat Medium, 20px, Line-height 1.5em, Color: Aether Dark Grey
  • Body Text: Open Sans Regular, 16px, Line-height 1.6em, Color: Aether Dark Grey
  • Small Text/Captions: Open Sans Regular, 14px, Line-height 1.5em, Color: Medium Grey

3.4 Typography Usage Guidelines

  • Readability: Prioritize readability. Ensure sufficient line height, letter spacing, and contrast.
  • Consistency: Use specified fonts and weights consistently. Avoid mixing too many font families.
  • Responsive Sizing: Implement responsive typography for optimal viewing across different screen sizes (e.g., scale down heading sizes on mobile).
  • Kerning & Tracking: Default settings are generally sufficient, but adjust slightly for display text if necessary to improve visual balance.

4. Brand Voice Guidelines

The brand voice of Aether Solutions is designed to resonate with our target audience, building trust and conveying our core values.

4.1 Core Brand Personality Traits

  • Innovative: We embrace new ideas and cutting-edge solutions.
  • Reliable: We deliver consistent quality and trustworthy results.
  • Clear: We communicate complex ideas simply and effectively.
  • Empathetic: We understand our clients' challenges and work to solve them.
  • Professional: We maintain high standards in all interactions and deliverables.

4.2 Tone of Voice

  • Informative & Authoritative: We are experts in our field, providing valuable insights and clear guidance.
  • Confident, yet Approachable: We know our capabilities but remain open and easy to engage with.
  • Optimistic & Forward-Thinking: We focus on solutions and future possibilities.
  • Concise & Direct: We get straight to the point, avoiding jargon where possible.

4.3 Keywords & Phrases (DOs and DON'Ts)

  • DO Use:

* "Solutions," "Integrate," "Optimize," "Streamline," "Innovate," "Future-proof," "Seamless," "Empower," "Strategic," "Partnership."

* Active voice: "We develop..." "Aether Solutions provides..."

* Benefit-oriented language: "Achieve efficiency," "Enhance productivity."

  • DON'T Use:

* Overly technical jargon without explanation.

* Casual or overly informal language (e.g., slang, emojis in formal contexts).

* Negative or defeatist language.

* Passive voice: "Solutions are provided by us..."

4.4 Communication Scenarios

  • Website & Marketing Materials: Formal, informative, persuasive, benefit-driven.
  • Social Media: Informative, engaging, slightly more conversational, but still professional.
  • Customer Service: Empathetic, problem-solving, reassuring, clear.
  • Internal Communications: Direct, collaborative, motivational.

5. Design Specifications & UX Recommendations

These guidelines ensure that the Aether Solutions brand identity translates effectively into user-friendly and aesthetically pleasing digital and physical experiences.

5.1 General Design Principles

  • Clarity: Information should be easy to understand and digest.
  • Consistency: Maintain a uniform look and feel across all platforms.
  • Accessibility: Design with all users in mind, ensuring adequate contrast, legible text, and intuitive navigation.
  • Simplicity: Avoid clutter; prioritize essential elements and clean layouts.
  • Scalability: Designs should adapt gracefully to various screen sizes and contexts.

5.2 Layout & Grid System (Wireframe Principles)

  • Grid-Based Layout: Utilize a consistent 12-column grid system for web and digital interfaces to ensure alignment and responsiveness.
  • Whitespace: Generous use of whitespace (padding, margins) to create breathing room, improve readability, and highlight key content.
  • Modular Design: Break down content into logical, self-contained modules or components for better organization and reusability.
  • Visual Hierarchy: Use size, color, contrast, and positioning to guide the user's eye to the most important elements first.
  • Content-First Approach: Design layouts around the content, ensuring it is always the primary focus.

5.3 Iconography Style

  • Style: Line-based, minimalist, geometric, and consistent stroke weight.
  • Color: Aether Blue or Aether Dark Grey on light backgrounds; White on Aether Blue or dark backgrounds.
  • Usage: For UI elements, feature representations, and infographics. Avoid overly complex or cartoonish icons.

5.4 Imagery & Photography Style

  • Mood: Professional, clean, authentic, aspirational, and slightly futuristic.
  • Subjects:

* People: Diverse, engaged in collaborative work, focused on technology or problem-solving. Show genuine interaction.

* Technology/Abstract: Clean shots of modern tech, abstract representations of data, networks, or digital concepts.

* Environments: Modern, well-lit office spaces, collaborative settings, or clean architectural shots.

  • Editing Style: Bright, natural lighting, slightly desaturated colors (with Aether Blue as a subtle accent), sharp focus. Avoid heavy filters or overly dramatic effects. Use high-resolution images only.

5.5 Interactive Elements (UX Focus)

  • Buttons (CTAs):

* Primary: Solid Aether Blue background, white text (Montserrat Semi-Bold). Hover state: slightly darker Aether Blue. Active state: Aether Blue with subtle inner shadow.

* Secondary: White background, Aether Blue border, Aether Blue text. Hover state: Aether Light Blue background.

* Accent: Solid Aether Orange background, white text. Hover state: slightly darker Aether Orange.

* States: Ensure clear visual feedback for hover, active, focus, and disabled states.

  • Form Fields: Clean, simple input fields with a light grey border. Focus state: Aether Blue border. Error state: Aether Orange border with accompanying error message.
  • Navigation: Clear, intuitive navigation using Montserrat or Open Sans. Current page/active state highlighted with Aether Blue.
  • Feedback/Notifications:

* Success: Aether Green background, white text.

* Warning: Aether Orange background, white text.

* Error: Red (specific error red, e.g., #D32F2F) background, white text.

brand_identity_kit.md
Download as Markdown
Copy all content
Full output as text
Download ZIP
IDE-ready project ZIP
Copy share link
Permanent URL for this run
Get Embed Code
Embed this result on any website
Print / Save PDF
Use browser print dialog
\n\n\n"); var hasSrcMain=Object.keys(extracted).some(function(k){return k.indexOf("src/main")>=0;}); if(!hasSrcMain) zip.file(folder+"src/main."+ext,"import React from 'react'\nimport ReactDOM from 'react-dom/client'\nimport App from './App'\nimport './index.css'\n\nReactDOM.createRoot(document.getElementById('root')!).render(\n \n \n \n)\n"); var hasSrcApp=Object.keys(extracted).some(function(k){return k==="src/App."+ext||k==="App."+ext;}); if(!hasSrcApp) zip.file(folder+"src/App."+ext,"import React from 'react'\nimport './App.css'\n\nfunction App(){\n return(\n
\n
\n

"+slugTitle(pn)+"

\n

Built with PantheraHive BOS

\n
\n
\n )\n}\nexport default App\n"); zip.file(folder+"src/index.css","*{margin:0;padding:0;box-sizing:border-box}\nbody{font-family:system-ui,-apple-system,sans-serif;background:#f0f2f5;color:#1a1a2e}\n.app{min-height:100vh;display:flex;flex-direction:column}\n.app-header{flex:1;display:flex;flex-direction:column;align-items:center;justify-content:center;gap:12px;padding:40px}\nh1{font-size:2.5rem;font-weight:700}\n"); zip.file(folder+"src/App.css",""); zip.file(folder+"src/components/.gitkeep",""); zip.file(folder+"src/pages/.gitkeep",""); zip.file(folder+"src/hooks/.gitkeep",""); Object.keys(extracted).forEach(function(p){ var fp=p.startsWith("src/")?p:"src/"+p; zip.file(folder+fp,extracted[p]); }); zip.file(folder+"README.md","# "+slugTitle(pn)+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\nnpm install\nnpm run dev\n\`\`\`\n\n## Build\n\`\`\`bash\nnpm run build\n\`\`\`\n\n## Open in IDE\nOpen the project folder in VS Code or WebStorm.\n"); zip.file(folder+".gitignore","node_modules/\ndist/\n.env\n.DS_Store\n*.local\n"); } /* --- Vue (Vite + Composition API + TypeScript) --- */ function buildVue(zip,folder,app,code,panelTxt){ var pn=pkgName(app); var C=cc(pn); var extracted=extractCode(panelTxt); zip.file(folder+"package.json",'{\n "name": "'+pn+'",\n "version": "0.0.0",\n "type": "module",\n "scripts": {\n "dev": "vite",\n "build": "vue-tsc -b && vite build",\n "preview": "vite preview"\n },\n "dependencies": {\n "vue": "^3.5.13",\n "vue-router": "^4.4.5",\n "pinia": "^2.3.0",\n "axios": "^1.7.9"\n },\n "devDependencies": {\n "@vitejs/plugin-vue": "^5.2.1",\n "typescript": "~5.7.3",\n "vite": "^6.0.5",\n "vue-tsc": "^2.2.0"\n }\n}\n'); zip.file(folder+"vite.config.ts","import { defineConfig } from 'vite'\nimport vue from '@vitejs/plugin-vue'\nimport { resolve } from 'path'\n\nexport default defineConfig({\n plugins: [vue()],\n resolve: { alias: { '@': resolve(__dirname,'src') } }\n})\n"); zip.file(folder+"tsconfig.json",'{"files":[],"references":[{"path":"./tsconfig.app.json"},{"path":"./tsconfig.node.json"}]}\n'); zip.file(folder+"tsconfig.app.json",'{\n "compilerOptions":{\n "target":"ES2020","useDefineForClassFields":true,"module":"ESNext","lib":["ES2020","DOM","DOM.Iterable"],\n "skipLibCheck":true,"moduleResolution":"bundler","allowImportingTsExtensions":true,\n "isolatedModules":true,"moduleDetection":"force","noEmit":true,"jsxImportSource":"vue",\n "strict":true,"paths":{"@/*":["./src/*"]}\n },\n "include":["src/**/*.ts","src/**/*.d.ts","src/**/*.tsx","src/**/*.vue"]\n}\n'); zip.file(folder+"env.d.ts","/// \n"); zip.file(folder+"index.html","\n\n\n \n \n "+slugTitle(pn)+"\n\n\n
\n \n\n\n"); var hasMain=Object.keys(extracted).some(function(k){return k==="src/main.ts"||k==="main.ts";}); if(!hasMain) zip.file(folder+"src/main.ts","import { createApp } from 'vue'\nimport { createPinia } from 'pinia'\nimport App from './App.vue'\nimport './assets/main.css'\n\nconst app = createApp(App)\napp.use(createPinia())\napp.mount('#app')\n"); var hasApp=Object.keys(extracted).some(function(k){return k.indexOf("App.vue")>=0;}); if(!hasApp) zip.file(folder+"src/App.vue","\n\n\n\n\n"); zip.file(folder+"src/assets/main.css","*{margin:0;padding:0;box-sizing:border-box}body{font-family:system-ui,sans-serif;background:#fff;color:#213547}\n"); zip.file(folder+"src/components/.gitkeep",""); zip.file(folder+"src/views/.gitkeep",""); zip.file(folder+"src/stores/.gitkeep",""); Object.keys(extracted).forEach(function(p){ var fp=p.startsWith("src/")?p:"src/"+p; zip.file(folder+fp,extracted[p]); }); zip.file(folder+"README.md","# "+slugTitle(pn)+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\nnpm install\nnpm run dev\n\`\`\`\n\n## Build\n\`\`\`bash\nnpm run build\n\`\`\`\n\nOpen in VS Code or WebStorm.\n"); zip.file(folder+".gitignore","node_modules/\ndist/\n.env\n.DS_Store\n*.local\n"); } /* --- Angular (v19 standalone) --- */ function buildAngular(zip,folder,app,code,panelTxt){ var pn=pkgName(app); var C=cc(pn); var sel=pn.replace(/_/g,"-"); var extracted=extractCode(panelTxt); zip.file(folder+"package.json",'{\n "name": "'+pn+'",\n "version": "0.0.0",\n "scripts": {\n "ng": "ng",\n "start": "ng serve",\n "build": "ng build",\n "test": "ng test"\n },\n "dependencies": {\n "@angular/animations": "^19.0.0",\n "@angular/common": "^19.0.0",\n "@angular/compiler": "^19.0.0",\n "@angular/core": "^19.0.0",\n "@angular/forms": "^19.0.0",\n "@angular/platform-browser": "^19.0.0",\n "@angular/platform-browser-dynamic": "^19.0.0",\n "@angular/router": "^19.0.0",\n "rxjs": "~7.8.0",\n "tslib": "^2.3.0",\n "zone.js": "~0.15.0"\n },\n "devDependencies": {\n "@angular-devkit/build-angular": "^19.0.0",\n "@angular/cli": "^19.0.0",\n "@angular/compiler-cli": "^19.0.0",\n "typescript": "~5.6.0"\n }\n}\n'); zip.file(folder+"angular.json",'{\n "$schema": "./node_modules/@angular/cli/lib/config/schema.json",\n "version": 1,\n "newProjectRoot": "projects",\n "projects": {\n "'+pn+'": {\n "projectType": "application",\n "root": "",\n "sourceRoot": "src",\n "prefix": "app",\n "architect": {\n "build": {\n "builder": "@angular-devkit/build-angular:application",\n "options": {\n "outputPath": "dist/'+pn+'",\n "index": "src/index.html",\n "browser": "src/main.ts",\n "tsConfig": "tsconfig.app.json",\n "styles": ["src/styles.css"],\n "scripts": []\n }\n },\n "serve": {"builder":"@angular-devkit/build-angular:dev-server","configurations":{"production":{"buildTarget":"'+pn+':build:production"},"development":{"buildTarget":"'+pn+':build:development"}},"defaultConfiguration":"development"}\n }\n }\n }\n}\n'); zip.file(folder+"tsconfig.json",'{\n "compileOnSave": false,\n "compilerOptions": {"baseUrl":"./","outDir":"./dist/out-tsc","forceConsistentCasingInFileNames":true,"strict":true,"noImplicitOverride":true,"noPropertyAccessFromIndexSignature":true,"noImplicitReturns":true,"noFallthroughCasesInSwitch":true,"paths":{"@/*":["src/*"]},"skipLibCheck":true,"esModuleInterop":true,"sourceMap":true,"declaration":false,"experimentalDecorators":true,"moduleResolution":"bundler","importHelpers":true,"target":"ES2022","module":"ES2022","useDefineForClassFields":false,"lib":["ES2022","dom"]},\n "references":[{"path":"./tsconfig.app.json"}]\n}\n'); zip.file(folder+"tsconfig.app.json",'{\n "extends":"./tsconfig.json",\n "compilerOptions":{"outDir":"./dist/out-tsc","types":[]},\n "files":["src/main.ts"],\n "include":["src/**/*.d.ts"]\n}\n'); zip.file(folder+"src/index.html","\n\n\n \n "+slugTitle(pn)+"\n \n \n \n\n\n \n\n\n"); zip.file(folder+"src/main.ts","import { bootstrapApplication } from '@angular/platform-browser';\nimport { appConfig } from './app/app.config';\nimport { AppComponent } from './app/app.component';\n\nbootstrapApplication(AppComponent, appConfig)\n .catch(err => console.error(err));\n"); zip.file(folder+"src/styles.css","* { margin: 0; padding: 0; box-sizing: border-box; }\nbody { font-family: system-ui, -apple-system, sans-serif; background: #f9fafb; color: #111827; }\n"); var hasComp=Object.keys(extracted).some(function(k){return k.indexOf("app.component")>=0;}); if(!hasComp){ zip.file(folder+"src/app/app.component.ts","import { Component } from '@angular/core';\nimport { RouterOutlet } from '@angular/router';\n\n@Component({\n selector: 'app-root',\n standalone: true,\n imports: [RouterOutlet],\n templateUrl: './app.component.html',\n styleUrl: './app.component.css'\n})\nexport class AppComponent {\n title = '"+pn+"';\n}\n"); zip.file(folder+"src/app/app.component.html","
\n
\n

"+slugTitle(pn)+"

\n

Built with PantheraHive BOS

\n
\n \n
\n"); zip.file(folder+"src/app/app.component.css",".app-header{display:flex;flex-direction:column;align-items:center;justify-content:center;min-height:60vh;gap:16px}h1{font-size:2.5rem;font-weight:700;color:#6366f1}\n"); } zip.file(folder+"src/app/app.config.ts","import { ApplicationConfig, provideZoneChangeDetection } from '@angular/core';\nimport { provideRouter } from '@angular/router';\nimport { routes } from './app.routes';\n\nexport const appConfig: ApplicationConfig = {\n providers: [\n provideZoneChangeDetection({ eventCoalescing: true }),\n provideRouter(routes)\n ]\n};\n"); zip.file(folder+"src/app/app.routes.ts","import { Routes } from '@angular/router';\n\nexport const routes: Routes = [];\n"); Object.keys(extracted).forEach(function(p){ var fp=p.startsWith("src/")?p:"src/"+p; zip.file(folder+fp,extracted[p]); }); zip.file(folder+"README.md","# "+slugTitle(pn)+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\nnpm install\nng serve\n# or: npm start\n\`\`\`\n\n## Build\n\`\`\`bash\nng build\n\`\`\`\n\nOpen in VS Code with Angular Language Service extension.\n"); zip.file(folder+".gitignore","node_modules/\ndist/\n.env\n.DS_Store\n*.local\n.angular/\n"); } /* --- Python --- */ function buildPython(zip,folder,app,code){ var title=slugTitle(app); var pn=pkgName(app); var src=code.replace(/^\`\`\`[\w]*\n?/m,"").replace(/\n?\`\`\`$/m,"").trim(); var reqMap={"numpy":"numpy","pandas":"pandas","sklearn":"scikit-learn","tensorflow":"tensorflow","torch":"torch","flask":"flask","fastapi":"fastapi","uvicorn":"uvicorn","requests":"requests","sqlalchemy":"sqlalchemy","pydantic":"pydantic","dotenv":"python-dotenv","PIL":"Pillow","cv2":"opencv-python","matplotlib":"matplotlib","seaborn":"seaborn","scipy":"scipy"}; var reqs=[]; Object.keys(reqMap).forEach(function(k){if(src.indexOf("import "+k)>=0||src.indexOf("from "+k)>=0)reqs.push(reqMap[k]);}); var reqsTxt=reqs.length?reqs.join("\n"):"# add dependencies here\n"; zip.file(folder+"main.py",src||"# "+title+"\n# Generated by PantheraHive BOS\n\nprint(title+\" loaded\")\n"); zip.file(folder+"requirements.txt",reqsTxt); zip.file(folder+".env.example","# Environment variables\n"); zip.file(folder+"README.md","# "+title+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\npython3 -m venv .venv\nsource .venv/bin/activate\npip install -r requirements.txt\n\`\`\`\n\n## Run\n\`\`\`bash\npython main.py\n\`\`\`\n"); zip.file(folder+".gitignore",".venv/\n__pycache__/\n*.pyc\n.env\n.DS_Store\n"); } /* --- Node.js --- */ function buildNode(zip,folder,app,code){ var title=slugTitle(app); var pn=pkgName(app); var src=code.replace(/^\`\`\`[\w]*\n?/m,"").replace(/\n?\`\`\`$/m,"").trim(); var depMap={"mongoose":"^8.0.0","dotenv":"^16.4.5","axios":"^1.7.9","cors":"^2.8.5","bcryptjs":"^2.4.3","jsonwebtoken":"^9.0.2","socket.io":"^4.7.4","uuid":"^9.0.1","zod":"^3.22.4","express":"^4.18.2"}; var deps={}; Object.keys(depMap).forEach(function(k){if(src.indexOf(k)>=0)deps[k]=depMap[k];}); if(!deps["express"])deps["express"]="^4.18.2"; var pkgJson=JSON.stringify({"name":pn,"version":"1.0.0","main":"src/index.js","scripts":{"start":"node src/index.js","dev":"nodemon src/index.js"},"dependencies":deps,"devDependencies":{"nodemon":"^3.0.3"}},null,2)+"\n"; zip.file(folder+"package.json",pkgJson); var fallback="const express=require(\"express\");\nconst app=express();\napp.use(express.json());\n\napp.get(\"/\",(req,res)=>{\n res.json({message:\""+title+" API\"});\n});\n\nconst PORT=process.env.PORT||3000;\napp.listen(PORT,()=>console.log(\"Server on port \"+PORT));\n"; zip.file(folder+"src/index.js",src||fallback); zip.file(folder+".env.example","PORT=3000\n"); zip.file(folder+".gitignore","node_modules/\n.env\n.DS_Store\n"); zip.file(folder+"README.md","# "+title+"\n\nGenerated by PantheraHive BOS.\n\n## Setup\n\`\`\`bash\nnpm install\n\`\`\`\n\n## Run\n\`\`\`bash\nnpm run dev\n\`\`\`\n"); } /* --- Vanilla HTML --- */ function buildVanillaHtml(zip,folder,app,code){ var title=slugTitle(app); var isFullDoc=code.trim().toLowerCase().indexOf("=0||code.trim().toLowerCase().indexOf("=0; var indexHtml=isFullDoc?code:"\n\n\n\n\n"+title+"\n\n\n\n"+code+"\n\n\n\n"; zip.file(folder+"index.html",indexHtml); zip.file(folder+"style.css","/* "+title+" — styles */\n*{margin:0;padding:0;box-sizing:border-box}\nbody{font-family:system-ui,-apple-system,sans-serif;background:#fff;color:#1a1a2e}\n"); zip.file(folder+"script.js","/* "+title+" — scripts */\n"); zip.file(folder+"assets/.gitkeep",""); zip.file(folder+"README.md","# "+title+"\n\nGenerated by PantheraHive BOS.\n\n## Open\nDouble-click \`index.html\` in your browser.\n\nOr serve locally:\n\`\`\`bash\nnpx serve .\n# or\npython3 -m http.server 3000\n\`\`\`\n"); zip.file(folder+".gitignore",".DS_Store\nnode_modules/\n.env\n"); } /* ===== MAIN ===== */ var sc=document.createElement("script"); sc.src="https://cdnjs.cloudflare.com/ajax/libs/jszip/3.10.1/jszip.min.js"; sc.onerror=function(){ if(lbl)lbl.textContent="Download ZIP"; alert("JSZip load failed — check connection."); }; sc.onload=function(){ var zip=new JSZip(); var base=(_phFname||"output").replace(/\.[^.]+$/,""); var app=base.toLowerCase().replace(/[^a-z0-9]+/g,"_").replace(/^_+|_+$/g,"")||"my_app"; var folder=app+"/"; var vc=document.getElementById("panel-content"); var panelTxt=vc?(vc.innerText||vc.textContent||""):""; var lang=detectLang(_phCode,panelTxt); if(_phIsHtml){ buildVanillaHtml(zip,folder,app,_phCode); } else if(lang==="flutter"){ buildFlutter(zip,folder,app,_phCode,panelTxt); } else if(lang==="react-native"){ buildReactNative(zip,folder,app,_phCode,panelTxt); } else if(lang==="swift"){ buildSwift(zip,folder,app,_phCode,panelTxt); } else if(lang==="kotlin"){ buildKotlin(zip,folder,app,_phCode,panelTxt); } else if(lang==="react"){ buildReact(zip,folder,app,_phCode,panelTxt); } else if(lang==="vue"){ buildVue(zip,folder,app,_phCode,panelTxt); } else if(lang==="angular"){ buildAngular(zip,folder,app,_phCode,panelTxt); } else if(lang==="python"){ buildPython(zip,folder,app,_phCode); } else if(lang==="node"){ buildNode(zip,folder,app,_phCode); } else { /* Document/content workflow */ var title=app.replace(/_/g," "); var md=_phAll||_phCode||panelTxt||"No content"; zip.file(folder+app+".md",md); var h=""+title+""; h+="

"+title+"

"; var hc=md.replace(/&/g,"&").replace(//g,">"); hc=hc.replace(/^### (.+)$/gm,"

$1

"); hc=hc.replace(/^## (.+)$/gm,"

$1

"); hc=hc.replace(/^# (.+)$/gm,"

$1

"); hc=hc.replace(/\*\*(.+?)\*\*/g,"$1"); hc=hc.replace(/\n{2,}/g,"

"); h+="

"+hc+"

Generated by PantheraHive BOS
"; zip.file(folder+app+".html",h); zip.file(folder+"README.md","# "+title+"\n\nGenerated by PantheraHive BOS.\n\nFiles:\n- "+app+".md (Markdown)\n- "+app+".html (styled HTML)\n"); } zip.generateAsync({type:"blob"}).then(function(blob){ var a=document.createElement("a"); a.href=URL.createObjectURL(blob); a.download=app+".zip"; a.click(); URL.revokeObjectURL(a.href); if(lbl)lbl.textContent="Download ZIP"; }); }; document.head.appendChild(sc); } function phShare(){navigator.clipboard.writeText(window.location.href).then(function(){var el=document.getElementById("ph-share-lbl");if(el){el.textContent="Link copied!";setTimeout(function(){el.textContent="Copy share link";},2500);}});}function phEmbed(){var runId=window.location.pathname.split("/").pop().replace(".html","");var embedUrl="https://pantherahive.com/embed/"+runId;var code='';navigator.clipboard.writeText(code).then(function(){var el=document.getElementById("ph-embed-lbl");if(el){el.textContent="Embed code copied!";setTimeout(function(){el.textContent="Get Embed Code";},2500);}});}