Symfony Profiler

[
  "product" => App\Entity\Product\Product {#7310
    #id: 11218
    #code: "IEEE00005753"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039554 {#7274
      date: 2025-06-27 17:52:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39881
        #name: "IEEE/ISO/IEC 26531:2015"
        #slug: "ieee-iso-iec-26531-2015-ieee00005753-242870"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This International Standard provides requirements for the management of the content used in product life cycle, software, and service management system documentation. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports the reuse of content objects among deliverables and supports multiple deliverable formats. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. The standard defines the characteristics of an effective and efficient process through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. The standard includes business case considerations for acquisition of a content management system. This International Standard is independent of the software tools and markup languages that may be used to manage documentation content, and applies to both printed documentation and on-screen documentation.<br />\n
          \t\t\t\t<br />\n
          This standard states requirements for efficient development and management of content produced throughout the life-cycle of a system and software product; for the provision of user documentation for systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content to be managed with this standard includes user information such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product; product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports; service management items such as service-level agreements, records, policies, procedures, and other documents. The purpose of this standard is to define a process for content management and the requirements of a component content management system through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents. The intended users of this International Standard are managers and developers of information (technical documentation) and acquirers and suppliers of content management systems. Any organization that develops content, regardless of size, can benefit from maintaining an effective content management solution and following best practices for the development and management of technical content. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This standard is not a management system standard. The content management process presented in clauses 6 through 11 of this International Standard is a specialization (lower-level process) of the Information Management process required in ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard for Systems and software engineering -- Content management for product life-cycle, user, and service management documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1679868000 {#7292
      date: 2023-03-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#93066
  +product: App\Entity\Product\Product {#7310
    #id: 11218
    #code: "IEEE00005753"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039554 {#7274
      date: 2025-06-27 17:52:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39881
        #name: "IEEE/ISO/IEC 26531:2015"
        #slug: "ieee-iso-iec-26531-2015-ieee00005753-242870"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This International Standard provides requirements for the management of the content used in product life cycle, software, and service management system documentation. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports the reuse of content objects among deliverables and supports multiple deliverable formats. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. The standard defines the characteristics of an effective and efficient process through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. The standard includes business case considerations for acquisition of a content management system. This International Standard is independent of the software tools and markup languages that may be used to manage documentation content, and applies to both printed documentation and on-screen documentation.<br />\n
          \t\t\t\t<br />\n
          This standard states requirements for efficient development and management of content produced throughout the life-cycle of a system and software product; for the provision of user documentation for systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content to be managed with this standard includes user information such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product; product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports; service management items such as service-level agreements, records, policies, procedures, and other documents. The purpose of this standard is to define a process for content management and the requirements of a component content management system through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents. The intended users of this International Standard are managers and developers of information (technical documentation) and acquirers and suppliers of content management systems. Any organization that develops content, regardless of size, can benefit from maintaining an effective content management solution and following best practices for the development and management of technical content. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This standard is not a management system standard. The content management process presented in clauses 6 through 11 of this International Standard is a specialization (lower-level process) of the Information Management process required in ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard for Systems and software engineering -- Content management for product life-cycle, user, and service management documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1679868000 {#7292
      date: 2023-03-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 11218
    #code: "IEEE00005753"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039554 {#7274
      date: 2025-06-27 17:52:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39881
        #name: "IEEE/ISO/IEC 26531:2015"
        #slug: "ieee-iso-iec-26531-2015-ieee00005753-242870"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This International Standard provides requirements for the management of the content used in product life cycle, software, and service management system documentation. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports the reuse of content objects among deliverables and supports multiple deliverable formats. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. The standard defines the characteristics of an effective and efficient process through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. The standard includes business case considerations for acquisition of a content management system. This International Standard is independent of the software tools and markup languages that may be used to manage documentation content, and applies to both printed documentation and on-screen documentation.<br />\n
          \t\t\t\t<br />\n
          This standard states requirements for efficient development and management of content produced throughout the life-cycle of a system and software product; for the provision of user documentation for systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content to be managed with this standard includes user information such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product; product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports; service management items such as service-level agreements, records, policies, procedures, and other documents. The purpose of this standard is to define a process for content management and the requirements of a component content management system through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents. The intended users of this International Standard are managers and developers of information (technical documentation) and acquirers and suppliers of content management systems. Any organization that develops content, regardless of size, can benefit from maintaining an effective content management solution and following best practices for the development and management of technical content. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This standard is not a management system standard. The content management process presented in clauses 6 through 11 of this International Standard is a specialization (lower-level process) of the Information Management process required in ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard for Systems and software engineering -- Content management for product life-cycle, user, and service management documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1679868000 {#7292
      date: 2023-03-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductType {#93246
  +product: App\Entity\Product\Product {#7310
    #id: 11218
    #code: "IEEE00005753"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039554 {#7274
      date: 2025-06-27 17:52:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39881
        #name: "IEEE/ISO/IEC 26531:2015"
        #slug: "ieee-iso-iec-26531-2015-ieee00005753-242870"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This International Standard provides requirements for the management of the content used in product life cycle, software, and service management system documentation. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports the reuse of content objects among deliverables and supports multiple deliverable formats. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. The standard defines the characteristics of an effective and efficient process through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. The standard includes business case considerations for acquisition of a content management system. This International Standard is independent of the software tools and markup languages that may be used to manage documentation content, and applies to both printed documentation and on-screen documentation.<br />\n
          \t\t\t\t<br />\n
          This standard states requirements for efficient development and management of content produced throughout the life-cycle of a system and software product; for the provision of user documentation for systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content to be managed with this standard includes user information such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product; product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports; service management items such as service-level agreements, records, policies, procedures, and other documents. The purpose of this standard is to define a process for content management and the requirements of a component content management system through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents. The intended users of this International Standard are managers and developers of information (technical documentation) and acquirers and suppliers of content management systems. Any organization that develops content, regardless of size, can benefit from maintaining an effective content management solution and following best practices for the development and management of technical content. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This standard is not a management system standard. The content management process presented in clauses 6 through 11 of this International Standard is a specialization (lower-level process) of the Information Management process required in ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard for Systems and software engineering -- Content management for product life-cycle, user, and service management documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1679868000 {#7292
      date: 2023-03-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Standard"
  -typeAttributeCode: "type"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 11218
    #code: "IEEE00005753"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039554 {#7274
      date: 2025-06-27 17:52:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39881
        #name: "IEEE/ISO/IEC 26531:2015"
        #slug: "ieee-iso-iec-26531-2015-ieee00005753-242870"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This International Standard provides requirements for the management of the content used in product life cycle, software, and service management system documentation. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports the reuse of content objects among deliverables and supports multiple deliverable formats. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. The standard defines the characteristics of an effective and efficient process through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. The standard includes business case considerations for acquisition of a content management system. This International Standard is independent of the software tools and markup languages that may be used to manage documentation content, and applies to both printed documentation and on-screen documentation.<br />\n
          \t\t\t\t<br />\n
          This standard states requirements for efficient development and management of content produced throughout the life-cycle of a system and software product; for the provision of user documentation for systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content to be managed with this standard includes user information such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product; product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports; service management items such as service-level agreements, records, policies, procedures, and other documents. The purpose of this standard is to define a process for content management and the requirements of a component content management system through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents. The intended users of this International Standard are managers and developers of information (technical documentation) and acquirers and suppliers of content management systems. Any organization that develops content, regardless of size, can benefit from maintaining an effective content management solution and following best practices for the development and management of technical content. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This standard is not a management system standard. The content management process presented in clauses 6 through 11 of this International Standard is a specialization (lower-level process) of the Information Management process required in ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard for Systems and software engineering -- Content management for product life-cycle, user, and service management documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1679868000 {#7292
      date: 2023-03-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductMostRecent {#93321
  +product: App\Entity\Product\Product {#7310
    #id: 11218
    #code: "IEEE00005753"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039554 {#7274
      date: 2025-06-27 17:52:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39881
        #name: "IEEE/ISO/IEC 26531:2015"
        #slug: "ieee-iso-iec-26531-2015-ieee00005753-242870"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This International Standard provides requirements for the management of the content used in product life cycle, software, and service management system documentation. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports the reuse of content objects among deliverables and supports multiple deliverable formats. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. The standard defines the characteristics of an effective and efficient process through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. The standard includes business case considerations for acquisition of a content management system. This International Standard is independent of the software tools and markup languages that may be used to manage documentation content, and applies to both printed documentation and on-screen documentation.<br />\n
          \t\t\t\t<br />\n
          This standard states requirements for efficient development and management of content produced throughout the life-cycle of a system and software product; for the provision of user documentation for systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content to be managed with this standard includes user information such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product; product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports; service management items such as service-level agreements, records, policies, procedures, and other documents. The purpose of this standard is to define a process for content management and the requirements of a component content management system through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents. The intended users of this International Standard are managers and developers of information (technical documentation) and acquirers and suppliers of content management systems. Any organization that develops content, regardless of size, can benefit from maintaining an effective content management solution and following best practices for the development and management of technical content. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This standard is not a management system standard. The content management process presented in clauses 6 through 11 of this International Standard is a specialization (lower-level process) of the Information Management process required in ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard for Systems and software engineering -- Content management for product life-cycle, user, and service management documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1679868000 {#7292
      date: 2023-03-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93734
    #id: 12861
    #code: "IEEE00010824"
    #attributes: Doctrine\ORM\PersistentCollection {#93716 …}
    #variants: Doctrine\ORM\PersistentCollection {#93713 …}
    #options: Doctrine\ORM\PersistentCollection {#93709 …}
    #associations: Doctrine\ORM\PersistentCollection {#93711 …}
    #createdAt: DateTime @1751040707 {#93742
      date: 2025-06-27 18:11:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#93721
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93727 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93762
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93734}
        #id: 46453
        #name: "IEEE/ISO/IEC 26531:2023"
        #slug: "ieee-iso-iec-26531-2023-ieee00010824-244519"
        #description: """
          Revision Standard - Active.<br />\n
          This document provides requirements for the management of the content used in product life cycle, software, and service management system information for users. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports multiple deliverable formats and the reuse of content objects among deliverables. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This document defines the characteristics of an effective and efficient process through which content is gathered, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or other content published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this document can fulfil business needs for content development and management, especially the need for a single source of authoritative information. This document includes business case considerations for acquisition of a content management system. This document is independent of the software tools and markup languages that may be used to manage information for users and applies to both printed and on-screen information for users.<br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for efficient development and management of information produced; 1. throughout the life cycle of a system and software product;2. for the provision of information for users of systems and software; 3. for the management of IT and support services. This document is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Content management for product life cycle, user and service management information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93725 …}
    #channels: Doctrine\ORM\PersistentCollection {#93718 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93723 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93720 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93735 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93705
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1689285600 {#93741
      date: 2023-07-14 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1680127200 {#93740
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 68
    -documents: Doctrine\ORM\PersistentCollection {#93731 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93729 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#106935
  +product: App\Entity\Product\Product {#93734
    #id: 12861
    #code: "IEEE00010824"
    #attributes: Doctrine\ORM\PersistentCollection {#93716 …}
    #variants: Doctrine\ORM\PersistentCollection {#93713 …}
    #options: Doctrine\ORM\PersistentCollection {#93709 …}
    #associations: Doctrine\ORM\PersistentCollection {#93711 …}
    #createdAt: DateTime @1751040707 {#93742
      date: 2025-06-27 18:11:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#93721
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93727 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93762
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93734}
        #id: 46453
        #name: "IEEE/ISO/IEC 26531:2023"
        #slug: "ieee-iso-iec-26531-2023-ieee00010824-244519"
        #description: """
          Revision Standard - Active.<br />\n
          This document provides requirements for the management of the content used in product life cycle, software, and service management system information for users. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports multiple deliverable formats and the reuse of content objects among deliverables. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This document defines the characteristics of an effective and efficient process through which content is gathered, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or other content published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this document can fulfil business needs for content development and management, especially the need for a single source of authoritative information. This document includes business case considerations for acquisition of a content management system. This document is independent of the software tools and markup languages that may be used to manage information for users and applies to both printed and on-screen information for users.<br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for efficient development and management of information produced; 1. throughout the life cycle of a system and software product;2. for the provision of information for users of systems and software; 3. for the management of IT and support services. This document is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Content management for product life cycle, user and service management information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93725 …}
    #channels: Doctrine\ORM\PersistentCollection {#93718 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93723 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93720 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93735 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93705
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1689285600 {#93741
      date: 2023-07-14 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1680127200 {#93740
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 68
    -documents: Doctrine\ORM\PersistentCollection {#93731 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93729 …}
  }
  +appearance: "state-active"
  +labels: [
    "Active"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#93734
    #id: 12861
    #code: "IEEE00010824"
    #attributes: Doctrine\ORM\PersistentCollection {#93716 …}
    #variants: Doctrine\ORM\PersistentCollection {#93713 …}
    #options: Doctrine\ORM\PersistentCollection {#93709 …}
    #associations: Doctrine\ORM\PersistentCollection {#93711 …}
    #createdAt: DateTime @1751040707 {#93742
      date: 2025-06-27 18:11:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#93721
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93727 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93762
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93734}
        #id: 46453
        #name: "IEEE/ISO/IEC 26531:2023"
        #slug: "ieee-iso-iec-26531-2023-ieee00010824-244519"
        #description: """
          Revision Standard - Active.<br />\n
          This document provides requirements for the management of the content used in product life cycle, software, and service management system information for users. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports multiple deliverable formats and the reuse of content objects among deliverables. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This document defines the characteristics of an effective and efficient process through which content is gathered, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or other content published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this document can fulfil business needs for content development and management, especially the need for a single source of authoritative information. This document includes business case considerations for acquisition of a content management system. This document is independent of the software tools and markup languages that may be used to manage information for users and applies to both printed and on-screen information for users.<br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for efficient development and management of information produced; 1. throughout the life cycle of a system and software product;2. for the provision of information for users of systems and software; 3. for the management of IT and support services. This document is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Content management for product life cycle, user and service management information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93725 …}
    #channels: Doctrine\ORM\PersistentCollection {#93718 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93723 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93720 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93735 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93705
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1689285600 {#93741
      date: 2023-07-14 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1680127200 {#93740
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 68
    -documents: Doctrine\ORM\PersistentCollection {#93731 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93729 …}
  }
]

App\Twig\Components\ProductMostRecent {#107002
  +product: App\Entity\Product\Product {#93734
    #id: 12861
    #code: "IEEE00010824"
    #attributes: Doctrine\ORM\PersistentCollection {#93716 …}
    #variants: Doctrine\ORM\PersistentCollection {#93713 …}
    #options: Doctrine\ORM\PersistentCollection {#93709 …}
    #associations: Doctrine\ORM\PersistentCollection {#93711 …}
    #createdAt: DateTime @1751040707 {#93742
      date: 2025-06-27 18:11:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1753970953 {#93721
      date: 2025-07-31 16:09:13.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#93727 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#93762
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#93734}
        #id: 46453
        #name: "IEEE/ISO/IEC 26531:2023"
        #slug: "ieee-iso-iec-26531-2023-ieee00010824-244519"
        #description: """
          Revision Standard - Active.<br />\n
          This document provides requirements for the management of the content used in product life cycle, software, and service management system information for users. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports multiple deliverable formats and the reuse of content objects among deliverables. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This document defines the characteristics of an effective and efficient process through which content is gathered, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or other content published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this document can fulfil business needs for content development and management, especially the need for a single source of authoritative information. This document includes business case considerations for acquisition of a content management system. This document is independent of the software tools and markup languages that may be used to manage information for users and applies to both printed and on-screen information for users.<br />\n
          \t\t\t\t<br />\n
          This document specifies requirements for efficient development and management of information produced; 1. throughout the life cycle of a system and software product;2. for the provision of information for users of systems and software; 3. for the management of IT and support services. This document is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard - Systems and software engineering--Content management for product life cycle, user and service management information for users"
        -notes: "Active"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#93725 …}
    #channels: Doctrine\ORM\PersistentCollection {#93718 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#93723 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#93720 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#93735 …}
    -apiLastModifiedAt: DateTime @1743289200 {#93705
      date: 2025-03-30 00:00:00.0 Europe/Paris (+01:00)
    }
    -lastUpdatedAt: DateTime @1689285600 {#93741
      date: 2023-07-14 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1680127200 {#93740
      date: 2023-03-30 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 68
    -documents: Doctrine\ORM\PersistentCollection {#93731 …}
    -favorites: Doctrine\ORM\PersistentCollection {#93729 …}
  }
  +label: "Most Recent"
  +icon: "check-xs"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106868
    #id: 12673
    #code: "IEEE00010426"
    #attributes: Doctrine\ORM\PersistentCollection {#106851 …}
    #variants: Doctrine\ORM\PersistentCollection {#106848 …}
    #options: Doctrine\ORM\PersistentCollection {#106844 …}
    #associations: Doctrine\ORM\PersistentCollection {#106846 …}
    #createdAt: DateTime @1751040587 {#106836
      date: 2025-06-27 18:09:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#106849
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106862 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107069
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106868}
        #id: 45701
        #name: "IEEE/ISO/IEC P26531"
        #slug: "ieee-iso-iec-p26531-ieee00010426-244328"
        #description: """
          Revision Standard - Superseded - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document states requirements for efficient development and management of information content produced throughout the life cycle of a system and software product; for the provision of information for users of systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content to be managed with this standard includes information for users such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product; product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports; service management items such as service-level agreements, records, policies, procedures, and other documents. The purpose of this standard is to define a process for content management and the requirements of a component content management system through which content is gathered, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database can support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents.<br />\n
          The purpose of this document is to define a process for the development and acquisition of a component content management system and the requirements of a component content management system through which content is created, gathered, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that can be assembled to produce complete documents for print, electronic output, or content published through electronic media. This database is defined as a Component Content Management system (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/ISO/IEC Draft International Standard - Systems and Software Engineering -- Content Management for Product Life Cycle, User, and Service Management Documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106859 …}
    #channels: Doctrine\ORM\PersistentCollection {#106853 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106857 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106855 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106869 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106876
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1667170800 {#106880
      date: 2022-10-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1658440800 {#106834
      date: 2022-07-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 65
    -documents: Doctrine\ORM\PersistentCollection {#106866 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106864 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#107084
  +product: App\Entity\Product\Product {#106868
    #id: 12673
    #code: "IEEE00010426"
    #attributes: Doctrine\ORM\PersistentCollection {#106851 …}
    #variants: Doctrine\ORM\PersistentCollection {#106848 …}
    #options: Doctrine\ORM\PersistentCollection {#106844 …}
    #associations: Doctrine\ORM\PersistentCollection {#106846 …}
    #createdAt: DateTime @1751040587 {#106836
      date: 2025-06-27 18:09:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#106849
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106862 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107069
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106868}
        #id: 45701
        #name: "IEEE/ISO/IEC P26531"
        #slug: "ieee-iso-iec-p26531-ieee00010426-244328"
        #description: """
          Revision Standard - Superseded - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document states requirements for efficient development and management of information content produced throughout the life cycle of a system and software product; for the provision of information for users of systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content to be managed with this standard includes information for users such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product; product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports; service management items such as service-level agreements, records, policies, procedures, and other documents. The purpose of this standard is to define a process for content management and the requirements of a component content management system through which content is gathered, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database can support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents.<br />\n
          The purpose of this document is to define a process for the development and acquisition of a component content management system and the requirements of a component content management system through which content is created, gathered, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that can be assembled to produce complete documents for print, electronic output, or content published through electronic media. This database is defined as a Component Content Management system (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/ISO/IEC Draft International Standard - Systems and Software Engineering -- Content Management for Product Life Cycle, User, and Service Management Documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106859 …}
    #channels: Doctrine\ORM\PersistentCollection {#106853 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106857 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106855 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106869 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106876
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1667170800 {#106880
      date: 2022-10-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1658440800 {#106834
      date: 2022-07-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 65
    -documents: Doctrine\ORM\PersistentCollection {#106866 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106864 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#106868
    #id: 12673
    #code: "IEEE00010426"
    #attributes: Doctrine\ORM\PersistentCollection {#106851 …}
    #variants: Doctrine\ORM\PersistentCollection {#106848 …}
    #options: Doctrine\ORM\PersistentCollection {#106844 …}
    #associations: Doctrine\ORM\PersistentCollection {#106846 …}
    #createdAt: DateTime @1751040587 {#106836
      date: 2025-06-27 18:09:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#106849
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106862 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107069
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106868}
        #id: 45701
        #name: "IEEE/ISO/IEC P26531"
        #slug: "ieee-iso-iec-p26531-ieee00010426-244328"
        #description: """
          Revision Standard - Superseded - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document states requirements for efficient development and management of information content produced throughout the life cycle of a system and software product; for the provision of information for users of systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content to be managed with this standard includes information for users such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product; product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports; service management items such as service-level agreements, records, policies, procedures, and other documents. The purpose of this standard is to define a process for content management and the requirements of a component content management system through which content is gathered, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database can support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents.<br />\n
          The purpose of this document is to define a process for the development and acquisition of a component content management system and the requirements of a component content management system through which content is created, gathered, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that can be assembled to produce complete documents for print, electronic output, or content published through electronic media. This database is defined as a Component Content Management system (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/ISO/IEC Draft International Standard - Systems and Software Engineering -- Content Management for Product Life Cycle, User, and Service Management Documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106859 …}
    #channels: Doctrine\ORM\PersistentCollection {#106853 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106857 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106855 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106869 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106876
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1667170800 {#106880
      date: 2022-10-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1658440800 {#106834
      date: 2022-07-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 65
    -documents: Doctrine\ORM\PersistentCollection {#106866 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106864 …}
  }
]

App\Twig\Components\ProductMostRecent {#107136
  +product: App\Entity\Product\Product {#106868
    #id: 12673
    #code: "IEEE00010426"
    #attributes: Doctrine\ORM\PersistentCollection {#106851 …}
    #variants: Doctrine\ORM\PersistentCollection {#106848 …}
    #options: Doctrine\ORM\PersistentCollection {#106844 …}
    #associations: Doctrine\ORM\PersistentCollection {#106846 …}
    #createdAt: DateTime @1751040587 {#106836
      date: 2025-06-27 18:09:47.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#106849
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#106862 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#107069
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#106868}
        #id: 45701
        #name: "IEEE/ISO/IEC P26531"
        #slug: "ieee-iso-iec-p26531-ieee00010426-244328"
        #description: """
          Revision Standard - Superseded - Draft.<br />\n
          <br />\n
          \t\t\t\t<br />\n
          This document states requirements for efficient development and management of information content produced throughout the life cycle of a system and software product; for the provision of information for users of systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content to be managed with this standard includes information for users such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product; product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports; service management items such as service-level agreements, records, policies, procedures, and other documents. The purpose of this standard is to define a process for content management and the requirements of a component content management system through which content is gathered, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database can support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents.<br />\n
          The purpose of this document is to define a process for the development and acquisition of a component content management system and the requirements of a component content management system through which content is created, gathered, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that can be assembled to produce complete documents for print, electronic output, or content published through electronic media. This database is defined as a Component Content Management system (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "IEEE/ISO/IEC Draft International Standard - Systems and Software Engineering -- Content Management for Product Life Cycle, User, and Service Management Documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#106859 …}
    #channels: Doctrine\ORM\PersistentCollection {#106853 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#106857 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#106855 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#106869 …}
    -apiLastModifiedAt: DateTime @1754517600 {#106876
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1667170800 {#106880
      date: 2022-10-31 00:00:00.0 Europe/Paris (+01:00)
    }
    -author: ""
    -publishedAt: DateTime @1658440800 {#106834
      date: 2022-07-22 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 65
    -documents: Doctrine\ORM\PersistentCollection {#106866 …}
    -favorites: Doctrine\ORM\PersistentCollection {#106864 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 11218
    #code: "IEEE00005753"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039554 {#7274
      date: 2025-06-27 17:52:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39881
        #name: "IEEE/ISO/IEC 26531:2015"
        #slug: "ieee-iso-iec-26531-2015-ieee00005753-242870"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This International Standard provides requirements for the management of the content used in product life cycle, software, and service management system documentation. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports the reuse of content objects among deliverables and supports multiple deliverable formats. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. The standard defines the characteristics of an effective and efficient process through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. The standard includes business case considerations for acquisition of a content management system. This International Standard is independent of the software tools and markup languages that may be used to manage documentation content, and applies to both printed documentation and on-screen documentation.<br />\n
          \t\t\t\t<br />\n
          This standard states requirements for efficient development and management of content produced throughout the life-cycle of a system and software product; for the provision of user documentation for systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content to be managed with this standard includes user information such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product; product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports; service management items such as service-level agreements, records, policies, procedures, and other documents. The purpose of this standard is to define a process for content management and the requirements of a component content management system through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents. The intended users of this International Standard are managers and developers of information (technical documentation) and acquirers and suppliers of content management systems. Any organization that develops content, regardless of size, can benefit from maintaining an effective content management solution and following best practices for the development and management of technical content. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This standard is not a management system standard. The content management process presented in clauses 6 through 11 of this International Standard is a specialization (lower-level process) of the Information Management process required in ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard for Systems and software engineering -- Content management for product life-cycle, user, and service management documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1679868000 {#7292
      date: 2023-03-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  "showFullLabel" => "true"
]

[
  "showFullLabel" => "true"
]

App\Twig\Components\ProductState {#107200
  +product: App\Entity\Product\Product {#7310
    #id: 11218
    #code: "IEEE00005753"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039554 {#7274
      date: 2025-06-27 17:52:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39881
        #name: "IEEE/ISO/IEC 26531:2015"
        #slug: "ieee-iso-iec-26531-2015-ieee00005753-242870"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This International Standard provides requirements for the management of the content used in product life cycle, software, and service management system documentation. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports the reuse of content objects among deliverables and supports multiple deliverable formats. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. The standard defines the characteristics of an effective and efficient process through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. The standard includes business case considerations for acquisition of a content management system. This International Standard is independent of the software tools and markup languages that may be used to manage documentation content, and applies to both printed documentation and on-screen documentation.<br />\n
          \t\t\t\t<br />\n
          This standard states requirements for efficient development and management of content produced throughout the life-cycle of a system and software product; for the provision of user documentation for systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content to be managed with this standard includes user information such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product; product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports; service management items such as service-level agreements, records, policies, procedures, and other documents. The purpose of this standard is to define a process for content management and the requirements of a component content management system through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents. The intended users of this International Standard are managers and developers of information (technical documentation) and acquirers and suppliers of content management systems. Any organization that develops content, regardless of size, can benefit from maintaining an effective content management solution and following best practices for the development and management of technical content. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This standard is not a management system standard. The content management process presented in clauses 6 through 11 of this International Standard is a specialization (lower-level process) of the Information Management process required in ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard for Systems and software engineering -- Content management for product life-cycle, user, and service management documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1679868000 {#7292
      date: 2023-03-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +appearance: "state-suspended"
  +labels: [
    "Superseded"
  ]
  -stateAttributeCode: "state"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}

[
  "product" => App\Entity\Product\Product {#7310
    #id: 11218
    #code: "IEEE00005753"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039554 {#7274
      date: 2025-06-27 17:52:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39881
        #name: "IEEE/ISO/IEC 26531:2015"
        #slug: "ieee-iso-iec-26531-2015-ieee00005753-242870"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This International Standard provides requirements for the management of the content used in product life cycle, software, and service management system documentation. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports the reuse of content objects among deliverables and supports multiple deliverable formats. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. The standard defines the characteristics of an effective and efficient process through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. The standard includes business case considerations for acquisition of a content management system. This International Standard is independent of the software tools and markup languages that may be used to manage documentation content, and applies to both printed documentation and on-screen documentation.<br />\n
          \t\t\t\t<br />\n
          This standard states requirements for efficient development and management of content produced throughout the life-cycle of a system and software product; for the provision of user documentation for systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content to be managed with this standard includes user information such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product; product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports; service management items such as service-level agreements, records, policies, procedures, and other documents. The purpose of this standard is to define a process for content management and the requirements of a component content management system through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents. The intended users of this International Standard are managers and developers of information (technical documentation) and acquirers and suppliers of content management systems. Any organization that develops content, regardless of size, can benefit from maintaining an effective content management solution and following best practices for the development and management of technical content. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This standard is not a management system standard. The content management process presented in clauses 6 through 11 of this International Standard is a specialization (lower-level process) of the Information Management process required in ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard for Systems and software engineering -- Content management for product life-cycle, user, and service management documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1679868000 {#7292
      date: 2023-03-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
]

App\Twig\Components\ProductMostRecent {#107227
  +product: App\Entity\Product\Product {#7310
    #id: 11218
    #code: "IEEE00005753"
    #attributes: Doctrine\ORM\PersistentCollection {#7700 …}
    #variants: Doctrine\ORM\PersistentCollection {#7743 …}
    #options: Doctrine\ORM\PersistentCollection {#7915 …}
    #associations: Doctrine\ORM\PersistentCollection {#7899 …}
    #createdAt: DateTime @1751039554 {#7274
      date: 2025-06-27 17:52:34.0 Europe/Paris (+02:00)
    }
    #updatedAt: DateTime @1754608621 {#7322
      date: 2025-08-08 01:17:01.0 Europe/Paris (+02:00)
    }
    #enabled: true
    #translations: Doctrine\ORM\PersistentCollection {#7921 …}
    #translationsCache: [
      "en_US" => App\Entity\Product\ProductTranslation {#7920
        #locale: "en_US"
        #translatable: App\Entity\Product\Product {#7310}
        #id: 39881
        #name: "IEEE/ISO/IEC 26531:2015"
        #slug: "ieee-iso-iec-26531-2015-ieee00005753-242870"
        #description: """
          New IEEE Standard - Superseded.<br />\n
          This International Standard provides requirements for the management of the content used in product life cycle, software, and service management system documentation. Content management allows an organization to control the storage and retrieval of content objects, track content revisions, maintain a content audit trail, and enable a collaborative environment. Component content management supports the reuse of content objects among deliverables and supports multiple deliverable formats. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. The standard defines the characteristics of an effective and efficient process through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a component content management system (CCMS), as distinct from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats including but not limited to documents. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. The standard includes business case considerations for acquisition of a content management system. This International Standard is independent of the software tools and markup languages that may be used to manage documentation content, and applies to both printed documentation and on-screen documentation.<br />\n
          \t\t\t\t<br />\n
          This standard states requirements for efficient development and management of content produced throughout the life-cycle of a system and software product; for the provision of user documentation for systems and software; for the management of IT services. This standard is independent of the tools, protocols, and systems used for content management. It does not address configuration management of software assets. The content to be managed with this standard includes user information such as topic collections, manuals, guides, embedded user assistance, style guides, videos and other media, and other content that supports the effective use of a system or software product; product life cycle information such as design documents, use cases, personas, project management plans, feature requests, models, scripts, testing plans, test scripts, defect reports; service management items such as service-level agreements, records, policies, procedures, and other documents. The purpose of this standard is to define a process for content management and the requirements of a component content management system through which content is gathereed, managed, and published, including the requirements of a system that is supported by an electronic database. Such a database should support documents or topics and content units that may be assembled to produce complete documents for print, electronic output, or content collections published through electronic media. This database is defined as a Component Content Management System (CCMS), which differs from a document management system. The objective of component content management is to create content objects once and use them through linking mechanisms in multiple output formats, including but not limited to documents. The intended users of this International Standard are managers and developers of information (technical documentation) and acquirers and suppliers of content management systems. Any organization that develops content, regardless of size, can benefit from maintaining an effective content management solution and following best practices for the development and management of technical content. Systems conforming to this standard can fulfilll business needs for content development and management, especially the need for a single source of authoritative information. Content objects that are unique and are maintained as independent database objects are efficient to review, approve, and update; may be combined to produce multiple deliverables; and are cost-effective to translate. This standard is not a management system standard. The content management process presented in clauses 6 through 11 of this International Standard is a specialization (lower-level process) of the Information Management process required in ISO/IEC/IEEE 15288:2008 and ISO/IEC/IEEE 12207:2008.
          """
        #metaKeywords: null
        #metaDescription: null
        #shortDescription: "ISO/IEC/IEEE International Standard for Systems and software engineering -- Content management for product life-cycle, user, and service management documentation"
        -notes: "Superseded"
      }
    ]
    #currentLocale: "en_US"
    #currentTranslation: null
    #fallbackLocale: "en_US"
    #variantSelectionMethod: "match"
    #productTaxons: Doctrine\ORM\PersistentCollection {#7533 …}
    #channels: Doctrine\ORM\PersistentCollection {#7627 …}
    #mainTaxon: Proxies\__CG__\App\Entity\Taxonomy\Taxon {#7311 …}
    #reviews: Doctrine\ORM\PersistentCollection {#7612 …}
    #averageRating: 0.0
    #images: Doctrine\ORM\PersistentCollection {#7644 …}
    -supplier: Proxies\__CG__\App\Entity\Supplier\Supplier {#7325 …}
    -subscriptionCollections: Doctrine\ORM\PersistentCollection {#7389 …}
    -apiLastModifiedAt: DateTime @1754517600 {#7317
      date: 2025-08-07 00:00:00.0 Europe/Paris (+02:00)
    }
    -lastUpdatedAt: DateTime @1679868000 {#7292
      date: 2023-03-27 00:00:00.0 Europe/Paris (+02:00)
    }
    -author: ""
    -publishedAt: DateTime @1431640800 {#7318
      date: 2015-05-15 00:00:00.0 Europe/Paris (+02:00)
    }
    -releasedAt: null
    -confirmedAt: null
    -canceledAt: null
    -edition: null
    -coreDocument: "26531"
    -bookCollection: ""
    -pageCount: 60
    -documents: Doctrine\ORM\PersistentCollection {#7464 …}
    -favorites: Doctrine\ORM\PersistentCollection {#7499 …}
  }
  +label: "Historical"
  +icon: "historical"
  -mostRecentAttributeCode: "most_recent"
  -localeContext: Sylius\Component\Locale\Context\CompositeLocaleContext {#1833 …}
}