× Warning! This forum is in archival status. New contributions may not work.
static pages as an issue?
  • OK so I've created some articles and things are shaping up nicely but, now when it comes to filling the links and pages sections, pages seems to be an issue, why?

    Is there a specific reason why the about and email type pages are in an issue of there own and called static?

    Is there a reason they are called static?

    Does the static section get tied in automatically?

    Is the static section specific to the journal template or newscoop as an app?

    Why isn't this in the manual?

    Guy's if I'm sitting here scratching my head asking these questions don't you think other people will be doing the same thing. If you take the time and explain it to me I'll do a video on it. please don't take any of this as a criticism. Your documentation is far better than most opensource projects it's just that it has a few gaps in it, that's all.

    index.php/fa/90/0/

    Thanks
    Dai
  • 9 Comments sorted by
  • Vote Up0Vote Down Sava TatićSava Tatić
    Posts: 113Member, Administrator, Sourcefabric Team
    Hi Dai777,

    Static content can be handled in many ways by Newscoop, it's a matter
    of a concrete developer's choice. The Journal template package sets it
    up that way, i.e. parks the static content in a separate issue. But
    nothing gets placed there automatically. You have to add them to that
    particular issue.

    And yes, there should be a better and more intuitive way of doing it.
    We'll be addressing that in our ongoing refactoring of Newscoop.

    Now on to answers point by point:

    On Wed, Mar 16, 2011 at 12:41 PM, Dai777
    <newscoop-support@lists.sourcefabric.org> wrote:

    > Is there a specific reason why the about and email type pages are in an issue of there own and called static?
    It's a matter of convention chosen by the developer of the sample
    template package.

    > Is there a reason they are called static?

    You can call them whatever you want.

    > Do the static section get tied in automatically?

    No.

    > Is the static section specific to the journal template or newscoop as an app?

    It's specific to the Journal template package

    > Why isn't this in the manual?

    Sample template packages should come with documentation. That's
    something we will be working on, possibly as part of the forthcoming
    Newscoop cookbook.

    > Guy's if I'm sitting here scratching my head asking these questions don't you think other people will be doing the same thing. If you take the time and explain it to me I'll do a video on it. please don't take any of this as a criticism. Your documentation is far better than most opensource projects it's just that it has a few gaps in it, that's all.

    You are right, there are a gaps. And please point us to as many as you
    can (or even better, help us document stuff).

    So keep them coming.

    All the best,

    Sava

    --
    Sava Tatić
    Managing director, Sourcefabric o.p.s.
    sava.tatic@sourcefabric.org

    Salvátorská 10
    110 00 Praha 1, Czech Republic
    +420 2 22 36 25 40
    +1 647 889 2811 (Toronto)
    Skype: tictactatic

    http://www.sourcefabric.org
    http://www.twitter.com/Sourcefabric
  • Ok so if I create a static issue with all necessary pages how do I tie it to (include it in my mag/paper issue) an issue or is this done automatically? Don't fancy spending two hours creating pages as Static only to find out I'm doing it wrong and have to start all over again.

    ----- Original Message -----
    From: "Sava Tatić" <newscoop-support@lists.sourcefabric.org>
    To: dai7261@gmail.com
    Sent: Wednesday, 16 March, 2011 12:29:19 PM
    Subject: [newscoop-support] static pages as an issue?

    Hi Dai777,

    Static content can be handled in many ways by Newscoop, it's a matter
    of a concrete developer's choice. The Journal template package sets it
    up that way, i.e. parks the static content in a separate issue. But
    nothing gets placed there automatically. You have to add them to that
    particular issue.

    And yes, there should be a better and more intuitive way of doing it.
    We'll be addressing that in our ongoing refactoring of Newscoop.

    Now on to answers point by point:

    On Wed, Mar 16, 2011 at 12:41 PM, Dai777
    < newscoop-support@lists.sourcefabric.org > wrote:

    > Is there a specific reason why the about and email type pages are in an issue of there own and called static?
    It's a matter of convention chosen by the developer of the sample
    template package.

    > Is there a reason they are called static?

    You can call them whatever you want.

    > Do the static section get tied in automatically?

    No.

    > Is the static section specific to the journal template or newscoop as an app?

    It's specific to the Journal template package

    > Why isn't this in the manual?

    Sample template packages should come with documentation. That's
    something we will be working on, possibly as part of the forthcoming
    Newscoop cookbook.

    > Guy's if I'm sitting here scratching my head asking these questions don't you think other people will be doing the same thing. If you take the time and explain it to me I'll do a video on it. please don't take any of this as a criticism. Your documentation is far better than most opensource projects it's just that it has a few gaps in it, that's all.

    You are right, there are a gaps. And please point us to as many as you
    can (or even better, help us document stuff).

    So keep them coming.

    All the best,

    Sava

    --
    Sava Tatić
    Managing director, Sourcefabric o.p.s.
    sava.tatic@sourcefabric.org

    Salvátorská 10
    110 00 Praha 1, Czech Republic
    +420 2 22 36 25 40
    +1 647 889 2811 (Toronto)
    Skype: tictactatic

    http://www.sourcefabric.org
    http://www.twitter.com/Sourcefabric


  • Vote Up0Vote Down Micz FlorMicz Flor
    Posts: 184Administrator
    hi dai,

    the short answer is: there are no static pages. which is too simple an
    answer ;) because Imprint and About are on all sites. sourcefabric.org
    itself is basically a bunch of "static pages".

    how and where to put static pages depends on your template pack. you can
    do these in an issue - and put them all there. you can do that even in a
    separate publication (attention: then the search becomes and issue
    because it needs to search across publications).

    in other words: the logic of what content from where gets displayed as
    static pages depends on the template logic, the way you programmed it
    there, or the way it has been programmed in the template pack.

    if you want to work on video tutorials for these issues, possibly
    install a sample template pack and investigate inside the publication
    that is being installed along the template pack. (in fact: how to
    install template packs would be a good tutorial as well!)

    thanks, micz

    On Wed, 2011-03-16 at 13:53 +0000, Dai777 wrote:
    > Ok so if I create a static issue with all necessary pages how do I tie
    > it to (include it in my mag/paper issue) an issue or is this done
    > automatically? Don't fancy spending two hours creating pages as Static
    > only to find out I'm doing it wrong and have to start all over again.
    >
    >
    >
    >

    --
    Micz Flor
    Head of Communication, Sourcefabric
    micz.flor@sourcefabric.org

    Sourcefabric
    Prinzessinnenstraße 20
    10969 Berlin, Germany
    DE +49 (0)30 44044999

    Subscribe to our Newsletter:
    www.sourcefabric.org/newsletter/

    www.sourcefabric.org
    www.twitter.com/Sourcefabric

  • I have the sample journal installed this is how I figured it out so far. How do I create about type pages in an empty or site that is in the process of being built. I'm still none the wiser! If I want to create a bunch of page type pages and have them listed in the little boes to th eleft of the journal template as per demo site how do I do this?
    Tried last night just creating a page but, did not list in the boxes.
    ----- Original Message -----
    From: "Micz Flor" <newscoop-support@lists.sourcefabric.org>
    To: dai7261@gmail.com
    Sent: Wednesday, 16 March, 2011 2:16:55 PM
    Subject: [newscoop-support] static pages as an issue?

    hi dai,

    the short answer is: there are no static pages. which is too simple an
    answer ;) because Imprint and About are on all sites. sourcefabric.org
    itself is basically a bunch of "static pages".

    how and where to put static pages depends on your template pack. you can
    do these in an issue - and put them all there. you can do that even in a
    separate publication (attention: then the search becomes and issue
    because it needs to search across publications).

    in other words: the logic of what content from where gets displayed as
    static pages depends on the template logic, the way you programmed it
    there, or the way it has been programmed in the template pack.

    if you want to work on video tutorials for these issues, possibly
    install a sample template pack and investigate inside the publication
    that is being installed along the template pack. (in fact: how to
    install template packs would be a good tutorial as well!)

    thanks, micz

    On Wed, 2011-03-16 at 13:53 +0000, Dai777 wrote:
    > Ok so if I create a static issue with all necessary pages how do I tie
    > it to (include it in my mag/paper issue) an issue or is this done
    > automatically? Don't fancy spending two hours creating pages as Static
    > only to find out I'm doing it wrong and have to start all over again.
    >
    >
    >
    >

    --
    Micz Flor
    Head of Communication, Sourcefabric
    micz.flor@sourcefabric.org

    Sourcefabric
    Prinzessinnenstraße 20
    10969 Berlin, Germany
    DE +49 (0)30 44044999

    Subscribe to our Newsletter:
    www.sourcefabric.org/newsletter/

    www.sourcefabric.org
    www.twitter.com/Sourcefabric



  • Quote:
    Static content can be handled in many ways by Newscoop, it's a matter
    of a concrete developer's choice. The Journal template package sets it
    up that way, i.e. parks the static content in a separate issue. But
    nothing gets placed there automatically. You have to add them to that
    particular issue.



    Could you give instructions on how this is done, as I failed at it.


    --
    Sava Tatić
    Managing director, Sourcefabric o.p.s.
    sava.tatic@sourcefabric.org[/email]

    Salvátorská 10
    110 00 Praha 1, Czech Republic
    +420 2 22 36 25 40
    +1 647 889 2811 (Toronto)
    Skype: tictactatic

    http://www.sourcefabric.org
    http://www.twitter.com/Sourcefabric
    [/quote]
  • no one prepared to give instructions on how to include the static pages in the main issue.
  • Vote Up0Vote Down Sava TatićSava Tatić
    Posts: 113Member, Administrator, Sourcefabric Team
    HI Dai777,

    The author of the Journal templates has been busy preparing for an
    implementation project. If you can be patient for a while longer, I am sure
    he'll explain the logic he used to you. Won't you Ljubo?

    All the best,

    Sava
    On Mon, Mar 21, 2011 at 8:43 PM, Dai777 <
    newscoop-support@lists.sourcefabric.org> wrote:

    > no one prepared to give instructions on how to include the static pages
    > in the main issue.
    >



    --
    Sava Tatić
    Managing director, Sourcefabric o.p.s.
    sava.tatic@sourcefabric.org

    Salvátorská 10
    110 00 Praha 1, Czech Republic
    +420 2 22 36 25 40
    +1 647 889 2811 (Toronto)
    Skype: tictactatic

    http://www.sourcefabric.org
    http://www.twitter.com/Sourcefabric

  • Hello Dai777,

    we ususally put static pages in some special issue, number one for example. You can make it in one section or in several sections, your choice.

    If it's issue no. 1 and section no. 5, and articles are of type 'page', in template you would say

    {{ local }}
    {{ set_issue number="1" }}
    {{ set_section number="5" }}

    Now you can work with articles, for example making unordered list of article names linked to their full pages -

    <ul>
    {{ list_articles constraints="type is page" }}

    <li><a href="{{ uri options="Article" }}">{{ $gimme->article->name }}</a></li>

    {{ /list_articles }}
    </ul>

    And never forget to close local,

    {{ /local }}

    (about the 'local' - here: http://wiki.sourcefabric.org/display/NsLingo/Local)
    --
    Ljuba Rankovic
    Senior Front End Developer, Sourcefabric
    ljuba.rankovic@sourcefabric.org

    http://www.sourcefabric.org
    http://www.twitter.com/Sourcefabric
  • Is this how the Journal template ties in the static pages. Can you tell me which file contains this code if it is, so I can examine the code (I'm lazy, besides it good to look at the code).

    Can you tell when the main app will tie in the static pages automatically as you make the statement designed by journalists for journalists not designed by journalists for web developers. Not trying to be picky but, the vast majority of people just want an app the is point and click to leave them concerntrate on journalism.

    thanks Dai