diff --git a/community/bspwm/Packages-Desktop b/community/bspwm/Packages-Desktop
new file mode 100644
index 0000000..779756c
--- /dev/null
+++ b/community/bspwm/Packages-Desktop
@@ -0,0 +1,81 @@
+adwaita-maia-gtk3
+atool
+bc
+bmenu
+brandr
+breeze-maia-icon-themes
+bspwm-manjaro
+bspwm-ruler
+bspwm-ruler
+bspwm-scripts
+bspwm-wallpapers
+clonezilla
+compton
+console-solarized
+dash
+dconf
+delayed-hibernation
+desktop-file-utils
+dfc
+downgrade
+dunst
+feh
+file-roller
+fish
+fisherman
+gedit
+gnome-disk-utility
+gufw
+gvfs
+hibernator
+htop
+i3lock
+inxi
+lemonpanel
+libdnet
+libnotify
+lightfirefox
+limepanel
+lxappearance-gtk3
+manjaro-alsa
+manjaro-bspwm-settings
+mesa-demos
+mhwd-chroot
+mhwd-tui
+moc
+morc_menu
+mpv
+mygtkmenui
+ncdu
+networkmanager
+networkmanager-dispatcher-ntpd
+openresolv
+pacli
+perl-file-mimeinfo
+poppler
+ps_mem
+ranger
+rootmenu
+spacefm
+speedtest-cli
+st-manjaro
+sxhkd
+thermald
+tmux
+udevil
+xcursor-breeze
+xf86-input-elographics
+xf86-input-evdev
+xf86-input-keyboard
+xf86-input-libinput
+xf86-input-mouse
+xf86-input-void
+xlogin
+xorg-server
+xorg-server-utils
+yaourt
+zathura-pdf-poppler
+zenity
+zsh
+zsh-completions
+zsh-history-substring-search
\ No newline at end of file
diff --git a/community/bspwm/Packages-Live b/community/bspwm/Packages-Live
new file mode 120000
index 0000000..5e66e00
--- /dev/null
+++ b/community/bspwm/Packages-Live
@@ -0,0 +1 @@
+../../shared/Packages-Live
\ No newline at end of file
diff --git a/community/bspwm/Packages-Mhwd b/community/bspwm/Packages-Mhwd
new file mode 120000
index 0000000..9df3d5e
--- /dev/null
+++ b/community/bspwm/Packages-Mhwd
@@ -0,0 +1 @@
+../../shared/Packages-Mhwd
\ No newline at end of file
diff --git a/community/bspwm/Packages-Root b/community/bspwm/Packages-Root
new file mode 120000
index 0000000..60cc7bd
--- /dev/null
+++ b/community/bspwm/Packages-Root
@@ -0,0 +1 @@
+../../shared/Packages-Root
\ No newline at end of file
diff --git a/community/bspwm/desktop-overlay/etc/default/useradd b/community/bspwm/desktop-overlay/etc/default/useradd
new file mode 100644
index 0000000..e8c35b3
--- /dev/null
+++ b/community/bspwm/desktop-overlay/etc/default/useradd
@@ -0,0 +1,9 @@
+# useradd defaults file for ArchLinux
+# original changes by TomK
+GROUP=100
+HOME=/home
+INACTIVE=-1
+EXPIRE=
+SHELL=/bin/zsh
+SKEL=/etc/skel
+CREATE_MAIL_SPOOL=no
diff --git a/community/bspwm/desktop-overlay/etc/profile b/community/bspwm/desktop-overlay/etc/profile
new file mode 100644
index 0000000..9ac74c8
--- /dev/null
+++ b/community/bspwm/desktop-overlay/etc/profile
@@ -0,0 +1,31 @@
+# /etc/profile
+
+#Set our umask
+umask 022
+
+# Set our default path
+PATH="/usr/local/sbin:/usr/local/bin:/usr/bin:$HOME/.config/bspwm:$HOME/.config/bspwm/panel:$HOME/.bin"
+export PATH
+export XDG_CONFIG_HOME="$HOME/.config"
+export BSPWM_SOCKET="/tmp/bspwm-socket"
+export XDG_CONFIG_DIRS=/usr/etc/xdg:/etc/xdg
+
+# Load profiles from /etc/profile.d
+if test -d /etc/profile.d/; then
+	for profile in /etc/profile.d/*.sh; do
+		test -r "$profile" && . "$profile"
+	done
+	unset profile
+fi
+
+# Source global bash config
+if test "$PS1" && test "$BASH" && test -r /etc/bash.bashrc; then
+	. /etc/bash.bashrc
+fi
+
+# Termcap is outdated, old, and crusty, kill it.
+unset TERMCAP
+
+# Man is much better than us at figuring this out
+unset MANPATH
+BROWSER=/usr/bin/xdg-open
diff --git a/community/bspwm/desktop-overlay/etc/skel/.config/morc_menu/morc_menu_v1.conf b/community/bspwm/desktop-overlay/etc/skel/.config/morc_menu/morc_menu_v1.conf
new file mode 100644
index 0000000..b06ce49
--- /dev/null
+++ b/community/bspwm/desktop-overlay/etc/skel/.config/morc_menu/morc_menu_v1.conf
@@ -0,0 +1,156 @@
+# morc_menu_v1.conf
+# configuration file in support of morc_menu
+
+# To begin allowing you to customize the 'look' or 'skin' of the menu,
+# some explanation is called for: By default, the script uses a
+# low-resource front-end application called 'dmenu' to present its
+# menus. In this configuration file, you are be able to change the
+# parameters that the script uses to invoke 'dmenu', or you may
+# replace 'dmenu' with another front-end. The script has been tested
+# with front-ends 'rofi' and 'zenity', and may also work with 'yada'
+# and others. The script also allows you to import 'look' and 'skin'
+# data from definitions in other configuration files, to help you
+# maintain a consistent 'look' across different programs.
+
+# If you wish to import import 'look' and 'skin' data from definitions
+# in other configuration files, you must perform that first, before
+# defining how you wish to invoke your chosen front-end (sensible, as
+# in that situation, the invocation will be using definitions from
+# those files). You may define as many 'external_definition_file's as
+# you like. They will be read in the order you present them here, so
+# in a case of conflicting definitions, the last one wins. If the file
+# does not exist or can't be read, it is ignored, and the script
+# continues. The script will only read lines in the form 'foo=bar'. In
+# our default example we are reading a configuration file meant for
+# 'dmenu' usage.
+external_skin_definition_file=${HOME}/.dmenurc
+
+# Customize where on the screen you wish the menu to appear. If you
+# want the menu to appear at the wherever the mouse pointer is
+# resting, set the variable 'use_mouse_position' to 'TRUE', and you're
+# done - the script will figure out the correct x and y positions at
+# run-time. Otherwise, the script will always place the menu at the
+# 'x_position' and 'y_position' definitions you set below. All the
+# numeric values in this block are measured in pixels.
+# IMPORTANT:
+#   This only works when the 'menu_cmd' definition below correctly
+#   uses the string literals X_POSITION, Y_POSITION, as is the case in
+#   the default and in the examples below. Additionally, MENU_LINES
+#   and MENU_WIDTH must be correctly used, as in the examples below,
+#   in order for dynamically positioned menus not to try to display
+#   beyond the screen edge, and for there not to display unnecessary
+#   whitespace.
+x_position=300
+y_position=20
+# Until we learn how to directly measure font width and height, we
+# need to set 'line_height', 'avg_char_width', and 'menu_width'
+# manually by trial and error. If 'avg_char_width' is not zero, then
+# 'menu_width' will be ignored, and the value will be calculated at
+# run-time.
+line_height=22
+avg_char_width=13
+menu_width=350
+# use_mouse_position=TRUE
+use_mouse_position=TRUE
+
+# The third and final, step in customizing the 'look' or 'skin' of the
+# menu is to modify how the script invokes its menu command
+# ('menu_cmd') and its error notification (error_cmd'). In general,
+# the options available to you are limited by those of your chosen
+# front-end, so refer to its man page and other documentation.
+# Additionally, you may refer to variables defined in one of the
+# 'external_skin_definition_file's you specified above, and you may
+# use variables 'x_position' and 'y_position' to set where on the
+# screen you want your menu. Here are some examples:
+# IMPORTANT:
+#   In order for the script to properly position the menu, these
+#   definitions must include parameters that correctly use the string
+#   literals X_POSITION, Y_POSITION, MENU_LINES, and MENU_WIDTH, as is
+#   the case in the default and in the examples below. Additionally,
+#   MENU_LINES and MENU_WIDTH must be correctly used, as in the
+#   examples below, in order for dynamically positioned menus not to
+#   try to display beyond the screen edge, and for there not to
+#   display unnecessary whitespace.
+#
+# The script's default, using 'dmenu' 
+#menu_cmd="dmenu -i -l MENU_LINES -x X_POSITION -y Y_POSITION -w MENU_WIDTH "
+#menu_cmd="dmenu -i -l MENU_LINES -x X_POSITION -y Y_POSITION -w MENU_WIDTH "
+
+# Using a variable defined in an external_skin_definition_file, in
+# this case ${HOME}/.dmenurc
+menu_cmd="dmenu -i -l MENU_LINES -x X_POSITION -y Y_POSITION -w MENU_WIDTH ${DMENU_OPTIONS}"
+
+# Using 'zenity' and 'rofi'
+# Because there ought to be some reward for reading all this
+# documentation, note the use of the embedded linux command 'uname' to
+# set the zenity column title. 
+# menu_cmd="zenity --list --column=$(uname -no) "
+# menu_cmd="rofi "
+
+
+# Customize the 'look' or 'skin' of the error messages by modifying
+# the following string, which, as above for the menu command, will be
+# used to invoke your choice of menu front end.
+error_cmd="dmenu -i -l 40 -x 500 -y 150 -w 350 -nb red -nf black -fn DejaVu"
+# error_cmd="zenity --error "
+# error_cmd="rofi "
+
+
+# Distinguish between an executable item and a sub-menu selection
+menu_prefix=" "
+menu_suffix=" >"
+# If a 'menu_suffix' is defined, you can have the script align them
+# vertically, but this only works if you are using a fixed width font,
+# so if you've selected a proportional font, set 'align_suffix' to
+# 'FALSE'.
+align_suffix=TRUE
+
+# Desired categories: Any single .desktop definition can include an
+# arbitrarily long list of categories for itself, which would bloat
+# the menu with duplicate clutter, so the following space-delimited
+# variable white-lists the desired categories.
+desired_categories="Favorites Settings Development Documentation Education System Network Utility Graphics Office AudioVideo"
+
+
+# Category aliases: The common convention seems to be to rename some
+# categories, as in the default below. We implement the renaming sing
+# an associative array in which the index is the category as defined
+# in the .desktop file, and the value is the desired output
+declare -A category_aliases=( [Utility]=Accessories [AudioVideo]=Multimedia [Network]=Internet )
+
+
+# Unwanted names and execs: Entries with these names or execution
+# statements should black-listed from the menu.
+unwanted_names=( feh )
+unwanted_execs=( )
+
+
+# Maximum number of backups to keep: because almost no one will notice
+# accumulating cruft. Backups are automatically created in the user's
+# ${HOME}/.config/morc_menu folder, in the form
+# "categorized_menu${ext}_%y-%m-%d-%T" where ${ext} is either ".txt"
+# or "_xml.txt" and the suffix is a timestamp. If you want to keep a
+# particular backup forever, rename it to fail a match against
+# "categorized_menu${ext}_*"
+max_num_backups=5
+
+# Information about the menu and how to customize it are by default
+# presented in a trailng menu entry "about morc_menu". You may exclude
+# presentation of that menu item by setting 'exclude_about' to TRUE
+exclude_about="TRUE"
+#exclude_about="False"
+
+# Adding top-level menu entries for frequently used applications:
+# That's what 'favorites' are. See below for how to do that.
+
+# Adding 'favorites' and custom entries: Neither of those
+# customizations are performed in this configuration file. In both
+# cases, define each extra entry by creating a new ".desktop" file or
+# by editing an existing one. For system-wide customization, this will
+# be performed by a system administrator in the
+# /usr/share/applications folder; For user-personal customizations,
+# this will be performed by the user in the
+# ${HOME}/.local/share/applications folder. Favorites are defined by
+# adding that word to the list of categories in the .desktop file.
+# Other additional entries are made by adding a new .desktop file, or
+# adding a category to an existing one.
\ No newline at end of file
diff --git a/community/bspwm/desktop-overlay/etc/sysctl.d/20-quiet-printk.conf b/community/bspwm/desktop-overlay/etc/sysctl.d/20-quiet-printk.conf
new file mode 100644
index 0000000..47146d2
--- /dev/null
+++ b/community/bspwm/desktop-overlay/etc/sysctl.d/20-quiet-printk.conf
@@ -0,0 +1 @@
+kernel.printk = 3 3 3 3
diff --git a/community/bspwm/desktop-overlay/etc/systemd/user/dbus.service b/community/bspwm/desktop-overlay/etc/systemd/user/dbus.service
new file mode 100644
index 0000000..1851818
--- /dev/null
+++ b/community/bspwm/desktop-overlay/etc/systemd/user/dbus.service
@@ -0,0 +1,7 @@
+[Unit]
+Description=D-Bus Message Bus
+Requires=dbus.socket
+
+[Service]
+ExecStart=/usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation
+ExecReload=/usr/bin/dbus-send --print-reply --session --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig
diff --git a/community/bspwm/desktop-overlay/etc/systemd/user/dbus.socket b/community/bspwm/desktop-overlay/etc/systemd/user/dbus.socket
new file mode 100644
index 0000000..7e77219
--- /dev/null
+++ b/community/bspwm/desktop-overlay/etc/systemd/user/dbus.socket
@@ -0,0 +1,9 @@
+[Unit]
+Description=D-Bus Message Bus Socket
+Before=sockets.target
+
+[Socket]
+ListenStream=/run/user/%U/dbus/user_bus_socket
+
+[Install]
+WantedBy=default.target
diff --git a/community/bspwm/desktop-overlay/etc/udevil/udevil.conf b/community/bspwm/desktop-overlay/etc/udevil/udevil.conf
new file mode 100644
index 0000000..c072e26
--- /dev/null
+++ b/community/bspwm/desktop-overlay/etc/udevil/udevil.conf
@@ -0,0 +1,335 @@
+##############################################################################
+#
+# udevil configuration file    /etc/udevil/udevil.conf
+#
+# This file controls what devices, networks, and files users may mount and
+# unmount via udevil (set suid).
+# 
+# IMPORTANT:  IT IS POSSIBLE TO CREATE SERIOUS SECURITY PROBLEMS IF THIS FILE
+# IS MISCONFIGURED - EDIT WITH CARE
+#
+# Note:  For greater control for specific users, including root, copy this
+# file to /etc/udevil/udevil-user-USERNAME.conf replacing USERNAME with the
+# desired username (eg /etc/udevil/udevil-user-jim.conf).
+#
+# Format:
+#   OPTION = VALUE[, VALUE, ...]
+#
+# DO NOT USE QUOTES except literally
+# Lines beginning with # are ignored
+#
+##############################################################################
+
+
+# To log all uses of udevil, set log_file to a file path:
+# log_file = /var/log/udevil.log
+
+# Approximate number of days to retain log entries (0=forever, max=60):
+log_keep_days = 10
+
+
+# allowed_types determines what fstypes can be passed by a user to the u/mount
+# program, what device filesystems may be un/mounted implicitly, and what
+# network filesystems may be un/mounted.
+# It may also include the 'file' keyword, indicating that the user is allowed
+# to mount files (eg an ISO file).  The $KNOWN_FILESYSTEMS variable may
+# be included to include common local filesystems as well as those listed in
+# /etc/filesystems and /proc/filesystems.
+# allowed_types_USERNAME, if present, is used to override allowed_types for
+# the specific user 'USERNAME'.  For example, to allow user 'jim' to mount
+# only vfat filesystems, add:
+# allowed_types_jim = vfat
+# Setting allowed_types = * does NOT allow all types, as this is a security
+# risk, but does allow all recognized types.
+# allowed_types = $KNOWN_FILESYSTEMS, file, cifs, smbfs, nfs, curlftpfs, ftpfs, sshfs, davfs, tmpfs, ramfs
+allowed_types = $KNOWN_FILESYSTEMS, file
+
+
+# allowed_users is a list of users permitted to mount and unmount with udevil.
+# Wildcards (* or ?) may be used in the usernames.  To allow all users,
+# specify "allowed_users=*".  UIDs may be included using the form UID=1000.
+# For example:  allowed_users = carl, UID=1000, pre*
+# Also note that permission to execute udevil may be limited to users belonging
+# to the group that owns /usr/bin/udevil, such as 'plugdev' or 'storage',
+# depending on installation.
+# allowed_users_FSTYPE, if present, is used to override allowed_users when
+# mounting or unmounting a specific fstype (eg nfs, ext3, file).
+# Note that when mounting a file, fstype will always be 'file' regardless of
+# the internal fstype of the file.
+# For example, to allow only user 'bob' to mount nfs shares, add:
+# allowed_users_nfs = bob
+# The root user is NOT automatically allowed to use udevil in some cases unless
+# listed here (except for unmounting anything or mounting fstab devices).
+allowed_users = *
+
+
+# allowed_groups is a list of groups permitted to mount and unmount with
+# udevil.  The user MUST belong to at least one of these groups.  Wildcards
+# or GIDs may NOT be used in group names, but a single * may be used to allow
+# all groups.
+# Also note that permission to execute udevil may be limited to users belonging
+# to the group that owns /usr/bin/udevil, such as 'plugdev' or 'storage',
+# depending on installation.
+# allowed_groups_FSTYPE, if present, is used to override allowed_groups when
+# mounting or unmounting a specific fstype (eg nfs, ext3, file).  For example,
+# to allow only members of the 'network' group to mount smb and nfs shares,
+# use both of these lines:
+# allowed_groups_smbfs = network
+# allowed_groups_nfs = network
+# The root user is NOT automatically allowed to use udevil in some cases unless
+# listed here (except for unmounting anything or mounting fstab devices).
+allowed_groups = *
+
+
+# allowed_media_dirs specifies the media directories in which user mount points
+# may be located.  The first directory which exists and does not contain a
+# wildcard will be used as the default media directory (normally /media or
+# /media/$USER).
+# The $USER variable, if included, will be replaced with the username of the
+# user running udevil.  Wildcards may also be used in any directory EXCEPT the
+# default.  Wildcards will not match a /, except a /** suffix for recursion.
+# allowed_media_dirs_FSTYPE, if present, is used to override allowed_media_dirs
+# when mounting or unmounting a specific fstype (eg ext2, nfs).  For example,
+# to cause /media/network to be used as the default media directory for
+# nfs and ftpfs mounts, use these two lines:
+# allowed_media_dirs_nfs   = /media/network, /media, /media/$USER
+# allowed_media_dirs_ftpfs = /media/network, /media, /media/$USER
+# NOTE: If you want only the user who mounted a device to have access to it
+# and be allowed to unmount it, specify /media/$USER as the first
+# allowed media directory (only /media/$USER is created on demand).
+# IMPORTANT:  If an allowed file is mounted to a media directory, the user may
+# be permitted to unmount its associated loop device even though internal.
+# INCLUDING /MNT HERE IS NOT RECOMMENDED.  ALL ALLOWED MEDIA DIRECTORIES
+# SHOULD BE OWNED AND WRITABLE ONLY BY ROOT.
+allowed_media_dirs = /media, /media/$USER, /run/media/$USER
+
+
+# allowed_devices is the first criteria for what block devices users may mount
+# or unmount.  If a device is not listed in allowed_devices, it cannot be
+# un/mounted (unless in fstab).  However, even if a device is listed, other
+# factors may prevent its use.  For example, access to system internal devices
+# will be denied to normal users even if they are included in allowed_devices.  
+# allowed_devices_FSTYPE, if present, is used to override allowed_devices when
+# mounting or unmounting a specific fstype (eg ext3, ntfs).  For example, to
+# prevent all block devices containing an ext4 filesystem from being
+# un/mounted use:
+# allowed_devices_ext4 =
+# Note: Wildcards may be used, but a wildcard will never match a /, except
+# for "allowed_devices=*" which allows any device.  The recommended setting is
+# allowed_devices = /dev/*
+# WARNING:  ALLOWING USERS TO MOUNT DEVICES OUTSIDE OF /dev CAN CAUSE SERIOUS
+# SECURITY PROBLEMS.  DO NOT ALLOW DEVICES IN /dev/shm
+allowed_devices = /dev/*
+
+
+# allowed_internal_devices causes udevil to treat any listed block devices as
+# removable, thus allowing normal users to un/mount them (providing they are
+# also listed in allowed_devices).
+# allowed_internal_devices_FSTYPE, if present, is used to override
+# allowed_internal_devices when mounting or unmounting a specific fstype
+# (eg ext3, ntfs).  For example, to allow block devices containing a vfat
+# filesystem to be un/mounted even if they are system internal devices, use:
+# allowed_internal_devices_vfat = /dev/sdb*
+# Some removable esata drives look like internal drives to udevil.  To avoid
+# this problem, they can be treated as removable with this setting.
+# WARNING:  SETTING A SYSTEM DEVICE HERE CAN CAUSE SERIOUS SECURITY PROBLEMS.
+allowed_internal_devices = /dev/*
+
+
+# allowed_internal_uuids and allowed_internal_uuids_FSTYPE work similarly to
+# allowed_internal_devices, except that UUIDs are specified instead of devices.
+# For example, to allow un/mounting of an internal filesystem based on UUID:
+# allowed_internal_uuids = cc0c4489-8def-1e5b-a304-ab87c3cb626c0
+# WARNING:  SETTING A SYSTEM DEVICE HERE CAN CAUSE SERIOUS SECURITY PROBLEMS.
+# allowed_internal_uuids = 
+
+
+# forbidden_devices is used to prevent block devices from being un/mounted
+# even if other settings would allow them (except devices in fstab).
+# forbidden_devices_FSTYPE, if present, is used to override
+# forbidden_devices when mounting or unmounting a specific fstype
+# (eg ext3, ntfs).  For example, to prevent device /dev/sdd1 from being
+# mounted when it contains an ntfs filesystem, use:
+# forbidden_devices_ntfs = /dev/sdd1
+# NOTE: device node paths are canonicalized before being tested, so forbidding
+# a link to a device will have no effect.
+forbidden_devices =
+
+
+# allowed_networks determines what hosts may be un/mounted by udevil users when
+# using nfs, cifs, smbfs, curlftpfs, ftpfs, or sshfs.  Hosts may be specified
+# using a hostname (eg myserver.com) or IP address (192.168.1.100).
+# Wildcards may be used in hostnames and IP addresses, but CIDR notation 
+# (192.168.1.0/16) is NOT supported.  IP v6 is supported.  For example:
+# allowed_networks = 127.0.0.1, 192.168.1.*, 10.0.0.*, localmachine, *.okay.com
+# Or, to prevent un/mounting of any network shares, set:
+# allowed_networks =
+# allowed_networks_FSTYPE, if present, is used to override allowed_networks
+# when mounting or unmounting a specific network fstype (eg nfs, cifs, sshfs,
+# curlftpfs).  For example, to limit nfs and samba shares to only local
+# networks, use these two lines:
+# allowed_networks_nfs = 192.168.1.*, 10.0.0.*
+# allowed_networks_cifs = 192.168.1.*, 10.0.0.*
+allowed_networks = *
+
+
+# forbidden_networks and forbidden_networks_FSTYPE are used to specify networks
+# that are never allowed, even if other settings allow them (except fstab).
+# NO REVERSE LOOKUP IS PERFORMED, so including bad.com will only have an effect
+# if the user uses that hostname.  IP lookup is always performed, so forbidding
+# an IP address will also forbid all corresponding hostnames.
+forbidden_networks = 
+
+
+# allowed_files is used to determine what files in what directories may be
+# un/mounted.  A user must also have read permission on a file to mount it.
+# Note: Wildcards may be used, but a wildcard will never match a /, except
+# for "allowed_files=*" which allows any file, and a /** suffix, which matches
+# all files recursively.
+# For example, to allow only files in the /share directory to be mounted, use:
+# allowed_files = /share/*
+# To allow all files in the /share directory AND all subdirectories use:
+# allowed_files = /share/**
+# NOTE:  Specifying allowed_files_FSTYPE will NOT work because the fstype of
+# files is always 'file'.
+allowed_files = *
+
+
+# forbidden_files is used to specify files that are never allowed, even if
+# other settings allow them (except fstab).  Specify a full path.
+# Note: Wildcards may be used, but a wildcard will never match a /, except
+# for "forbidden_files = *", or a /** suffix, which matches all recursively.
+# NOTE: file paths are canonicalized before being tested, so forbidding
+# a link to a file will have no effect.
+forbidden_files = 
+
+
+# default_options specifies what options are always included when performing
+# a mount, in addition to any options the user may specify.
+# Note:  When a device is present in /etc/fstab, and the user does not specify
+# a mount point, the device is mounted with normal user permissions using
+# the fstab entry, without these options.
+# default_options_FSTYPE, if present, is used to override default_options
+# when mounting a specific fstype (eg ext2, nfs).
+# The variables $USER, $UID, and $GID are changed to the user's username, UID,
+# and GID.
+# FOR GOOD SECURITY, default_options SHOULD ALWAYS INCLUDE: nosuid,noexec,nodev
+# WARNING:  OPTIONS PRESENT OR MISSING CAN CAUSE SERIOUS SECURITY PROBLEMS.
+default_options           = nosuid, noexec, nodev, noatime
+default_options_file      = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, ro
+# mount iso9660 with 'ro' to prevent mount read-only warning
+default_options_iso9660   = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, ro, utf8
+default_options_udf       = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
+default_options_vfat      = nosuid, noexec, nodev, noatime, fmask=0133, dmask=0022, uid=$UID, gid=$GID, utf8
+default_options_exfat     = nosuid, noexec, nodev, noatime, umask=0077, uid=$UID, gid=$GID, iocharset=utf8, namecase=0, nonempty
+default_options_msdos     = nosuid, noexec, nodev, noatime, fmask=0133, dmask=0022, uid=$UID, gid=$GID
+default_options_umsdos    = nosuid, noexec, nodev, noatime, fmask=0133, dmask=0022, uid=$UID, gid=$GID
+default_options_ntfs      = nosuid, noexec, nodev, noatime, fmask=0133, uid=$UID, gid=$GID, utf8
+default_options_cifs      = nosuid, noexec, nodev, uid=$UID, gid=$GID
+default_options_smbfs     = nosuid, noexec, nodev, uid=$UID, gid=$GID
+default_options_sshfs     = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, nonempty, allow_other
+default_options_curlftpfs = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID, nonempty, allow_other
+default_options_ftpfs     = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
+default_options_davfs     = nosuid, noexec, nodev, uid=$UID, gid=$GID
+default_options_tmpfs     = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
+default_options_ramfs     = nosuid, noexec, nodev, noatime, uid=$UID, gid=$GID
+
+
+# allowed_options determines all options that a user may specify when mounting.
+# All the options used in default_options above must be included here too, or
+# they will be rejected.  If the user attempts to use an option not included
+# here, an error will result.  Wildcards may be used.
+# allowed_options_FSTYPE, if present, is used to override allowed_options
+# when mounting a specific fstype (eg ext2, nfs).
+# The variables $USER, $UID, and $GID are changed to the user's username, UID,
+# and GID.
+# If you want to forbid remounts, remove 'remount' from here.
+# WARNING:  OPTIONS HERE CAN CAUSE SERIOUS SECURITY PROBLEMS - CHOOSE CAREFULLY
+allowed_options           = nosuid, noexec, nodev, noatime, fmask=0133, dmask=0022, uid=$UID, gid=$GID, ro, rw, sync, flush, iocharset=*, utf8, remount
+allowed_options_nfs       = nosuid, noexec, nodev, noatime, ro, rw, sync, remount, port=*, rsize=*, wsize=*, hard, proto=*, timeo=*, retrans=*
+allowed_options_cifs      = nosuid, noexec, nodev, ro, rw, remount, port=*, user=*, username=*, pass=*, password=*, guest, domain=*, uid=$UID, gid=$GID, credentials=*
+allowed_options_smbfs     = nosuid, noexec, nodev, ro, rw, remount, port=*, user=*, username=*, pass=*, password=*, guest, domain=*, uid=$UID, gid=$GID, credentials=*
+allowed_options_sshfs     = nosuid, noexec, nodev, noatime, ro, rw, uid=$UID, gid=$GID, nonempty, allow_other, idmap=user, BatchMode=yes, port=*
+allowed_options_curlftpfs = nosuid, noexec, nodev, noatime, ro, rw, uid=$UID, gid=$GID, nonempty, allow_other, user=*
+allowed_options_ftpfs     = nosuid, noexec, nodev, noatime, ro, rw, port=*, user=*, pass=*, root=*, uid=$UID, gid=$GID
+allowed_options_exfat     = nosuid, noexec, nodev, noatime, fmask=0133, dmask=0022, uid=$UID, gid=$GID, umask=0077, namecase=*, ro, rw, sync, flush, iocharset=*, remount, nonempty
+
+
+# mount_point_mode, if present and set to a non-empty value, will cause udevil
+# to set the mode (permissions) on the moint point after mounting  If not
+# specified or if left empty, the mode is not changed.  Mode must be octal
+# starting with a zero (0755).
+# mount_point_mode_FSTYPE, if present, is used to override mount_point_mode
+# when mounting a specific fstype (eg ext2, nfs).
+# NOT SETTING A MODE CAN HAVE SECURITY IMPLICATIONS FOR SOME FSTYPES
+mount_point_mode = 0755
+# don't set a mode for some types:
+mount_point_mode_sshfs =
+mount_point_mode_curlftpfs =
+mount_point_mode_ftpfs =
+
+
+# Use the settings below to change the default locations of programs used by
+# udevil, or (advanced topic) to redirect commands to your scripts.
+# When substituting scripts, make sure they are root-owned and accept the
+# options used by udevil (for example, the mount_program must accept --fake,
+# -o, -v, and other options valid to mount.)
+# Be sure to specify the full path and include NO OPTIONS or other arguments.
+# These programs may also be specified as configure options when building
+# udevil.
+# THESE PROGRAMS ARE RUN AS ROOT
+# mount_program   = /bin/mount
+# umount_program  = /bin/umount
+# losetup_program = /sbin/losetup
+# setfacl_program = /usr/bin/setfacl
+
+
+# validate_exec specifies a program or script which provides additional
+# validation of a mount or unmount command, beyond the checks performed by
+# udevil.  The program is run as a normal user (if root runs udevil,
+# validate_exec will NOT be run).  The program is NOT run if the user is
+# mounting a device without root priviledges (a device in fstab).
+# The program is passed the username, a printable description of what is
+# happening, and the entire udevil command line as the first three arguments.
+# The program must return an exit status of 0 to allow the mount or unmount
+# to proceed.  If it returns non-zero, the user will be denied permission.
+# For example, validate_exec might specify a script which notifies you
+# of the command being run, or performs additional steps to authenticate the
+# user.
+# Specify a full path to the program, with NO options or arguments.
+# validate_exec =
+
+
+# validate_rootexec works similarly to validate_exec, except that the program
+# is run as root.  validate_rootexec will also be run if the root user runs
+# udevil.  If both validate_exec and validate_rootexec are specified, 
+# validate_rootexec will run first, followed by validate_exec.
+# The program must return an exit status of 0 to allow the mount or unmount
+# to proceed.  If it returns non-zero, the user will be denied permission.
+# Unless you are familiar with writing root scripts, it is recommended that
+# rootexec settings NOT be used, as it is easy to inadvertently open exploits.
+# THIS PROGRAM IS ALWAYS RUN AS ROOT, even if the user running udevil is not.
+# validate_rootexec =
+
+
+# success_exec is run after a successful mount, remount, or unmount.  The 
+# program is run as a normal user (if root runs udevil, success_exec
+# will NOT be run).
+# The program is passed the username, a printable description of what action
+# was taken, and the entire udevil command line as the first three arguments.
+# The program's exit status is ignored.
+# For example, success_exec might run a script which informs you of what action
+# was taken, and might perform further actions.
+# Specify a full path to the program, with NO options or arguments.
+# success_exec =
+
+
+# success_rootexec works similarly to success_exec, except that the program is
+# run as root.  success_rootexec will also be run if the root user runs udevil.
+# If both success_exec and success_rootexec are specified,  success_rootexec
+# will run first, followed by success_exec.
+# Unless you are familiar with writing root scripts, it is recommended that
+# rootexec settings NOT be used, as it is easy to inadvertently open exploits.
+# THIS PROGRAM IS ALWAYS RUN AS ROOT, even if the user running udevil is not.
+# success_rootexec =
+
diff --git a/community/bspwm/desktop-overlay/usr/share/gtk-3.0/gtk.css b/community/bspwm/desktop-overlay/usr/share/gtk-3.0/gtk.css
new file mode 100755
index 0000000..33c658d
--- /dev/null
+++ b/community/bspwm/desktop-overlay/usr/share/gtk-3.0/gtk.css
@@ -0,0 +1,10 @@
+.window-frame, .window-frame:backdrop {
+  box-shadow: 0 0 0 black;
+  border-style: none;
+  margin: 0;
+  border-radius: 0;
+}
+    
+.titlebar {
+  border-radius: 0;
+}
\ No newline at end of file
diff --git a/community/bspwm/desktop-overlay/usr/share/gtk-3.0/settings.ini b/community/bspwm/desktop-overlay/usr/share/gtk-3.0/settings.ini
new file mode 100644
index 0000000..2d91741
--- /dev/null
+++ b/community/bspwm/desktop-overlay/usr/share/gtk-3.0/settings.ini
@@ -0,0 +1,17 @@
+[Settings]
+gtk-theme-name=Adwaita-Maia
+gtk-icon-theme-name=Breeze-Maia-Dark
+gtk-font-name=xos4 Terminus 13
+gtk-cursor-theme-name=Breeze
+gtk-cursor-theme-size=0
+gtk-toolbar-style=GTK_TOOLBAR_ICONS
+gtk-toolbar-icon-size=GTK_ICON_SIZE_LARGE_TOOLBAR
+gtk-button-images=1
+gtk-menu-images=1
+gtk-enable-event-sounds=1
+gtk-enable-input-feedback-sounds=1
+gtk-xft-antialias=0
+gtk-xft-hinting=0
+gtk-xft-hintstyle=hintmedium
+gtk-application-prefer-dark-theme=1
+gtk-decoration-layout=:menu,appmenu,close
diff --git a/community/bspwm/live-overlay b/community/bspwm/live-overlay
new file mode 120000
index 0000000..27b9d2a
--- /dev/null
+++ b/community/bspwm/live-overlay
@@ -0,0 +1 @@
+../../shared/manjaro/live-overlay
\ No newline at end of file
diff --git a/community/bspwm/mkinitcpio.conf b/community/bspwm/mkinitcpio.conf
new file mode 120000
index 0000000..d624606
--- /dev/null
+++ b/community/bspwm/mkinitcpio.conf
@@ -0,0 +1 @@
+../../shared/mkinitcpio.conf
\ No newline at end of file
diff --git a/community/bspwm/profile.conf b/community/bspwm/profile.conf
new file mode 100755
index 0000000..a67cdc3
--- /dev/null
+++ b/community/bspwm/profile.conf
@@ -0,0 +1,73 @@
+##########################################
+###### use this file in the profile ######
+##########################################
+
+displaymanager="none"
+
+pxe_boot="false"
+
+plymouth_boot="false"
+
+nonfree_mhwd="true"
+
+use_overlayfs="true"
+
+multilib="false"
+
+################ install ################
+
+# configure calamares for netinstall
+# netinstall="false"
+
+# the default url for the netinstall.yaml
+# netgroups="https://raw.githubusercontent.com/manjaro/manjaro-tools-iso-profiles/master/shared/netinstall"
+
+# configure calamares to use chrootcfg instead of unpackfs
+# chrootcfg="false"
+
+# use geoip for localization
+# geoip='true'
+
+# unset defaults to given value
+# plymouth_theme=manjaro-elegant
+
+# unset defaults to given values
+# names must match systemd service names
+enable_systemd=('cronie' 'ModemManager' 'NetworkManager' 'tlp' 'tlp-sleep' 'systemd-fsck@' 'systemd-fsck-root')
+disable_systemd=('pacman-init')
+
+# unset defaults to given values,
+# names must match openrc service names
+# enable_openrc=('acpid' 'bluetooth' 'cgmanager' 'consolekit' 'cronie' 'cupsd' 'dbus' 'syslog-ng' 'NetworkManager' 'tlp' 'tlp-sleep')
+# disable_openrc=()
+
+# the same workgroup name if samba is used
+# smb_workgroup=""
+
+################# livecd #################
+
+# unset defaults to given value
+hostname="manjaro-bspwm"
+
+# unset defaults to given value
+# username="manjaro"
+
+# unset defaults to given value
+# password="manjaro"
+
+# the login shell
+# defaults to bash
+login_shell=/bin/zsh
+
+# unset defaults to given values
+# addgroups="video,audio,power,disk,storage,optical,network,lp,scanner,wheel"
+
+# unset defaults to given values
+# names must match systemd service names
+# services in enable_systemd array don't need to be listed here
+# enable_systemd_live=('manjaro-live' 'mhwd-live' 'pacman-init' 'pacman-boot')
+
+# unset defaults to given values,
+# names must match openrc service names
+# services in enable_openrc array don't need to be listed here
+# enable_openrc_live=('manjaro-live' 'mhwd-live' 'pacman-init' 'pacman-boot')