Never ones to rest on our laurels, here’s our new website. In my previous post (originally for our customers’ eyes only, but now public) I promised that, by way of thanks for their helpful feedback, we’d have a new documentation site up and running in the first half of this year. Well, it’s two weeks later, and here it is. And it’s not just a new documentation site. You’ll find our blog (with many archive posts rescued from the Wayback machine after the Digital Book World blog shut down) and useful information about Bibliocloud all in one place. This speedy development is thanks in no small part to the sort of tools that are available to programmers nowadays.

Our new website is a Middleman app, a static site generator. Hosting and a ton of amazing deployment features are provided by Netlify, the single best web app of any type I have ever used. Effortless DNS management comes from DNSimple, and a really great new search is provided by Algolia Docsearch. We’ve got a direct integration with our CRM tool, Pipedrive, on the Request a demo page, which helps us to get back to prospective customers quickly. Testing is done with Rspec, and git version control is done by Bitbucket, which has a Continuous Integration, erm, integration with Netlify which builds and deploys the static HTML and CSS files each time we push the code to the master branch. (And, as a minor point of personal pride, we wrote it without any CSS framework, or jQuery.)

All these bulletproof tools mean we have been able to write this website from scratch in our spare time in two weeks. It’s a work in progress, but the structure is in place to build what we hope will be the best bibliographic software website, bar none.

For example, we’ll post news about our new style guide in due course, once we’ve applied all the rules to our existing content. This style guide builds on and complements our component library and brings the sort of consistency of language, tone, colour, typography and more that makes our documentation and application straightforward to use, search, read and understand. Here’s to consistency and harmony!

We’ll also be refining the documentation search, in particular. It’s fresh out of the box at the moment: we’ll be refining it to make sure the top results remain the most relevant, over time. We’re delighted with its speed, relevance and coverage already.

22.49.54

We’ve started to post regular product updates on the blog, too, so do subscribe to our feed or bookmark our blog to keep up to date with product news, as well as our musings. The whole team pitch in with thoughts and contributions, so you can look forward to hearing news from a combination of Sara, Dave, Andy, Rob and me.

I hope you enjoy having a look, and seeing how it unfolds. We’re looking forward to it, too!

Archives

    Most popular

  1. Ruby code and why you should care
  2. A quick look at data visualisation and analysis
  3. Menial publishing jobs are destroying our future
  4. It's us in the industry who need to be able to code
  5. A manifesto for skills
  6. Learning how to code, the long way around
  7. Company news

  8. New website
  9. 2018 Customer survey report
  10. 2017 in review
  11. Sara O'Connor to join the team!
  12. And now we are five
  13. Prizes galore
  14. Product news

  15. 'Continuing to solve real problems': Futurebook 40, London Book Fair 2018 and the Works page
  16. How many authors is too many?
  17. Better ONIX fragments
  18. Advanced advance information!
  19. Schedules page
  20. Publishers hack their own bibliographic data
  21. Case studies

  22. Burleigh Dodds Science Publishing
  23. Zed Books
  24. IOP Publishing
  25. Code

  26. A publisher’s guide to APIs
  27. What publishers need to know about Ruby on Rails
  28. How APIs can make publishing more efficient
  29. A day in the life of a programmer
  30. eCommerce

  31. To go direct, publishers must mean business
  32. Don’t outsource your publishing business away
  33. Who has the balance of power over data?
  34. Inbound marketing
  35. The business case for going direct
  36. Why publishers must use direct sales
  37. ONIX

  38. A hidden benefit
  39. Thema Subject Codes Update November 2017
  40. ONIX. Not very standard
  41. Three ways to do more with ONIX
  42. A non-technical, beginners’ guide to ONIX for Books
  43. ONIX Changes
  44. BIC, Thema and artificial intelligence...
  45. How to create a catalogue automatically using ONIX and InDesign
  46. Skills

  47. Embrace the code
  48. Mechanical sympathy
  49. Publishers can learn a few things from programmers
  50. A taste of code
  51. Strategy

  52. Rejuvenation
  53. Why ‘easy’ publishing solutions hardly ever are
  54. The right tool for the job
  55. No computer system can fix a broken publisher
  56. Five things I've learned since moving into enterprise product management
  57. Managing expectations
  58. Start with Why – How to refine your publishing mission
  59. The real price of a strategy shift
  60. Technical debt
  61. Decisions, decisions
  62. Creative industries and the division of labour
  63. A company of one's own.
  64. Responsibility, Authority, Capability
  65. Sometimes, size matters
  66. The search for publishing's holy grails