Skip to main content

Our Blog

  1. Our Plans, Features and What’s at the Heart of Colloq

    When we started out building Colloq, we had a few premises that we want to stick to. What started with the aim to build a better platform has now turned into real, usable product with great features. In this post we want to highlight some of the features of our current plans for a better understanding of what Colloq is about and what you can do with it.

    Read more…

  2. Sort Your Sponsors & Speakerdeck Coverage Support

    This week we added event sponsor sorting for our Organizer Premium and Pro accounts which allows you to add a custom order and show your most important sponsors first. We also enhanced the coverage link cards to show Open Graph images, detect Speakerdeck slidedecks automatically, and you can now see your own submitted links without a subscription.

    Read more…

  3. More Coverage Services & Embedding Colloq

    This week we added two more services to our link parser to provide a better experience to our users, let you embed a Colloq link, and eased the creation of recurring events a little bit.

    Read more…

  4. How Our Password Check Works

    Security and privacy are a big concern for us at Colloq and we do take it seriously. We want to make Colloq a safe and secure platform and are taking certain measures to help ensure it is and stays this way. Because of that, our platform features an advanced password validity check that we want to talk about.

    Read more…

  5. Sprint 40: Improved Create Events & Nicer Error Pages

    In the second sprint after our launch we focused on fixing bugs that our users reported and enhancing their experience on our service. Here’s what changed…

    Read more…

  6. Why we don’t have a Lanyrd import

    While we’re completely aware that many of you have collected and curated a lot of useful content on Lanyrd, we’re most likely not going to offer any data import. This post describes why.

    Read more…

  7. Sprint 37–39: The many things before, during and after our launch

    This week we finally went live with Colloq. Here’s what happened during the weeks leading up to our launch and the few days after it.

    Read what happened behind the scenes

  8. Hey there, we’re here!

    Today we can excitedly announce that we’re now live with our new platform Colloq. If you’re as excited as we are, please sign up, spread the word, and support our platform by using it actively. — Cheers, Anselm, Tobias & Holger.

    Read more…

  9. Updates for Sprint 33 – 36

    Since our last blog entry we’ve done a lot but not writing another update for you. It’s time to tell you the current status.

    Read more…

  10. Our Latest Update on Sprint 32

    Last week we shifted from writing about our progress on Twitter to explaining what we do in more detail here on our blog. Today we want to share the latest updates on our current and upcoming sprint with you.

    Read more…

  11. Why We Don’t Publish Our Sprint Goals On Twitter Anymore

    A few weeks ago we started to tweet our Sprint goals and after a Sprint we posted whether we achieved it or not. This week we stopped doing that and we want to tell you why. While we believe openness is key to our service, Twitter is not the right decision to share complex information such as project progress in a very short message.

    Read the Status Update

  12. Safari’s <details>/<summary> rem font-size issue

    Current Safari versions have weird issues with the rem unit that can be hard to debug. For reference, we write about weird font-sizing in Safari when using a <details> element on a website. This blog article is about WebKit Bug 173876.

    Read more…

  13. Securing Platform Stability With Acceptance Testing

    Building a brand new service means a lot of changes in the beginning. Definitions change, permission models change, and modules get refactored often. At some point we got the feeling that we’re not sure if all the permissions were implemented as per definition. For some components we realised that we didn’t even have a definition at all. Writing Acceptance tests helps us building a more robust platform.

    Read more…

  14. The Tools We Use To Stay Afloat

    Like many people we’re used to working with Jira and other big tools for project management. These tools work quite well for large projects and teams. But at Colloq where we are only three people, using Jira would hinder our productivity—it’s too complex for our use case. This is the story about what tools we use and how we make them work for us.

    Continue reading about our tools…

  15. Remote Managing A Side-Project Across The Globe

    Most of us know that running a side-project can be a daunting and rather difficult task to successfully manage, even and especially on your own. For a project involving three people, all working on client projects in parallel, making progress on a side-project is a challenge. We learned this the hard way, and here’s how we turned it around…

    Read more

  16. Hello World. Hello Colloq.

    The story of Colloq began at a conference. We’ve been frequently going to conferences for a few years now and always talked about a better way to preserve the content that conferences produce. It made us realise that none of us was satisfied with the existing offers and that it was time to do something about it. On April 1st we published our first landing page.

    Read more about how this project started »