socialbase.info.yml in Open Social 8.9

themes/socialbase/socialbase.info.yml

File

themes/socialbase/socialbase.info.yml

# The display name for this theme. The name will appear on the Appearance page.
name: Social Base theme
# A brief description of the theme. The description will appear on the
# Appearance page.
description: Base theme for Open social installations. Create your own subtheme or enable Social Blue
# The screenshot is the image used on the appearance page. The setting is
# optional, and if not specified, Drupal will automatically look for a file
# called 'screenshot.png' in the root of the theme's folder. If a different file
# name or type is wanted, the screenshot setting must be used.
#
# If the theme does not supply a screenshot, and uses a base theme that does,
# the screenshot will be inheritted from the base theme.
screenshot: screenshot.png

# The type defines the extension type (module, theme, etc.)
# This is required and should always be set to 'theme' for a theme.
type: theme

# The base theme setting specifies another theme to use as a "parent" theme.
# Templates, CSS, and other properties are inherited from the base theme. If a
# base theme is not specified, Stable will automatically be used as the base
# theme. To op-out of using Stable, set base theme to 'false'.
#
# base theme: false
#
# socialbase uses bootstrap as its base theme
base theme: bootstrap


# The supported Drupal version.
core: 8.x

# Libraries-extend is used to attach libraries to other libraries. If the
# original library is conditionally included, the library it is extended with
# will be included under the same conditions.
libraries-extend:
  core/drupal.ajax:
    - socialbase/form--autocomplete
  core/drupal.tabledrag:
    - socialbase/tabledrag
  # attach the timepicker library to all date fields
  core/drupal.date:
    - socialbase/form--datepicker
  #extend the core datepicker with a stylesheet and attach the listener
  core/jquery.ui.datepicker:
    - socialbase/form--timepicker
  # Attach the bootstrap library script and css component.
  # Note that the socialbase library scripts needs to load first. That is
  # why we added weights to the library JS files in socialbase.
  bootstrap/popover:
    - socialbase/popover
  core/drupal.dialog.ajax:
    - socialbase/modal
  editor/drupal.editor:
    - socialbase/modal
  image_widget_crop/cropper.integration:
    - socialbase/cropper.integration
  # Attach our own libary_builder library to the one in Drupal core. Our
  # library re-adds some CSS files that we remove elsewhere for our own modals
  # to work properly. However, that removal breaks the layout builder.
  layout_builder/drupal.layout_builder:
    - socialbase/layout_builder

stylesheets-remove:
  - like_and_dislike.icons.css

# Libraries-override is used to override any of the assets defined by a library.
# Use it to remove files, replace files with your own, replace a library with
# your own library, or remove the library completely.
# See https://www.drupal.org/node/2497313.
libraries-override:
  # The library name.
  core/normalize: false
  # Remove jQuery UI styles
  core/jquery.ui:
    css:
      component:
        assets/vendor/jquery.ui/themes/base/core.css: false
      theme:
        assets/vendor/jquery.ui/themes/base/theme.css: false
  core/jquery.ui.button:
    css:
      component:
        assets/vendor/jquery.ui/themes/base/button.css: false
  core/jquery.ui.datepicker:
      # CSS files are always labeled as such. This format is required.
      css:
        # The SMACSS category is required. See https://www.drupal.org/node/1887922
        component:
          # The path to the file. It is not a path relative to your theme. This
          # should be the same as the path specified in the library file where it
          # was defined. Setting to 'false' prevents the file from being
          # included.
          assets/vendor/jquery.ui/themes/base/datepicker.css: false
  core/jquery.ui.dialog:
    css:
      component:
        assets/vendor/jquery.ui/themes/base/dialog.css: false
  core/jquery.ui.menu:
    css:
      component:
        assets/vendor/jquery.ui/themes/base/menu.css: false
  system/base: false
  views/views.module: false
  classy/file: false
  like_and_dislike/behavior:
    js:
      js/like_and_dislike_service.js: false
  like_and_dislike/icons: false
  private_message/inbox_block: false

# Libraries contain CSS and JavaScript files. The libraries setting is used to
# globally add libraries, which means they will appear on every page. Libraries
# are not limited to ones defined in the the theme. Ones from other themes and
# modules can be included as long as they are installed.
#
# Libraries are defined in [theme name].libraries.yml. To conditionally include
# libraries see https://www.drupal.org/theme-guide/8/assets.

# The "libraries:" section will add a library to _all_ pages.
# The order here is determined first by SMACSS category and after that you can determine the order here.
libraries:
# The following are libraries defined by Social base in socialbase.libraries.yml.
  - socialbase/print
  - socialbase/base
  # Atoms
  - socialbase/alert
  - socialbase/badge
  - socialbase/button
  - socialbase/cards
  - socialbase/close-icon
  - socialbase/form-controls
  - socialbase/list
  - socialbase/spinner
  # Molecules
  - socialbase/dropdown
  - socialbase/form-elements
  - socialbase/form-input-groups
  - socialbase/imagecrop
  - socialbase/media
  - socialbase/mentions
  - socialbase/navbar
  - socialbase/tour
  - socialbase/like
  # Templates
  - socialbase/layout

# This section is used by the contrib module, Component Libraries. It allows you
# to reference .twig files in your components/ directory.
component-libraries:
  base:
    paths:
      - components/01-base
  atoms:
    paths:
      - components/02-atoms
  molecules:
    paths:
      - components/03-molecules
  organisms:
    paths:
      - components/04-organisms
  templates:
    paths:
      - components/05-templates

# Special stylesheets for CKEditor to use while editing.
ckeditor_stylesheets:
  - assets/css/ckeditor.css

regions:
  hidden: Hidden
  header: Header
  breadcrumb: Breadcrumb
  hero: Hero
  secondary_navigation: Secondary navigation
  content_top: Content top
  title: Page title
  content: Content
  complementary_top: Complementary top
  complementary_bottom: Complementary bottom
  content_bottom: Content bottom
  sidebar_first: Sidebar First
  sidebar_second: Sidebar Second
  footer: Footer
# Remove regions_hidden part in your subtheme.
# The Hidden region should be visible when you enable a sub theme due to core bug.
regions_hidden:
  - hidden