Re: [rt-pmc] Paragraph URLs

[Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx>]

I'm not smart enough with php to trim to paragraphs etc  I was just going to butcher the text at some number of characters (and perhaps follow it with "this project doesn't really know what they are doing and is trying to mask that fact by using a lot of words)  OMG?!  Did I type that out loud?  ;-)

But seriously, butchering the paragraphs is a fallback position.  I'd much rather have the teams figure out a good, *concise*, paragraph that describes their project.

As for where it is used, I don't know about the RT project paragraphs in particular they are intended to be used in scenarios like this.  You can see this sort of thing in action on the WTP page (http://eclipse.org/webtools).  Those subproject descriptions are paragraph blurbs supplied by the different subprojects.

The general model is that projects have a "full description" that can cover the project in all its glory. For situations where brevity is an asset, the "paragraph description" comes to play. The key point is brevity as that is the reason for the notion of paragraph descriptions/urls in the first place.

Jeff

On 2010-10-06, at 4:28 PM, Jesse McConnell wrote:

> If you trim dynamically to the first paragraph that would be fine for
> jetty...if you want it just flat out shorter let me know and I'll chop
> it down..but that paragraph is used in other locations I believe is it
> not?
> 
> jesse
> 
> --
> jesse mcconnell
> jesse.mcconnell@xxxxxxxxx
> 
> 
> 
> On Wed, Oct 6, 2010 at 15:20, Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx> wrote:
>> Thanks (almost) everyone for setting up their paragraph project descriptions and URL value in the project database.  The new RT page [0] is coming along.
>> 
>> I do have one request: Please trim your paragraph descriptions.
>> 
>> The point of the paragraph is to convey, in a very minimal format, the jist of your project. All the content has to do is motivate people to click on the project link to find out more. In isolation a few more lines does not hurt but in aggregate it makes the project list very long and daunting.  The paragraph text is meant specifically for aggregation in lists like we see on the new RT page.  So in an effort to manage the overall page length, I suggest that project paragraphs should render no more than ~4 lines on the RT project web page.
>> 
>> One of the values of this effort is that it forces you to decide what the heck your project is doing!
>> 
>> If you really want to have a longer paragraph description then make the first 4 lines count as I may trim excess when rendering the RT page if it starts getting too long.
>> 
>> Jeff
>> 
>> [0] http://eclipse.org/rt/testweb
>> 
>> _______________________________________________
>> rt-pmc mailing list
>> rt-pmc@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/rt-pmc
>> 
> _______________________________________________
> rt-pmc mailing list
> rt-pmc@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/rt-pmc