Commit 22be387c authored by Jamie Tanna's avatar Jamie Tanna

Update Table of Contents for Goldman Markdown

As part of #843 we're upgrading past Hugo v0.60 which introduced Goldman
as the Markdown handler, which has changed the way that the Table of
Contents is handled:

- we need to explicitly set the headings to include
- we want a `<ul>` not an `<ol>`
- we need to remove the manual `<a name>` as it's autogenerated now (and
  has been for some time)
- some `<a name>`s have been updated
parent 0c228f16
......@@ -85,6 +85,10 @@ notAlternative = true
[markup.goldmark.renderer]
# allow inline HTML, such as spoiler warnings
unsafe = true
[markup.tableOfContents]
startLevel = 1
endLevel = 6
ordered = false
[menu]
[[menu.main]]
......
......@@ -136,7 +136,7 @@ So once you've actually made your changes, you need to be able to send it back t
If you're looking at getting started and would like some help, feel free to drop me a message in one of the formats in the page footer.
## Hacktoberfest Session <a name="hacktoberfest-session"></a>
## Hacktoberfest Session
On 6th October, I am running a [Git Workshop][git-workshop] which will serve as an introduction to Git and version control. In the interactive section of the workshop, I will be taking Hacksoc members through their first contribution - through a Pull Request to a blog post about Hacktoberfest on the Hacksoc website. The initial Pull Request can be found [on GitHub][hacksoc-repo-hacktoberfest-pr].
......
......@@ -116,7 +116,7 @@ __2014-2015__ - Industrial Placement as Application Engineer at Intel, Reading
- Spent more time working on automation pieces like [Docker Build System for Android on Intel Architecture] which I enjoyed more than the day job
- Found that it wasn't quite what I wanted to do, at the end of the day
- But that's _great_! I was able to tick something off the list
- Deciding what you part of tech want to move into is such a massive list, it's great to at least have one less choice (for more choices, see [There's more to Tech than just "regular software engineer"](#there-s-more-to-tech-than-just-regular-software-engineer))
- Deciding what you part of tech want to move into is such a massive list, it's great to at least have one less choice (for more choices, see [There's more to Tech than just "regular software engineer"](#theres-more-to-tech-than-just-regular-software-engineer))
- Got a year's experience and some pay, as well as being able to travel and network
- Solving real problems with real clients
......
......@@ -18,7 +18,7 @@ I'd like to call out that this is not due to a negative experience, nor any issu
The decision was made in late September, but as I've not yet had the chance to write up the reasoning, I thought I'd leave the announcement until I could explain the factors that led to the decision.
As mentioned in the write-up of my talk at [_DevOpsDays London 2018_]({{< ref 2018-10-25-devopsdays-london-2018 >}}#overengineering-your-personal-website-how-i-learn-things-best), I found that writing the transcript for my talk was stressing me out. Reflecting on this a little made me realise realise I'd not been enjoying that aspect of preparing my Packt courses.
As mentioned in the write-up of my talk at [_DevOpsDays London 2018_]({{< ref 2018-10-25-devopsdays-london-2018 >}}#overengineering-your-personal-website---how-i-learn-things-best), I found that writing the transcript for my talk was stressing me out. Reflecting on this a little made me realise realise I'd not been enjoying that aspect of preparing my Packt courses.
One of the saving graces of conference or meetup speaking is that you don't have to be 100% perfect in your delivery. You can mumble some words, miss a bit of the content you wanted to share, or just say the wrong thing and then correct yourself!. Although you obviously want to have a well delivered and informative talk, it doesn't need to be perfect. You also don't need your words to perfectly match a pre-written script, as I found with my transcript actually just being a guide for the live signing and closed captioning to understand the words I would roughly be using.
......
......@@ -30,7 +30,7 @@ The final great thing about this is that it gives pure programmatic access to th
You can follow along on [my issue tracker's label `microservices-site`][issues].
[DevOpsDays talk]: {{< ref 2018-10-25-devopsdays-london-2018 >}}#overengineering-your-personal-website-how-i-learn-things-best
[DevOpsDays talk]: {{< ref 2018-10-25-devopsdays-london-2018 >}}#overengineering-your-personal-website---how-i-learn-things-best
[Talks]: /talks/
[Projects]: /projects/
[Blogroll]: /blogroll/
......
......@@ -134,7 +134,7 @@ What do you want to achieve with it? Which of the above particularly won you ove
Then, it's worth looking at whether you want to potentially have some server maintenance, and use a dynamic site software like [WordPress](https://wordpress.org), or [Known](https://withknown.com/), or are happy to use a [Static Site Generator](https://www.staticgen.com/), which does not necessarily require a server.
Once you have an idea of the tool, it's worth looking at designs, and seeing if there are any themes that you'd be happy using (see [_The site's design_ section below](#the-site-s-design)).
Once you have an idea of the tool, it's worth looking at designs, and seeing if there are any themes that you'd be happy using (see [_The site's design_ section below](#the-sites-design)).
## Inspiration
......
......@@ -258,7 +258,7 @@ But this also means that you need to architect your applications in the right wa
- they should be able to restart cleanly
- state should not be stored in the application, otherwise sticky sessions make things a whole lot more complicated for scaling
Nicky spoke about the ability to very easily perform a cross-region failover automagically. Nicky spoke about the importance of testing these things before they go bad, which [Euan Finlay's talk _Don't Panic_ at last year's DevOpsDays London]({{< ref "2018-10-25-devopsdays-london-2018" >}}#don-t-panic) goes into in a bit more depth.
Nicky spoke about the ability to very easily perform a cross-region failover automagically. Nicky spoke about the importance of testing these things before they go bad, which [Euan Finlay's talk _Don't Panic_ at last year's DevOpsDays London]({{< ref "2018-10-25-devopsdays-london-2018" >}}#dont-panic) goes into in a bit more depth.
Nicky warned us against the care required in performing these failovers, and ensuring that the new stack doesn't get infected by the same root cause as the first, leading to both becoming unhealthy or failing altogether! Nicky recommended that to avoid this, you should run a rolling update to be able to ensure that only a few instances are affected at a time, giving you a chance to validate the change before switching more over.
......@@ -719,4 +719,4 @@ We talked a little bit about monolithic applications and how to split them down,
One participant shared the talk [From Monolith to Microservices and back](https://www.youtube.com/watch?v=0jODVkkwiMc) that talks through some of the reasons you would actually want a monolith.
It's also worth a read of [the Open Space _What's wrong with a good monolith?_ at DevOpsDays London 2018]({{< ref "2018-10-25-devopsdays-london-2018" >}}#what-s-wrong-with-a-good-monolith).
It's also worth a read of [the Open Space _What's wrong with a good monolith?_ at DevOpsDays London 2018]({{< ref "2018-10-25-devopsdays-london-2018" >}}#whats-wrong-with-a-good-monolith).
Subproject commit 1a037a8d2985203587d0113c7ecb97fcce0f72d1
Subproject commit 79d54b976864d476ecf9964d31ff0b7f3f11ca8f
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment