I had YouTube videos that showed how to use Wraith Scribe. The main problem with that is that the features changes so rapidly, and there can be so many nuances / best practices that it may not make sense to fit it all in video(s).
Likewise, depending on level of expertise, it may not make sense to consume all the information in a linear fashion. So, I've created a documentation page where you can easily search for the thing that you want to read about it.
For example, let's say you want to learn more about long descriptions and what they mean, you can just type "long description" in the search bar and the most relevant results will show up on the live search. This lets you get to the most relevant information in a matter of seconds.
Also, another good thing about transitioning into a documentation page as opposed to a YouTube video for tutorials is that I don't need to re-record an entire video from scratch if I just updated a button. Nor does it make much sense to have a YouTube video tutorial for each tiny button. With documentation, I can update a button and just update a couple of sentences in the documentation correspondingly, which is much easier to manage.
If you find anything incorrect or outdated on that page, please let me know!
Classifying Input Prompts
Prior, I've had AI classify whether user prompts are longer descriptions or whether it's a blog title. But the classification is iffy at times. So instead, I've made it more straightforward to use by providing a dropdown. If you want to input a title and have Wraith Scribe riff off that, just pick "title." If you don't have a title idea but just have a generic topic in mind, just pick "topic." Likewise, if you want to inject your own unique ideas and are opinionated on what should go into the article (but don't want to write it out in detail), just pick "long description."
Additionally, for each of the 3 categories, I've added examples in the placeholder text so it's more clear on what the AI would expect as an input. See below for an example:
I've also elaborated on this a lot more in this part of the documentation as well.
Prior, the settings for you to write the article and publishing options are all jumbled together. They're not classified into appropriate, pretty accordions:
The publishing settings are collapsed by default. The reasoning behind is that while you might change the number of target words / tone for each new article, it should be more rare for you to change your publication options. For example, if you're making 10 articles for a Wordpress site in a row, you unlikely need to see those options every time. But let me know if this isn't the case.
In the rare cases you do need to change your publishing settings, you can just expand the publishing settings.
Autosaving your settings
Also, all the settings are now auto-saved, across sessions and devices. Because your workflow is unlikely to differ from one article to the next, things like the language to write in, tone, etc. will be restored when you write future articles. This makes it:
- More convenient because you don't have to reset the settings to just the way you want every single time.
- Makes it less error prone. You may intend to write an article a certain way and forget to manually change a dropdown to suit your workflow. Now that the settings are saved, you don't have to explicitly change the settings each time which means there's less human error involved when configuring your articles.
I've added credit rollovers so that unused credits will be rolled over to the next month.