BuddyPress.org

BP Codex is working https://codex.buddypress.org/

Re Group pages, check out https://wordpress.org/extend/plugins/buddypress-docs/

If you are using the BuddyPress template pack then deactivate it.

You use the groups extension API https://codex.buddypress.org/developer-docs/group-extension-api

what @hnla said plus I want to add we should use the WordPress codex as a template on how to structure the content. People are familiar with WordPress and it makes sense to display the content as such.

@misterhill

1. Initial scan reveals that we can make the templates compatible by creating two/three files only and uploading it to your theme folder in server. The thing is, the page title won’t look like the “Contact Us” title on this page http://themes.blahlab.com/vagenta/?page_id=70 but would be within the content area of the left column. If you prefer that the page titles on the BP templates look like that of “Contact Us” title, then you’d need to revise 16 BP template files

I would opt for creating two/three files only intead of revising 16 files. What say you?

2. Either way. Open up your theme’s header.php file, copy all source, paste in pastebin.com, click submit, and post the generated URI here. If you haven’t changed anything in the header-buddypress.php as well as the code for the page.php posted in pastebin links posted above, no need to repost. But I need you to paste your theme’s index.php, loop-page.php, sidebar.php and footer.php files in pastebin and post the pastebin url’s here.

Thanks for your comments and interesting discussion so far. If it feels that BuddyPress is evolving quickly; great! I’d to point out some numbers about how long the last few releases took:

1.2 – 1.5 = ~18 months
1.5 – 1.6 = ~9 months
1.6 – 1.7 (what we’re building now) = ~3 months so far.

We would like to eventually have around 3 major versions of BuddyPress out every year; we need to speed up and attract new contributors to achieve this. I don’t think the frequency of releases has any direct correlation to the quality or quantity of articles on the Codex.

If anyone would like to group together and work on the codex in a co-ordinated way, we’d love that. Let us know what we can do to help.

@hnla You are precisely correct if we allowed everyone to contribute to the codex it would be a conglomerate of miss-information. Imagine what buddypress would be like if we just allowed anyone to contribute. Honestly I personally think it would be a nightmare. I think we need to get a team that is willing and able to work on this. Just as buddypress has a core team, we need a codex team. Not separating one from the other because they need to be synchronized and share information. Can we try to get this team rolling somehow? How do we recruit the best and most knowledgeable? They would also need a common meeting place for codex discussion so where shall it be?

@aaron-nall – where can I check to see if/when your plugin has been released?

Hi

ok, what you did is not a mess but this is simple full width page.
If you want to get it in eight row div than put buddypress layout in that div before sidebar div.

There have been a few attempts to kick start the codex the last not being the first. It is the case that those that have the ability and knowledge required to add accurate and worthwhile entries are also jobbing pros and time is the enemy earning a living having to take precedence on time available then any free time generally given over to development projects.

On the last attempts to organize, I tried to emphasize the need for preliminary organizing and structuring of the codex before diving in and adding (the principle of simply get stuff in there then worry about organizing is counter productive and leaves info dotted around hard to find with no one willing to the boring task of finding and moving around) imho this is still required, partly as doing so identifies what information is actually required and focusses attention and efforts.

On a somewhat contentious note there are two factors that ought to be accepted, as mentioned earlier, in reality allowing anyone to dive in and add detail is not necessarily a good idea, yes I understand the principle of general participation and how that ought to produce the fastest route to a comprehensive set of docs, but in reality it is more likely to produce or possibly produce docs with bad practise advice or just plain inaccurate advice. If this is allowed then you have to have someone checking all entries to ensure they are valid. The second point is that focus must be on dev docs, not! on beginners guides – necessarily – The need for detailed lists of all template tags, functions grouped by component, what works in the components , how to deal with same functions or function requirements outside of those components or loops, how BP works all the nav aspects, how to then modify and customize those aspects. Some of this does exist but it needs re-shaping and bringing up to date. There needs to be a top level overview that sets out the principles so the work flow is understood and which then drills down into detail.

On the above point about where discussions are held, there was and is a group, threads from last time; if the the irc dev chat isn’t the place then that group/threads should be re-animated

@ethanvan I’ve also just emailed you for a copy – @aaron-nall – I’m looking forward to trying out your plugin too…

@modemlooper I agree with you. Everyone chipping in is not the right approach. That means you got the blind leading the blind no offense to the blind of course. Only people who know the inner workings of the software should contribute otherwise the codex will be full of blunders and misinformation. I don’t know the software as well as some but I know enough to know this is an undertaking that needs strong leadership to get this up to par. Why bring it up in a dev chat when you can do it here? There should not be a gleek club of certain people that is relevant. Closing off others is one of the reasons the codex is a mess and plugin development has slowed down. I do not mean everyone should be able to contribute because that would create a mess but the people that are the most qualified and willing to devote their time should be the ones leading otherwise I don’t see this project going much further in the future because it will only contain a gleek club of people with the same philosophies and old ideas. Its time for some fresh talent to come in with new ideas and help out if they are willing to do so! The codex is the key to acquiring this talent. A good starting point for coders will benefit the project immensely.

@mercime We had a team but it fell apart after a few weeks. I think it’s because there was no leadership. It was a do anything to help approach and that seems daunting. WordPress has loads more people on development/documentation and that is the reason this codex is behind. Just not enough people/time to get it done. We should bring this up during the dev chat.

What is bbp.org? Does the same thing happen when you use the bp-default theme? It would help if you provide more information about your installation.

EDIT – Is this in relation with your post re BP Group Hierarchy plugin https://buddypress.org/community/groups/creating-extending/forum/topic/bp-group-hierarchy-enhanced/ ?

Great points raised in this thread. All are welcome to contribute to and improve the BuddyPress Codex. We can set up a BP Codex team to help audit and work on the documentation hand in hand, er, shoulder to shoulder with the BP core devs.

No. The plugin has its own theme files. You just need to create a mobile version of your custom page inside the plugin folder. buddypress-mobile/templates/default/page.php <- duplicate and convert to custom

Deactivate BuddyPress Group Extras plugin. It requires the Group component which you deactivated. @travis123

@wpnewbie69 please feel free to post at
https://buddypress.org/community/groups/bp-jobs-board/forum/
http://jobs.wordpress.net/

@ethanvan has a good point. The codex needs documentation badly. I have noticed a slowdown in plugin development and its precisely because even experienced coders have no reference. It seems like there is a select few that know how to do this. It would definitely make things better if these developers had education from documentation on the codex versus making guesses. I think there needs to be a firm initiative set with getting the codex up to par, and if people like @ethanvan are willing to devote their time to documenting the codex then the core team should welcome the effort and start a team of people who are willing to do this and send them documentation about new changes before new versions of the software is released so everything is more synchronized. I know its open source and people do this in their own time so spare me the lecture. I am about solutions, not drama! @travel-junkie it would help greatly if people learned to crawl before they walk so the philosophy you shared only holds back development because there should be more than just a gleek club of people that knows how to get around the inner workings of the software. There is strength in numbers so get the people who are the best to contribute instead of being like a hidden society.

@ethanvan I will email you at the address mentioned above because I would like to see if I can fix the plugin if so I will send you a working copy. Thanks!