you should be okie to reupload the buddypress directory into wp-content/plugins without reinstalling but if it will make you feel better having a flawless installation for peace of mind go right ahead.
The overlaps are exactly what’s been happening, so unifying the theme in terms of html markup is a goal. I use Less to code CSS so minification is not a problem, just the amount of CSS there is to write in the first place.
Thanks for the heads up about bp-legacy, I meant to say that’s what I was doing and not bp-default. There was a blog about the changes and some info in the codex.
http://pixelcoder.co.uk/members/alistair is my latest endeavour with BuddyPress. It’s nowhere near complete and I’m at that stage where I’d like someone else to work with and help with the theme. To do code reviews, refinement and design.
I’m going to continue writing here as it seems to fit right now. I’m going to outline how I’ve approached BuddyPress theme development at my last iteration. Hopefully someone can see where they could jump in to help contribute to the creation of a new theme.
Concepts
Concepts have always been tough, I usually miss out some important aspect of the design. Like if I was designing a concept for the activity streams, I’d leave of the threaded comments aspect of BuddyPress. However I’ve gotten good at outlining some of the features in the concept stage. Usually I take a BuddyPress install using the Twenty Twelve theme and copy all of the components into a Photoshop document and cross-reference design like that.
The concepts would be an iterative process, with the wealth of templates in BuddyPress designing them all in Photoshop first is very desirable but not very practical. I would love to have the time to really design all components in Photoshop first before moving into code.
Templates
Taking any Photoshop concepts and making them into templates usually is a static process for me, I’ve done the activity stream page design in Photoshop, I then use a boiler plate I have to rough out the html and css of this page. Again and iterative process. If I had 1 Photoshop file to work with, let’s say BuddyPress registration, I’d do the template of that in raw HTML and CSS.
BuddyPress
Taking those templates previously coded has been a bit of a pain for me, I write markup differently to how the bp-default theme shipped, so it really is a case of building these files from scratch. Dropping in the loops, the BuddyPress function calls and actions at each template iteration. This leaves for problems, but I’ve got it down well now and know how BuddyPress works. So it’s like building a WordPress theme on steroids. I’ve even spent a while taking the bp-default theme and removing all the markup it shipped with. This makes building new BuddyPress themes a whole bunch easier to shape. Although I’m still not perfect at this.
Iteration
The above workflow procedures have served me well in getting off the ground with BuddyPress theme development but they haven’t taken me the whole way. I end up failing to use the CASCADE that CSS offers and ultimately reside to the fact I have to repeat my self lots with CSS.
The repetition I don’t fear, but the labour involved really does effect the overall fun in development and really the theme that had so much potential when building the activity stream and registration pages becomes a hard slog to getting something that works. Photoshop concepts suffer in design and the code suffers from bloat (hence my whole piece about designing all the concepts first).
