A simple and concise example of a page from the documentation which we, as a community, could readily produce for macOS. Fancy giving us a hand?
We have two options: we can carry on watching the decline in docs, and struggle more trying to solve problems, or we can organise and produce our own docs. No one else is going to do it for us. Want to help?
macOS is now largely undocumented. It’s time to do the job ourselves: what about an open collaborative project?
Is Sierra’s Apple Help on its way out? If not, how does it differ from that documented 8 years ago for Leopard – when the current docs were last revised.
So how can you add proper help to your app? Amazingly, Xcode’s Help doesn’t even mention Help. It’s time to invest in Help Crafter.
JSON is a popular standard for data obtained from internet sources. How well is it supported by spreadsheets? And two major upgrades: Tinderbox 7 and Dash 4.
I was surprised to discover that few books on Swift explain how to use its structured documentation system. No wonder we don’t document our code properly.
Time to pause for breath, I think, for macOS and Xcode. Apple needs to bring the docs up to date, and attend to the detail.
For any company to put more effort and expenditure into its packaging than its documentation is hardly user-oriented.
My iMac has two major flaws: no manual, and no way of removing an optical disk stuck in its drive. Or am I missing solutions?