Skip to content

Latest commit

 

History

History
573 lines (332 loc) · 22.6 KB

CHANGELOG.md

File metadata and controls

573 lines (332 loc) · 22.6 KB
Raw

4.1.1

Fixes

4.1.0

4.0.0

Breaking

  • BREAKING: drop support for end-of-life Ruby versions 2.7 and 3.0. The minimum Ruby version is now 3.1.
  • BREAKING: drop support for IE8
  • Upgrade to govuk-frontend v5.7.1 and introduce new Javascript entry point

To upgrade you need to:

  • create a govuk_frontend.js file your project’s source/assets/javascripts directory
  • add //= require govuk_frontend_all into it

Fixes

  • Update gem dependencies.
  • Declare some missing indirect dependencies to prepare for Ruby 3.4. This also resolves some warnings about this at build time.
  • Remove aria-hidden from search label to let assistive technologies see its accessible name
  • Use hidden attribute to show/hide expiry notices instead of just CSS
  • Only use dialog role for table of contents when it behaves like one (accessibility fix)
  • Prevent interactive elements being obscured by sticky table of contents header
  • Only wrap images with alt text in hyperlinks

3.5.0

New features

#344

3.4.0

New features

Fixes

3.3.1

This change solves a potential security issue with HTML snippets. Pages indexed in search results have their entire contents indexed, including any HTML code snippets. These HTML snippets would appear in the search results unsanitised, making it possible to render arbitrary HTML or run arbitrary scripts.

You can see more detail about this issue at #323: Fix XSS vulnerability on search results page

3.3.0

New features

There are some steps you should follow as the Technical Documentation Template (TDT) now uses GOV.UK Frontend 4.4.1.

  1. Update your documentation site to use the latest template version. You can follow the TDT guidance on using the latest template version.
  2. Check your documentation site displays correctly. If your site does not display correctly, you can refer to the GOV.UK Frontend release notes for more information, or contact the GOV.UK Design System team.

Fixes

3.2.1

Fixes

3.2.0

New features

You can now configure your Tech Docs Template (TDT) to build your documentation site to use relative links to pages and assets.

Thanks @eddgrant for contributing this feature and the associated fixes.

This change was introduced in pull request #291: Support sites deployed on paths other than "/" (by generating relative links).

3.1.0

New features

There are some steps you should follow as the Technical Documentation Template (TDT) now uses GOV.UK Frontend 4.0.0.

  1. Update your documentation site to use the latest template version. You can follow the TDT guidance on using the latest template version.
  2. Check your documentation site displays correctly. If your site does not display correctly, you can refer to the GOV.UK Frontend 4.0.0 release note for more information.

3.0.1

Fixes

We’ve made the following fixes to the tech docs gem in pull request #281: Don't break TOC when OpenAPI description includes headers:

  • we now render OpenAPI Markdown with the same Markdown renderer as other documents
  • table of contents (TOC) uses TechDocsHTMLRenderer to render the headings with IDs

Thanks to @jamietanna for contributing to this issue and its solution.

3.0.0

Breaking changes

The search user experience is now more accessible for screenreader users. Search results are now on a separate page instead of a modal window.

Users can no longer see search results as they type. They must press the Return key or select the search button to see the search results page.

This was added in pull request #263: Change search to only show results after submit.

Fixes

2.4.3

2.4.2

2.4.1

2.4.0

2.3.0

2.2.2

2.2.1

2.2.0

Accessibility Fixes

Docs

2.1.1

Fixes

We’ve made fixes in the following pull requests:

Ruby version bump

We've updated the Ruby version supported:

2.1.0

New features

Exclude pages from search engine results

You can now exclude a page from search engine results by including prevent_indexing: true in the page's frontmatter.

This was added in pull request #192: Fixes and improvements to meta tags.

Fixes

We’ve made fixes in the following pull requests:

2.0.13

2.0.12

2.0.11

Fixes

2.0.10

Fixes

2.0.9

Fixes

2.0.8

Use of govuk-lint replaced with rubocop-govuk due to the former becoming deprecated.

2.0.7

A small release to fix an issue where code blocks font size was too large on some browsers.

See pull request #131: Improve code font sizing for details.

2.0.6

This release contains accessibility fixes:

  • anchor header links are now properly hidden to assistive technologies
  • side navigation items now have consistent visible focus when tabbing between them
  • side navigation items have unique Ids
  • code elements now scale properly when you enlarge your text
  • links with code elements now look correct
  • contribution links are now within a landmark

You can look at the 2.0.6 milestone for the closed issues, and pull request #129: Accessibility improvements for details on how these issues were fixed.

2.0.5

Adds new global configuration option that controls whether review banners appear or not at the bottom of pages when expiry dates are set in the frontmatter.

Fixes the hard-coded service link in the header.

Selectively include only the CSS for the GOV.UK Frontend components that we are using, to reduce the size of the CSS file served to the user (#118)

Fix service name to link to the configured service_link, rather than being hardcoded to / (#119)

Add the show_review_banner global configuration option allowing users to hide the page review banner.

2.0.4

Adds footer_links option for displaying links in the footer and ability to hide pages from left hand navigation.

2.0.3

Fixes a couple of styling issues: #100 and #106.

2.0.2

This fixes ensures all assets from govuk-frontend are bundled; we were missing some PNG, SVG and ICO files.

2.0.1

This fixes an issue where Travis CI wasn’t packaging up the gem with the govuk-frontend module. Without this the tech-docs have no css styles.

2.0.0

This release adds GOV.UK Frontend (part of the GOV.UK Design System) and remove the legacy framework GOV.UK Frontend Toolkit. This required a lot of markup being ported over to use the design system’s markup and all custom CSS to use new variables and mixins.

Custom components such as the table of contents (toc) were updated to use the WCAG 2.1 AA compliant focus states too.

It was also necessary to upgrade the Ruby version to 2.6.3 so that we could bump the gem versions of govuk_lint, rubocop and sprockets. The new version of sprockets allowed us to pull through assets from node_modules/govuk-frontend without having to manually include them as was the case before with govuk_frontend_toolkit.

1.8.3

Fixes bug where search results disappear when opening results in a new tab, making it difficult to open several results in a batch (PR #86).

1.8.2

Adds a show_expiry config option to allow you to choose whether to show the review due date and expired banner from your pages. Find out more about the page expiry and review feature.

1.8.1

This release fixes a bug (#79 - reported in alphagov/tech-docs-template#183) which prevented a multipage site from being generated when a custom http_prefix was configured.

1.8.0

🎉 Our first contributor from outside of GDS. Thanks @timja from HMCTS! 🤝

New features: you can now configure a different GitHub branch for the repo to generate the "View source" link in the footer. Use github_branch in your config file (#71). You can also specify a full_service_name in the config, which is used in the browser title and meta tags (#72).

This version also fixes a bug with unclickable links (#74 - reported in alphagov/tech-docs-template#123).

1.7.0

New features: this release adds support for a full-width page (#63) and adding HTML to the head of the page (#64).

This release also makes sure that all pages are returned in the /api/pages.json endpoint (#66).

1.6.3

The gem now uses middleman-search-gds rather than middleman-search, which removes the need for projects to point to the alphagov github repository in their Gemfiles. We will continue to maintain our own fork until the changes are merged into the upstream project.

1.6.2

This version fixes an issue with Middleman hanging (PR #54). It also allows the API reference page to include multiple servers and their descriptions (PR #53).

1.6.1

Make api_path configuration optional

A bug in the previous release prevented the docs from being generated if api_path was missing. This is now fixed.

1.6.0

Version 1.6.0 adds API reference generation, and improves the search function.

New feature: API reference

Specify an OpenAPI spec file using api_path, for example: api_path: source/pets.yml.

To output the generated content in the page of your choice, write api> in any markdown parsed file (.md, .html.md, .html.md.erb). You can also specify to just print a specific path: api> /pets

This generates request and response schemas and examples for each API operation.

More info:

Search result improvements

The search indexing pipeline has been tweaked to provide expected results. The display of the search results has also been

If you're using search then you'll need to add this line to your project Gemfile:

gem 'middleman-search', git: 'git://github.com/alphagov/middleman-search.git'

More info:

Correct fork of middleman in example project

The example gem project now uses alphagov/middleman-search. This prevents bundle exec middleman serve from crashing.

More info:

Accessibility improvements

Accessibility improvements to search, collapsible navigation, and the logo.

More info:

Additional configuration options for review system

default_owner_slack and owner_slack_workspace are now configurable for use within the review system.

More info:

Correct fork of middleman in example project

The example gem project now uses alphagov/middleman-search. This prevents bundle exec middleman serve from crashing.

More info:

Accessibility improvements

Accessibility improvements to search, collapsible navigation, and the logo.

More info:

Search result improvements

The search indexing pipeline has been tweaked to provide expected results. The display of the search results has also been improved.

If you're using search then you'll need to add this line to your project Gemfile:

gem 'middleman-search', git: 'git://github.com/alphagov/middleman-search.git'

More info:

1.5.0

New feature: Search

Adds search functionality. This indexes pages only and is not recommended for single-page sites. To enable write enable_search: true in in tech-docs.yml.

More info:

Google Analytics tracking for old headings

An event category 'Broken fragment ID' will be pushed to Google Analytics when a user lands on a page with a URL that points to a fragment ID that does not exist on the page.

More info:

1.4.0

Adds multiple page navigation support and collapsible top level navigation items. When enabled the table of contents will display other pages on the site.

More info:

1.3.1

Minor update to Google Analytics tracking

More info:

1.3.0

Version 1.3.0 contains accessibility fixes (#20) and a fix to make the site more robust when certain options aren't set in the configs (#17).

New feature: passing options to GovukTechDocs.configure

You can now pass options into GovukTechDocs.configure for the livereload extension.

GovukTechDocs.configure(self, livereload: { js_host: 'localhost' })

See PR #18.

New feature: page parents

You can now specify a page’s parent in its frontmatter. This affects which item is selected in the navigation.

More info:

1.2.0

New feature: redirects

You can now specify redirects in the frontmatter and config/tech-docs.yml.

You can use this when you change a page URL.

More info:

New feature: contribution banner

You can now show a block at the bottom of the page that links to the page source on GitHub, so readers can easily contribute back to the documentation.

https://github.com/alphagov/tech-docs-gem/blob/main/docs/configuration.md#show_contribution_banner

New feature: page review system

An optional page review system to make sure documentation stays up to date.

More info:

Better meta tags

Pages now include better meta tags for search engines, Twitter, Facebook and Slack to pick up.

1.1.0

You can now specify google_site_verification in tech-docs.yml. You can use this to verify your site in Google Webmaster tools.

https://github.com/alphagov/tech-docs-gem/blob/main/docs/configuration.md#google_site_verification

1.0.0

The first release of the template as a gem. Most CSS, JS, images and layouts are now imported from the gem and can be removed from your project.

The following script upgrades your project. This will work if you've not made any modifications to the files distributed by the template. If you have, you'll need to port your changes back in.

rm -rf lib source/images source/layouts source/favicon.ico source/javascripts/* source/stylesheets/*

echo "//= require govuk_tech_docs" > source/javascripts/application.js
echo "@import 'govuk_tech_docs';" > source/stylesheets/screen.css.scss

echo '$is-print: true;

@import "govuk_tech_docs";' > source/stylesheets/print.css.scss

echo '$is-ie: true;
$ie-version: 8;

@import "govuk_tech_docs";' > source/stylesheets/screen-old-ie.css.scss

echo "require 'govuk_tech_docs'

GovukTechDocs.configure(self)" > config.rb

echo "source 'https://rubygems.org'

# For faster file watcher updates on Windows:
gem 'wdm', '~> 0.1.0', platforms: [:mswin, :mingw]

# Windows does not come with time zone data
gem 'tzinfo-data', platforms: [:mswin, :mingw, :jruby]

gem 'govuk_tech_docs'" > Gemfile

bundle install