Bug 1161718 - Review quickstart README metadata to optimize it for the Google search
Summary: Review quickstart README metadata to optimize it for the Google search
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Quickstarts
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER09
: 6.2.0
Assignee: Peter Palaga
QA Contact: Tomas Kyjovsky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-07 17:16 UTC by sgilda
Modified: 2017-12-08 15:08 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description sgilda 2014-11-07 17:16:54 UTC
Description of problem:

See https://issues.jboss.org/browse/JDF-787

The jboss.org development team plans to do the following:

- Parse the first line of each README file to remove the quickstart name prefix and use the rest for Google SEO title. That field is limited to ~55 characters.
- Use the 'Summary:' metadata for the description. This field is limited to 155 characters.

This information is what shows up on the search result page, so the better it better describes the example. 

I went through all the JBoss EAP quickstart README files to shorten the title and lengthen the Summary to be more descriptive. We need to do this for all of the other quickstarts, including:

* Portal: https://github.com/jboss-developer/jboss-portal-quickstarts

See related JBoss EAP bugs for details:

* https://bugzilla.redhat.com/show_bug.cgi?id=1160776
* https://bugzilla.redhat.com/show_bug.cgi?id=1159374


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Peter Palaga 2015-03-17 15:04:22 UTC
Should have been ON_QA already.

Comment 5 Filip Kiss 2015-03-18 12:30:34 UTC
Verified in 6.2.0.ER9


Note You need to log in before you can comment on or make changes to this bug.