2 ms·
We did exactly this and it's been great. We started with our content editors just using WordPress and on one project we transitioned them to using Kramdown insi
by busterarm 9y ago
We did exactly this and it's been great.
We started with our content editors just using WordPress and on one project we transitioned them to using Kramdown inside WordPress to build a Jekyll site. Once they were familiar with both, the next project we gave them Jekyll and they can enter content and meta info via Forestry.
Forestry has been a big help to us with support and quick turnaround for feature requests and it's been pretty smooth-sailing for our content team.
For internal documentation/knowledge-sharing, we started a MediaWiki.
- danpalmer 9y agoYep. We use MediaWiki for internal documentation, particularly for the support team, and we use FeinCMS (a Django CMS/blogging package) for our “tips” blog. Unfortunately neither of these work for obscure internal data models that we have, or the time to integrate one isn’t worth it for an A/B test we might throw away next week (although if we decide to ship the A/B test we would take that time to integrate a CMS or add an editing interface on top of our DB).
- busterarm 9y agoI actually do like A/B tests in Git, especially if you have great commit messages and tags around this, because there really should be a historical record of all experiments that have been run. Throwing them away is a tremendous waste of knowledge. We found this to be true with our marketing and that was the reason for the push to setting up a Wiki. Even if we don't retain code around an experiment, we have a documentation format for recording what we made, what our expectations were and our results.
- danpalmer 9y agoI mean more about the data required for an A/B test. For example, we want to test showing a set of images on a page. Some users get set A, some get set B, some get none, and images need to be changed weekly. The list of image URLs might be in a file in git, and get changed by a product manager each week for the duration of the test. The A/B test would be run by our A/B testing service, which stores historical tests and reports indefinitely. We’d then come and move the URLs into the database and add an editing tool later on if we decided to ship the A/B test.