* Added method for autogrow behaviour and changed event triggers.
* Changed overflow styles for autogrow form elements.
* Update class on icons in navbar https://www.drupal.org/node/2872929
* Update instruction: In your sub theme provide a fill color for either `.navbar-nav__icon` which is the new icon class. Or like we did in social blue provide a fill for `.navbar-nav > li > a`. The default color is white. The size of the icon is in socialbase. The float class is removed and not needed.
* Provide a condition before printing the *topic type* in `node--topic--teaser.html.twig`. Although topic type in a required field by default, this can be changed in an installation.
* Update instruction: In your sub theme provide a fill color for either
`.navbar-nav__icon` which is the new icon class. Or like we did in social blue
provide a fill for `.navbar-nav > li > a`. The default color is white. The size
of the icon is in socialbase. The float class is removed and not needed.
* Provide a condition before printing the *topic type* in
`node--topic--teaser.html.twig`. Although topic type in a required field by
default, this can be changed in an installation.
### v2.1.3 -- Apr 2017
* Changed wave-effect styles.
...
...
@@ -17,8 +22,10 @@
* Document and rename alert, badge, list in style guide
* Add Bar chart and Donut chart to MorrisJs documentation
* Optimise small teaser templates
* Add two columns and three columns layout, with sidebar_first and sidebar_second regions.
* Renamed in page-full twig block nodefull_header to metainfo and added twig block metaengage.
* Add two columns and three columns layout, with sidebar_first and
sidebar_second regions.
* Renamed in page-full twig block nodefull_header to metainfo and added twig
block metaengage.
### v2.1.1 -- Feb 2017
* Removed pug style guide files
...
...
@@ -32,19 +39,24 @@
Complete overhaul of theme_hooks and clean up of templates
* All theme_hooks_suggestions and theme_hook_preprocess functions are moved to individual files in the includes folder
* All theme_hooks_suggestions and theme_hook_preprocess functions are moved to
individual files in the includes folder
* Cleaned up form hooks
* Renamed classes in `card` component
* Renamed classes in `teaser` component
* Removed Pug version of styleguide -> styleguide is moved to socialblue theme
* Inserted documentation in component scss files for existing components in styleguide
* Inserted documentation in component scss files for existing components in
styleguide
* Added range slider to atoms > form-controls
* Moved layout from base component to template component folder
* Added Javascript library folder to components for better abstraction of javascript libraries/enhancements
* Added Javascript library folder to components for better abstraction of
javascript libraries/enhancements
* Added Morris.js dependency via bower (gulp plugin)
* Removed theme settings options that are default
* Removed bootstrap function to colorize and iconize buttons. This is now done via form hooks
* Updated the way we override the bootstrap panel implementation for details and fieldsets. Updated corresponding template files
* Removed bootstrap function to colorize and iconize buttons. This is now done
via form hooks
* Updated the way we override the bootstrap panel implementation for details and
The Social Base theme is designed as a base theme for Open Social. This base theme holds has a lot of sensible defaults. It doesn't however contain much styling. We expect every developer to want to change this for his/her project. As you can see there is also a theme called **socialblue**. Socialblue is the demo/styling sub theme for Open Social.
The Social Base theme is designed as a base theme for Open Social. This base
theme holds has a lot of sensible defaults. It doesn't however contain much
styling. We expect every developer to want to change this for his/her project.
As you can see there is also a theme called **socialblue**. Socialblue is the
demo/styling sub theme for Open Social.
# Changing the style of the theme #
If you are a Drupal themer you know how to create a (sub)theme. There are no tricks in our setup you need to know for Open Social. The easiest way to start is to grab a copy of Social Blue and rename all instances of social Blue to your new theme name. Social Base and Social Blue will get updates each release, so it is best not to make changes in here you want to keep.
Make sure that Social Base is always set as the base theme and inherit the regions from social Base if you do not change the page template.
# Development of your theme #
Before you start theming there are a few things that might be convenient. In html/sites/default there is a services.yml file. Make sure to set
* twig.config -> debug: true
* twig.config -> auto_reload: true
* twig.config -> cache: false
Also in sites default you will find an example.settings.local.php file. Duplicate this file and remove the example part. After you have configured these files you need to rebuild the caches. This will speed up you development process.
If you are a Drupal themer you know how to create a (sub)theme. There are no
tricks in our setup you need to know for Open Social. The easiest way to start
is to grab a copy of Social Blue and rename all instances of social Blue to your
new theme name. Social Base and Social Blue will get updates each release, so it
is best not to make changes in here you want to keep.
Make sure that Social Base is always set as the base theme and inherit the
regions from social Base if you do not change the page template.
# Development of your theme #
Before you start theming there are a few things that might be convenient. In
html/sites/default there is a services.yml file. Make sure to set
* twig.config -> debug: true
* twig.config -> auto_reload: true
* twig.config -> cache: false
Also in sites default you will find an example.settings.local.php file.
Duplicate this file and remove the example part. After you have configured these
files you need to rebuild the caches. This will speed up you development
process.
### Goodies used
...
...
@@ -28,15 +41,20 @@ If you are a Drupal themer you know how to create a (sub)theme. There are no tri
<dt># assets</dt>
<dd>Our gulp tasks will generate our CSS, JS and images that Drupal uses.</dd>
<dt># components</dt>
<dd>This is working folder. The folder is categorised following atomic design principles. Most re-usable css values are turned into variables for consistency.</dd>
<dd>This is working folder. The folder is categorised following atomic design
principles. Most re-usable css values are turned into variables for consistency.
</dd>
<dt># config</dt>
<dd>Drupal installation files</dd>
<dt># js - deprecated</dt>
<dd>Old javascript folder, needs to cleaned up (all JS should be in components are generated to assets folder)</dd>
<dd>Old javascript folder, needs to cleaned up (all JS should be in components
are generated to assets folder)</dd>
<dt># libraries</dt>
<dd>External libraries. Install via Gulp Bower task.</dd>
<dt># src</dt>
<dd>Drupal plugins - mainly overrides for the bootstrap base theme. @see [Drupal Bootstrap documentation](https://drupal-bootstrap.org/api/bootstrap/docs%21plugins%21README.md/group/plugins/8)</dd>
<dd>Drupal plugins - mainly overrides for the bootstrap base theme.
<dd>This folder contains all twig templates for the theme.</dd>
...
...
@@ -44,14 +62,16 @@ If you are a Drupal themer you know how to create a (sub)theme. There are no tri
# Contributing to socialbase #
Social Base uses Gulp.js as a task runner, so that it can do many tasks automatically:
Social Base uses Gulp.js as a task runner, so that it can do many tasks
automatically:
- Build CSS from your Sass using libSass and node-sass.
- Add vendor prefixes for the browsers you want to support using Autoprefixer.
- Watch all of your files as you develop and re-build everything on the fly.
Set up your front-end development build tools:
1.[Install Yarn](https://yarnpkg.com/en/docs/install), see their website for documentation
1.[Install Yarn](https://yarnpkg.com/en/docs/install), see their website for
documentation
2. Install the gulp-cli tool globally. Normally, installing a Node.js globally
is not recommended, which is why both Gulp and Grunt have created wrapper
...
...
@@ -62,7 +82,8 @@ Set up your front-end development build tools:
npm install -g gulp-cli
```
3. The package.json file contains the versions of all the node packages you need. To install them run:
3. The package.json file contains the versions of all the node packages you
need. To install them run:
```
yarn install
```
...
...
@@ -73,13 +94,18 @@ Set up your front-end development build tools:
options.drupalURL = 'http://localhost';
```
4. There are different gulp tasks. What each gulp task does is described in the gulpfile with the task itself. To run a gulp task, type:
4. There are different gulp tasks. What each gulp task does is described in the
gulpfile with the task itself. To run a gulp task, type:
```
gulp [taskname]
```
# Notice
We are constantly improving and updating the theme setup for Open Social. It might be the readme is not always up to date. Also check the changelog file for changes. You can report issues via the drupal.org [issue queue](https://www.drupal.org/project/issues/social?categories=All). The following items are on our roadmap:
* Remove JS folder and make sure all scripts are placed in their corresponding component.
We are constantly improving and updating the theme setup for Open Social. It
might be the readme is not always up to date. Also check the changelog file for
changes. You can report issues via the drupal.org [issue queue](https://www.drupal.org/project/issues/social?categories=All).
The following items are on our roadmap:
* Remove JS folder and make sure all scripts are placed in their corresponding
component.
* Add components library module and create twig templates in the components folder.
* Provide a starterkit in favor a manual copying Social Blue to start a new theme.
