d4goxn / gh-api-test Goto Github PK

Design should follow kasra.co homepage design

Acceptance

• If an article is published it should show up on the home page immediately
• New articles show up in reverse chronological order (newest on top)
• Follows current tile design

Jira: KSR-29

Upon saving the article (before publishing) the Editor is presented with a default permalink. That permalink can be changed by the Editor.

Acceptance

• The article permalink should be limited to 90 characters including the domain URL therefore for http://kasra.co/ (16 characters) it would be 74 characters
• Editor can enter new permalink and it gets saved
• Spaces are converted to dashes (for example "how to boil water" becomes "how-to-boil-water"
• Remove symbols from URL. Only alphanumeric characters and dashes are allowed in URL
• Lower case all english letters
• Editor is notified when new permalink is existing
• Article can be saved after changing permalink
• URL can be in Arabic

Jira: KSR-34

Jira: KSR-14

Acceptance

1. Every article detail page has a way to share via Google+

Jira: KSR-22

Acceptance

• Editor can add a new author
• Editor can use an existing author
• As an Editor I can see who the editor is and who the author is

Jira: KSR-52

Gold standard: Buzzfeed listacle editor

Acceptance

• Blocks are numbered chronologically
• Blocks can be any type of block (text, image+text, video+text, quote, etc)

Jira: KSR-12

UX provides email template

Acceptance

• Editorial comment area/box available
• Comments can be saved
• Displays who and timestamp
• Anyone who can make a change to the article can comment
• Anyone who made a change receives an email when a comment is left

Jira: KSR-53

Acceptance

1. As a visitor I must be able to access search from any page on any device
2. As a visitor I can use advanced operands to search
3. As a visitor I want to have a way to see how I can perform advanced searches using operands
4. Highlight searched terms
5. Exclude certain fields/metadata

Jira: KSR-8

Jira: KSR-36

Jira: KSR-46

Acceptance

Usability:

• Can get to the the list of all authors with no more that 2 clicks/hovers

Functionality:

• Home page has a link that points to a page with all authors
• Link takes me to the correct page
• The page shows a segmented list of all authors
• Authors are clickable and take me to the author's page

Jira: KSR-1

UX/UI will be provided

Acceptance

• All taxonomies are implemented
• I can only choose one item of any taxonomy except for targeted region(s)

Jira: KSR-55

Jira: KSR-45

Jira: KSR-15

Good examples:

Quoted text: Editor used for commenting on Kinja sites such as gizmodo.com

Section headers, font formatting, hyperlinking and embedding: Buzzed post editor

Acceptance

• Quote block is inserted as a separate element and not as part of the body

Jira: KSR-37

Jira: KSR-42

Acceptance

• Content designed and structured to enhance reading of recipes

Jira: KSR-16

Acceptance

• Popularity should measure Facebook activity (shares + likes + comments)
• Popularity number should be visible on all tiles/polaroids (homepage and landing pages including author pages)
• Total Facebook activity should reconcile with the breakdown of activities in the ADP
• Facebook activity number should be clickable
• On click Facebook share dialog box should show up

Jira: KSR-26

3 columns: Share it, Breaking Now and New

Acceptance

1. On mobile I default to one column and can change it to one of the 2 other columns
2. On tablet portrait I should be able to choose which of the 2 columns I see

Jira: KSR-25

tweetable? A short piece of text (under Twitter's 140. character limit) that you can have in the post as pre-baked tweet and which people can tweet directly by clicking on a link.

See (using the hard way):

http://www.blogtyrant.com/click-to-tweet-this-quote-blog-posts/

Acceptance

1. As an Editor I can embed tweetable anywhere in the article
2. As an Editor I am limited to only 130 characters of text
3. As a Visitor when I click "Tweet this" the quote is automatically inserted in the tweet box along with "@kasra" and the article's short URL

Jira: KSR-20

Acceptance

• All scheduled articles show up on visual calendar
• Article title are visible in calendar
• Articles can be dragged and dropped
• Articles cannot be dropped in past dates
• Calendar indicate the scheduling time of the article
• Scheduling time can be changed in calendar view

Jira: KSR-60

Acceptance

• Editor can publish immediately
• Editor can schedule an article for publishing by choosing

-- Date

-- Time

-- Timezone

• Scheduled articles are published at the exact data and time
• If the Editor has system (local computer) time zone that is different that the UI time zone then the article must be published at the chosen time and time zone

Jira: KSR-32

Acceptance

• Validate if the author's info is filled in (own or other's)

-- Bio (minimum 50 characters)

Jira: KSR-5

Design should follow kasra.co ADP design

Acceptance

• Every post has an article detail page
• Visible article elements

-- Title

-- Secondary title

-- Header image

-- Author name

-- Author image

-- Publish date

Jira: KSR-64

Jira: KSR-51

Acceptance

1. As a visitor I should see the search results divided into different taxonomies (e.g. If I search for Katrina I want to see a the author Katrina Johnson show up in search results for authors but I also want to see articles that talked about Hurricane Katrina)
2. As I Visitor I want to clearly see the term I searched for highlighted in the search results
3. As a visitor I want to see the term I searched for in case I am searching for (e.g. search term stays in the search bar or there's a message that says "search results for 'Katrina')
4. As a visitor I want to have an indication of how many results my query returned
5. As a visitor I don't want to see duplicates in my results

Jira: KSR-9

This is a basic text editor with minimal formatting options. We want to limit the formatting options to the above in order to preserve a consistent writing style across all writers. For example no italics or strikethroughs.

I highlight a string and then click a button that says bold and it adds around it.

UX/UI will be provided

Acceptance

• Numbered list of potential titles
• Add character count - max 100 characters - to each title input

Jira: KSR-54

Design should follow:

http://www.buzzfeed.com/post

Acceptance

Create an article

• There is a button/link to create an article

Article title

• Article title is available
• Editor is able to type in an Arabic title
• Title limit is 100 characters

Article body

• Block text available to write main body
• Arabic and Right-To-Left are supported

Saving article

• There is a button/link to save the article
• Automatically generate a URL based on the article title replacing spaces with dashes
• URL is limited to 74 characters
• Error check whether URL exists already
• If URL already exists stick a -n at the end

Jira: KSR-30

WhatsApp send for iOS:

http://www.whatsapp.com/faq/en/iphone/23559013

WhatsApp send for Android:

https://www.whatsapp.com/faq/en/android/28000012

Campaign tracking code (verify with Alice):

?utm_source=WhatsApp&utm_medium=Mobile&utm_campaign=Button

Acceptance

1. Whatsapp share button appears on all iOS phones
2. Whatsapp share button appears on all Android phones
3. WhatsApp share button does not appear on tablets or desktop
4. Text shared has the full article title
5. Text shared includes the long URL (Arabic)
6. Google tracking code appended to URL
7. URL and tracking code clickable and takes user to article page
8. Article page URL path shows the tracking code

Jira: KSR-23

Buzzfeed UX/UI

Schema:

Google+

Jira: KSR-48

Jira: KSR-44

Acceptance

1. Able to toggle back and forth

Jira: KSR-21

Jira: KSR-43

Jira: KSR-58

Buzzfeed UX/UI

Acceptance

• Image can be uploaded from local computer
• Image can be .jpg, .jpeg, .png, or .gif
• Editor can choose location of the inline image block between the article body blocks
• Editor cannot hotlink some other site's image
• Article cannot be published without some type of content block (image, text, etc)
• Images wider than 800px should be scaled to 800px wide.

Jira: KSR-33

Acceptance

1. Any visitor (doesn't have to be logged in) can submit a suggestion to any published piece as inappropriate
2. The visitor cannot submit a suggestion without providing type of suggestion, first name, last name, email address and reason why they think the content is inappropriate
3. The visitor should be presented with the following suggestion types: (a) correction, (b) flag inappropriate, (c) copyright issue, (d) comment moderation or (e) other
4. The visitor should be alerted when entered data is incorrect or in the wrong format (e.g. empty field or incorrect email address format)
5. Visitor is encouraged to sign up for the newsletter when submitting their report
6. Visitors who opt-in for the newsletter should be added to the master list of newsletter subscribers
7. An acknowledgment email is sent to the visitor after submitting the form
8. A notification email is sent to the community manager alerting him/her of a new submission
9. As a community manager I should be able to see a report of all submissions along with all entered submission details and system captured details username (if logged in), timestamp, IP address, time on page
10. As a community manager I should able to accept or reject a flag
11. As a community manager I should be able to see an archive of all processed and unprocessed flags
12. As a community manager I should be able to write internal comments for each flag (e.g. "I need to discuss with author to decide whether to accept/reject")

Jira: KSR-7

Jira: KSR-63

Jira: KSR-17

Provide trigger table and email template

Acceptance

Status: Notify

Pitch: Editor

In progress: No one

Drafted: Editor

Edited: Visual designer

Visual: Proofreader

Scheduled: Editor and Writer

Jira: KSR-59

Replace short url plugin

Acceptance

• When an article is saved (before publishing) it gets assigned a short url
• Short url can not be changed by the Editor
• No two articles can share the same permalink
• Short URL points to Long URL (http 301 permanent redirect)
• Short URLs for legacy articles should be preserved
• New short urls should be a hash of the long url
• Check for collisions before saving a short url
• URLs are generated when an pitch is accepted
• URLs are frozen when an article is published

Jira: KSR-35

Acceptance

1. Article is autosaved when closing the browser and before hitting the save button
2. Autosave every 1 minute
3. Image data urls are updated with remote urls as images are saved

Jira: KSR-19

UX/UI will be provided

Acceptance

Editor can set the article status to one of the following:

• Pitch
• In progress
• Drafted
• Edited
• Visual
• Proofread
• Scheduled

Jira: KSR-31

Currently this capability if offered by Yoast Plugin

Acceptance

• Article is published with one title
• Google sees the SEO title
• SEO title is limited to 150 characters
• Defaults to article title, can be overwritten. Reverts to article title if deleted

Jira: KSR-50

Jira: KSR-18

Acceptance

• Author page should indicate with text or symbol the type of author
• Clicking on the type takes me to all authors of that type

Jira: KSR-2

Acceptance

• Editor can hit a save button
• Editor can reopen article and continue where the editor left off
• Saving works regardless of the article status
• Publish date doesn't change

Jira: KSR-49

Buzz feed UX/UI

Acceptance

• User is asked to fill in image criteria

-- source

-- etc

Jira: KSR-57

Acceptance

• World Cup content does not show up in the homepage under "Share it" or "Breaking now" columns
• Ramadan content does not show up in the homepage under "Share it" or "Breaking now" columns

Jira: KSR-28

Acceptance

• Links to parent categories and their children are available to Visitors on their tablets
• Links to parent categories and their children are available to Visitors on their mobile devices

Jira: KSR-27