The Fine Uploader S3 documentation currently lives in the blog. This is a bad place for technical documentation that discusses the API and provides code examples, especially for a complex, detailed, and ever-evolving like S3 support.
I realized that this kind of documentation belongs in the blog even before the Azure module was developed. We should re-organize the S3 feature documentation, following the Azure model. For example, the high-level commentary on Fine Uploader S3 can stay in the blog, along with the step-by-step setup of buckets, IAM users, etc. However, code examples, API details, etc, should be moved onto the docs site S3 feature page. This way, as the API and features related to S3 change, we can be sure that the corresponding S3 feature documentation is versioned alongside the code as well.
@feltnerm I added this to the 5.1 milestone. I think this is important to get a handle on this soon. Let's discuss and SP tomorrow.
It seems like all the stuff under client-side integration would fall under that category (in the docs) whilst (almost) everything else looks like it can exist in the blog
pushed to 5.2
This will hopefully happen as part of 5.3 along with a rewrite of the getting started guide.
I think the docs will simply have to evolve into the docs site over time.