librelist archives

« back to archive

More config? External menus?

More config? External menus?

From:
Nicolas Doye
Date:
2013-08-21 @ 20:29
Hi all,

I'm thinking of adding a couple of features to Nesta, but first I want to 
check that they'd be useful, they're not already in there and that I 
understand the design properly.

The main feature I want is to have menu items that are links to external sites.
The other feature is to add more stuff in the config. (From what I can see
@keywords in layout.haml is never set so would be a prime candidate).

Question: how much abuse of the supplied views is too much? I could do 
some of this, but I figured others may like or need it.

Back to menus. menu.txt is just a list of local file locations, so to 
extend this to remote resources, we'd need some optional syntax in there 
or make it an option to have another file (menu.haml/mdown etc.) which 
could be used. (Clearly this brings in other issues).

It would be quite simple to make menu.txt behave so that if the link looks
like a markdown link (for example), it gets rendered as an external link. 
Does that sound OK? Obviously, people who have files called 
[stupid-example](http://whatever.example).haml on their filesystem are 
going to be screwed, but I'm going to go out on a limb and say no-one has 
files starting with '[' on any existing Nesta installation.

nic

http://worldofnic.org
@nicdoye




Re: [nesta] More config? External menus?

From:
Graham Ashton
Date:
2013-08-22 @ 09:21
On 21 Aug 2013, at 21:29, Nicolas Doye <nic@worldofnic.org> wrote:

> I'm thinking of adding a couple of features to Nesta, but first I want 
to check that they'd be useful, they're not already in there and that I 
understand the design properly.

Hi Nic. Always a good plan to check in first.

> The main feature I want is to have menu items that are links to external sites.

The menu.txt file is (conceptually, at least) intended to be used for 
local navigation (both primary and secondary). As such I'd never 
considered using it to link to external sites. Technically it'd be easy 
(URLs could just be used in place of a path to a page in menu.txt, and 
words to label it could follow the URL, separated by a space), but 
logically, I'm not sure it's a good idea. I'm up for being persuaded, it's
just that right now I don't see the use case.

Are you keen to intermingle local and remote links the in the sidebar, 
without any organisation or labelling? From a design point of view, how 
would this look?

If you take a look at the side bar on http://effectif.com/ you'll see a 
bunch of links organised into groups. Only the Topics section has links 
from menu.txt, the rest are just coded up in sidebar.haml. If you want to 
take a similar approach, I'd recommend this:

  $ mkdir -p views
  $ cp $(bundle show nesta)/views/sidebar.haml views/

Covered in more detail here:

http://nestacms.com/docs/design/editing-default-templates

Perhaps you were thinking of just adding links to menu.txt and pulling 
small sections in with the `Nesta::Menu.for_path` helper? You'd still need
a separate side bar template to add some labelling though.

The menus down the side of nestacms.com's doc pages are pulled in 
separately like that. See:

Links to the code and an example of the results should help explain what I mean...

https://github.com/gma/nestacms.com/blob/master/views/docs_index.haml

http://nestacms.com/docs/creating-content/menus

> Question: how much abuse of the supplied views is too much? I could do 
some of this, but I figured others may like or need it.


It's encouraged to whatever degree you want/need to do it. The supplied 
views are there to give you a good starting point if you want a simple 
blog design, but I often skin up commercial sites from scratch.

> The other feature is to add more stuff in the config. (From what I can 
see @keywords in layout.haml is never set so would be a prime candidate).

Something like this pull request from Sean Redmond, perhaps?

https://github.com/gma/nesta/pull/136

I plan on merging that.

Oh, and @keywords should be page specific, so is set with the keywords meta tag:

http://nestacms.com/docs/creating-content/metadata-reference#keywords_meta_tag

Cheers,
Graham

Re: [nesta] More config? External menus?

From:
Nicolas Doye
Date:
2013-08-22 @ 10:06
Hi Graham,

   1. I misunderstood the use of Nesta's supplied views
   2. You're right, abusing menu.txt is the wrong thing to do. Coding it up
   is better (also, see point 1 above).
   3. Sean Redmond's change is better (more comprehensive/flexible) than
   what I was thinking.
   4. Of course, you're right about keywords.

Thanks for putting me straight on these. And for not calling me an idiot ;-)

I'm using Nesta on OpenShift and am really enjoying the simplicity of
editing markdown files and pushing the changes through git. So big thanks
for all your work.

nic


On 22 August 2013 10:21, Graham Ashton <graham@effectif.com> wrote:

> On 21 Aug 2013, at 21:29, Nicolas Doye <nic@worldofnic.org> wrote:
>
> > I'm thinking of adding a couple of features to Nesta, but first I want
> to check that they'd be useful, they're not already in there and that I
> understand the design properly.
>
> Hi Nic. Always a good plan to check in first.
>
> > The main feature I want is to have menu items that are links to external
> sites.
>
> The menu.txt file is (conceptually, at least) intended to be used for
> local navigation (both primary and secondary). As such I'd never considered
> using it to link to external sites. Technically it'd be easy (URLs could
> just be used in place of a path to a page in menu.txt, and words to label
> it could follow the URL, separated by a space), but logically, I'm not sure
> it's a good idea. I'm up for being persuaded, it's just that right now I
> don't see the use case.
>
> Are you keen to intermingle local and remote links the in the sidebar,
> without any organisation or labelling? From a design point of view, how
> would this look?
>
> If you take a look at the side bar on http://effectif.com/ you'll see a
> bunch of links organised into groups. Only the Topics section has links
> from menu.txt, the rest are just coded up in sidebar.haml. If you want to
> take a similar approach, I'd recommend this:
>
>   $ mkdir -p views
>   $ cp $(bundle show nesta)/views/sidebar.haml views/
>
> Covered in more detail here:
>
> http://nestacms.com/docs/design/editing-default-templates
>
> Perhaps you were thinking of just adding links to menu.txt and pulling
> small sections in with the `Nesta::Menu.for_path` helper? You'd still need
> a separate side bar template to add some labelling though.
>
> The menus down the side of nestacms.com's doc pages are pulled in
> separately like that. See:
>
> Links to the code and an example of the results should help explain what I
> mean...
>
> https://github.com/gma/nestacms.com/blob/master/views/docs_index.haml
>
> http://nestacms.com/docs/creating-content/menus
>
> > Question: how much abuse of the supplied views is too much? I could do
> some of this, but I figured others may like or need it.
>
>
> It's encouraged to whatever degree you want/need to do it. The supplied
> views are there to give you a good starting point if you want a simple blog
> design, but I often skin up commercial sites from scratch.
>
> > The other feature is to add more stuff in the config. (From what I can
> see @keywords in layout.haml is never set so would be a prime candidate).
>
> Something like this pull request from Sean Redmond, perhaps?
>
> https://github.com/gma/nesta/pull/136
>
> I plan on merging that.
>
> Oh, and @keywords should be page specific, so is set with the keywords
> meta tag:
>
>
> http://nestacms.com/docs/creating-content/metadata-reference#keywords_meta_tag
>
> Cheers,
> Graham
>



-- 
web: http://worldofnic.org
twitter: @nicdoye

Re: [nesta] More config? External menus?

From:
Jake Subs
Date:
2013-08-22 @ 12:38
> I'm using Nesta on OpenShift

Out of interest, how are you finding OpenShift? Do they have a
low-volume free plan like heroku?

Was thinking of using them for a different project...

On 22 August 2013 11:06, Nicolas Doye <nic@worldofnic.org> wrote:
> Hi Graham,
>
> I misunderstood the use of Nesta's supplied views
> You're right, abusing menu.txt is the wrong thing to do. Coding it up is
> better (also, see point 1 above).
> Sean Redmond's change is better (more comprehensive/flexible) than what I
> was thinking.
> Of course, you're right about keywords.
>
> Thanks for putting me straight on these. And for not calling me an idiot ;-)
>
> I'm using Nesta on OpenShift and am really enjoying the simplicity of
> editing markdown files and pushing the changes through git. So big thanks
> for all your work.
>
> nic
>
>
> On 22 August 2013 10:21, Graham Ashton <graham@effectif.com> wrote:
>>
>> On 21 Aug 2013, at 21:29, Nicolas Doye <nic@worldofnic.org> wrote:
>>
>> > I'm thinking of adding a couple of features to Nesta, but first I want
>> > to check that they'd be useful, they're not already in there and that I
>> > understand the design properly.
>>
>> Hi Nic. Always a good plan to check in first.
>>
>> > The main feature I want is to have menu items that are links to external
>> > sites.
>>
>> The menu.txt file is (conceptually, at least) intended to be used for
>> local navigation (both primary and secondary). As such I'd never considered
>> using it to link to external sites. Technically it'd be easy (URLs could
>> just be used in place of a path to a page in menu.txt, and words to label it
>> could follow the URL, separated by a space), but logically, I'm not sure
>> it's a good idea. I'm up for being persuaded, it's just that right now I
>> don't see the use case.
>>
>> Are you keen to intermingle local and remote links the in the sidebar,
>> without any organisation or labelling? From a design point of view, how
>> would this look?
>>
>> If you take a look at the side bar on http://effectif.com/ you'll see a
>> bunch of links organised into groups. Only the Topics section has links from
>> menu.txt, the rest are just coded up in sidebar.haml. If you want to take a
>> similar approach, I'd recommend this:
>>
>>   $ mkdir -p views
>>   $ cp $(bundle show nesta)/views/sidebar.haml views/
>>
>> Covered in more detail here:
>>
>> http://nestacms.com/docs/design/editing-default-templates
>>
>> Perhaps you were thinking of just adding links to menu.txt and pulling
>> small sections in with the `Nesta::Menu.for_path` helper? You'd still need a
>> separate side bar template to add some labelling though.
>>
>> The menus down the side of nestacms.com's doc pages are pulled in
>> separately like that. See:
>>
>> Links to the code and an example of the results should help explain what I
>> mean...
>>
>> https://github.com/gma/nestacms.com/blob/master/views/docs_index.haml
>>
>> http://nestacms.com/docs/creating-content/menus
>>
>> > Question: how much abuse of the supplied views is too much? I could do
>> > some of this, but I figured others may like or need it.
>>
>>
>> It's encouraged to whatever degree you want/need to do it. The supplied
>> views are there to give you a good starting point if you want a simple blog
>> design, but I often skin up commercial sites from scratch.
>>
>> > The other feature is to add more stuff in the config. (From what I can
>> > see @keywords in layout.haml is never set so would be a prime candidate).
>>
>> Something like this pull request from Sean Redmond, perhaps?
>>
>> https://github.com/gma/nesta/pull/136
>>
>> I plan on merging that.
>>
>> Oh, and @keywords should be page specific, so is set with the keywords
>> meta tag:
>>
>>
>> http://nestacms.com/docs/creating-content/metadata-reference#keywords_meta_tag
>>
>> Cheers,
>> Graham
>
>
>
>
> --
> web: http://worldofnic.org
> twitter: @nicdoye



-- 
[~] Jake Rayson
[w] www.jrayson.co.uk
[e] subs@growdigital.org
[t] @growdigital

Re: [nesta] More config? External menus?

From:
Nicolas Doye
Date:
2013-08-22 @ 13:30
You can have 3 gears for free (each gear is a website/application/etc). I
believe 3 gears is the equivalent of one EC2 t1.micro instance.

They're easy to spin up and take down. (Using the rhc command or the web
interface). I've used them for both Sinatra and Java EE 6 apps. I have a
test one talking to MongoHQ, too, ready for when I have time to do
something...

They have some sort of auto-scaling magic if you have enough spare gears.
(I haven't tried that).

Plus you can download OpenShift Origin and run a dev/test server at home if
you want.

I did have a site stop at once, so I'd monitor it externally if it was for
a customer.

nic


On 22 August 2013 13:38, Jake Subs <subs@growdigital.org> wrote:

> > I'm using Nesta on OpenShift
>
> Out of interest, how are you finding OpenShift? Do they have a
> low-volume free plan like heroku?
>
> Was thinking of using them for a different project...
>
> On 22 August 2013 11:06, Nicolas Doye <nic@worldofnic.org> wrote:
> > Hi Graham,
> >
> > I misunderstood the use of Nesta's supplied views
> > You're right, abusing menu.txt is the wrong thing to do. Coding it up is
> > better (also, see point 1 above).
> > Sean Redmond's change is better (more comprehensive/flexible) than what I
> > was thinking.
> > Of course, you're right about keywords.
> >
> > Thanks for putting me straight on these. And for not calling me an idiot
> ;-)
> >
> > I'm using Nesta on OpenShift and am really enjoying the simplicity of
> > editing markdown files and pushing the changes through git. So big thanks
> > for all your work.
> >
> > nic
> >
> >
> > On 22 August 2013 10:21, Graham Ashton <graham@effectif.com> wrote:
> >>
> >> On 21 Aug 2013, at 21:29, Nicolas Doye <nic@worldofnic.org> wrote:
> >>
> >> > I'm thinking of adding a couple of features to Nesta, but first I want
> >> > to check that they'd be useful, they're not already in there and that
> I
> >> > understand the design properly.
> >>
> >> Hi Nic. Always a good plan to check in first.
> >>
> >> > The main feature I want is to have menu items that are links to
> external
> >> > sites.
> >>
> >> The menu.txt file is (conceptually, at least) intended to be used for
> >> local navigation (both primary and secondary). As such I'd never
> considered
> >> using it to link to external sites. Technically it'd be easy (URLs could
> >> just be used in place of a path to a page in menu.txt, and words to
> label it
> >> could follow the URL, separated by a space), but logically, I'm not sure
> >> it's a good idea. I'm up for being persuaded, it's just that right now I
> >> don't see the use case.
> >>
> >> Are you keen to intermingle local and remote links the in the sidebar,
> >> without any organisation or labelling? From a design point of view, how
> >> would this look?
> >>
> >> If you take a look at the side bar on http://effectif.com/ you'll see a
> >> bunch of links organised into groups. Only the Topics section has links
> from
> >> menu.txt, the rest are just coded up in sidebar.haml. If you want to
> take a
> >> similar approach, I'd recommend this:
> >>
> >>   $ mkdir -p views
> >>   $ cp $(bundle show nesta)/views/sidebar.haml views/
> >>
> >> Covered in more detail here:
> >>
> >> http://nestacms.com/docs/design/editing-default-templates
> >>
> >> Perhaps you were thinking of just adding links to menu.txt and pulling
> >> small sections in with the `Nesta::Menu.for_path` helper? You'd still
> need a
> >> separate side bar template to add some labelling though.
> >>
> >> The menus down the side of nestacms.com's doc pages are pulled in
> >> separately like that. See:
> >>
> >> Links to the code and an example of the results should help explain
> what I
> >> mean...
> >>
> >> https://github.com/gma/nestacms.com/blob/master/views/docs_index.haml
> >>
> >> http://nestacms.com/docs/creating-content/menus
> >>
> >> > Question: how much abuse of the supplied views is too much? I could do
> >> > some of this, but I figured others may like or need it.
> >>
> >>
> >> It's encouraged to whatever degree you want/need to do it. The supplied
> >> views are there to give you a good starting point if you want a simple
> blog
> >> design, but I often skin up commercial sites from scratch.
> >>
> >> > The other feature is to add more stuff in the config. (From what I can
> >> > see @keywords in layout.haml is never set so would be a prime
> candidate).
> >>
> >> Something like this pull request from Sean Redmond, perhaps?
> >>
> >> https://github.com/gma/nesta/pull/136
> >>
> >> I plan on merging that.
> >>
> >> Oh, and @keywords should be page specific, so is set with the keywords
> >> meta tag:
> >>
> >>
> >>
> http://nestacms.com/docs/creating-content/metadata-reference#keywords_meta_tag
> >>
> >> Cheers,
> >> Graham
> >
> >
> >
> >
> > --
> > web: http://worldofnic.org
> > twitter: @nicdoye
>
>
>
> --
> [~] Jake Rayson
> [w] www.jrayson.co.uk
> [e] subs@growdigital.org
> [t] @growdigital
>



-- 
web: http://worldofnic.org
twitter: @nicdoye

Re: [nesta] More config? External menus?

From:
Graham Ashton
Date:
2013-08-22 @ 14:29
Also, in case anybody was thinking of trying it, we have docs:

http://nestacms.com/docs/deployment/openshift

On 22 Aug 2013, at 14:30, Nicolas Doye <nic@worldofnic.org> wrote:

> You can have 3 gears for free (each gear is a website/application/etc). 
I believe 3 gears is the equivalent of one EC2 t1.micro instance.
> 
> They're easy to spin up and take down. (Using the rhc command or the web
interface). I've used them for both Sinatra and Java EE 6 apps. I have a 
test one talking to MongoHQ, too, ready for when I have time to do 
something...
> 
> They have some sort of auto-scaling magic if you have enough spare 
gears. (I haven't tried that).
> 
> Plus you can download OpenShift Origin and run a dev/test server at home
if you want.
> 
> I did have a site stop at once, so I'd monitor it externally if it was 
for a customer.
> 
> nic
> 
> 
> On 22 August 2013 13:38, Jake Subs <subs@growdigital.org> wrote:
> > I'm using Nesta on OpenShift
> 
> Out of interest, how are you finding OpenShift? Do they have a
> low-volume free plan like heroku?
> 
> Was thinking of using them for a different project...

Re: [nesta] More config? External menus?

From:
Jake Subs
Date:
2013-08-22 @ 14:40
Good to know, thank you :)

On 22 August 2013 15:29, Graham Ashton <graham@effectif.com> wrote:
> Also, in case anybody was thinking of trying it, we have docs:
>
> http://nestacms.com/docs/deployment/openshift
>
> On 22 Aug 2013, at 14:30, Nicolas Doye <nic@worldofnic.org> wrote:
>
>> You can have 3 gears for free (each gear is a website/application/etc).
I believe 3 gears is the equivalent of one EC2 t1.micro instance.
>>
>> They're easy to spin up and take down. (Using the rhc command or the 
web interface). I've used them for both Sinatra and Java EE 6 apps. I have
a test one talking to MongoHQ, too, ready for when I have time to do 
something...
>>
>> They have some sort of auto-scaling magic if you have enough spare 
gears. (I haven't tried that).
>>
>> Plus you can download OpenShift Origin and run a dev/test server at 
home if you want.
>>
>> I did have a site stop at once, so I'd monitor it externally if it was 
for a customer.
>>
>> nic
>>
>>
>> On 22 August 2013 13:38, Jake Subs <subs@growdigital.org> wrote:
>> > I'm using Nesta on OpenShift
>>
>> Out of interest, how are you finding OpenShift? Do they have a
>> low-volume free plan like heroku?
>>
>> Was thinking of using them for a different project...
>



-- 
[~] Jake Rayson
[w] www.jrayson.co.uk
[e] subs@growdigital.org
[t] @growdigital