Skip to content
Snippets Groups Projects
  1. Mar 30, 2022
  2. Mar 02, 2022
  3. Feb 08, 2022
  4. Feb 04, 2022
  5. Sep 20, 2021
  6. Aug 20, 2021
  7. Aug 18, 2021
  8. Jul 08, 2021
  9. Jun 23, 2021
  10. Jun 18, 2021
  11. Sep 14, 2020
  12. Sep 11, 2020
  13. Aug 26, 2020
  14. Aug 13, 2020
  15. Aug 11, 2020
    • PLanCompS's avatar
      Separate sorting of numbers and strings for navigation order · 4fc59a57
      PLanCompS authored
      The values of `title` and `nav_order` can be numbers or strings.
      Jekyll gives build failures when sorting on mixtures of different types,
      so numbers and strings need to be sorted separately.
      
      Here, numbers are sorted by their values, and come before all strings.
      An omitted `nav_order` value is equivalent to the page's `title` value
      (except that a numerical `title` value is treated as a string).
      
      The case-sensitivity of string sorting is determined by `site.nav_sort`.
      4fc59a57
  16. Aug 10, 2020
    • PLanCompS's avatar
      Ensure pages with nav_exclude are ignored by navigation · 83ec5533
      PLanCompS authored
      Pages with `nav_exclude: true` were included when sorting on `title` or `nav_order`. That could cause build failures when the type of value of the field differs from that on other pages, as reported in https://github.com/pmarsceill/just-the-docs/issues/406.
      
      Pages with `nav_exclude: true` or no `title` are never displayed in the navigation, so removing them from `pages_list` cannot break existing sites. This change also allows the removal of some tests in the code. (The indentation of the code should now be adjusted, but that has been deferred, to restrict the size of the diff for review.)
      
      For testing, the title of `404.html` has been changed to the number `404`,  the page `docs/untitled-test.md`  has been added, and `nav_sort_order` has been set to `case_sensitive`. Those updates give build failures with the current version of `_includes/nav.html`, but not after the suggested changes.
      
      It will still be possible for build failures to occur due to sorting fields of *non-excluded* pages with differing types of values (e.g., `nav_order`a mixture of numbers and strings). To make the code completely safe will require relatively complicated changes,.
      83ec5533
  17. Jul 07, 2020
    • PLanCompS's avatar
      Major refactoring · 61053f67
      PLanCompS authored
      The additions to `_config.yml` go together with the changes to `code.scss`,
      to facilitate adjusttments by users. See `docs/linenos-test` for the details.
      The CSS code has been significantly refactored and simplified,
      and seems to produce sensible results (at least on Safari and Firefox).
      61053f67
  18. Jun 25, 2020
  19. Jun 18, 2020
  20. May 01, 2020
  21. Apr 27, 2020
  22. Apr 25, 2020
    • PLanCompS's avatar
      Made case-insenstive sorting the default · c46ccd34
      PLanCompS authored
      Added a configuration option to determine whether the sort order is case-sensitive.
      The default is case-insensitive.
      
      To test:
      - open `/just-the-docs/docs/utilities/` in the browser,
        and check that the navigation links in `Utilities` are sorted alphabetically;
      - in `docs/utilities/layout.md', change the preamble to `title: layout`,
        and check that the  links in `Utilities` are still sorted alphabetically;
      - add `nav_sort: case_sensitive` in the configuration file,
        and check that the link to `layout` is now listed last under `Utilities`.
      c46ccd34
  23. Apr 24, 2020
  24. Mar 24, 2020
  25. Jan 12, 2020
  26. Jan 02, 2020
  27. Dec 29, 2019
Loading