V401.1.12

Changes.md

@@ -1,3 +1,53 @@
+Change Log in version 401.1.12 (2022112314)
+===========================================
+1. Fix 'itemid' not being regenerated for 'customjsfiles'.
+2. Reduce drawer flicker on page load when the navbar is sticky.
+3. Add ability to move custom menus into a single menu to save navbar space by giving 'custommenutitle' setting a value.
+   Note: At bottom of the 'Navbar' settings tab.
+4. Improve custom menu code to facilitate simple inclusion of Font Awesome icons.
+5. Fix dropdown menu id's.
+6. Remember the tab currently selected when saving settings.
+7. Functionality using a 'custom menu' such as 'Custom menu items', 'Header menus' and 'Tools menu' now supports the
+   following format:
+    text|url|title|langs|fontawesome classes or name|capability.
+   where:
+     text - Text to show for the entry.
+     url - URL of the entry.
+     title - Title attribute in the link tag value.
+     langs - Only show on the given language codes - separate more than one with a comma.
+     fontawesome classes or name - State the Font Awesome classes or name for the icon that is placed before the text.
+     capability - State the capability to check that the user has on the page before showing, for example
+       'moodle/course:manageactivities' to only show to editing teachers.
+8. Renamed 'Tools menu dropdown' setting tab to 'Tools menu'.
+9. Add 'customusermenuitems' to the user menu.
+10. Add FontAwesome support to 'customusermenuitems' as the third parameter, name or CSS classes.
+11. Add duplicate entries for 'custommenuitems' and 'customusermenuitems' on a new 'Custom menu' settings tab.
+12. Settings language strings tidy.
+13. Social icons improvement to use either icon name or CSS classes.
+14. Replace 'menuhovercolor' with 'menubkhovercolor' and 'menufonthovercolor' to fix menu hovering.
+15. Add 'courseindexenabled' setting on the 'Course index' tab to enable / disable the 'Course Index'.
+16. Fix header information overridden when set in the context header leading to missing output.
+17. Add 'Information blocks'.  This is designed to be a replacement for the marketing blocks that are
+    now deprecated.  The code that they use has always been problematic and subject to contained file
+    based content being lost on occasion, or rather not lost but misplaced in terms of linkage at times.
+    I've never been able to entirely rectify or resolve the issues.  Therefore instead of reinventing the
+    wheel, I've gone for a block region based solution whereby proven and tested block code is employed.
+    Instead of defining the content in the theme settings, you'll create blocks and place them in the
+    'information' region on the front page.  Of course you'll find all of the other settings in place
+    to control the layout and visiblity as before, on the theme's 'Information blocks' settings tab.
+    When editing you'll see the full block header with each block having the same width to allow easy
+    manipulation, i.e. the layout you set is not applied.  Its only when editing is off that the layout
+    is applied and the block titles removed.  If you see the word 'Overflow' then that means that you have
+    more blocks than you've defined in the layout rows to allow.  Admins will see 'Marketing blocks are
+    deprecated, please migrate to using the Information block region.'.  When editing, block regions will
+    have their name at the top.  In testing with re-ordering the blocks I did find this problematic and
+    could not work out entiry why as the theme code is doing what it should do, the core code is telling
+    the backend via an AJAX call about the reordering, just that after doing so then it seemed that cron
+    had to run for the changes to become permanent.  It is my intention that other settings employing the
+    same code as the marketing blocks will also migrate to this improved solution.
+18. Improve the look of the calendar block controls and fix the next and previous icons.
+19. Improve the layout builder to have new clearer responsive images.
+
 Change Log in version 401.1.11 (2022112312)
 ===========================================
 1. New setting 'mobileprimarynav' to control the display of the mobile primary navigation.  This is found on the

Support.md → SupportAndSponsorship.md

@@ -13,11 +13,30 @@ If you would like to sponsor me, get support or fund improvements, then please d
 - GitHub | Please outline your issue / improvement on '[Adaptable issues](https://github.com/gjbarnard/moodle-theme_adaptable/issues)'.
 - @gjbarnard | [X](https://x.com/gjbarnard).
 
-Bespoke work
-------------
+Sponsorship information
+-----------------------
+By becoming a sponsor you help to keep the theme alive and working as underlying technologies change and the core Moodle software moves
+forward.  In return I’ll provide you access to additional functionality for the theme and prioritise questions from sponsors through a
+sponsors only area on GitHub.
+
+Sponsorship is not support or a contract to provide such, nor is it a commitment to provide updates, future versions or improvements.
+What it is though is an incentive to me to keep the theme going and maintained, and intend to do so for as long as possible.
+
+How much you offer for sponsorship is up to you to decide and for us to then agree upon based upon the use and value of the theme to you.
+Sponsorship can be a one off payment or many payments over time, the choice is yours.
+
+Please contact me using the details above along with how much you'd like to offer and an outline of who you are and how much you
+use the theme.  I will then outline the steps that need to be taken so that you can become a sponsor.  Note that I can only do
+business to business transactions.
+
+Improvements and bespoke work
+-----------------------------
+Adaptable is already a complicated theme and therefore I am reluctant to add any major features, indeed my aim is to reduce the
+complexity without actually removing functionality.  There is though the possibility of improving what is already there and / or
+creating a child theme that adds the specific functionality that you require.
 
 If you would like your own customised version or a new child theme of Boost / Classic, then typically with a setting and a few style
-changes this is usually two to three hours work.  At my current rate this will be between 88 and 132 GBP.  I charge by the minute with
+changes this is usually two to three hours work.  At my current rate this will be between 94 and 141 GBP.  I charge by the minute with
 a minimum time of fifteen.  Please contact me for further details with an outline of what you would like.
 
 Open source software