3 ms·
Square peg in a round hole. It sounds "non-engineers" means content managers and they just invented a really crummy CMS. Surely they could at least use Jekyll o
by tootie 9y ago
Square peg in a round hole. It sounds "non-engineers" means content managers and they just invented a really crummy CMS. Surely they could at least use Jekyll or something and let the content managers use markdown. They're shifting the cost of dev time to content management resources when they could just spend some cash on a commercial CMS like Contentful or Prismic that is easy to configure and far safer and more scalable.
- busterarm 9y agoWe 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.
- danpalmer 9y agoWe actually have various CMSs for content like blog posts and human readable text. We use the solution in the article for things like the current delivery estimate, which changes twice a year and is a Python timedelta object (example, but more complex than that) or adding new tags to our support ticket system (not user facing). For those, we don’t want or need to spend the overhead of making an editing interface. As for integrating another CMS, the whole point is that it’s just Python files in the repo, zero effort for developers, very little effort for everyone else, when editing is infrequent.
- WorldMaker 9y agoI find it interesting that you mention you are using Django, since my feeling has always been that easy/dumb/quick CMS CRUD interfaces has long been its bread-and-butter, especially the Django Admin. That said, I don't question the benefits of version controlling data, and the usefulness of GitHub's web interface for quick and dirty commit work. I am surprised that a quick search doesn't seem to turn up someone already trying to build a NetlifyCMS-like tool for inside the Django Admin. That seems like a natural fit for Django's CRUD philosophies.
- danpalmer 9y agoWe use a Django admin based CMS for part of our product, but most CMS solutions are about things like blog posts or knowledge bases, not for complex data models and changing configuration of an application (like our current shipping estimate). Building editing interfaces in Django is relatively straightforward, but by not doing it we can save hours, maybe a day, and that’s worth it if we’d only use the editing interface for 5 minutes a month, or are testing a new thing that we might throw away in a week.