Log in, sign in

Log in, sign inI recently experimented with writing a new 401 page for the IndieWeb wiki to replace the default nginx page we have. My experiment is not live yet, but I wanted to document a few of the decisions I made while writing the page.First, I chose the title “You need to be logged in to see this page” which both conveys that the user cannot view the page and why (they need to be signed in). Second, the log in button is prominently placed on the page so that a reader can navigate to the log in page. Third, I used “logged in” and “log in” consistently, instead of also using “sign in”.In my first draft of the page, I used “sign in” in the document title and “log in” on the document. I did this primarily because both terms are so similar and they happened to come to mind as I was writing each section. But then I realised that using two terms to convey the same thing was not necessary – why use two terms when one will do?This got me thinking about the design of Artemis. Artemis uses…