Know more about the features and bug-fixes that are being rolled out from Quintype.
Filtering stories to rank them into a collection can now be done with Story Attributes. Stories can be filtered by a single story attribute or multiple story attributes together.
Certain Story Attributes are essential for the smooth functioning of a front-end website. With Bold, Story or Card Attributes can be set as mandatory and they need to be filled before submitting a story for review.
While creating an Attribute, they can be set as mandatory. If the mandatory story attribute is not filled in, story publish will throw a validation error.
Content Publishing happens along multiple themes. Focus teams working on stories that belong to sports, or politics or human rights should be able to view, edit or approve the stories that belongs to the content themes that they are part of.
Teams can be created based on groups of Story Attributes and members can be added to each of the teams.
Adding team members can be done from the users profile. One person can be added to multiple teams. Actions that can be performed by users are dependent on the editorial permissions.
Text toolbar now includes sub-script and super-script, H2-H6, bold, italics, underline, strike-through etc.
The Advanced Search will now be able to aggregate content across Sections, Story Templates and Collections. Additionally the advanced search will also be able to aggregate stories to any entities associated to collections.
For Example; Magazines in Quintype Platform can be represented with Entities and their Issues equate to collections in our domain terminology. If stories regarding a particular topic, say wildlife are added onto multiple issues, each of these issues belonging to a magazine, the new API will provide the ability to aggregate these stories to the magazine.
Every collection comes with an Issue Date, a preset date that can be set which is separate from the collection update or created date.
API for collections tagged with entities now supports filtering the list with Collection Issued Before and Collection Issued After dates.
Stories can now be tagged with entities and Entity by Slug API will retrieve the entity details from the Entity slug. This will enable reader to click on a slug and then receive the full page of information with respect to the slug and may be related stories as well.
We have enabled the new and improved interface on production and it can be used by individual users. To enable Bold for your account, go to My Profile and click on "Switch to Bold".
Quintype Bold supports syndication of YouTube Videos into the Editor. Different Channels can be syndicated into a section and set to be published manually or automatically.
With Quintype Bold, Section & Menu colour can be added from a colour picker. The selected colour will be a part of the API response.
Facebook is rate-limiting logins and engagement requests and to handle that we are introducing a threshold which, if hit, will throttle the requests to Facebook for 20 minutes till the rate-limit resets.
Publisher data can now be made available as a RSS feed export.
Quintype Search API ow supports facetted search. Initial release gives the ability to aggregate search results based on Sections, Story Templates and Time-Range.
Have a magazine that goes to the stands later this week? Create and schedule the corresponding collection from Bold and schedule the publish to coincide with the date the magazine is hitting the stands.
Any newly created collection can be scheduled to a specific date and time. Already published collections cannot be scheduled.
This feature will be available with the new and updated CMS.
Creating a great story involves multiple people. Some of them may be involved in greater capacities than others. There can be photographers, videographers, info-graphics creators, content editors, copy writers, graphic artists, illustrators and many more involved with the creation of a great story.
We are introducing 'Authors' and 'Contributors' to give proper credit to people who worked on the story at major and minor capacities. We have also introduced 'Roles' so that everyone involved can be credited for what they did for the story.
Creating Contributor Roles
Contributor roles work across 'Authors and Contributors' enabling each publisher to set up a set of roles that will describe the kinds of contributions that can be made for their stories.
After enabling 'Contributor Roles' from Settings >Configure >Features a new menu item will be added in 'Configure' which will enable the screen to create Roles.
Using Contributor Roles
Once enabled the author details in our APIs will be enhanced with roles and a new entry will be added for contributors.
This feature will be available upon the launch of the new and upgraded CMS.
Asana is a web and mobile application designed to help teams organize, track, and manage their work.
Available with the new iteration of Bold, Asana Integration will enable the users to see the tasks and sub-tasks that are assigned to the user, close the tasks from the editor itself.
For all the tasks that are coming to Bold, the users will be able to create a story and upload a set of images. These images will be shown as the defaults when searching for images in the story.
The list of all tasks with at least one task assigned to you will be listed here.
All the Tasks which has at least one sub-task assigned to the logged in contributor.
The Tasks are organised into:
Today : Set of tasks that needs to be completed today.
Tomorrow: Set of tasks that needs to be completed tomorrow.
Later : All the tasks that are due from the day after.
Create/ Go To Story
From a task, a new story can be created (Create Story), if no story is created for the task already. If a story is created, then you can navigate to the (View Story).
Open the Task and open the Media Upload screen.
Single Task Page
As a contributor opens a task, they will see the sub-tasks , do the respective tasks ( like Image upload / create or modify a story ) and close the subtasks ( or the task itself ) from the page.
The images uploaded to the task are listed in the single task file.
The images that are uploaded into the tasks will be shown as the default images that will be shown for the story created from the task.
Close Tasks at Story Publish
When a story associated to as task is about to be Published, the person who is publishing the story will be able to close the sub-tasks that were created for the parent task.
What happens in ASANA?
When a story is created from a task inside Bold, all the state transitions for the story ( Submission, Approval, Publish etc ) will be added as comments onto the main task in Asana.
Each comment will have details about the story, the editor and the preview links and the published story URL. The name of the user initiating this action is also captured in the comment.
The minimum image width for images in AMP stories are updated to 1200px. This will ensure that the images are displayed in good clarity thereby rendering beautiful AMP content. Ensure that the images that are uploaded to your stories are more than 1200px in width.
AMP stories immerse readers in tappable, full-screen content. Building on the possibilities of the AMP project, this format enables the creation of visual content that is fast, open, and user-first.
Read more about Visual Stories here
From the Quintype Editor, Visual Stories can be created like any other story.
How does it work?
Quintype supports one default template for AMP stories with our Standard Theme
Creating your own Visual Stories.
Visual Stories supports e a vast range of customisations and while Quintype provides an easy way to create the story content, creating Visual Stories need your Website App to support them. Talk to your account manager and discover how your website can use Visual Stories to drive compelling narratives and beautiful templates. If your AMP Story supports more story elements than the ones listed above, we can enable them for your template.
We have integrated with Gupshup to send verification codes to user’s phones.
Press play to listen to first audio release note:
Amazon Polly turns text to life-like speech. We have integrated with service to provide audio files (.mp3) of the story and make it available as part of our APIs. This audio can be streamed by a supported player by the front end apps
How do I use this feature ?
Amazon Polly Pricing can be found here.
Quintype has introduced the ability to customise the title for Push Notifications send from the Editor. This ensures greater control over the content being pushed to the subscribers.
Publishers can configure the default Story Access Level. This ensures that all the stories that are created anew can be set to either Public, Login or Subscription. All the stories created post that will default to this access level.
This can be changed from story metadata before publishing. Contact your Account Manager to enable this and understand how this can help your website.
We will be gradually switching our publishers from the current Adobe Creative SDK Image Editor to PhotoEditor SDK. PhotoEditor SDK provides a large suite of image editing options with in-built social media ready cropping tools, text art etc.
Check out the new Editor Features here.
You can manually enable the New Image Editor from Admin>Configure>Photo Editor
This will be enabled for all from October 31, 2018.
RSS Feeds from Quintype ( your-website/stories.rss ) provides the entire story content. As part of being more subscription friendly, Quintype has introduced the ability to show teaser content in the RSS feed and provide redirect the consumer to your website for the full content.
Once enabled, all the stories that are marked as “subscription” in the Editor, will show only the first story element and then provide a link to “Continue Reading”.
You can enable this feature from Admin>Configure>Metered RSS
You can now upload CSVs, PDFs and Doc files upto 25 Mb in size.
Added email addresses in the author names drop down to better help identify authors with identical names.
As part of enhancing the user experience on collections, the number of stories in a collection can be configured. This will ensure that editors can keep adding stories to collections and not worry about the number of stories being an ever increasing list.
We will be enabling this feature for all publishers on 15th October. If you want to enable this on an earlier date, talk to your account manager.
Syndicating content between Quintype Publishers now retains the cards at the destination.
Editor now supports moEngage as a push notification provider, in addition to One Signal and iZooto.
Publishers need to get an account with moEngage and then contact your Account Manager to add or modify your push notification provider.
The Recommended Collections from Quintype now supports personalisation based on the user, location and the story being read.
Please contact your Account Manager to get the license from our external partner for using recommendations in your website.
Quintype supports an ever-increasing list of feeds that can be syndicated. PTI support has now gone live. The syndicated content can be in open (draft) or directly published to your website.
Copyscape is a premium tool for editorially ensuring that your content is not copied from elsewhere in the internet.
Publishing syndicated stories are now enhanced by auto-filling the SEO details from the syndicated content.
Trending Collections with filters are enabled now. We have updated our elasticsearch version and have enabled the filters for Trending Collections.
Default Values for Author Collections
Saving Author Collections that are created automatically has become more simple as we have started auto-filling the collection Name and Description from the author name and bio.
Any collection updates are now restricted to the latest version of the collection. If any update is attempted on an out-of-date collection version, it will prevent the save and ask the user to refresh the collection page to get the latest collection data.
An older story version can be viewed and also restored from the editor interface. The Activity Log has two new buttons, one of which will display the story version in a new tab and the other to restore the version.
Restoring a story version is possible only from the Activity Log.
Quintype Platform has added support for creating static pages with custom HTML from the editor.
The page to add new static pages can be found at : Add Static Page : Admin>Static Pages
The first release version supports :
For adding Static Page support to your website, talk to your Account Manager/Support.
UC News specifies an API format for content shared to their services. Now stories are also available at the UC News specific API end point which can be accessed at: website.com/api/v1/uc-news.
When submitting a story to UC News give PageNumber and PageSize
UC API Specifications can be found here
Added the option to re-publish a story without changing the publish date. This ensures that the story re-publish does not change the story order.
What happens to RSS Feeds and sites which Syndicated the content?
The story update will go as an update in the RSS and to all the sites which syndicate your content.
Automatically create virtual collections for all authors to ensure that the best stories by the author can be ranked and displayed in their page.
Contact your Account Manager or email@example.com to add Author Collections to your website.
Embedding Dailymotion videos have been simplified and incorporated into the Social Links Story Element. This removes the requirement of copying the embed code and putting that as a JSEmbed in the editor. Just get the URL, paste it into the Social Links Story Element, and the video gets automatically embedded.
The Social Links story element embeds content from multiple websites via their URLs. It supports Twitter, SoundCloud, Instagram, YouTube, Facebook and Dailymotion.
As part of streamlining the collection editing experience, we are now indicating the presence of multiple users on the same collection page.
This can ensure better coordination while modifying collections. Unlike story pages, collections are not lockable at this point.
All the applied filters will be retained if a users clicks into a story and returns to the workspace. This will ensure that already applied filters need not be reapplied every time a user navigates to the workspace.
Filtering by Author has been added to automated collections. Currently Collections can be filters by tags, sections, story types and authors.
Automated collections filtered by Authors can be user to showcase the stories written by an Author.
The ‘Default’ source filter can now be configured to show ‘All Stories’ in the Published tab. This will ensure that, in the default view, Published tab can show a holistic view of all the stories that has been published to your website.
Currently the default filter can be configured by the publisher to show multiple sources ( Editor, IANS etc ) together; additionally it will now be able to show published stories from all sources. To enable this, talk to your account manager
By default YouTube gives the shortened URL when sharing (ex : https://youtu.be/R6TdNbiAUnE ). We have enabled support for the same in our Social Links Story Element.
A new story-version is created when a story goes through the workflow and on every story save. The editor showed each of these saves in the Story Audit Log. Now these versions can be viewed and the content copied onto the current version of the story, if needed.
Viewing the story versions can be turned on from Admin>Configure. Once this feature is on, each entry in the story audit log will be enhanced with a “View” option, clicking on which will open the particular version in a new tab. This version is read-only and hence cannot be edited. The contents can be copied and pasted into the latest story version if needed.
The older version will open in a new tab, with a banner on top mentioning the time at which the version was created. While content can be copied from the story elements, no changes can be made to the version data.
Sections Reports can now be dowloaded from Analytics>Reports
Reports can be downloaded for All Sections and Sub-Sections within any section. The report lists the sections ( or the subsections ), the views received and the number of stories published. ‘All Sections’ reports calculates the page views received by their sub-sections also.
The report is in CSV format and can be imported to MS Excel, Numbers or Google Sheets.
Single or multiple entities of different types can be added to story and card attributes. Previously, we supported a single entity type in story attributes.
Ability to add a ‘person entity type’ and ’company entity type’ as story/card attribute so that I can add Warren Buffet ( Person ) and Berkshire Hathway ( Company Name) to the same story attribute.
Sentry is an open-source error tracking platform that provides complete app logic, deep context, and visibility across the entire stack in real time. Developers can fix bugs at every stage of the product lifecycle, well before users ever encounter a problem.
We have enhanced the error messaging on Live Blogs, this includes:
We have created fallbacks to ensure that if collections are unable to receive trending data, they will fallback to show the latest published stories. This will ensure that the user-experience on our websites are not hindered due to any unexpected outages.
We have introduced a confirmation before navigating away from Sorters if there are unsaved ( and hence un-published ) changes.
We have standardised the buttons for saving and publishing a Sorter and Collections. It has been updated to “Save & Publish” which used to be “Publish Sort Order” for Sorters and a “Floppy Icon” for Collections.
Tag search logic has been updated to give more relevant results while adding them to stories.
VOD is a custom Video-On-Demand platform ( http://vod-platform.net/ ). VOD video embed is available as a new story element from the editor. After uploading a video, copy and use the embed code to show the videos on the website.
As part of improving data privacy, we will be removing the last octet of the IP address of a visitor to any of the publisher’s site prior to storing the same for analytics and other purposes.
Eg, If a visitor is viewing a page from a IP address identified as 18.104.22.168, we will be storing the same in our database as 192.0.0.0
This will not limit any of the features dependent on IP address. This change is also not retrospective
You will now be able to pin a card in a live blog if you want the information within the card to appear on top of the live blog. A new icon (indicated in the image below) will enable you to pin a card within a live blog
Ensuring that the platform support a place to manage redirections can let the publishers control their redirects in case of permanent ( 301 ) or temporary (302_ content retracts / redirections.
Accessible to anyone with Admin Permissions.
Page location : Admin/Redirects.
This page enables the admin to:
1: Add new redirect URLS ( Old URL and the corresponding redirect URL )
2: Update existing Redirects
3: Delete Redirects
For any non-english language, the slug used to be auto-generated by transliterating the language, this can lead to random slug-names. Providing an option to control the slug creation will ensure that publishers can control every aspect of their content.
Tag slugs can now be edited from the Tag Manager.
When a new section is added, the section slug is also customisable instead of being automatically generated. The slug for a section is mandatory and will be automatically filled with the slugified section name, if the section name is in English. For any non-English slugs, the field will remain empty. Once saved, the slug is not editable.
As part of consolidating the tabs available in the workspace and simplifying it, we have introduced the ability to filter the dashboard content based on the Source.
The Workspace will open with Default as the source and it will include all the stories created in the Editor. This can be configured to add or remove sources.
In the default view, all the stories that are created from the Editor will appear across different workflow states (open, published etc). If IANS is selected as the Source, and applied, the content in the workspace will be sorted likewise. By default, all the IANS stories will be in the Published column.
If a published IANS story is retracted, it will be moved to the Open column. Previously, if a published syndicated story was retracted, it would be placed in the Open column along with all the other stories from the editor. Additionally, the categories from the source are also retained and syndicated content can be further filtered based on them.
This enabled the workspace content to be further customised to see specific categories from a source. Multiple Sources and their categories can be selected at once and the workspace content is filtered likewise on Apply.
There is no change in the UGC workflow right now. But they will be migrated to follow the same workflow with UGC as a source. UGC stories will appear in the Open state and their progress through the workflow can be monitored directly when filtered with UGC as the source.
Easily add a place-holder menu item which opens a submenu without redirecting to any page.
Our Editor, being a fully online-only application, displaying internet connectivity status is important for seamless usability.
We have added a red persistent banner alert messages on internet connectivity loss and a green dismiss-able banner when the internet comes back.
Adding a story when a news is being broken will ensure that maximum SEO juice goes to the story page, as search engines can index the page from start. An associated story created along side breaking news requires minimum additional effort and directly publishes the story.
After adding a link in the editor it can be set to ‘no-follow’. This will ensure that search engine juice does not get translated to the source site.
Added Zendesk Chat help from the Editor to Quintype Support. We will be doing a staggered release for this feature to publishers.
This is being scaled across publishers gradually over a period of time
Lock Story for Edit
With this feature, multiple users can now view a story while one of them is editing the same. This helps the others review the story while it is being edited. This feature works in tandem with ‘Non blocking auto save’. Both the features can be enabled by the admin using ‘Admin>Configure’ option. Please ensure that all the users are logged out of the editor when this feature is toggled on.
Feature toggle to enable the feature (Admin->Configure->General)
- Non blocking story save
- Block Concurrent Story Edit