You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
馃搾 Note: This is an EPIC ticket - it must be broken out into small individual tasks, each no more than 1 day of work
Background
At the moment we create new feed entries like this:
And they come out in the feed like this:
The process of authoring the entry is quite tricky and error prone. And worse, errors, once published, cannot be corrected since the user's QGIS session caches the entries locally.
To address this we would like to develop a front end (non django admin based) view for authoring content with the following capabilities and considerations:
We cannot use the root URL because that is where the feed is published.
After logging in with a beautiful login screen branded with out new QGIS branding, they are provided with tools to manage feed items.
A list of feed items, sortable and filterable by date published, author, language
A button to create a new feed item - clicking will take you to a blank feed item form
Clicking on an item on the list will take you to a feed item form
The feed item form shall display on the left, all the widgets needed to edit the entry, and on the right, a preview of the entry as it will be rendered in QGIS. Any edits made in the form shall immediately update the preview.
Once a feed item is created or modified, there will be a review step where the user is asked to confirm that they have checked everything carefully
The form shall implement such checks as needed to ensure the feed item does not cause issues when rendered in QGIS. This shall include
Only the following html tags should be allowed; p, strong, italics. These tags should be editable using a rich editor like mcedit, but there should always be a 'raw' view that can be used to check for hidden characters like \r
If a link is set, the link should be checked for validity
There should be a hard limit on the number of characters allowed this should be configurable in admin. A starting default or 500 characters would be good I think
The form must first be placed in a holding area before final submission
The form must be approved by someone with an 'approver' role before it is published
Caution
This feed site is very high traffic and no changes can reduce its stability. Any changes must be covered in tests and demonstrated to be robust.
The requirements are well noted. I will split the ticket into small tasks firstly, add details and size for each of them after that in order to process tasks.
馃搾 Note: This is an EPIC ticket - it must be broken out into small individual tasks, each no more than 1 day of work
Background
At the moment we create new feed entries like this:
And they come out in the feed like this:
The process of authoring the entry is quite tricky and error prone. And worse, errors, once published, cannot be corrected since the user's QGIS session caches the entries locally.
To address this we would like to develop a front end (non django admin based) view for authoring content with the following capabilities and considerations:
Workflow
User has a nice login screen if they visit https://feed.qgis.org/manage
We cannot use the root URL because that is where the feed is published.
After logging in with a beautiful login screen branded with out new QGIS branding, they are provided with tools to manage feed items.
Caution
This feed site is very high traffic and no changes can reduce its stability. Any changes must be covered in tests and demonstrated to be robust.
CC @Xpirix
The text was updated successfully, but these errors were encountered: