Feature #7670

Shorten the press/ page

Added by sycamoreone 2014-07-27 18:22:56 . Updated 2015-03-22 12:15:11 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2014-07-27
Due date:
% Done:

50%

Feature Branch:
sycamoreone:doc/rework-press-page
Type of work:
Website
Blueprint:

Starter:
0
Affected tool:
Deliverable for:

Description

The press/ page should be reworked.
It is getting quite long and unwieldy.

For example the older media appearances
could go into sub-pages.


Subtasks


History

#1 Updated by sycamoreone 2014-07-27 18:41:07

  • Tracker changed from Bug to Feature
  • Status changed from New to Confirmed

#2 Updated by BitingBird 2014-07-27 19:56:25

If it were possible to have the previous years’content hidden, and to click on them to open it, would be great. Does some CSS magic do that?

#3 Updated by intrigeri 2014-07-27 20:02:18

> If it were possible to have the previous years’content hidden, and to click on them
> to open it, would be great. Does some CSS magic do that?

We have similar tricks on the download page.

#4 Updated by tchou 2014-07-28 14:53:18

Split “Page for journalist” and “Media appearances”

Hello,

I think the point was to split the page too :

  • A page for journalist (a first draft)
    • Announcements and press releases
    • Quick links to better understand Tails
    • + add logos and illustration
    • + good way to write us
  • A page for “Media appearances”

And maybe “Awards”, “Video” and “Books” should go somewhere else, in dedicated places.

For the “page for journalists”, we could have a look to other (FLOSS or not) project to have a look the have it is (maybe I should do a feature for that and asign it to me).

#5 Updated by sajolida 2014-07-28 18:26:32

> If it were possible to have the previous years’content hidden, and to click on them to open it, would be great. Does some CSS magic do that?

We can do that with the toggle and toggleable directives of ikiwiki:

http://ikiwiki.info/ikiwiki/directive/toggle/
http://ikiwiki.info/ikiwiki/directive/toggleable/

We’re already doing something similar on the Download page with the ISO
verification instructions.

#6 Updated by sycamoreone 2014-07-28 19:01:26

tchou wrote:
> And maybe “Awards”, “Video” and “Books” should go somewhere else, in dedicated places.
>
> For the “page for journalists”, we could have a look to other (FLOSS or not) project to have a look the have it is (maybe I should do a feature for that and asign it to me).

tchou: Maybe you look into a page for journalists and I take a stab at splitting up / adding some markup to the existing page?

#7 Updated by sycamoreone 2015-02-21 07:15:59

  • Assignee set to sycamoreone

#8 Updated by sycamoreone 2015-02-24 20:54:22

Using the toggle directive works nicely.

I now have 2014-2011 as toggle-able sections like on the download page. Should I also make “Awards”, “Conferences” etc. toggle-able?

And do you have any objections against putting the content of these sections into “media_appearances_201x” pages to be included as inline pages (like it is done on the download page)?

#9 Updated by BitingBird 2015-02-24 22:35:47

I think Awards and Conferences are not big enough for it to be worth hidding yet.

No opinion on inline pages, if you think it’s better I’d say do it :)

#10 Updated by KingdomKeeper 2015-02-24 23:09:25

sycamoreone wrote:
> The press/ page should be reworked.
> It is getting quite long and unwieldy.
>
> For example the older media appearances
> could go into sub-pages.

Something that I would suggest is that instead of hosting a press page is to create a downloadable media kit. The kit would contain notable awards and mentions in the press (updated as needed), downloadable vector and JPEG/PNG logo, and any other relevant information at the time.

#11 Updated by sajolida 2015-02-26 15:18:03

> Using the toggle directive works nicely.

Looks like a good idea.

> And do you have any objections against putting the content of these
> sections into “media_appearances_201x” pages to be included as inline
> pages (like it is done on the download page)?

What do we gain by doing this? We usually use inline when the same
content needs to be used in different places. Is it the case here?
Otherwise, if we can keep the content of page and only add toggle on top
of that I think that’s enough.

#12 Updated by sycamoreone 2015-03-02 19:29:03

sajolida wrote:
> > Using the toggle directive works nicely.
>
> Looks like a good idea.
>
> > And do you have any objections against putting the content of these
> > sections into “media_appearances_201x” pages to be included as inline
> > pages (like it is done on the download page)?
>
> What do we gain by doing this? We usually use inline when the same
> content needs to be used in different places. Is it the case here?

The content might be used in a media kit, as suggested by KingdomKeeper, but right now it isn’t used anywhere else. The rationale would be that there is a lot of content between the open and end tags of the directives, so it is quite hard to see the structure.

#13 Updated by sajolida 2015-03-03 12:54:25

Fair enough, do that.

#14 Updated by sycamoreone 2015-03-12 21:53:56

  • Status changed from Confirmed to In Progress
  • Assignee deleted (sycamoreone)
  • QA Check set to Ready for QA
  • Feature Branch set to sycamoreone:doc/rework-press-page

#15 Updated by sycamoreone 2015-03-12 22:00:02

  • Assignee set to sajolida
  • Target version set to Tails_1.3.2

#16 Updated by BitingBird 2015-03-12 22:03:36

  • % Done changed from 0 to 50

#17 Updated by sajolida 2015-03-13 14:47:14

  • Subject changed from Rework the press/ page to Shorten the press/ page
  • Status changed from In Progress to Resolved
  • Assignee deleted (sajolida)
  • QA Check deleted (Ready for QA)

Merge sycamoreone:doc/rework-press-page as of today. I renamed this ticket as “Shorten the press/ page” (it’s initial description and what has been done so far). So I can close it. sycamoreone if you want to continue working on one of the many ideas that were raised in the previous comments, please create dedicated tickets as I think they will need more discussion and development than this one.

#18 Updated by BitingBird 2015-03-13 15:16:37

Youhou, congrats! It looks really great :)

#19 Updated by BitingBird 2015-03-22 12:15:11

  • Target version changed from Tails_1.3.2 to Tails_1.3.1