Updated Frequently Asked Questions (markdown)

Frequently-Asked-Questions.md

@@ -6,6 +6,7 @@
 * [Why Aren't Device Type Component Modifications Retroactive?](#why-arent-device-type-component-modifications-retroactive)
 * [Why Can't Circuits Have More Than Two Terminations?](#why-cant-circuits-have-more-than-two-terminations)
 * [Why Can't I Pass Exported Data Directly Into the Import Form?](#why-cant-i-pass-exported-data-directly-into-the-import-form)
+* [How Can I Model Half-Width Devices?](#how-can-i-model-half-width-devices)
 
 # Why Doesn't NetBox Scan for IPs?
 
@@ -92,3 +93,9 @@ However, this data is formatted for intended consumption by a human, which is to
 For example, when exporting a list of devices, NetBox will include the assigned site and rack (if any), but not the rack's group. If there are multiple racks with the same name within the site, each within a different group, this data will not be sufficient to import devices: Additional information (i.e. the group assigned to each rack) is needed so that NetBox knows which rack to assign to each device. It would be extremely inefficient to include all such possible information in the default export format for all objects.
 
 Additionally, redirecting data exported from NetBox back into NetBox is not a common use case. If you find yourself doing this, you may want to consider a more programmatic approach using the REST API or Python shell. However, if you decide this is the required course of action, you always have the option of creating a custom export template to arrange whatever data you need in whatever format you like. These can easily be used to export data in a format that is acceptable to NetBox's bulk import forms.
+
+# How Can I Model Half-Width Devices?
+
+Some rack-mounted devices don't consume the entire horizontal rack unit, such as the [Mellanox Spectrum SN2010](https://www.cdw.com/product/mellanox-spectrum-sn2010-switch-22-ports-managed-rack-mountable/5119458). These devices do not mount within a rack directly: They require a separate mounting bracket to be affixed within a rack unit.
+
+To model these devices in NetBox, first create a device type to represent the mounting bracket and assign it the appropriate number of device bays (however many child devices the bracket is capable of holding). Then, ensure that the device type which represents the child device has its subdevice role set to "child." Next, install the parent device (representing the bracket) in the rack, and the child devices within its device bays. This ensures that you have adequately represented the real-world installation of these devices.