@karmatosed — placing multiple elements on screens looks like site designs to me (specifically, it looks like landing page designs), rather than simple template parts. If you keep them simple / one function, it becomes much easier for a designer / developer to make use of them in their site.
Maybe as a guideline — maximum of one loop per template part. [EDIT – which is what most of the current bp-default screens, despite their faults, manage to achieve, and pretty much as @modemlooper suggested above — It’s not an argument about no presentation vs presentation, it’s an argument of simple single function template parts vs complex layouts. @modemlooper‘s suggested approach would incorporate and display neatly all of the BuddyPress content – but do it in a simple and more re-usable way]
I think you’ve already got too many cooks without needing more wireframes from me — designing by committee is never good.
@rogercoathup: Anyone is welcome at this state to do wireframes we are considering ideas (even those ones that may be more out there). That was always the aim of this process not a design phase. We’re then going to discuss this all in this week’s developer meeting to which you are welcome to attend. Infact, as you have a valuable opinion on this I really hope you do turn up.
I think most of the designs can be done with one loop or at least for mine. Yes, the profile may not be we were explore a ‘tag/shortcode’ concept. 3column was more a ‘try’ wireframe so of course that can’t. As for the messages, stream and other ones I mocked up (can only really speak for my own) they certainly were one loop focused.
A last call if people have any wireframes can they get them up here by 17:00 UTC today. We can then use this as a list to discuss during the dev meeting tomorrow at 19:00 UTC. I suspect also the wider things discussed may be raised if people want. Ideally once we’ve looked at each wireframe though.
I’m going to do a summary post with all the wireframes in for bpdevl.wordpress.com so we can have a one place to look at during discussion and maybe gather some other opinions over night if anyone has any to contribute and can’t make the meeting. Of course, comments here are still welcome just trying to open it up to as many voices and get some summaries going on.
I want to have a go at one, but by today? Noooot going to happen Will probably be later this week; my feel is we’ll need another week at least to refine wireframes further.
I’m certainly not against more refining. Perhaps then tomorrow is more of a discussion develop from there – probably better plan. I’ll do a ‘so far’ summary post then seems fair?
i really like what modemlooper put together i was getting a similar picture in my head and was planning to take another whack today. i do think optionally adding friends and groups to the area he designated as the sidebar, in similar fashion to karmatosed’s mockup, is visually interesting and efficient would make it 3 column if thats still where we are headed.
so the question remains, in my head at least, is the default theme going to be made to be responsive?
@ubernaut: We’re not building a theme… so in short the theme can be responsive if the theme you are using is yes as the theme is around the components As for components – I think if they aren’t we’re doing something wrong. After all the theme could or couldn’t be responsive.
ok sorry for being slow here there will be no default theme as of 1.7? the de facto default would then be 2011 or whatever is WP default at the time of release?
As of 1.7 BuddyPress will not require a theme. The BP-Default theme will (as far as has been said) remain a legacy theme bundled to allow people to still be able to make the transition and have child themes of BP-Default. What we are wireframing is ideas for how the components could be laid out and function – not a theme. When you load up BuddyPress without having any theme that supports BuddyPress active – that’s what we’re looking at in wireframes.
- The topic ‘Wireframe collections’ is closed to new replies.