Menu
▾
▴
tikiwiki-artwork
|
From: luciash d' b. <lu...@ti...> - 2014-10-02 01:51:38
|
Here is how I think could the all other pages look like. Please note all the exports are done for browser viewport resolution 1024x640 and of course on larger screens there could be one of the side columns displayed (or both - but maybe that is becoming cluttered again - we should rethink if we really need all of those modules displayed around) and for smaller screens (tablets and smart phones) it would of course need to be designed and adjusted accordingly still. This is how the top header would collapse (hide) up (with CSS animation) behind the viewport edge and menu bar would slide to top when page scrolled down a bit (also notice there would be shadow appearing and the black bar becomes semi-transparent so user gets indication the bars are floating above the page content and the top right arrow for scrolling to bottom of the page would change direction with rotation animation and points up to scroll to top now): Now how the header would react when hovered near the top edge or touched/swiped on touch screen (it would reveal the top header again for quick access to the links placed in there): Also notice the Search link with font-icon - it would reveal on click the search form with search, go and edit buttons + advanced link maybe. luci |
|
From: Nelson Ko <ne...@sy...> - 2015-01-12 13:32:38
|
Hi luci, I like this idea. Can you sync up with Gary to table Community Theme as one of the discussion topics for the January webinar (Bernard has volunteered to be the coordinator) on 22 Jan? Thanks! On Wed, Oct 1, 2014 at 9:51 PM, luciash d' being <lu...@ti...> wrote: > Here is how I think could the all other pages look like. > > Please note all the exports are done for browser viewport resolution > 1024x640 and of course on larger screens there could be one of the side > columns displayed (or both - but maybe that is becoming cluttered again - > we should rethink if we really need all of those modules displayed around) > and for smaller screens (tablets and smart phones) it would of course need > to be designed and adjusted accordingly still. > > > > > This is how the top header would collapse (hide) up (with CSS animation) > behind the viewport edge and menu bar would slide to top when page scrolled > down a bit (also notice there would be shadow appearing and the black bar > becomes semi-transparent so user gets indication the bars are floating > above the page content and the top right arrow for scrolling to bottom of > the page would change direction with rotation animation and points up to > scroll to top now): > > > > > Now how the header would react when hovered near the top edge or > touched/swiped on touch screen (it would reveal the top header again for > quick access to the links placed in there): > > > > Also notice the Search link with font-icon - it would reveal on click the > search form with search, go and edit buttons + advanced link maybe. > > luci > > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Tikiwiki-artwork mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork > > |
|
From: luciash d' b. <lu...@ti...> - 2015-01-12 21:26:30
|
Hi Nelson, good idea. What do you think Gary? luci On 01/12/2015 02:32 PM, Nelson Ko wrote: > Hi luci, > > I like this idea. Can you sync up with Gary to table Community Theme > as one of the discussion topics for the January webinar (Bernard has > volunteered to be the coordinator) on 22 Jan? > > Thanks! > > On Wed, Oct 1, 2014 at 9:51 PM, luciash d' being <lu...@ti... > <mailto:lu...@ti...>> wrote: > > Here is how I think could the all other pages look like. > > Please note all the exports are done for browser viewport > resolution 1024x640 and of course on larger screens there could be > one of the side columns displayed (or both - but maybe that is > becoming cluttered again - we should rethink if we really need all > of those modules displayed around) and for smaller screens > (tablets and smart phones) it would of course need to be designed > and adjusted accordingly still. > > > > > This is how the top header would collapse (hide) up (with CSS > animation) behind the viewport edge and menu bar would slide to > top when page scrolled down a bit (also notice there would be > shadow appearing and the black bar becomes semi-transparent so > user gets indication the bars are floating above the page content > and the top right arrow for scrolling to bottom of the page would > change direction with rotation animation and points up to scroll > to top now): > > > > > Now how the header would react when hovered near the top edge or > touched/swiped on touch screen (it would reveal the top header > again for quick access to the links placed in there): > > > > Also notice the Search link with font-icon - it would reveal on > click the search form with search, go and edit buttons + advanced > link maybe. > > luci > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS > Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > Tikiwiki-artwork mailing list > Tik...@li... > <mailto:Tik...@li...> > https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork > > > > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > vanity: www.gigenet.com > > > _______________________________________________ > Tikiwiki-artwork mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork |
|
From: Gary Cunningham-L. <ga...@cu...> - 2015-01-15 14:12:01
|
Hi all, Yes, it's a good idea to discuss the Community sites theme at the 22 January webinar. About the theme design ideas that luci posted to the list, I was wondering if some details/features wouldn't have to be FiveAlive-lite-specific. That is, we have the social network layout template already that will produce the narrow page-top heading for any theme. Or, maybe there is an easy way like a profile to do the same thing with CSS only. The point being that no doubt people will see the project site and think "I'd like my pages to work like that, but I want to use 'X Theme' instead." Nelson pointed out in a conversation a few days ago that we don't want to add complexity at this point, but if the header treatment and scroll effects can be done in a way that works with any selected theme, it'd be great; or maybe as a partial step, done first for the community sites and tested and then polished up to be a feature for Tiki 15. (What I'm referring to is the narrow header as a module zone to contain the logo, menu, search, etc., and the scroll effects that luci described in the earlier emails.) -- Gary On 1/13/2015 6:26 AM, luciash d' being wrote: > Hi Nelson, > > good idea. > What do you think Gary? > > luci > > > > On 01/12/2015 02:32 PM, Nelson Ko wrote: >> Hi luci, >> >> I like this idea. Can you sync up with Gary to table Community Theme >> as one of the discussion topics for the January webinar (Bernard has >> volunteered to be the coordinator) on 22 Jan? >> >> Thanks! >> >> On Wed, Oct 1, 2014 at 9:51 PM, luciash d' being <lu...@ti... >> <mailto:lu...@ti...>> wrote: >> >> Here is how I think could the all other pages look like. >> >> Please note all the exports are done for browser viewport >> resolution 1024x640 and of course on larger screens there could be >> one of the side columns displayed (or both - but maybe that is >> becoming cluttered again - we should rethink if we really need all >> of those modules displayed around) and for smaller screens >> (tablets and smart phones) it would of course need to be designed >> and adjusted accordingly still. >> >> >> >> >> This is how the top header would collapse (hide) up (with CSS >> animation) behind the viewport edge and menu bar would slide to >> top when page scrolled down a bit (also notice there would be >> shadow appearing and the black bar becomes semi-transparent so >> user gets indication the bars are floating above the page content >> and the top right arrow for scrolling to bottom of the page would >> change direction with rotation animation and points up to scroll >> to top now): >> >> >> >> >> Now how the header would react when hovered near the top edge or >> touched/swiped on touch screen (it would reveal the top header >> again for quick access to the links placed in there): >> >> >> >> Also notice the Search link with font-icon - it would reveal on >> click the search form with search, go and edit buttons + advanced >> link maybe. >> >> luci >> >> >> ------------------------------------------------------------------------------ >> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS >> Reports >> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk >> _______________________________________________ >> Tikiwiki-artwork mailing list >> Tik...@li... >> <mailto:Tik...@li...> >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork >> >> >> >> >> ------------------------------------------------------------------------------ >> New Year. New Location. New Benefits. New Data Center in Ashburn, VA. >> GigeNET is offering a free month of service with a new server in Ashburn. >> Choose from 2 high performing configs, both with 100TB of bandwidth. >> Higher redundancy.Lower latency.Increased capacity.Completely compliant. >> vanity:www.gigenet.com >> >> >> _______________________________________________ >> Tikiwiki-artwork mailing list >> Tik...@li... >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork > > > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > www.gigenet.com > > > > _______________________________________________ > Tikiwiki-artwork mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork > |
|
From: Jonny B. <jo...@ti...> - 2015-01-16 14:54:48
|
Hi Gary and all I was hoping the "social network layout" would go away before we released/branched 14.x and that we would be able to do the same thing using the standard layout but with modules as you say. Towards this end i did create a "zone" module in https://sourceforge.net/p/tikiwiki/code/52430 and there have been a few fixes since, but i've never managed to get it "quite right" and i guess i didn't document or tell anyone about it (my bad, as usual ;) The idea is that you can add one of these to the top module zone, and then put other modules inside it, and if you give it "navbar navbar-inverse navbar-fixed-top" (as the "zone class") it should then just work and do the clever responsive collapsing stuff... however it doesn't quite :( I just made a quick profile here https://profiles.tiki.org/Bootstrap_navbar for it, not tested so be careful and for me the collapsing thing doesn't work - i think either i've misunderstood something critical or there's a bug... More soon! jonny > On 15 Jan 2015, at 14:11, Gary Cunningham-Lee <ga...@cu...> wrote: > > Hi all, > > Yes, it's a good idea to discuss the Community sites theme at the 22 > January webinar. > > About the theme design ideas that luci posted to the list, I was > wondering if some details/features wouldn't have to be > FiveAlive-lite-specific. That is, we have the social network layout > template already that will produce the narrow page-top heading for any > theme. Or, maybe there is an easy way like a profile to do the same > thing with CSS only. The point being that no doubt people will see the > project site and think "I'd like my pages to work like that, but I want > to use 'X Theme' instead." > > Nelson pointed out in a conversation a few days ago that we don't want > to add complexity at this point, but if the header treatment and scroll > effects can be done in a way that works with any selected theme, it'd be > great; or maybe as a partial step, done first for the community sites > and tested and then polished up to be a feature for Tiki 15. > > (What I'm referring to is the narrow header as a module zone to contain > the logo, menu, search, etc., and the scroll effects that luci described > in the earlier emails.) > > -- Gary > > On 1/13/2015 6:26 AM, luciash d' being wrote: >> Hi Nelson, >> >> good idea. >> What do you think Gary? >> >> luci >> >> >> >> On 01/12/2015 02:32 PM, Nelson Ko wrote: >>> Hi luci, >>> >>> I like this idea. Can you sync up with Gary to table Community Theme >>> as one of the discussion topics for the January webinar (Bernard has >>> volunteered to be the coordinator) on 22 Jan? >>> >>> Thanks! >>> >>> On Wed, Oct 1, 2014 at 9:51 PM, luciash d' being <lu...@ti... >>> <mailto:lu...@ti...>> wrote: >>> >>> Here is how I think could the all other pages look like. >>> >>> Please note all the exports are done for browser viewport >>> resolution 1024x640 and of course on larger screens there could be >>> one of the side columns displayed (or both - but maybe that is >>> becoming cluttered again - we should rethink if we really need all >>> of those modules displayed around) and for smaller screens >>> (tablets and smart phones) it would of course need to be designed >>> and adjusted accordingly still. >>> >>> >>> >>> >>> This is how the top header would collapse (hide) up (with CSS >>> animation) behind the viewport edge and menu bar would slide to >>> top when page scrolled down a bit (also notice there would be >>> shadow appearing and the black bar becomes semi-transparent so >>> user gets indication the bars are floating above the page content >>> and the top right arrow for scrolling to bottom of the page would >>> change direction with rotation animation and points up to scroll >>> to top now): >>> >>> >>> >>> >>> Now how the header would react when hovered near the top edge or >>> touched/swiped on touch screen (it would reveal the top header >>> again for quick access to the links placed in there): >>> >>> >>> >>> Also notice the Search link with font-icon - it would reveal on >>> click the search form with search, go and edit buttons + advanced >>> link maybe. >>> >>> luci >>> >>> >>> ------------------------------------------------------------------------------ >>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS >>> Reports >>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper >>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer >>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Tikiwiki-artwork mailing list >>> Tik...@li... >>> <mailto:Tik...@li...> >>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA. >>> GigeNET is offering a free month of service with a new server in Ashburn. >>> Choose from 2 high performing configs, both with 100TB of bandwidth. >>> Higher redundancy.Lower latency.Increased capacity.Completely compliant. >>> vanity:www.gigenet.com >>> >>> >>> _______________________________________________ >>> Tikiwiki-artwork mailing list >>> Tik...@li... >>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork >> >> >> >> ------------------------------------------------------------------------------ >> New Year. New Location. New Benefits. New Data Center in Ashburn, VA. >> GigeNET is offering a free month of service with a new server in Ashburn. >> Choose from 2 high performing configs, both with 100TB of bandwidth. >> Higher redundancy.Lower latency.Increased capacity.Completely compliant. >> www.gigenet.com >> >> >> >> _______________________________________________ >> Tikiwiki-artwork mailing list >> Tik...@li... >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork >> > > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > _______________________________________________ > Tikiwiki-artwork mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork |
|
From: Gary Cunningham-L. <ga...@cu...> - 2015-01-16 17:06:11
|
Hi, I understand your opinion of the "social network layout" but I kind of like its way - just one configuration step in L&F admin and the site layout is changed. It's a kind of package deal as you get the fixed topbar, and the top_modules zone gets removed, and the right amount of padding gets added to the main container to make sure that all content can be seen at the top of the page (not hidden under the topbar). I know this can all be done with modules and CSS, but it seems to me that it's more steps, and maybe not as easy for users. My current thinking is to duplicate/improve the layout that the Tiki project sites have (which is now implemented with custom CSS at the sites) using the social network layout first, as the tpl is there and pretty easy to get into shape. This CSS will be "confined" as all the rules have the template layout tpl name as the first selector, so won't interfere with the other layouts. Then the same design rules can probably be used for the My Module approach. About the standard Tiki layout, I don't know if there is one now. The Basic layout template has the one-container Bootstrap default layout and the others have variations of the three-container layout (header, middle and footer). The social network style is another variation. Each has an advantage for site design, I think. -- Gary On 1/16/2015 11:03 PM, Jonny Bradley wrote: > Hi Gary and all > > I was hoping the "social network layout" would go away before we > released/branched 14.x and that we would be able to do the same thing > using the standard layout but with modules as you say. > > Towards this end i did create a "zone" module in > https://sourceforge.net/p/tikiwiki/code/52430 and there have been a > few fixes since, but i've never managed to get it "quite right" and i > guess i didn't document or tell anyone about it (my bad, as usual ;) > > The idea is that you can add one of these to the top module zone, and > then put other modules inside it, and if you give it "navbar > navbar-inverse navbar-fixed-top" (as the "zone class") it should then > just work and do the clever responsive collapsing stuff... however it > doesn't quite :( > > I just made a quick profile here > https://profiles.tiki.org/Bootstrap_navbar for it, not tested so be > careful and for me the collapsing thing doesn't work - i think either > i've misunderstood something critical or there's a bug... > > More soon! > > jonny > > > >> On 15 Jan 2015, at 14:11, Gary Cunningham-Lee >> <ga...@cu...> wrote: >> >> Hi all, >> >> Yes, it's a good idea to discuss the Community sites theme at the >> 22 January webinar. >> >> About the theme design ideas that luci posted to the list, I was >> wondering if some details/features wouldn't have to be >> FiveAlive-lite-specific. That is, we have the social network >> layout template already that will produce the narrow page-top >> heading for any theme. Or, maybe there is an easy way like a >> profile to do the same thing with CSS only. The point being that no >> doubt people will see the project site and think "I'd like my pages >> to work like that, but I want to use 'X Theme' instead." >> >> Nelson pointed out in a conversation a few days ago that we don't >> want to add complexity at this point, but if the header treatment >> and scroll effects can be done in a way that works with any >> selected theme, it'd be great; or maybe as a partial step, done >> first for the community sites and tested and then polished up to be >> a feature for Tiki 15. >> >> (What I'm referring to is the narrow header as a module zone to >> contain the logo, menu, search, etc., and the scroll effects that >> luci described in the earlier emails.) >> >> -- Gary >> >> On 1/13/2015 6:26 AM, luciash d' being wrote: >>> Hi Nelson, >>> >>> good idea. What do you think Gary? >>> >>> luci >>> >>> >>> >>> On 01/12/2015 02:32 PM, Nelson Ko wrote: >>>> Hi luci, >>>> >>>> I like this idea. Can you sync up with Gary to table Community >>>> Theme as one of the discussion topics for the January webinar >>>> (Bernard has volunteered to be the coordinator) on 22 Jan? >>>> >>>> Thanks! >>>> >>>> On Wed, Oct 1, 2014 at 9:51 PM, luciash d' being >>>> <lu...@ti... <mailto:lu...@ti...>> wrote: >>>> >>>> Here is how I think could the all other pages look like. >>>> >>>> Please note all the exports are done for browser viewport >>>> resolution 1024x640 and of course on larger screens there could >>>> be one of the side columns displayed (or both - but maybe that >>>> is becoming cluttered again - we should rethink if we really >>>> need all of those modules displayed around) and for smaller >>>> screens (tablets and smart phones) it would of course need to >>>> be designed and adjusted accordingly still. >>>> >>>> >>>> >>>> >>>> This is how the top header would collapse (hide) up (with CSS >>>> animation) behind the viewport edge and menu bar would slide >>>> to top when page scrolled down a bit (also notice there would >>>> be shadow appearing and the black bar becomes semi-transparent >>>> so user gets indication the bars are floating above the page >>>> content and the top right arrow for scrolling to bottom of the >>>> page would change direction with rotation animation and points >>>> up to scroll to top now): >>>> >>>> >>>> >>>> >>>> Now how the header would react when hovered near the top edge >>>> or touched/swiped on touch screen (it would reveal the top >>>> header again for quick access to the links placed in there): >>>> >>>> >>>> >>>> Also notice the Search link with font-icon - it would reveal >>>> on click the search form with search, go and edit buttons + >>>> advanced link maybe. >>>> >>>> luci >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI >>>> DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? >>>> Download White paper Comply to PCI DSS 3.0 Requirement 10 and >>>> 11.5 with EventLog Analyzer >>>> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk >>>> >>>> _______________________________________________ >>>> Tikiwiki-artwork mailing list >>>> Tik...@li... >>>> <mailto:Tik...@li...> >>>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork >>>> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA. >>>> GigeNET is offering a free month of service with a new server >>>> in Ashburn. Choose from 2 high performing configs, both with >>>> 100TB of bandwidth. Higher redundancy.Lower latency.Increased >>>> capacity.Completely compliant. vanity:www.gigenet.com >>>> >>>> >>>> _______________________________________________ >>>> Tikiwiki-artwork mailing list >>>> Tik...@li... >>>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> New Year. New Location. New Benefits. New Data Center in Ashburn, VA. >>> GigeNET is offering a free month of service with a new server in >>> Ashburn. Choose from 2 high performing configs, both with 100TB >>> of bandwidth. Higher redundancy.Lower latency.Increased >>> capacity.Completely compliant. www.gigenet.com >>> >>> >>> >>> _______________________________________________ Tikiwiki-artwork >>> mailing list Tik...@li... >>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork >>> >> >> >> ------------------------------------------------------------------------------ >> >> New Year. New Location. New Benefits. New Data Center in Ashburn, VA. >> GigeNET is offering a free month of service with a new server in >> Ashburn. Choose from 2 high performing configs, both with 100TB of >> bandwidth. Higher redundancy.Lower latency.Increased >> capacity.Completely compliant. http://p.sf.net/sfu/gigenet >> _______________________________________________ Tikiwiki-artwork >> mailing list Tik...@li... >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork > > > ------------------------------------------------------------------------------ > > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in > Ashburn. Choose from 2 high performing configs, both with 100TB of > bandwidth. Higher redundancy.Lower latency.Increased > capacity.Completely compliant. http://p.sf.net/sfu/gigenet > _______________________________________________ Tikiwiki-artwork > mailing list Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork > |
|
From: Nelson Ko <ne...@sy...> - 2015-01-16 17:37:06
|
Thought I'd chime in on my opinion as well (though I am not sure if I understand all the issues involved)... I think layouts serve an important purpose in that they set the overall framing of the site, and they can also be useful to get from zero to different variants of quite a bit of functionality rather quickly for new sites/admins, However, when there is a functionality that is added, it should first be added as a module, and then into a layout. This is not to say that a particular layout cannot come with modules "baked into" it though (as that provides a quick way to shorten the process to getting useful functionality working for new users/site admins without having to go through all the modules), but it should be possible in other layouts to get the functionality too by adding modules after the fact. Does this make sense? On Fri, Jan 16, 2015 at 11:43 AM, Gary Cunningham-Lee < ga...@cu...> wrote: > Hi, > > I understand your opinion of the "social network layout" but I kind of > like its way - just one configuration step in L&F admin and the site > layout is changed. It's a kind of package deal as you get the fixed > topbar, and the top_modules zone gets removed, and the right amount of > padding gets added to the main container to make sure that all content > can be seen at the top of the page (not hidden under the topbar). I know > this can all be done with modules and CSS, but it seems to me that it's > more steps, and maybe not as easy for users. > > My current thinking is to duplicate/improve the layout that the Tiki > project sites have (which is now implemented with custom CSS at the > sites) using the social network layout first, as the tpl is there and > pretty easy to get into shape. This CSS will be "confined" as all the > rules have the template layout tpl name as the first selector, so won't > interfere with the other layouts. > > Then the same design rules can probably be used for the My Module approach. > > About the standard Tiki layout, I don't know if there is one now. The > Basic layout template has the one-container Bootstrap default layout and > the others have variations of the three-container layout (header, middle > and footer). The social network style is another variation. Each has an > advantage for site design, I think. > > -- Gary > > > On 1/16/2015 11:03 PM, Jonny Bradley wrote: > > Hi Gary and all > > > > I was hoping the "social network layout" would go away before we > > released/branched 14.x and that we would be able to do the same thing > > using the standard layout but with modules as you say. > > > > Towards this end i did create a "zone" module in > > https://sourceforge.net/p/tikiwiki/code/52430 and there have been a > > few fixes since, but i've never managed to get it "quite right" and i > > guess i didn't document or tell anyone about it (my bad, as usual ;) > > > > The idea is that you can add one of these to the top module zone, and > > then put other modules inside it, and if you give it "navbar > > navbar-inverse navbar-fixed-top" (as the "zone class") it should then > > just work and do the clever responsive collapsing stuff... however it > > doesn't quite :( > > > > I just made a quick profile here > > https://profiles.tiki.org/Bootstrap_navbar for it, not tested so be > > careful and for me the collapsing thing doesn't work - i think either > > i've misunderstood something critical or there's a bug... > > > > More soon! > > > > jonny > > > > > > > >> On 15 Jan 2015, at 14:11, Gary Cunningham-Lee > >> <ga...@cu...> wrote: > >> > >> Hi all, > >> > >> Yes, it's a good idea to discuss the Community sites theme at the > >> 22 January webinar. > >> > >> About the theme design ideas that luci posted to the list, I was > >> wondering if some details/features wouldn't have to be > >> FiveAlive-lite-specific. That is, we have the social network > >> layout template already that will produce the narrow page-top > >> heading for any theme. Or, maybe there is an easy way like a > >> profile to do the same thing with CSS only. The point being that no > >> doubt people will see the project site and think "I'd like my pages > >> to work like that, but I want to use 'X Theme' instead." > >> > >> Nelson pointed out in a conversation a few days ago that we don't > >> want to add complexity at this point, but if the header treatment > >> and scroll effects can be done in a way that works with any > >> selected theme, it'd be great; or maybe as a partial step, done > >> first for the community sites and tested and then polished up to be > >> a feature for Tiki 15. > >> > >> (What I'm referring to is the narrow header as a module zone to > >> contain the logo, menu, search, etc., and the scroll effects that > >> luci described in the earlier emails.) > >> > >> -- Gary > >> > >> On 1/13/2015 6:26 AM, luciash d' being wrote: > >>> Hi Nelson, > >>> > >>> good idea. What do you think Gary? > >>> > >>> luci > >>> > >>> > >>> > >>> On 01/12/2015 02:32 PM, Nelson Ko wrote: > >>>> Hi luci, > >>>> > >>>> I like this idea. Can you sync up with Gary to table Community > >>>> Theme as one of the discussion topics for the January webinar > >>>> (Bernard has volunteered to be the coordinator) on 22 Jan? > >>>> > >>>> Thanks! > >>>> > >>>> On Wed, Oct 1, 2014 at 9:51 PM, luciash d' being > >>>> <lu...@ti... <mailto:lu...@ti...>> wrote: > >>>> > >>>> Here is how I think could the all other pages look like. > >>>> > >>>> Please note all the exports are done for browser viewport > >>>> resolution 1024x640 and of course on larger screens there could > >>>> be one of the side columns displayed (or both - but maybe that > >>>> is becoming cluttered again - we should rethink if we really > >>>> need all of those modules displayed around) and for smaller > >>>> screens (tablets and smart phones) it would of course need to > >>>> be designed and adjusted accordingly still. > >>>> > >>>> > >>>> > >>>> > >>>> This is how the top header would collapse (hide) up (with CSS > >>>> animation) behind the viewport edge and menu bar would slide > >>>> to top when page scrolled down a bit (also notice there would > >>>> be shadow appearing and the black bar becomes semi-transparent > >>>> so user gets indication the bars are floating above the page > >>>> content and the top right arrow for scrolling to bottom of the > >>>> page would change direction with rotation animation and points > >>>> up to scroll to top now): > >>>> > >>>> > >>>> > >>>> > >>>> Now how the header would react when hovered near the top edge > >>>> or touched/swiped on touch screen (it would reveal the top > >>>> header again for quick access to the links placed in there): > >>>> > >>>> > >>>> > >>>> Also notice the Search link with font-icon - it would reveal > >>>> on click the search form with search, go and edit buttons + > >>>> advanced link maybe. > >>>> > >>>> luci > >>>> > >>>> > >>>> > ------------------------------------------------------------------------------ > >>>> > >>>> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > >>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI > >>>> DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? > >>>> Download White paper Comply to PCI DSS 3.0 Requirement 10 and > >>>> 11.5 with EventLog Analyzer > >>>> > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > >>>> > >>>> > _______________________________________________ > >>>> Tikiwiki-artwork mailing list > >>>> Tik...@li... > >>>> <mailto:Tik...@li...> > >>>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork > >>>> > >>>> > >>>> > >>>> > >>>> > ------------------------------------------------------------------------------ > >>>> > >>>> > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > >>>> GigeNET is offering a free month of service with a new server > >>>> in Ashburn. Choose from 2 high performing configs, both with > >>>> 100TB of bandwidth. Higher redundancy.Lower latency.Increased > >>>> capacity.Completely compliant. vanity:www.gigenet.com > >>>> > >>>> > >>>> _______________________________________________ > >>>> Tikiwiki-artwork mailing list > >>>> Tik...@li... > >>>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork > >>> > >>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> > >>> > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > >>> GigeNET is offering a free month of service with a new server in > >>> Ashburn. Choose from 2 high performing configs, both with 100TB > >>> of bandwidth. Higher redundancy.Lower latency.Increased > >>> capacity.Completely compliant. www.gigenet.com > >>> > >>> > >>> > >>> _______________________________________________ Tikiwiki-artwork > >>> mailing list Tik...@li... > >>> https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork > >>> > >> > >> > >> > ------------------------------------------------------------------------------ > >> > >> > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > >> GigeNET is offering a free month of service with a new server in > >> Ashburn. Choose from 2 high performing configs, both with 100TB of > >> bandwidth. Higher redundancy.Lower latency.Increased > >> capacity.Completely compliant. http://p.sf.net/sfu/gigenet > >> _______________________________________________ Tikiwiki-artwork > >> mailing list Tik...@li... > >> https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork > > > > > > > ------------------------------------------------------------------------------ > > > > > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > > GigeNET is offering a free month of service with a new server in > > Ashburn. Choose from 2 high performing configs, both with 100TB of > > bandwidth. Higher redundancy.Lower latency.Increased > > capacity.Completely compliant. http://p.sf.net/sfu/gigenet > > _______________________________________________ Tikiwiki-artwork > > mailing list Tik...@li... > > https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork > > > > > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > _______________________________________________ > Tikiwiki-artwork mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork > |
|
From: Torsten <tik...@tw...> - 2015-01-16 19:51:20
|
Hi, I agree, that functionality in general should not be added into a legacy layout - this recalls for me, why I have been not liking the specific approach of the social navbar at the first place. *BUT* We have the selfcontained themes now with a different directory structure and there is space for custom templates. *SO* What do you all think to simply change the 'social navbar' to a 'social theme' => /themes/socialtheme/templates/layout_view.tpl (<- social navbar layout). *Additionally * Couldn't this be an opportunity to create a section in themes.tiki.org for custom layout files for certain purposes? The layout files (actually the code) could be provided as code plugins on wiki pages. Aditionally a documentation section where we describe how to play around with the different templates and styles and how to customise. Just thinking. T. On 16.01.2015 18:36, Nelson Ko wrote: > Thought I'd chime in on my opinion as well (though I am not sure if I > understand all the issues involved)... > > I think layouts serve an important purpose in that they set the > overall framing of the site, and they can also be useful to get from > zero to different variants of quite a bit of functionality rather > quickly for new sites/admins, > > However, when there is a functionality that is added, it should first > be added as a module, and then into a layout. This is not to say that > a particular layout cannot come with modules "baked into" it though > (as that provides a quick way to shorten the process to getting useful > functionality working for new users/site admins without having to go > through all the modules), but it should be possible in other layouts > to get the functionality too by adding modules after the fact. > > Does this make sense? > > > |
|
From: Gary Cunningham-L. <ga...@cu...> - 2015-01-18 12:25:00
|
Hi, Some more thoughts, below: On 1/17/2015 3:10 AM, Torsten wrote: > Hi, > > I agree, that functionality in general should not be added into a legacy > layout - this recalls for me, why I have been not liking the specific > approach of the social navbar at the first place. > > *BUT* > > We have the selfcontained themes now with a different directory > structure and there is space for custom templates. > > *SO* > > What do you all think to simply change the 'social navbar' to a 'social > theme' => /themes/socialtheme/templates/layout_view.tpl (<- social > navbar layout). Sorry, but I don't think this is a good idea. I don't think people should have to choose between a layout (where things are on the page, etc.) and a theme (colors, typography, background images, white space, etc.). Suppose someone likes the social navbar idea but wants to use it with their own theme? To me, the social navbar on/off is a choice similar to one column/two columns/three columns; it should be available to all themes. I kind of think of this as a matrix with themes on one axis and layout templates (as well as modules and other content-displaying elements) on the other. This is what people generally expect to be able to do when configuring a web site. > > *Additionally * > > Couldn't this be an opportunity to create a section in themes.tiki.org > for custom layout files for certain purposes? > The layout files (actually the code) could be provided as code plugins > on wiki pages. It's a natural extension to show and discuss, etc. layout templates there. Actually the demo ability is already in place; you can choose the layout using a module. I don't know what roadmap there might be for layout templates, but if they can be a cool thing, we should promote it at themes.t.o. (Actually I have done one variation on the social networking style layout that uses only the topbar_module - no content is coded directly in the tpl. And I made a layout template for a one-column page with vertical parallel scrolling effects - maybe this can be done with Tiki's current templates but it was just an experiment.) > > Aditionally a documentation section where we describe how to play around > with the different templates and styles and how to customise. Yes, we definitely need docs on all aspects, not only templates and styles but also how to optimize site content to be responsive and display well in all devices. This is another aspect that generally people haven't had to think about before. -- Gary > Just thinking. > > T. > > > > > On 16.01.2015 18:36, Nelson Ko wrote: >> Thought I'd chime in on my opinion as well (though I am not sure if I >> understand all the issues involved)... >> >> I think layouts serve an important purpose in that they set the >> overall framing of the site, and they can also be useful to get from >> zero to different variants of quite a bit of functionality rather >> quickly for new sites/admins, >> >> However, when there is a functionality that is added, it should first >> be added as a module, and then into a layout. This is not to say that >> a particular layout cannot come with modules "baked into" it though >> (as that provides a quick way to shorten the process to getting useful >> functionality working for new users/site admins without having to go >> through all the modules), but it should be possible in other layouts >> to get the functionality too by adding modules after the fact. >> >> Does this make sense? >> >> >> > > > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > > > > _______________________________________________ > Tikiwiki-artwork mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-artwork > |
|
From: Torsten <tik...@tw...> - 2015-01-16 17:46:31
|
Hi Gary, Jonny and all, I support the idea of a non-complicated one-step (or one-configuration) approach as base for average users. Tiki is massive and I frequentlky witness users (even admins) being overchallenged by the sheer amount of options. To make basic configurations complicated in a mandatory way is imho the opposit way than the route we should go. We have to make life easier for the users. Not to missunderstand: I LOVE 'custom modules' and a 'custom module zone module' etc. might be more than awesome, make Tiki outstanding in another more aspect. But! We are on the way losing the average user. I usually use plain html Bootstrap Navbars with smarty and all types of modules and menus inside. This is one way to use Tikis capabilities. A MyModuleZone might be another way for a number of users. But the easiest way and fully appropriate I think is the layout approach of Gary. Why we should get rid of it? It is optional. T. On 16.01.2015 17:43, Gary Cunningham-Lee wrote: > ... just one configuration step in L&F admin and the site > layout is changed. It's a kind of package deal as you get the fixed > topbar, and the top_modules zone gets removed, and the right amount of > padding gets added to the main container to make sure that all content > can be seen at the top of the page (not hidden under the topbar). > > I know this can all be done with modules and CSS, but it seems to me > that it's more steps, and maybe not as easy for users. ... |
Thanks for helping keep SourceForge clean.
X