From MS docs:
A split view control has an expandable/collapsible pane and a content area.
A split view's content area is always visible. The pane can expand and collapse or remain in an open state, and can present itself from either the left side or right side of an app window. The pane has four modes: Overlay, Inline, CompactOverlay, CompactInline. (Detailed in links below)
public class SplitView : Control
{
public SplitView();
[Content]
public object Content { get; set; }
public SplitViewPanePlacement PanePlacement { get; set; }
public Brush PaneBackground { get; set; }
public object Pane { get; set; }
public double OpenPaneLength { get; set; }
public bool IsPaneOpen { get; set; }
public SplitViewDisplayMode DisplayMode { get; set; }
public double CompactPaneLength { get; set; }
public LightDismissOverlayMode LightDismissOverlayMode { get; set; }
public SplitViewTemplateSettings TemplateSettings { get; }
public static StyledProperty CompactPaneLengthProperty { get; }
public static StyledProperty ContentProperty { get; }
public static StyledProperty DisplayModeProperty { get; }
public static StyledProperty IsPaneOpenProperty { get; }
public static StyledProperty OpenPaneLengthProperty { get; }
public static StyledProperty PaneBackgroundProperty { get; }
public static StyledProperty PanePlacementProperty { get; }
public static StyledProperty PaneProperty { get; }
public static StyledProperty LightDismissOverlayModeProperty { get; }
public static DirectProperty TemplateSettingsProperty { get; }
public event EventHandler<EventArgs> PaneClosed;
public event EventHandler<SplitViewPaneClosingEventArgs> PaneClosing;
public event EventHandler<EventArgs> PaneOpened;
public event EventHandler<EventArgs> PaneOpening;
}
public sealed class SplitViewPaneClosingEventArgs
{
public bool Cancel { get; set; }
}
// Provides calculated values that can be referenced as **TemplatedParent** sources when defining templates for a SplitView.
public sealed class SplitViewTemplateSettings : AvaloniaObject
{
public GridLength CompactPaneGridLength { get; }
public double NegativeOpenPaneLength { get; }
public double NegativeOpenPaneLengthMinusCompactLength { get; }
public GridLength OpenPaneGridLength { get; }
public double OpenPaneLength { get; }
public double OpenPaneLengthMinusCompactLength { get; }
}
public enum SplitViewDisplayMode
{
Overlay = 0,
Inline = 1,
CompactOverlay = 2,
CompactInline = 3
}
public enum SplitViewPanePlacement
{
Left = 0,
Right = 1
}
// Defines constants that specify whether the area outside of a *light-dismiss* UI is darkened.
public enum LightDismissOverlayMode
{
Auto = 0,
On = 1,
Off = 2
}
Gif source: https://nicksnettravels.builttoroam.com/uwp-splitview/

I agree that this control would be useful, however I'm hesitant to accept any more controls into Avalonia itself because they become a maintenance burden on the core developers and we don't have enough time as it is.
Personally, I think the best way to do this would be to port it, hosted by the maintainer in their own repository, and add the control to https://github.com/AvaloniaCommunity/awesome-avalonia for visibility.
I'm working on creating a library for Fluent Design/WinUI inspired things for use with Avalonia, sort of inspired by #3950, and I've ported the SplitView control. This is all a work in progress, but the SplitView is finished and works.
https://github.com/amwx/FluentAvalonia

Most helpful comment
I'm working on creating a library for Fluent Design/WinUI inspired things for use with Avalonia, sort of inspired by #3950, and I've ported the SplitView control. This is all a work in progress, but the SplitView is finished and works.
https://github.com/amwx/FluentAvalonia