This feature is at the top of the feature requests with 129 votes. Next one is 82 vote. https://feedback.document360.com/feature-request?sort=top
I get your emails with new features and I don't feel any of them are relevant, and this top feature doesn't seems to move forward at all.
Why isn't this prioritized?
Johannes Akesson Apologize for the delay in this request.
@All, we clearly understand the pain point of all users and empathize the scenarios' mentioned in everyone's post. We do have concrete reasons for the delay, conflicts within editor compatibility and support of spell checker. We will work towards this and provide an update on this.
Thiru: Thank you. Do you know if there is a workaround, like a Chroma extension or some other way to get spelling?
There is already a feature request for this https://feedback.document360.com/feature-request/p/spelling-checker
This has 129 upvotes and has been requested since 2021.
Shakeer Hussain S
Hi Esther Beyda - Thank you for submitting your feature request. We appreciate your suggestion and understand the value that this feature could bring to our users. Our team will evaluate the feasibility of adding a spell checker to the Markdown editor and consider it for inclusion in a future release. We will keep you updated on the progress of this request.
Its 2023 and for me, neither Grammarly or Chrome's in-built spell checker is working.... despite this being under review back in 2021..?
I don't write in the WYSWIG editor. I write in the markdown editor.
Thanks for all your valuable feedback. Apologies for the deferred response. Here is an update for you all, if the Grammarly extension is enabled in your browser, spell checking happens fine in WYSWIG editor. Furthermore, browser spell checker when turned ON as well this works. We believe this should resolve your needs, in case of otherwise scenario kindly let us know.
Thiru: We work in Markdown and understand the problem is there not in WYSWIG
Hi Thiru, thanks for your note -- the request relates to the Markdown Editor though; not the WYSIWYG variant.
Thiru: Hi Thiru, thanks for the comments, but we are also having the issue in Markdown and not in WYSWIG. Also, our organization is very strict with the type of add-ins / extensions we allow so we cannot rely on a third party extension for our spell checking. Thanks.
Thiru: Thiru: We just want Chromes built-in spell checker to also be enabled in MarkDown editor. Nothing more.
Looks like we'll be copy/pasting into Visual Code for a while. Grammerly works nicely in Visual Code.
I completely agree, we are going to have to do our entire workflow outside of d360 so grammarly can do its thing, then pull documents back into d360 to publish. this is a gigantic gap.
If we were aware of this gap, we might not have gone with D360.
Spell and Grammar checker is a must. For Content management - this is a basic requirement.