* build: move frontend assets to Bootstrap 5.3 and Tom Select
* feat: migrate templates and scripts to Bootstrap 5, dropping jQuery
Templates
- Rename Bootstrap 4 classes and data attributes (data-bs-*, ms-/me-/ps-/pe-,
text-start/end, form-group -> mb-3, input-group wrappers removed, badges,
custom controls -> form-check/form-select, media -> d-flex, btn-close, ...)
- Dark mode now uses Bootstrap 5.3 colour modes (data-bs-theme on <html>),
set from <head> to avoid a flash of the light theme
- Remove the Bootstrap 4 /bootstrap/ demo page
- Contextual table classes (table-success etc.) still work as plain
backgrounds for the rigboard key
JavaScript
- Remove jQuery: src.js/interaction.js and every inline template script are
rewritten in plain JS on top of small helpers (helpers.js, bundled with
Bootstrap into jpop.js so inline scripts can use them)
- Replace bootstrap-select/ajax-bootstrap-select with Tom Select. The remote
search now sends the `q` parameter and reads `text`, which is what the
API actually uses (the old picker sent `term` and read `label`)
- HTML fragments are fetched with an X-Requested-With header so views keep
rendering their modal variants, and fetched scripts are re-executed
- Remove the Bootstrap 4 plugin script includes
* fix: stop rigboard header buttons stretching to full width under Bootstrap 5
* fix: restore dark-mode brand colours and contextual table colours under Bootstrap 5
* fix: brighten dark-mode links and make coloured card outlines visible
* fix: calendar layout and grid borders, navbar search button width, guard missing modal links
* fix: readable text in dark-mode Tom Select inputs and placeholders, restore form-control column widths
* build: split the Dockerfile into cached stages with prod and dev targets
* deploy: make compose.yml development-only with live reload, and document it
* fix: keep badge text colour for links inside badges
* fix: restore table-bordered grid lines in dark mode
* fix: include Bootstrap's progress styles and keep progress labels readable
* Add basic markdown support site wide
* Improved MD support.
Add some styling for images in MD
Add support for the bastardisation of the MD html for RML.
* Add processing for <ul> in RML
* Add OL processing to RML
* Fix a bug with squares appearing around the last page number
* Remove rml formatting in event_detail
* Improve handling of code blocks in RML
* Add MD to rigboard
Reduce MD title sizes as they were offensively large
* Add parsing of markdown when editing event items
* Improved list handling in RML
* Add tests for markdown support.
Focuses mainly on RML as that's where it will break
* Add indications of where MD support is enabled as per comment by @samozzy in #178.
Isn't quite a full description, but for the most part this should be enough for the people who know how to use it see where they can use it.
* Add failing test for markdown processing none
* Fix for failing test in e0d56e
* Add failing test for using single line breaks as per comment on #214
* Enable line break extension for single breaks in paragraphs by new lines.
Pass tests in ef3de607c3
* Enable GH flavour linebreaks in JS rendered markdown
* Made RML bullets pretty :)
* Added WYSIWYG editor. Works for notes & description, fails miserably for items :(
* Fixed for event items. Will probably fail tests because selenium can't type in simpleMDE :(
* FIX: Re-enable markdown on paperwork
Strikethrough is broken in all sorts of places for whatever reason
* FEAT: Markdown support on asset comments
* FIX: Prevent js injection through markdown fields
* Initial fixes
* Basic dark theme for simplemde
* Swap to locally delivered SimpleMDE
* Region for selenium testing of SimpleMDE
Bleh, Javascript all around
* Tests passing!
Fixed not using region for item modal, and overflow error on paperwork with really long description. Looks junk but I'm not really bothered
* Pep8 fixes
* Fallback for null HCapatcha sitekey
I.e. when we're on a branch
* Fix item description print being broken
* Actually fix sitekey problem
* Fixes for using markdown in asset comments
* Properly initialise markdown on asset comments
Co-authored-by: David Taylor <david@taylorhq.com>
Co-authored-by: FreneticScribbler <aj@aronajones.com>