I'm interested in demonstrating some common practice and use cases for Umbraco, and have agreed in principle to a series of 4 Skrift articles where I'll collaborate with volunteers to explore different ways of achieving different client briefs.
This series of 4 articles will give a Dev (or Devs) an opportunity to develop a solution to a brief that I agree with the Skrift Editorial Team (Janae, Erica and Kyle). The brief should be a constrained feature of a larger project, e.g. a page type in a wider site, not the whole site!
Ideally we'll find volunteers for the design, front end and back end, but where that's impractical I'll supply front end code from a template.
Volunteers for solution design and build could be from the same agency or employer, but ideally we'll have one or two reviewers that offer constructive feedback and alternative approaches they would take.
The intent is a completely positive experience where we discover different ways of approaching problems that Umbraco typically solves. We're not establishing "Best Practice" and we're not critical of the work, instead we discuss the merits of different approaches.
The article will follow a formula, where a brief is presented, solution discussed by the contributor, reviewers feedback and I wrap up.
I'd like to give an opportunity to appear in Skrift to those people who wouldn't normally consider themselves a writer. I'll support them through the process, and do the heavy lifting in terms of the technical writing. They can focus on developing a solution to the problem in the best way they know how, I'll help them to describe the solution for the reader.