[Design Team] #90: no way to cleanly associate images with articles in insight - using ugly hack

[fedora-badges]

#90: no way to cleanly associate images with articles in insight - using ugly
hack
--------------------------------------+-------------------------------------
Reporter:  mchua                      |       Owner:  duffy        
    Type:  task                       |      Status:  new          
Priority:  major                      |   Component:  HTML/CSS Work
Severity:  Long-Term / Complex Issue  |    Keywords:  insight      
--------------------------------------+-------------------------------------
 from mizmo, formerly at https://fedorahosted.org/marketing-team/ticket/52
 (see discussion there)

afaik the way zikula is currently configured there is no way to cleanly
 associate images with articles in insight. i'll try to break this down
 clearly:

* our zikula instance currently does not allow for uploading and
 hosting images. so you need to upload your images and host them from
 somewhere external to zikula.
     * when people see images they are interested in on the front page of
 insight, they are going to want to be able to click the image to zoom in
 on it. right now that isn't possible without handwritten html. you need to
 upload a thumb version and a full size version of the image externally,
 then wrap the img tag of the thumb with a link tag to point out to the
 full size image. and that is hacky.
     * the mechanism for displaying images on the front page is extremely
 fragile. you need to put the img tag for the article as the VERY FIRST
 thing in the 'lead page teaser' field of the article. if you dont it can
 mess up how it comes out looking. also, you CANNOT add an img tag in the
 'lead page teaser' field of an article that is in the 'featured stories'
 area to the left of mmcgrath's picture on the top - it will blow
 everything up.

[fedora-badges]

#90: no way to cleanly associate images with articles in insight - using ugly
hack
--------------------------------------+-------------------------------------
Reporter:  mchua                      |        Owner:  duffy        
    Type:  task                       |       Status:  new          
Priority:  major                      |    Component:  HTML/CSS Work
Severity:  Long-Term / Complex Issue  |   Resolution:               
Keywords:  insight                    |  
--------------------------------------+-------------------------------------
Comment (by mchua):

I moved this ticket to the design queue primarily because I think the
 ideal workflow is something that needs to be spec'd out by a designer
 ("how would you like to be able to do this?") - so in my mind, ''that'' is
 the first part of the task at hand here. It may be that after that portion
 of the task is done, the implementation will need to be taken up by
 someone else, but we'll cross that bridge when we come to it.

[fedora-badges]

#90: no way to cleanly associate images with articles in insight - using ugly
hack
--------------------------------------+-------------------------------------
Reporter:  mchua                      |        Owner:  nobody       
    Type:  task                       |       Status:  new          
Priority:  major                      |    Component:  HTML/CSS Work
Severity:  Long-Term / Complex Issue  |   Resolution:               
Keywords:  insight                    |  
--------------------------------------+-------------------------------------
Changes (by duffy):

* owner:  duffy => nobody

[fedora-badges]

#90: no way to cleanly associate images with articles in insight - using ugly
hack
--------------------------------------+----------------------------
Reporter:  mchua                      |       Owner:  nobody
    Type:  task                       |      Status:  closed
Priority:  major                      |   Component:  HTML/CSS Work
Severity:  Long-Term / Complex Issue  |  Resolution:  invalid
Keywords:  insight                    |  Blocked By:
Blocking:                             |
--------------------------------------+----------------------------
Changes (by ryanlerch):

* resolution:   => invalid
 * status:  new => closed