BudyPress 2.9.0 ‘La Lombarda’

We’re  happy to announce the launch & availability of it’s latest release 2.9 ‘La Lombarda’ available for download or updatable from your WordPress install plugin directory.

As always this release has been a huge team effort from both the core contributors and many new contributors with first time patches and we thank everyone for their time and effort put in to bring this release home.

I personally thank everyone for the support I’ve had as a first time release lead, an interesting experience. special thanks must go to @mercime for acting as release deputy, keeping the devchats abridged and posted on bpdevel and for the help on the first beta packaging run at an ungodly hour of the morning 🙂

A full changelog can be viewed here – Codex Changelog 2.9.0

Please report any issues to our Trac home

Happy updating!

hnla.

#2-9-0, #new-release

BuddyPress 2.9.0-RC1

Today sees BP 2.9.0 move to the final testing phase Release Candidate 1.

This is the last chance to test out this release and report back any issues found before final release in approximately two weeks time.

Any issues found can be reported to our trac ticket home , or raised on the support forum.

For a full list of commits see 2.9 tickets A full changelog will be available when we release the final version.

You can download the plugin to test from the WP repo BP 2.9.0-RC1 or grab a copy from our SVN repo.

A reminder to all theme developers that there are changes to template markup that could effect layouts and ask that they check their themes carefully, the changes are listed below along with changelog links; again any issues or problems please report as soon as possible to the BP trac or slack channel.

Template changes

In this release there are a number of improvements to templates that add a level of improved a11y performance and markup changes for better semantics & Standards.

Theme authors may want to pay particular attention to changes to profile field visibility links and the profile field descriptions where significant markup changes are made that effect positioning of these elements – changesets for these are r11617 & r11618

Nouveau – new template pack

If you’re looking for Nouveau as we mentioned in the beta2 announcement we have delayed the release of this new template pack to ensure it receives as much code checking & refinement as possible and we’ll be looking to probably package this as it’s own release shortly after 2.9 is released.

We thank you in advance for all testing and reports and it need not be mentioned but please don’t run Beta or RC releases in a production environment only on test installs.

Regards,
The BuddyPress team.

BuddyPress 2.9 Beta 2

Today sees BP 2.9 move to Beta 2 ( Beta 1 skipped for technical reasons ) testing phase and we would request all plugin authors, theme developers and other interested parties test out this release and feedback any issues found to our ticket trac home .

You can download the plugin to test from the WP repo BP 2.9.0-beta2 or grab a copy from our SVN repo.

Amongst other improvements and fixes to look out for are:

  • Fixing display of older activity comments.
  • Correction of message when removing friends that are not friends.
  • Group invites – omit sending to previously invited members.
  • Profile image upload fix for IE Edge breaksIOS fix.
  • Correct issue with hidden group & CSS specificity.
  • URL compatibility for LightSpeed.
  • Fix inability resizing of member avatar for cyrillic character filenames.

For a full list of commits see 2.9 tickets

Template changes

In this release there are a number of improvements to templates that add a level of improved a11y performance and markup changes for better semantics & Standards.

Theme authors may want to pay particular attention to changes to profile field visibility links and the profile field descriptions where significant markup changes are made that effect positioning of these elements – changesets for these are r11617 & r11618

Nouveau – new template pack

While we were definitely aiming for release of this feature for 2.9, the necessary final fixes and feature enhancements along with the necessary code reviews were going to prove very tight to get finished in time and would have likely meant a degree of rushing. We have decided that as this is such a major new feature, the first new theme in many years and that expectations will be high for it that we should not rush to put out a product that might be even slightly sub optimal.

However fear not we are very concerned that the project is focussed on through the last stages of 2.9 and has primary focus during the next release cycle to ensure an early completion.

It is further proposed that we’ll actually release Nouveau in a much shorter release cycle as 3.0, this way we can get an early release and not have the project just sitting in trunk until the end of the year.

Companion Styles: twentyseventeen

Companion stylesheets to support the latest WP twentyseventeen theme is now committed to BP core and will be included in the 2.8 release.

While further iterations are forthcoming shortly to address some design concerns feedback would be helpful especially browser /device testing.

Any issues spotted can be notified on this ticket:

https://buddypress.trac.wordpress.org/ticket/7338

Your comments and testing are appreciated 🙂

~hnla.

#companion-styles, #stylesheets, #theme

Nouveau Template Chat

At slightly short notice (although briefly mentioned last week on slack) I’m resuming the template chats for Thursdays @ 20:00 utc ( or earlier if it suits more people? )

As today is at short notice the chat is a more informal one to get the ball rolling again and I hope anyone that is interested will check in and lend a voice.

We’ll keep to a short meeting of 30 mins – depending on how things go this might roll on longer.

As the Nouveau project is in a fairly complete state vis a vis templates, styles, majority of the directory structure, functions/classes etc this is the opportune moment to discuss the areas that will dictate how the template pack is managed and executed in BP core and these areas to some extent dictate how work on the project in general moves forward.

The discussion points are therefore:

  1. Agreement or otherwise that template packs or templates are run in the core bp-templates folder.
  2. If running from core do we want to implement the template switching process? See ‘UI to Pick Template Packs‘ Trac ticket & to be considered in this point is that imath has effected a very effective solution here currently in use if running Nouveau as a plugin
  3. If we do run multiple templates – what if any are the implications of supporting these multiple packs in terms of time updating them if required?
  4. In terms of styles I’ve followed a ‘partials’ approach to breaking the various components into smaller file includes compiled into the main .scss sheet, the principle notion here was that those ‘ _partials’ are maintained in <code>/src/bp-templates/shared/styles/</code> and can be used as a base set for any new set of templates (obviously not being compiled into the ‘build’ for final releases). Although I have kept things flexible so we have options I think this best approach so would seek consensus &/or opinion here.

There is a fair bit to discuss just in the points above, ideally we seek consensus on these points so we can move forward but am  not expecting we can achieve this in one chat session but making a start is the important thing.

Hope to see as many there as possible.

~hnla

P.S. Please feel free to leave any comments about the points above or any other thoughts on the Nouveau templates project.

P.P.S. The template pack is available here on the BuddyPress github account ‘Next Template Packs

#template-packs

Nouveau – A BP Template Pack Story

Well a few further updates 🙂

Following on from our first introductory update The State of the BP Nouveau template pack we are happy to provide a little more insight into the ongoing development of this project.

Since that first update we have updated many files pushing some ~110 commits ~410 commits in total to date.

We have comprehensively re-factored and structured the directory layout and created many new include files. Styles are re-worked into a modular series of partial files representing two levels  – those that are called and compiled as the base styles and those that are unique to given TP & living in the TP directory.

The focus of the last couple of weeks has really been on template re-factoring, updating markup , improving semantics, adding or removing classes as required while working through screens updating styles. Updating visual styles also involves paying attention to  the structure and formatting of the files, looking at the nesting of rules (less depth allowed in lint rules) , attempting to ensure we have lighter files with selector specificity that’s lower and less troublesome to override and ultimately to hopefully compile css files that are a little smaller in kb.
Amongst other additions since last we wrote there have been:

  • Navigational user selected styles
    We now provide a vertical navigation selection for user object navs seen here

Nouveau Vertical Nav Menu

  • Additional styles for Navs or links exist too so we can have  a default subnav view or a tabbed look, the tabbed look  work as styles & classes  that can be dropped on most ul list links so we can use them on links such as the profile group links or the message screen links:tabbed-navsThese styles for tabbed navs work from classes to apply the styles in the same way the vertical navs function so in time we will add these to the customizer when we’ve worked out what elements benefit from the choices (apart from the obvious).

 

  • Messages gained a massive upgrade courtesy of @im4th as described in the last update further to this we have updated some of the markup for better semantics and tweaked the styling a bit for both the inbox messages listing & preview screen & single message thread views:

messages-inboxmessage-thread

  • All Nav elements in general have received a review and class tokens upgrade to try and make them a little more useful  and clear – gone is reference to ‘tabs’ unless they are specifically visually styled as such. Navs have had a round of default styling as a base line on which we can build out further styles and attention to some very simple screen widths so that we have something that will work for small mobile/tablet devices. small-screen-navs
  • On User screens we have looked at creating a more uniform approach and consistency to headings and simple explanatory text so for example on the user settings screens we have added headings and text to all screens so it’s clear exactly what your looking at, this process is replicated across all screens where required.

user-headings

  • Whats new textarea gets a tidy up of styles to compliment the work carried out by imath for both small and wide screen views.
  • General tables get a freshen up and font sizes managed for th/td cells.
  • BP Lists get attention for heading/meta font sizes & layouts for small / wide screens.
  • Update the Group Create steps screens, improves the markup and classes and pulls out the BP core steps navigation to include in nouveau template-tags file and adjusts markup.
  • Updates for mixins & scss variable files – improves color choices by variable reference, create more individual specific vars to allow changing of  more specific elements without changing all e.g $nav-hover: $dark-grey; allows $nav-hover to take a different color or var while another element can still use $dark-grey as set. Mixins get updates  for responsive text  to compliment the general font size mixin, this allows a value to be divided by a percentage on smaller breakpoints. New clearfix mixin allows clearfix rules to be added to an element fed as a param of the mixin. Add a variation of the messages box used in companion styles; this mixin allows backgrounds  and color to be passed to message element rulesets, authors can now override the defaults for border, background, color. Update our password strength warning colors for variable definitions rather than hardcoded hex.

Moving forward we have more templates to still run over and review for the best markup structure classes and of course a full and detailed review of accessibility improvements we can bring to our templates which @mercime will be tackling at a convenient moment.

@im4th is currently looking at the implementation of the template pack selector for core on this ticket :

https://buddypress.trac.wordpress.org/ticket/7157

As well as continuing to drive new and exciting functionality for bp-nouveau. (take a look at the proposal here for example: https://github.com/buddypress/next-template-packs/issues/64)

We encourage everyone to download and follow along with the development plugin, you can download from:

https://github.com/buddypress/next-template-packs/archive/master.zip

or of course checkout to your plugins local dev via git:

https://github.com/buddypress/next-template-packs.git

We have specific Template dev Chats on Thursdays @ 19:00 UTC on BP’s slack channel, please come along and provide feedback or simply follow along all and any participation is hugely welcome.

If you’re running the plugin and spot an issue or have an idea for an improvement then you can use BP’s issue tickets on the next-template-pack repo to report them:

https://github.com/buddypress/next-template-packs/issues

And last but not least please feel free to leave any comments or questions on this post and we’ll attempt to respond to them 🙂

 

Regards, the Template Pack Team.

 

BuddyPress Style Modules

Introducing an  initiative to provide community written styles for BuddyPress sites.

Today we are excited to launch the trial of a new project within Buddypress that sets out to provide an approach for people to develop small style snippets to enhance aspects of a BuddyPress site.

It is hoped that  development of styles under this approach will engage authors to create interesting new looks for BP components and provide users with a rich library of code snippets to enhance their site with.

Initially this is a trial to see whether we get sufficient interest in the concept to continue and develop further, perhaps enhancing the loading process with enqueueing of files based on directory scanning and loading of files as an array but run from the core theme compat class, removing the need for users to copy the loading functions to their functions file.

Provision of modules and use of them is entirely the discretion of the authors and users, while BP will run some basic checks on the module BP does not guarantee that the modules will work in all given situations or installs, or accept any liability in their use. Support for a module remains the responsibility of the author to ensure the continued effectiveness of the module with updates to themes, WP or BP.

Snippets is a loose term best thought of as styling parts of a BP screen or component without necessarily having to be concerned in managing the development of a whole theme and related styles.

An example of a style module may be found in the provided members list module that re-factors the member lists as  panel boxes in a grid layout, another could be a new look for the user profile entries, or even simpler updating certain elements in the activity list for font sizes. Importantly style modules can be as simple or complicated as one wants them or needs them to be, there is no stipulation on what constitutes a module in terms of provided styling, you do not need to be a coding guru we would encourage anyone to have a go if they have a good idea for enhancing an area of BuddyPress.

As a guide to what could be styled we could look at areas such as:

  • Activity posting form. The ‘what’s new’ form is ripe for styling and enhancing using a mixture of styles and scripting.
  • Activity Comments – new takes on presenting nested comments using styles and/or scripting.
  • Simply style an instance of the logged in user  – maybe make your own objects in lists etc less obvious using opacity, or conversely bring to prominence.
  • Style the new user types.

Authoring Modules

Anyone wishing to provide a module needs to look at the example module (the example  module may be used as it is fully functional) and study the guidance notes in the repo.

Having created your module you will open a ticket on bp trac and upload the module folder zipped along with readme.md and a screenshot, plus a basic description on the ticket of your module. A member of the core contribution team will review the module just to check some basic standards are adhered to and that the module works in respect of a standard WP theme, unless there is a clear statement that the module supports a given theme (preferably supporting a WP theme repo theme)

When the basic checks are finished the module would be included in the styles module repo on BP github and  listed on the  ‘Style Modules List‘ wiki page.

You can read more on the BP github repo and if there are any questions please use the comments in this post.

Users

Installing modules requires creating a  directory to hold them and then downloading the zip from the list link:

Modules are always located in the folder /style-modules/ so to use the members-list-module  you would need to create a folder structure that looks like this:
wp-content/my-theme/buddypress/style-modules/

You will then unzip the module into this style-modules directory.

In the modules readme file will be an example set of functions to enqueue your new modules styles and/or JS files, this is copied to a suitable point in your functions.php file.


We’re looking forward to submissions and are on standby to answer any questions that you may have regarding authoring or using style modules as they become available. Please feel free to use the comments on this post for general questions regarding this initiative or more specific questions can be raised   on the github issues tracker for the ‘style-modules’.