wiktor_walc's comments

I’m Wiktor Walc, the CTO of Tiugo Technologies, which acquired ButterCMS in 2022. I completely understand the frustration and impact this may have had on your operations, and I wanted to personally apologize for how we handled the recent domain transfer and the communication surrounding it.

What Happened:

Domain transfers typically go smoothly, especially since we made sure to keep DNS records and the underlying infrastructure completely intact to minimize any risk. Unfortunately, this time, things didn’t go as planned.

An additional verification email sent by Amazon in August was mistakenly flagged by Gmail as a phishing attempt and placed in the spam folder, so it went unnoticed. As a result, we failed to verify the domain on time, and it was temporarily suspended. The moment we received the suspension notice from AWS, we immediately resolved the issue and restored the domain.

Missteps in Communication:

We recognize that there was a delay in communication after the domain issue had already been resolved, which was due to a breakdown in our internal processes. This misstep caused frustration, and we are committed to improving our communication practices moving forward. This happened because the team was not yet fully integrated into our communication processes. A few days after resolving the issue, we posted an explanation on our status page, which can be found here: https://status.buttercms.com/

Moving Forward:

This incident has been a valuable learning experience for us, and we are taking concrete steps to prevent similar occurrences in the future. Our improvements include:

- Faster responses on social media to keep you informed

- Real-time updates on the status page to ensure transparency

- Resolve outdated code examples to provide better support

We are also making long-term improvements to ButterCMS to ensure stability and security. A dedicated DevOps team has been assigned, and we’ve scaled up our engineering resources. Currently, we are planning the roadmap for the upcoming year and would greatly appreciate any suggestions or feature requests you may have.

Once again, I do apologize for the inconvenience this incident caused, and I truly appreciate your patience and understanding.

If you have any questions or feedback, please don’t hesitate to reach out.

Just got this newsletter message stating that Techcrunch will stop charging for providing access to their content. Interesting strategic shift.

(CKEditor team member speaking) Proper handling pasting from Word really takes a lot of time and it's hardly possible to provide a high quality solution alone. We will deliver some basic (in our understanding) support for pasting from office in our most recent editor (https://ckeditor.com/ckeditor-5/) in 2-3 weeks and it already took long weeks of development (see https://github.com/ckeditor/ckeditor5-paste-from-office/issu...), even with our years of experience in rich text editing and with this particular feature.

If pasting from Word is absolutely critical feature for you you may want to check older editors on the market, like CKEditor 4 or even... TinyMCE, one of our competitors. These editors are on the market for 6+ years and had enough time and people to deal with the crap that MS Word produces - correctly preserving as much formatting as possible, without wasting a lot of your end users time on recreating the same content again in an online rich text editor.

CKEditor team member here :)

If you are looking for a modern, modular editor, with a custom data model and collaboration check CKEditor 5 (https://ckeditor.com/docs/ckeditor5/latest/features/index.ht... and https://ckeditor.com/ckeditor-5/). It comes with decent mobile and Edge support already (Electron is supported too). Paste from Word will be delivered within 2-3 weeks. For collaboration we already offer a complete and stable solution out of the box where you don't have to code anything. If you are curious check https://ckeditor.com/blog/Lessons-learned-from-creating-a-ri...

If you are looking for a completely framework-agnostic rich text editor, then check CKEditor 5 (https://ckeditor.com/ckeditor-5/). It comes with it's own UI library which you can swap freely with any other UI thanks a to highly decoupled architecture.

Recently we realised that our public communication about collaboration is quite confusing ;( We mention "Cloud Services" everywhere, but the reality is that you can have an onpremise installation of our collaboration backend that you can host/control by yourself. The SAAS offer was first, that's why the current website looks how it looks. The onpremise offer is currently in a closed private-beta state, so if there is anyone willing to give it a try, we're open. We'll make it fully public in a month or two, after we polish the documentation and so on.

Hey Tade0! As much as we love CKEditor 5 that we created, we also love our users who are still widely using CKEditor 4. Some of them invested many, many months to create custom plugins, adopt CKEditor to their systems and so on. So, being a responsible company, we will maintain this product still for several years. As a company that creates components, which are embed into other systems, we have to simply deliver stuff that others, including big enterprise customers, can rely on. I know it's a bit unusual in JavaScript world to maintain software for 8(!) or even more years, but this is what we do. Yes, we're a bit crazy.

Yes, that's correct. The demo for mobiles is intentionally hidden because both examples on ckeditor.com are right-now desktop-like. We'd be working soon on a solution that would provide much better UX for mobiles, once we do it we'd show a dedicated demo for mobile devices.

Yep, I'm working there ;) Please send us the details via contact form https://ckeditor.com/contact/ or feel free to PM me directly at ["w.walc", ["cksource", "com"].join(".")].join("@")

Once again I'm sorry for the lack of reply. Back in I.2013 our team was much smaller and we were overloaded with post release stuff shortly after launching CKEditor 4.0.0. So lots of emails were left unattended :( Tade0 (buongiorno!) was right that at that time we were not looking for junior developers, but ofc the lack of reply was a mistake on my side.

I'm sorry for this, but please note that this was a conscious decision to show products at the current state. We wanted to give the voice to the community to help us prioritise the development as soon as it makes sense. If we showed everything to the public once its fully ready (having all the nice to have features in place, brilliant support for mobiles), you would have no chance to let us know, for example, how you would like those features to behave etc. How exactly do you see the mobile support and so on. We did not want to blindly copy CKEditor 4, adding just the new architecture to it.