Storage Cap

We are introducing a storage cap this release, so that users don't take up infinite space in our database. As of this release, the storage cap will be set at 2 GB per user.

When it comes to team workspaces, the storage taken up from documents in the team workspace will factor into the storage of the workspace owner; not individual users. This is going to be the implementation this release, but this is definitely something that can change later; according to needs of users. The storage cap itself is not something set in stone as well, and can be changed in future releases.

For this release, the 2 GB cap will be applicable to everyone. We will set up options for users that need more storage in this release if there is time, or in the next release.

I'm very sorry if this causes any inconvenience to you, but this is needed to keep all functional features on Bluebird Documentation free.

Arabic Language Compatibility

We're adding Arabic compatibility to Bluebird Documentation!!! Here is how this would work...

Users will be able to specify a preferred language in account settings, or on the home page. This will change the language on any of the website buttons, static text, etc. Users will also be able to choose the language they'd like to write documents in. However, document content will stay in the language that it was written in when viewing. A user can then choose to implement a forced translation of the document if needed when viewing.

To keep the text easy to read, we've chosen this font.

Email Notifications

Email Subscriptions to Individual Users

This is the ability to subscribe your email to a particular user. When that user posts a public document, or replies to your comment on their public document, you'll receive an email notification.

We'll also be adding quick navigation to see all public documents of the subscribed user in the BBD UI.

Email subscriptions to a Team Workspace

This is the ability to subscribe your email to an organization. Organization owners can allow this feature. If subscribed to a team workspace, you'll get notifications when a public document is posted, or a member of that team workspace replies to your comments.

We'll also be adding quick navigation to see all public documents of the subscribed team workspace in the BBD UI.

Team Workspace Email Notifications

We'll also be adding email notifications for team workspace members. These can be managed in the team workspace settings page.

These will include things like email notifications for new documents that are created within the workspace, new comments, replies to comments, etc.

Email Notification Settings

These new enhancements will also require plenty of configuration and management by users. We'll be adding settings to manage these notifications in account settings and team workspace settings.

While not tied directly to email notifications, we'll also be adding the possibility to block users. This is in the case of users abusing comments for documents. The document author (or workspace members) should be able to block users or delete comments.

Notification Center

Don't worry, we don't want to spam you with notifications! XD

We'll be establishing a notification center; in the future, several different categories of notifications will come through here.

First category of notifications to come through the notification center will be the same as the email notifications: if you've subscribed to an individual and/or organization, or your getting notifications for comments on your documents. Again, these will all be manageable in settings. Whether you'd like this category of notifications to come to both your notification center and your email, just one of them, etc.

The second category of notifications to go through the notification center will be certain documentation reminders. One pain point that Bluebird Documentation aims to address is keeping your documentation concise, so that there is rich content unloading, but not a lot of content dumping. What we're going to start with is notifications for documents that haven't been viewed or edited in a long time. If a document is identified to not be viewed or edited in a long time, you might get a notification saying something to remind you to check out this document; see if it's needed anymore. Of course, you'll be able to manage these page specific notification settings as well.

Search Engine Optimization

Currently, being a client rendered application, there isn't much SEO for public documentation. We're looking at launching a Next.js project to help with SEO for public documentation; making public documentation more visible in searches!

Since this release is quite packed, this new project will be worked on last. If not much has been started on this as we approach the release deadline, then we'll probably move this to next release.

General Enhancements

1. Ability to make team workspace documents public. This will be done through our new server rendered project.
2. Lost document recovery/management. If there is an error on our end, it might be possible that there are loose documents that aren't displayed in the sidebar. This is usually because a page does not have an assigned parent document. Again, if this occurs, it's usually because of an error in our backend. We'll be adding the means to view and resolve these lost documents.
3. Visual upgrade to comments section in individual and workspace documents.
4. Adding Bluesky as an option for social media links.
5. The ability to save custom strokes in My Notebook.
6. Adding shape strokes to My Notebook.
7. In the "What we offer" section in the home page, make it so that "personal documents" sounds more for documentation, and not things like passports, birth certificates, etc.
8. Add a "most recent" widget to individual and workspace document dashboards.
9. Text boxes for My Notebook.
10. Add the ability for the select tool in My Notebook to rotate strokes.
11. Remove the background from the dropdown menus in the header component.

Bugfixes

1. Users that have access to another workspaces cannot create a workspace of their own.
2. We shouldn't be saving document snapshots if the content of the document is empty.
3. If a document is navigated to by means other than clicking on it from the sidebar, it's not highlighted in the sidebar to show document currently being viewed.
4. When creating or editing a team workspace walkthrough, it is possible to submit changes with an empty walkthrough name. This should not be the case. There should be a check to make sure that all required fields are present before changes can be submitted.