Documentation updates

[werdlerk]

Summary of changes:

• Added Gemfile.lock for the Jekyll static site generator

• Updated layout/styling a bit

  • Changed "Powered by Zilverline" to the Zilverline logo.
  • Moved link to source code to GitHub icon at top right.
  • Enabled site wide search
  • Enabled copy code button for all highlighted code blocks.
  • Added sitemap.xml for better SEO
  • Created new section "Handbook". These contain pages previously from "Reference" which didn't reference an exact technical item to explain. The Reference section now contains only pages that explain technical references.
  • Moved guide for integrating Sequent with Rails to new section "Handbook"
  • Made all pages use the class wide so the pages are wider to display more content.
    On pages that have a TOC, this class is removed so the space on the right can be used for the TOC.

• Updated home page

• Updated all introduction pages

• Updated Rails & Sequent page

[werdlerk]

Question:

• At the page Modelling the domain, an AggregateRoot is created to ensure uniqueness for Author email addresses, called Usernames. This is a Singleton. Why is this named plural? Other AggregateRoots are singular and this being a Singleton, I would expect it also being named Username instead.
• On top of that, as it's defined for the purpose of maintaining usernames (uniqueness of email addresses), would a name like UsernameMaintainer be more adequate?

[lvonk]

• At the page Modelling the domain, an AggregateRoot is created to ensure uniqueness for Author email addresses, called Usernames. This is a Singleton. Why is this named plural? Other AggregateRoots are singular and this being a Singleton, I would expect it also being named Username instead.

Since it is a collection of usernames.

On top of that, as it's defined for the purpose of maintaining usernames (uniqueness of email addresses), would a name like UsernameMaintainer be more adequate?

It depends your domain experts. In this fictional case it was me and I chose Usernames as most appropriate name.

UsernameMaintainer sounds really technical to me, so I think UsernameList or Usernames is better.

[werdlerk]

We need to add a graphic overview of all the steps that the blog application and sequent does for creating an Author and storing an AuthorRecord.
Something like the graphic from the Lars and Bob’s presentation at GOTO Amsterdam (page 34).

[lvonk]

Nice work ❤️ .