Basic spellcheck support has been in place for quite a while now.
Grammerly will require a good bit more work and Coda is still growing quite a bit at the moment. We do hear you that this is a wanted feature for sure, we’re just working on building out the product more before committing to the effort investment here.
When growing a product you find that adding features means there is more to account for, and work around, when adding larger changes to the foundational items. It’s easy to build features to the point of hindering future growth too. So our team puts a lot of thought into how they juggle what gets added and when. The order can have a big effect down the line. Efficient ordering of procedures doesn’t always correlate to order of importance.
Yup I agree. Grammarly support or any kind of spell checker would be fantastic!
hope you guys are considering this in the near future.
Nice platfrom btw
yes it is really a great support to have grammarly extension for auto correction of spelling and grammar. when I was working with a news paper writing service I realized the importance of this software that helps me spelling correction specially and also in the productivity.
I’m in that camp as well. This is an important capability. However, I have a hunch the Codans are up to something far more sustainable and strategically in the platform camp, rather than simply another vendor integration.
To be very clear, I have no inside track - I’m just speculating, but this is likely how it will unfold.
For more than a year, it’s probable that Codans have been toiling away on an API upgrade. There are numerous areas of the current API that have untenable voids; the big one - how to access the canvas content? From words, to sentences, to paragraphs, and whole sections. These are objects that are currently stranded on an island.
The Grammarly-like requirement necessitates real-time interaction; as you type, it needs to watch keystroke events unfold without any perceived hesitation. Coda, of course does have an event model because it can count words as we type. As such, we can easily surmise they have the underlying infrastructure for real-time interaction.
The current Pack architecture involves a synching process which has some latency; this is inadequate for real-time event handling, but I predict this will not be the case for much longer. Soon, there will probably be support for outbound webhooks that may also allow us to call Pack functions with a webhook formula. Imagine …
thisDocument.newWordEvent.myPackFunction(...)
Or…
thisDocument.highlightEvent.myPackFunction(...)
Once we see these three milestones unfold, the race will be on. Companies like Grammarly will have the infrastructure required to create a Pack capable of providing its own very clever experience. More importantly, Coda will have paved a very wide super-highway to support vastly more opportunities to make documents more intelligent and capable of assisting authors with real-time enhancements.
Lastly, this likely collection of underpinnings are also important for Coda apps to form tighter bonds that deliver on the promise of machine learning.
Just sayin’ (and speculating)
ps - I also predict we’ll soon see Pack studio capable of running Python code as well as javascript.
If this might help, I am not native speaker and using Grammarly on daily basis, as we are testing coda, finding out this issue might considering using notion.
There isn’t a setting for this. It’s the basic browser spell check that we allow to work in docs, so it might depend on the browser you’re using. I use Chrome and I’m see it pop up.
If you got to Chrome settings, you can make sure it’s toggle on there.