Over the last year I've been working on a SharePoint implementation in my day job as a contractor. I have a few years' experience doing content management and site collection administration on a SharePoint on-premise instance from a previous role, but this is brand new, SharePoint online, evergreen SAAS where O365 and Azure are important elements. There are a million things to learn, and a million more after that, and then you might, might know enough to say that you know what you're doing.
All of which is very exciting and I have indeed learnt millions of things. However, this has left me with a problem: this blog. AgileDocumentation was always intended to be a blog that was generally about technical writing and specifically about documenting in agile environments. Whilst I'm the Scrum Master/agile coach for the SharePoint project team, and I'm writing lots of documentation - how-tos, instructions, design docs, comms, etc - it's not an agile documentation role. So I haven't blogged much over the last year or so because my mind was on non-agile documentation things.
But I still think of myself as a writer. At my core, what I am, what I do, what I enjoy, is writing. So maybe I can't write about writing as much as I used to, but I can still write about technical subjects. And that's what I'm going to do.
Agile Documentation will still be in its heart a blog about technical writing, and I hope to return to that subject as much as possible. It's just that you might find it's pivoted towards the technical side of SharePoint, with some O365 and Azure thrown in, for a while at least. Think of it as an extended series on getting an enterprise-level content management system set up. That's documentation-related enough for me. For now.