Commit Graph

12 Commits

Author SHA1 Message Date
Joe Mooring 723a827fdc Namespace functions and methods 2023-11-04 21:01:42 -07:00
Joe Mooring a3a40ff999 Add return type to functions 2023-09-30 21:03:52 -07:00
Joe Mooring 94a76df291 Adjust table layout 2023-09-05 22:47:18 -07:00
Joe Mooring bbe1dff56a Use sentence case for heading 2023-09-01 09:23:02 -07:00
Bryce Wray acfa0be544 Add hosting provider fetch depth to GitInfo variables page 2023-09-01 09:19:07 -07:00
Joe Mooring bc53ea5ce5 Use sentence-style capitalization for headings 2023-07-13 09:55:39 -07:00
Joe Mooring 98226fe61e Remove orphaned param fron admonition calls (#2042) 2023-04-03 16:29:03 -07:00
Joe Mooring bc3ec033c8 Front matter cleanup (#2039) 2023-04-01 08:29:16 -07:00
Christian Oliff 5636c208bd Grammar and spelling fixes (#1836) 2022-10-07 19:57:44 +09:00
Patrick Kollitsch 963ddc994a docs: add a link to the mailmap documentation
I find that Hugo should contain more links to relevant documentation of features in other tools/documentations. Please let me know if we don't want that and I'll stop. In this specific case I read about `.mailmap` in the Hugo docs and as a developer knew what was meant, but I think less dev-y users might not understand this. Instead of starting to add paragraphs about the format maybe it's ok to link to the features docs? As I said, let me know if that is overkill/bloat. It would make my life easier than seeing a word and googling it :)

(for instance, if we link to git in this case we don't need to add extra-documentation about what the mailmap file should look like and what should be in there)
2021-12-26 17:05:52 +01:00
Bjørn Erik Pedersen 069828db89 Update git.md 2018-08-24 18:57:13 +02:00
Anthony Fok 77578f5bfc Move content/ into new contentDir content/en/
in preparation for adding new translations such as Chinese.

Paths for "readfile" shortcode are adjusted accordingly.

See #461
2018-05-01 11:23:28 -06:00