Forum Replies Created
For what it’s worth, we use Rackspace. Expensive but top of the line (or one of the tops).
Of course they can and should be Googling that stuff, but we both know that is rarely the issue. The goal isn’t to educate the masses. The goal is to reduce the time it takes to answer those people by just posting a link.
For example. Someone recently asked how to change the color of the buttons. Yes they need to know how to adjust BP css, but they also need to know how to use tools like Firebug etc. Perhaps some feel the second part is beyond the scope of these forums (and I tend to agree), but the goal is to reduce the time it takes to reply to each. By providing them with links to non-BP tutorials it would reduce the amount of follow up questions.
As BP is made easier to develop you will be getting a lot more questions by people that don’t even know what css stands for. You have one of two choices, either try and help the helpless or turn them away frustrated by their ignorance.
You are going to have to deal with these issues as BP turns from being a a plugin mostly for developers into more of a consumer assessable plugin.
@shawn38 Yes I agree to a point. It depends greatly on traffic, plugins, etc. But, it seems from what he wrote he is beyond that point. It is technically possible to run on a shared sever, but if your goal is to create a popular site you will need to switch to dedicated at some point. That point is different for everyone, but everyone that uses BP should be prepared to make that move at some point and it can come faster than you think. It’s my personal opinion that you should start out dedicated if possible so you don’t have to deal with the pain of moving later. You should at the very least find a shared host that allows for easy expansion.
Hostmonster and Bluehost should never be used. I’m sure there are more to add to that list, but those I have confirmed will throttle you regardless of users or plugins.
This is what I purpose….
Leave the menu and markup the way it currently is. Restyle them as buttons, remove the left margin on the first child so if it breaks the horizontal plane it will neatly just create another row of buttons. The current responsive code can still be used to create a vertical column like it does now.
Create “scroll tabs/buttons”. This will be an optional feature. Because you are already loading jquery for the ajax this will require very little additional code and no additional markup. It can also be used in a responsive layout. If js is disabled it will gracefully revert back to rows.
Not only will this setup not require vertical nav it will be close to what is currently in use. That will make it easier for developers and designers to upgrade.
No, I believe they do need dedicated. BP does not run well on a shared server. I have had a Hostmonster rep tell me they throttle all BP users and so do most other shared hosts. You may be able to run for a little while but soon you will get throttled and your site will slow to the point where it is almost unusable. You simply are not going to be able to run any real social network for $20 a month.
I’m completely ignorant about ajax and only slightly better with js. Most things I can figure out by trial and error, but not with ajax.
Two of the problems I’m have is with Fitvids.js (responsive video embeds) and prettyPhoto.js (lightbox).
It doesn’t deal with dynamic menus directly, but it does deal with menus that are too large for the display (responsive nav).
Here are a couple more links (they overlap a bit):
10 Responsive Navigation Solutions and Tutorials
7 Responsive Navigation Patterns
Here are a couple articles on responsive navigation:
The Case Against Vertical Navigation:
Another option would be to do both. You could make it an option within the short code for either vertical or horizontal nav. That way the end user can decide which works better for them.
My mockup does allow for another row. It even takes care of the left padding on the first tab in the row. It is very easy to do. It also requires no js unlike vertical nav would.
This isn’t what I was talking about but here is the member page which already has 2 rows:
OK then lets talk about the problems with dynamic horizontal navigation and the solutions for it.
How about scroll tabs?
Not to beat a dead horse, but this is a great example of why vertical navigation doesn’t work. Look how small the content area is. I know it will change depending on the theme, but you have less than a 3rd of the page. Now how would images or video look in that? Not only very small, but it would also look like Times Square.
Short-codes will be a welcome addition to BP, but they still have limitations. Many things can be easily changed with a little css or by a added function or two. However, menu items are not easily changed. It will require editing core js, template tags, and possibly other core files.
Here is a shot of our Activity page from our development site and how we are using tabs as buttons:
I’m reacting because you asked for reactions.
I have studied the development tracker and know what you are working on.
Vertical navigation is a lazy last century solution. It sacrifices content area and for element blocks.
Having a dynamic horizontal menu is a problem, but there are better solutions than vertical navigation.
First thing is they should not be styled as tabs. They should be styles as buttons. That way if it breaks the row it can simple create a new row of buttons, instead of having a broken tab list.
You can also use jquery to create scrolling tabs, such as Firefox uses.
There are better ways if you really want to find them. Those are just a few. Think of how it would work in a responsive theme and let that be your guide to solving these issues.
I should not have mentioned ads. I should have discussed sidebar width(s). That is more to the point.
I know what you are trying to do with 1.7, but my point is more about Tetris than Legos, but the same concept. While 1.7 wont be a theme or contain sidebars etc, it will inject content. How that content is displayed will have an effect on what it is displayed in. Thus it should allow for the most flexibility. Using things like vertical navigation on BP elements limits this. Another thing I’ve seen in some of the examples here (thanks to those that took the time to create them) is long rows of horizontal content such as message titles, activity title blocks etc. Avatar placement is also a issue because it cuts into content width (like in this forum). I believe avatars should in in the title field and not as a bullet point off in the left margin.
I don’t like the idea of relying on js, but have you looked into scroll tabs?
Perhaps use a select box as a fall back.
The point wasn’t mobile, but if it was px still apply. My point is the content area should be as wide as possible and vertical navigation is evil.
Let me say the work done here at BP is amazing. Everyone should be thanked. I have strong opinions on things, but that doesn’t mean to say they are all correct. I just want to make this amazing code the best it can be.
Next week we will be releasing a redesign we have been working on for over a year. Once it is live hopefully I can use it as an example of our ideas about how BP can be used. Maybe even create some tutorials. I am more of a designer than a coder, so much of what I can offer will be in that regard, but I am learning more everyday.
Yes, there is no room for it.
It only works with wide or full width layouts. At a minimum the vertical menu would have to be 140px wide to be readable. Then say another 15px for the left padding. That’s 155px less for the content, no matter the theme. I believe the content area should be as wide as possible not only for more flexibility, but also because it is the most important thing on the page.
That is using 2010. These issues will multiply fast for those with more complex themes, such as 3 columns, etc. This also makes building a responsive theme for tablets, mobile etc much harder.