Skip to content

Create New Ingredient

Before You Start

  • Do you have permission? You need to be a member of your project with power-user access rights to create ingredients. If you can't see the "Add new Ingredient" button, contact your project administrator.

  • Do you need a new ingredient? Check if your ingredient already exists in the feed. You only need to create a new ingredient if this is a completely new ingredient, not just a new version of an existing one.

How to Create an Ingredient

  1. Navigate to your feed - Go to your project and select the appropriate feed
  2. Click "Add new Ingredient" - Look for the blue button in the top-right area
  3. Fill out the form - Complete the required information in the side panel
  4. Submit - Click "Add to feed" when ready

Feed view

Filling Out the Form

New ingredient form

New ingredient form

Step 1: Basic Information

Ingredient Name (Required)

  • Choose a clear, descriptive name for your ingredient
  • Must be unique within your current feed (you can use the same name in different feeds)
  • Use only letters, numbers, hyphens (-), and underscores (_)
  • No spaces or special characters
  • 1-30 characters long
  • Important: You cannot change this name later

Examples: "BIOS_NVL", "WiFi_Driver_AX211", "Platform_KIT_PTL"

Official Ingredient

  • Turn this on if this is your team's official ingredient (not experimental)
  • Gives your ingredient a special badge so others know it's the official version
  • You can change this setting anytime

Family (Required)

  • Choose the category that best describes your component:
    • Firmware: BIOS, *code, IFWI, patches, microcode
    • Software: Drivers, tools, applications
    • Platform: Platform KITs
    • Other: Anything that doesn't fit the above categories

Type (Required)

  • Select the specific type of component (this list changes based on your Family choice)
  • Examples: If you chose "Firmware" family, you might see BIOS, IFWI, ACODE, etc.
  • Important: You cannot change this after creation

Step 2: Additional Information (All Optional)

Description

  • Add details about what this ingredient does
  • Helpful for others who might want to use your component
  • Maximum 250 characters

Validation Discipline

  • Select if your ingredient is associated with a specific validation team:
    • FV: Functional Validation
    • PIV: Platform Integration & Validation
    • PTP: Power Thermal Performance
    • EV: Electrical Validation
    • FIV: Firmware Integration & Validation
    • CORE: CORE Validation
    • RTFS: Runtime Fleet Stability

Step 3: Silicon Information (Optional)

Is this silicon-specific?

  • Turn this on if your ingredient is designed for a specific silicon
  • When enabled, you can specify which silicon, step, segment, and milestones

Silicon Family (If silicon-specific)

  • Choose the silicon family your ingredient targets
  • Examples: PTL (Panther Lake), DMR (Diamond Rapids)

Step, Segment, Milestone (If silicon selected)

  • Choose the appropriate values for your silicon
  • These help organize and track your ingredient through the development process
  • You can select multiple milestones

Step 4: Release Settings

These settings control how future versions of your ingredient will behave:

Will have dependencies

  • Turn this on if your ingredient includes or relies on other components
  • Example: An IFWI that contains multiple *ingredients has dependencies
  • When you create releases later, the system will ask you to specify these dependencies

Will have a package

  • Turn this on if your ingredient includes files that users need to download
  • Example: A driver package with installation files
  • When you create releases later, you'll be required to upload the files

After Creation

Once you click "Add to feed":

  • Your ingredient appears in the feed list immediately
  • You'll see a success message with an option to view your ingredient
  • You can start creating releases (versions) of your ingredient
  • You can edit most settings except the name, family, and type

What You Can Change Later

  • Description
  • Official status
  • Validation discipline
  • Silicon information
  • Release settings (dependencies and packages)

What You Cannot Change

  • Ingredient name
  • Family
  • Type

These are permanent because they affect how the system handles your ingredient and changing them could break existing integrations.

Tips for Success

  • Choose names carefully - Since you can't change the name later, pick something that will make sense long-term

  • Use descriptive names - Include silicon, variant, or purpose information to avoid confusion

  • Consider the future - Think about whether you'll need dependencies or packages when setting up release settings

  • When in doubt, ask - Contact VDC support team if you're unsure about family, type, or silicon selections

Need Help?

  • Can't find your silicon/type? Contact VDC support team to request additions
  • Not sure about classification? Ask your team lead or Contact VDC support team
  • Permission issues? Contact your project administrator
  • Technical problems? Use the support contact link in VDC

What's Next?

After creating your ingredient, you'll typically want to:

  1. Create your first release - Upload the actual files and metadata
  2. Set up workflows - Automate building and testing (if applicable)
  3. Share with your team - Let others know your ingredient is available