Nice work! Kind-of similar to what I'm doing with CodeWrite, just that the editor is separate and Dev.to (as well as other platforms) are supported through auto-filling. Might plug-in directly to the editors in the future.
Love the bookmark idea though - didn't think of that!
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
Thought about it already. Maybe in the future. Auto-filling on the web is pretty hard - especially with contenteditable rich editors. Techniques that I use won't work on every website, but on the vast majority. Might do a blog post on this.
So, if I manage to standardize it, then yeah, API might be on the way.
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
I meant an API to retrieve the HTML / markdown generated for processing.
I thought that way people can use your service to write, then publish to everywhere including their own site. Or is that what you meant was difficult 😋?
then go to one of Medium, Hashnode, or Dev.to, open pop-up and click publish
CodeWrite detects potential issues (e.g. images too large, code highlighting not supported), presents you with potential solutions (e.g. resize image to FHD, convert to GitHub Gists embeds) and "auto-fills" the post's content within the editor.
Auto-filling and issue-resolving mechanisms aren't the same for every website, and so they aren't good candidates for an API.
I could provide generalized access to the pop-up menu and created content, but this would leave too much work on the API user's side.
As for standard "Markdown exports" - they're in development, alongside GitHub Pages auto-filling.
Hopefully, I'm clear. CodeWrite is a rather unique idea and it's quite hard to explain it properly.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice work! Kind-of similar to what I'm doing with CodeWrite, just that the editor is separate and Dev.to (as well as other platforms) are supported through auto-filling. Might plug-in directly to the editors in the future.
Love the bookmark idea though - didn't think of that!
Great work on CodeWrite, I have added it to my list of "things to try".
Does it have an API (or will it have?) as it could be a great plug and play solution for people who build custom websites.
Thought about it already. Maybe in the future. Auto-filling on the web is pretty hard - especially with
contenteditablerich editors. Techniques that I use won't work on every website, but on the vast majority. Might do a blog post on this.So, if I manage to standardize it, then yeah, API might be on the way.
Sorry just re-read this.
I meant an API to retrieve the HTML / markdown generated for processing.
I thought that way people can use your service to write, then publish to everywhere including their own site. Or is that what you meant was difficult 😋?
Kind-of. Right now it works like that:
CodeWrite detects potential issues (e.g. images too large, code highlighting not supported), presents you with potential solutions (e.g. resize image to FHD, convert to GitHub Gists embeds) and "auto-fills" the post's content within the editor.
Auto-filling and issue-resolving mechanisms aren't the same for every website, and so they aren't good candidates for an API.
I could provide generalized access to the pop-up menu and created content, but this would leave too much work on the API user's side.
As for standard "Markdown exports" - they're in development, alongside GitHub Pages auto-filling.
Hopefully, I'm clear. CodeWrite is a rather unique idea and it's quite hard to explain it properly.