Wow, looks great! If you are interested in getting some exposure on our blog, email me at db AT wildapricot.com.
Looks good, nice and clean!
Checked it out, nicely done!
Russell, thanks for your understanding and support, much appreciated!
Hey Russell - I really appreciate this detailed feedback and will share it with a bunch of people on our team.
We are quite aware of the challenges in customization of WA sites - and have been looking for solutions. The reason behind this crazy complicated CSS is because we currently use the same HTML for all the themes in WA - so we had to go for an 'overkill' with DIVs to achieve the level of variety in themes (and we are still not satisfied with what we have).
We have been researching various options and eventually decided that we have to totally overhaul our CMS architecture - and we have been going down this this path starting in mid 2010.
You might want to review this thread for additional background:
In our next update 4.2 we are finally rolling out this new architecture - slowly and carefully, to minimize potential problems with existing heavily customized sites. Basically 4.2 will run on a totally new different templating architecture and it will become possible (as a beta) to do HTML customization of templates. Version 4.3 will follow-up on that and offer a new CMS UI to use new capabilities.
So please be patient with us and stay tuned for version 4.2 (May) and let's resume this dialog once you have a chance to lay with 4.2 and review the documentation. It will not address all of your comments right away but I am confident that it puts us on the right path to take WA CMS/customization to the new level.
FYI - If you wish, we can switch off the HTML cleaning script for your account. Just contact tech support.
Hey mitchiedog, thanks for a great comment! This is exactly the kind of input we are looking for!
I will forward this to our team working on the redesign of our template engine - and we will also discuss internally what else we can do to address the issues you raised.
Thanks, appreciate the post - good point.
One specific and very important item we are looking for feedback on is this:
We have heard from our partners that they find it hard to customize WA templates.
We are hearing you and we definitely want to address this - so we would highly appreciate inout from - as detailed and specific as possible:
what kind of customization issues you are facing when customizing WA templates? How would you ideally like to see it changed?
Thanks for sharing! Nice look, simple and elegant.
By the way, you might want to explore Theme Overrides for even deeper customization if needed:
Though my personal opinion is that for usability reasons showing login fields makes it easier for people to find/recognize login for what it is.
Sherrie, thanks, looks good!
Kyle, thanks for sharing, very nice site!
This looks like a customization created by our partner who helped them with their site - Nicasio http://www.nicasiodesign.com/wild-apricot.php
@Melodee - thanks for sharing, I like how simple and clean your site is!
I really like this one (customized by our partner NIcasio):
Good looking site!
Good point, I will discuss with my team what we can do about this. Maybe we can post on our newspage something like cool site of the week.
For current Wild Apricot clients - if you want to show off cool design or features of your site, feel free to post comments here - this will also give you a bit of Google SEO juice as our website ranks quite well.
I believe this help page addresses your question:
Let us know if you need additional information.
It's a bit complex but let's give it a try:
var userTextContainer = document.createElement('DIV');
userTextContainer.className = 'cssUserTextContainer';
userTextContainer.innerHTML = userAfterLoginBoxText;
var userLoginContainer = document.getElementById('idLoginContainer');
userNavigationContainer = userLoginContainer.parentNode;
Insert into Advanced CSS customization: DIV.cssUserTextContainer
margin: 10px 0px;
As we did not get any other requests regarding this, we have decided to remove it from our wishlist for now.
The thing with documents is that depending on document type and user settings it will either be either downloaded or opened inline. So target has less effect than for links.
Nevertheless this is a valid request and we will add it to our list.
We are discussing this and will follow-up with you.