What’s better than Markdown to format publications? a rich text editor!
The Noticeable dashboard is now including a rich text editor. Formatting and customizing the appearance of your publications is now simpler than ever.
You can include images, videos, format titles using different levels, put text in bold, italic, underline or even strike. Quotes are also supported along with lists, code snippets, tables, and dividers.
To apply formatting or actions, you can use the visual toolbar, shortcuts (e.g. CTRL+B to set your current selection in bold), or the Markdown syntax! Indeed, for backward compatibility but also because some of you love Markdown, we still support the syntax as you type.
There is another tip we would like to share. When writing your publication, the content is saved as soon as the editor loses focus or you click on Continue. However, it is also possible to trigger a save by pressing CTRL+S.
What about content published through the GraphQL API or Zapier? in this context, you don’t have a rich text editor. As a consequence, you can either use plaintext or the Markdown syntax.
PS: some of you asked, the editor is built on top of ProseMirror, a great open-source toolkit for building rich text editors (we contributed ESM support).
Did you like this update?
{error_message}
Leave your name and email so that we can reply to you (both fields are optional):
After several months of hard work, we are proud to introduce a whole new Noticeable!
It’s hard to enumerate all the changes in a single publication. They go from a refreshed logo to a new dashboard with an improved user interface, advanced analytics, new widgets that are fully configurable through a live editor, an easy to use JavaScript SDK to interact with the Noticeable widgets, and many new features including a WYSIWYG editor, pinned publications, private Newspages, and more. Besides, this does not include all the changes we made internally to move the service to the next level.
There is so much to say that we will introduce important changes in dedicated publications in the coming days. In the meantime, here are a few changes you should be aware of:
Timeline pages are now called Newspages.
Posts are now referred to as Publications.
Newspages are now served from the domain noticeable.news for users on the free plan.
Custom domains are no longer served and verified by Firebase. This enables faster SSL certificate generation and easier maintenance.
A new widget has been introduced and the legacy widget has been deprecated. You will receive an email with upgrade instructions by the end of the month.
We hope you will like what we made. As always, your comments are welcome. You can react below. 👇
Did you like this update?
{error_message}
Leave your name and email so that we can reply to you (both fields are optional):
We are happy to introduce a new feature for the Noticeable widget: cross-device synchronization.
By using cross-device synchronization, users identified using our SDK will have Widget read states maintained between devices: when they switch for instance from their mobile to a laptop. This new feature is available as part of the Business plan. You can read more about how to enable the feature in our help center:
Recently, some of you may have noticed a temporary slowdown with the API and the Timeline pages. The problem was coming from one of our database providers. We apologize for the inconvenience. The issue is now resolved.
You can now display segmented posts on your project Timelines.
Segmentation is a powerful mechanism to display posts to a given set of users based on your own conditions. Although segmentation is configurable with our Plug & Play Widget, by default Noticeable Timelines are not displaying segmented posts.
We are listening to you and starting Today, you can force a segmented posts (i.e. posts that define segments) to display on your project Timeline by adding the special segment Noticeable:Timeline to its list of segments.
A few weeks have elapsed since our last update. We’re currently busy at making changes to our internal infrastructure to support new features.
Some of you have noticed, in the Chrome developer console, a warning about an imminent HTML imports feature removal. Be reassured, the current version of the Widget will continue to work even after HTML imports removal from Google Chrome.
In the meantime, we’re also working on a new version of the Widget.
Stay tuned!
Did you like this update?
{error_message}
Leave your name and email so that we can reply to you (both fields are optional):
Adding images is crucial to make your product updates more appealing. By default, published images are automatically sized for the container that displays your product update (e.g. Widget or Timeline).
Although automatic shrinking is a visual requirement, this may be an issue when you want to draw special attention to details on an image. For this reason, we’ve made published images automatically zoomable when their natural size is larger than their container.
Click on the next image for a live sample:
Did you like this update?
{error_message}
Leave your name and email so that we can reply to you (both fields are optional):
Roles define what actions collaborators are allowed to perform. Today, we’ve introduced a new Admin role and refined collaborator permissions.
With Noticeable, project collaborators can have one of the following roles:
Viewer: this role grants read permission to your project data with 3 exceptions: access to billing data, API tokens and Zapier API key is forbidden.
Editor: an editor inherits viewer permissions and is granted write access to posts and labels only.
Admin: an admin inherits editor permissions and is granted write permission to all project data (posts, labels but also project, timeline and widget settings).
Owner: the user who creates a project is automatically granted the owner role with full read and write permissions to project data. Only one owner is allowed per project and it cannot be changed.
You can now also edit a collaborator role from your project settings without revoking and sending a new invitation.
Did you like this update?
{error_message}
Leave your name and email so that we can reply to you (both fields are optional):
