The final details for our North America data center (located in Ottawa) have been set. The move has been scheduled to occur on Sunday, 29 May 2011, starting with 12:00 AM EDT (check local times here).

During the migration, we will be moving all Business Catalyst sites and application infrastructure hosted on our legacy North America datacenter (located in Ottawa) to our new United States datacenter (located in New Jersey). The migration will take approximately 8 hours; during this time, any sites that are hosted on Ottawa datacenter will not be accessible and instead be replaced by a system maintenance message.

Sites hosted on other datacenters including Sydney, Dublin, and the new US datacenter will be unaffected. Partner Portal access and site creation will also be unaffected.

  • What's Happening?: We are migrating all sites and Business Catalyst application infrastructure from Ottawa to New Jersey in one bulk-move
  • Start Time: 12:00AM EDT Sunday 29 May 2011  (check local times here)
  • End Time: 8:00AM EDT Sunday 29 May 2011 (check local times here)
  • How Long Will It Take? We will have a scheduled maintenance window of 8 hours, during which all sites hosted on Ottawa will be unavailable (both frontend and Admin console access). Once the maintenance is complete all sites will automatically be up again with both frontend and Admin Console access.
  • What are we doing? We are going to replicate all databases between Ottawa and New Jersey. We will also setup a high-speed direct datalink between the 2 locations, to ensure databases are kept in sync prior and during the migration. At the scheduled time of the migration we will reconfigure DNS settings and make other related Business Catalyst architectural changes to point to the New Jersey datacenter. We will also need to restart all web servers.
  • Customer Action Required - sites hosted on legacy Ottawa datacenter with redelegated DNS: After the migration is complete you will need to update your DNS nameservers from ns[01,02,03].businesscatalyst.com to ns[1,2,3].worldsecuresystems.com.
  • Customer Action Required - sites hosted on legacy Ottawa datacenter with 3rd party hosted DNS: After the migration is complete you will need to change your DNS settings with your DNS host i.e GoDaddy etc, to point to the IP address of the New Jersey data center (192.150.2.140). This will re-enable FTP access to your site.
  • Customer Action Required - sites hosted on legacy Ottawa datacenter need to update payment gateway settings: Following the migration, customers using Optimal Payments, EBS, SagePay or Internet Secure payment gateways will need to update the Business Catalyst IP address in their payment gateway account. For each site affected, you will need to login to the payment gateway provider's Administration Console and update the provided IP address from 69.20.239.58 to 192.150.2.4

Communication Plan for Affected Sites

Like for the previous migrations, we've set-up a dedicated site to host information about migration scehdule and required actions: http://status-ottawa.businesscatalyst.com/

In addition to that, we're also going to send a series of email notifications to affected Partners and affected site owners who are billed directly by Business Catalyst. White-labeled Partners will need to notify their own customers about the scheduled maintenance. We have prepared sample emails which you can download here. Here is a list of emails you should expect until the migration:

  1. Monday 9 May - 1st Notification is sent to affected Partners and Site Owners with details of the scheduled migration and action required afterwards
  2. Thursday 12 May - Email containing a list of affected sites with their domains and whether the domain is redelegated to BC or hosted with a 3rd party registrar is sent to affected Partners
  3. Tuesday 17 May - Email containing a list of websites for which partners or customers need to update Business Catalyst IP in their payment gateway account; email will be sent to affected partners
  4. Moday 23 May - 2nd Notification is sent to affected Partners and site owners with details of the scheduled migration and action required afterwards
  5. Friday 27 May - 3rd and Final notification is sent to affected Partners and site owners.
  6. Monday 30 May - Partners and site owners will receive a notification when the maintenance is completed

Feel free to ask any questions through the comments thread below, and we'll answer as soon as possible.

Thank you,
Cristinel Anastasoaie
Adobe Business Catalyst Product Manager

View Comments

Last update: 4:00 AM BST 3 April

Migration from Legacy London Datacenter to New Dublin Datacenter is complete. Systems are up and operational as at 4:00 AM BST 3 April.

Pre-deployment

Task Status
Set-up high speed direct datalink between Legacy London DC and new Dublin DC
Done
Set-up reverse proxy server  Done
Execute migration dry-run Successful
Send first (out of 3) warning email communication to Customers Done
Enable Information Site at http://status-london.businesscatalyst.com
Done
Send second (out of 3) warning email communication to Customers Done
Send third and final email communication to Customers Done
Disable system alerts in London Datacenter
Done

Deployment

Task Status
Start maintenance Done
Stop email campaigns, workflow notifications on London Done
Enable maintenance page for sites on London Done
Shut down FTP & web servers on London Done
Shut down FTP, disable and queue email campaigns and workflow notifications in Dublin Done
Replicate London content (database & assets) in Dublin Done
Start final content synchronization (databases and assets) between London and Dublin Done
Reconfigure migrated sites in Dublin Done
Restart web servers on Dublin Done
Validate data on Dublin Done
Reconfigure DNS settings Done
Start-up reverse proxy server on London Done
Shut down maintenance pages Done
Enable system alerts on Dublin Done
Close maintenance with final validation checks
Done

Thank you for your patience and cooperation,
Eddy Chan
Adobe Business Catalyst Product Manager

View Comments

This is a notification that BC's European datacenter migration is scheduled to occur at 10:00PM Saturday 2 April. (check local times here). We will be moving all Business Catalyst sites and application infrastructure hosted on our legacy London datacenter to our new Dublin datacenter. The migration will take 8 hours; during this time, any sites that are hosted on London will not be accessible and instead be replaced by a system maintenance message.

Sites hosted on other datacenters including Sydney, Dublin, legacy North America and the new US datacenter will be unaffected. Partner Portal access and site creation will also be unaffected.

  • What's Happening?: We are migrating all sites and BC application infrastructure from London to Dublin in one bulk-move
  • Start Time: 10:00PM Saturday 2 April 2011 - check local times here
  • End Time: 6:00AM Sunday 3 April 2011 - check local times here
  • How Long Will It Take? We will have a scheduled maintenance window of 8 hours, during which all sites hosted on London will be unavailable (both frontend and Admin console access). Once the maintenance is complete all sites will automatically be up again with both frontend and Admin Console access.
  • What are we doing? We are going to replicate all databases between London and Dublin. We will also setup a high-speed direct datalink between the 2 locations, to ensure databases are kept in sync prior and during the migration. At the scheduled time of the migration we will reconfigure DNS settings and make other related BC architectural changes to point to the new Dublin Datacenter. We will also need to restart all web servers.
  • Customer Action Required - sites hosted on legacy London DC with redelegated DNS: After the migration is complete you will need to update your DNS nameservers from ns[01,02,03].businesscatalyst.com to ns[1,2,3].worldsecuresystems.com. Please see our informational site for more details
  • Customer Action Required - sites hosted on legacy London DC with 3rd party hosted DNS: After the migration is complete you will need to change your DNS settings with your DNS host i.e GoDaddy etc, to point to the IP address of the Dublin datacenter (192.150.8.140). This will re-enable FTP access to your site. Please see our informational site for more details

Communication Plan for Affected Sites

In addition to having setup an minisite at http://status-london.businesscatalyst.com/ to help you understand what is happening and provide detailed instructions, we will also be sending a series of notification emails to affected Partners and affected site owners who are billed directly by Business Catalyst. For white-labelled Partners, you will need to notify your own customers of the scheduled maintenance; we have prepared material which you can send to them, please download from here. Here's a list of emails you should be expecting throughout the week.

  1. Friday 24 March - 1st Notification is sent to affected Partners and Site Owners with details of the scheduled migration and action required afterwards
  2. Monday 28 March - Email containing a list of affected sites with their domains and whether the domain is redelegated to BC or hosted with a 3rd party registrar is sent to affected Partners
  3. Tuesday 29 March - 2nd Notification is sent to affected Partners and site owners with details of the scheduled migration and action required afterwards
  4. Friday 1 April - 3rd and Final notification is sent to affected Partners and site owners.
  5. Sunday 3 April - Partners and site owners will receive a notification when the maintenance is completed
Thanks for reading, please feel free to ask any questions via the comment thread below and I'll try to post an answer up as soon as possible.
Eddy Chan
Business Catalyst Product Manager
View Comments
Cristinel Anastasoaie

Asia-Pacific data center migration is completed

Last update: 10:45AM February 20, 2011

We have just finnished the migration of all sites from the Asia Pacific (legacy Sydney) data center to our new data center in Sydney.

Quick summary

  • Sites previously hosted on Asia Pacific (legacy Sydney) DC are now hosted on the new Sydney DC
  • All Sydney sites with internal DNS are now delivered from the new data center and are loading really fast
  • Old Sydney sites with external DNS are delivered through the reverse proxy solution and working fine, performance seems to be stable
  • FTP service does not work for sites with external DNS previously hosted on Asia Pacific (legacy Sydney) DC; you will need to update DNS information to fix this problem
  • Sites hosted on other data center are fully operational, all services are working

At this point systems are stable and we are confident that the migration was successful. Our operations and engineering team are working on final configurations on the new Sydney data center but we can declare that the migration is completed.

You can proceed with updating DNS settings:

If you discover any problem with your site following the migration, please report it to our support team.

Thank you all for your support through the process,
Cristinel Anastasoaie
Adobe Business Catalyst Product Manager

View Comments
Cristinel Anastasoaie

Update on migration schedule and duration

Last update: 3:00 AM February 19, Australian EDT

During this week, our engineering and operations teams executed a series of dry-runs to better predict the maintenance window duration as well as identify potential roadblocks.

While we haven't discovered anything that might stop us from going ahead with our migration plans, the exercises revealed that fact that we are reaching the 6 hours limit while executing the plan and therefore have no buffer time left.

In order to mitigate this risk we have decided to add 2 additional hours to the maintenance window. Thus, the migration will start at 12:00 AM February 20 Sydney time and last for 8 hours. Please use a time zone converter to find out the time in your local time zone.

I have udpated the already published communication on the bcstatus.com website to include these updates. Please expect the final email communication to be sent on Saturday, February 19.

Thank you,
Cristinel Anastasoaie
Adobe Business Catalyst Product Manager

View Comments
Cristinel Anastasoaie

Important: Final Migration Schedule

Important: For all future updates surrounding the migration, please refer to the dedicated bcstatus.com website.

Last update: 2:00 AM February 19, Australian EDT

This is the final announcement of the Sydney datacenter migration plan. The dry-run has been successfully completed and we have a green light to proceed with the migration plan previously made public.

Important notice: While confident that the migration will take place at the scheduled date and time, we are continuing to investigate migration scenarios. If between this announcement and the scheduled migration time we discover anything that might put the migration at risk, we are going to put our plan on hold until we find a solution.

As part of this migration, all sites located on the legacy Sydney datacenter will experience an offline maintenance window of up to 8 hours. Action will be required on your behalf - please read on for further details.

  • What is happening: We are migrating all sites and BC application infrastructure from Sydney Primus to Sydney Ultimo in one bulk-move
  • Target Start Date/Time: 12:00AM Sunday 20 February 2011 (Australian EDT) | 5:00AM Saturday 19 February 2011 (US Pacific) | 1:00PM Saturday 19 February 2011 (London) | Check local times here
  • Target End Date/Time: 8:00AM Sunday 20 February 2011 (Australian EDT) | 1:00PM Saturday 19 February 2011 (US Pacific) | 9:00PM Saturday 19 February 2011 (London) | Check local times here
  • How Long Will It Take? We will have a scheduled maintenance window of 8 hours, during which all sites hosted on Sydney Primus will be unavailable. Partner Portal access and new site creation will be unavailable at this time as well.
  • What are we doing? We will be replicating all databases between Sydney Primus and Sydney Ultimo. We will also setup a high-speed direct datalink between the 2 locations, to ensure databases are kept in sync prior to the migration. At the scheduled time of the migration we will reconfigure DNS settings and make other related BC architectural changes to point to the new Ultimo Datacenter. We will also need to restart all web servers.

Customer Impact

During the migration Business Catalyst services will be entirely or partially not available. See the below table for a high-level overview of the impacted services depending on their location:

Data centers Impact Details
Asia Pacific (legacy Sydney DC) 8 hours downtime; all services will be unavailable More details below
All other data centers Some services will not be available More details below

Actions required

Following the migration some actions are required on your behalf. Check the below for a summary of necessary actions:

Customers Action required Reason Details
Sites previously hosted on Asia Pacific (legacy Sydney) DC with external DNS Must update their DNS settings to point to the new data center IP address. Sydney legacy data center IP address will be decomissioned 60 days following the migration. More details below
All customers with domains redelegation to BC (including customers on Sydney) Must update nameserver information to point to new Business Catalyst nameservers. Legacy nameservers will be decommissioned  in 60 days following the migration More details below

Customer Impact - details

  • All Customers (on any data center): During the 8 hour maintenance window, you will experience the following:
    • BC Extension for Dreamweaver and Triangle will not work
    • BC Partners won't be able to login into Partner Portal
    • All user management functions will be unavailable (i.e. create user, edit user, delete user)
    • DNS management tools will be unavailable
    • Setting a start page will not work
    • Clicking "Webmail" from the Admin Console will not work
    • Users will receive an error upon logout
    • Users may experience intermittent logouts as session tokens expire
    • Users who are associated with a Partner Site on the legacy DC will be unable to login to all sites
  • Sites hosted on legacy Sydney data center: In addition to the above, all sites hosted on legacy Sydney data center will be offline for the maintenance window of 8 hours. There will be no front-end pages being served or Admin Console access.

If you have sites on the Legacy Sydney DC (Primus) with externally hosted DNS, you will receive a list of these affected sites via email on Friday, February 18.

Once the migration is completed, all sites will be fully functional with two exceptions:

  • Search will be unavailable for up to 2 days for All sites hosted on Asia Pacific (legacy Sydney) data center
  • FTP will be unavailable for Sites hosted on Asia Pacific (legacy Sydney) data center with internal DNS until DNS settings are updated.

Steps you need to take - externally hosted DNS

In order to ensure a smooth migration for your customers, please action the following steps:

Step 1. Email your affected clients our pro-forma notice email

We have published a set of pro-forma notification emails which you can send to your clients to warn them of the upcoming migration and the impact it will have on their site. There are two versions:

  • Whitelabled-email.html is the unbranded version and you should customize and use this version if you are a Premium Partner who has rebranded the CMS. You will need to change the logo at the top and put your own signature at the bottom before sending it out
  • Businesscatalyst-email.html is the BC branded version if you prefer to use our brand and name when sending the email to your clients. It contains the same migration details.

You can download the notification email package here.

Step 2. Set TTL down to 1800 for all client sites that have externally hosted DNS

For partners or site owners with externally hosted DNS, we advise you to set the TTL for your records down to 1800 (30 minutes) during the next week in preparation for the migration so that when you do make the required IP address change following the migration, the settings will take a shorter amount of time to propagate.

In the coming days you will receive a separate email from support@businesscatalyst.com including a complete list client sites under your Partner Portal that have their DNS hosted externally.

Step 3. Following migration, change the IP address of A-Records for all sites with externally hosted DNS

For all sites with externally hosted DNS, you will be required to update your DNS settings with your DNS host following the migration. This involves updating the IP address your domain points to, to match the IP address of the new Sydney Ultimo data center. We recommend that you update your external DNS settings as soon as possible following the migration.

Please refer to this page for detailed instructions on updating your external DNS settings.

The engineering team will be keeping a proxy server in the legacy Sydney Data center so that all requests coming in to the old legacy IP addresses will get routed through to the new data center transparently. Likewise the pages being served will come from the new DC through the proxy server back out to customers. This is not a permanent solution but gives you a longer window in which to make your DNS changes and also lessens impact to your customers when you do make the change. We will likely keep the proxy server running for a minimum of at least 30 days after the migration before we fully decommission the legacy data center.

Steps you need to take - internal (redelegated) DNS

For all other sites (including those hosted on all other datacenters) with domains redelegated to Business Catalyst, you will need to update your DNS redelegation to use our new nameservers. This process involves redelegating your domain from our legacy name servers (which use .businesscatalyst.com sub-domains), to our new name servers (which use .worldsecuresystems.com sub-domains). For instructions please refer to this knowledgebase article. You will have a time window of 60 days to do this following completion of the migration.

Following this date, we will be decommissioning our legacy nameservers.

Stay up to date

For the latest information regarding this upcoming migration, please bookmark and refer to:

As the BC Blog is itself hosted on the legacy AU datacenter, it will be unavailable during the migration. To keep you up to date, we've launched an independent site at bcstatus.com where you'll find all the latest news during the migration period.

Kind Regards,
Cristinel Anastasoaie
Adobe Business Catalyst Product Manager 

View Comments
Cristinel Anastasoaie

New Updates on Sydney Datacenter Migration

Date: 14 February 8:00AM Australian Eastern Daylight

I am posting to give you some updates on the Sydney legacy DC migration status.

Today we were scheduled to have a migration dry-run, but we ran into some last minute problems while setting up the rehearsal. More specifically, we were missing power adapters for some drives and they're not something you could find at the local store. This means the migration dry-run has been moved to Tuesday, February 15th.

Although we're moving the dry-run date, the scheduled migration date on Saturday is NOT in jeopardy.

However, until we are absolutely sure that the migration will happen on 20th, we will not be kicking off any email communication. This has been placed on hold until Wednesday, February 16th. I know this will be short notice, but the we don't want to risk having people make plans for Sunday only to have to cancel them a day later.

I've also updated the previous post to make sure it includes the new dates. I will keep you posted once I will get more information.

Thank you,
Cristinel Anastasoaie
Business Catalyst Product Manager

View Comments
Cristinel Anastasoaie

Another Update on Sydney Datacenter Migration - UPDATED

UPDATED: 14 February 8:00AM Australian Eastern Daylight

Updates: The dry-run has been pushed to Tuesday, February 15. First email communication will be sent on Wednesday, February 16.

For those who don't know who I am, I'm Cristinel, Eddy's Product Management counterpart from the Bucharest office in Romania. We work closely together in a team with Bardia on BC's product strategy and customer communications. Eddy has been in Bucharest this week working together with myself and the engineering team here.

In the coming weeks I will be driving the datacenter migration from a customer communications point of view as the timing of the migration means that it's favorable to manage this from Europe rather than from the US West Coast.

I want to share some information on where we are at with the migration plan and which are the next actions we'll take.

Sites will be Fully Functional after Migration

The engineering team has been working on improving the migration process this week to make it less disruptive to Partners and Site Owners. Technically speaking, we will be running a reverse proxy in the legacy datacenter after the migration is complete to redirect http requests to the new datacenter. The responses from the new datacenter will then be redirected through the reverse proxy to person browsing the site or logging in to the Admin Console.

What this means is that sites will be fully functional after the migration without any intervention from you regardless of whether you update the DNS settings or not. Customers will be able to browse the sites and Site Owners will be able to login to the Admin Console.

However you will still need to make changes to the DNS settings to keep sites running in the medium-term. Instead of making the changes in sync with the migration, you will now have 60 days to make these updates as that's how long we will keep the reverse proxy running for. This gives you the option of scheduling when you want to make the changes yourself. We will extend this window if required.

Migration Dry-Run Happening on Tuesday (section updated)

Partners have been requesting more information and detailed instructions that they can use themselves or send out to their site owner clients. We have held off on sending these out because the Engineering team will be performing the final dry run (in other words a 'dress rehearsal') for the migration on Tuesday after which we will know for sure that the migration will be occurring at the scheduled time and the estimated downtime is accurate.

Detailed Communications Plan for the Migration

Once the dry-run is successful and we have the final confirmation that the migration will be occurring at the scheduled time this is the detailed plan for the communications that we will be sending to you and your customers.

  1. Emails to BC Partners with client sites hosted on legacy Sydney Primus DC to inform about sites being migrated to a new DC
    1. First warning will be sent on Wednesday, February 16 at 12:00 PM (Australian EDT) | check local times here
    2. Final warning will be sent on Friday, February 18 at 16:00 (Australian EDT) | check local times here
    3. Email contains a summary of the migration plan, scheduled start and end time, impact on your customers, ask to update DNS settings and links email templates to send to your customers, related documentation and Service Status Pages
  2. Emails to BC Site owners with direct billing relationship with BC to inform their site is being migrated to a new DC
    1. First warning will be sent on Wednesday, February 16 at 12:00 PM (Australian EDT) | check local times here
    2. Final warning will be sent on Friday, February 18 at 16:00 (Australian EDT) | check local times here
    3. Email contains a summary of the migration plan, scheduled start and end time, impact to their Business, ask to contact Partner or update DNS settings and links to related documentation and Service Status Page
  3. Emails to All other BC Partners to inform about scheduled maintenance on Business Catalyst site
    1. First warning will be sent on Wednesday, February 16 at 12:00 PM (Australian EDT) | check local times here
    2. Final warning will be sent on Friday, February 18 at 16:00 (Australian EDT) | check local times here
    3. Email contains a summary of the legacy Sydney DC migration plan, scheduled start and end time, impact to their Business and links to related documentation and Service Status Page
  4. Additionally, we will identify the sites with externally hosted DNS and send an email to you with this list so you know which ones require which changes.
  5. Furthermore, we have setup an external site from which you can view the status of the migration, get more information and ask questions. During the migration, the Business Catalyst website will be down and all visitors will be redirected to the Service Status Page.

We will be making the site public once the dry-run is completed and we get final confirmation on dates.

Thanks for reading,
Cristinel Anastasoaie
Business Catalyst Product Manager
View Comments

What's Up at Business Catalyst in November

Apologies for it being a bit quiet on the BC blog lately, we had a large portion of the team preparing for and attending the Adobe Max conference in LA a couple of weeks ago. A big thank-you to all the Partners who made it out there, we genuinely enjoyed meeting with you. It was an enriching experience especially for our engineers to meet both new and established customers and talk all things BC over the course of the conference.

Now back onto topic; we'll be making our November release on 17 November at 1:00AM US PST (check local times here). This is a maintenance release with bug fixes only because the team has been tied up on longer term initiatives.

List of Bug Fixes to be Delivered in this Release

  1. Corrected a web app export bug which was generating an incorrect format error when trying to export
  2. Fixed a webpage copy bug so that users can now correctly copy pages that include the '|' character in the page name
  3. Culture and country code are now preserved from when going from a standard URL to the secure URL. This problem was generating incorrect currencies on invoices and within payment processing
  4. Fixed a redirect issue that was causing the system not to use HTTPS protocol when communicating with payment gateways (SagePay 3D secure)
  5. For our UK based sites we've fixed a payment processing issue where we were sending incorrect country codes to payment gateways. We now send "GB" instead of "UNITED KINGDOM" which has fixed payments processed by Sagepay
  6. For sites using the Mollie Payment Gateway, we are now passing the error messages from the gateway directly to the customer checking out so it's easier for them understand the issue if the payment fails
  7. We've updated our nameservers to point to rebranded nameservers i.e ns01.rebrandeddomain.com instead of ns01.businesscatalyst.cm when doing a NS lookup
  8. Newsletters quotas are now consumed in the correct month (the month they are sent) when a campaign is scheduled for delivery on the first of the month
  9. Updated the email newsletters report counter to accurately reflect the number of newsletters sent
  10. Fixed an intermittent email campaign bug causing one-off campaigns to hold for all BC sites when somebody tried to send a campaign with zero recipients
  11. Product search results tag { module_productresults,1,,,weight,,,} can now use the weight attribute (if specified) when sorting products
  12. Updated affiliate programs to correctly record commissions when using non-seamless gateways
  13. Fixed a Blogs bug causing articles to be published before their set release date
  14. Updated site invoices to display the discount value when using a promo code at site upgrade
  15. Fixed a problem that occurred when validating email addresses between the BC system and Paypal admin where case sensitivity was preventing the order from being created inside BC even though the payments were processed inside Paypal

Why we won't be implementing Customizable Web App URLs (in the near term)

I've been receiving mail on this topic as well as other high-ranking wishlist items. Earlier in October I asked the team do some estimating on how long it would take to develop Customizable URLs for Web-Apps hoping we could squeeze it in before the end of the year after completing the DNS work. The outcome is as follows: due to the major changes we have to make to the web-app import/export engine to accommodate this combined with the complexity in making the new Web-App URLs work with legacy Web-App URLs meant that this feature was going to take 2-3 months. As a Product Manager, I've decided that this is not the best use of our engineering resources and I've made a final decision that we won't be going forward with this in the near term, the engineering cost is too high.

I look back at 2010 and sure enough we've made some big modifications to DNS, we delivered Customizable URLs for Products and Announcements, we gave you a Redirect manager, we opened new Datacenters, we gave you FTP access to layouts/templates etc etc but none of these developments has really changed the core of the BC Application. I understand that some of you are eagerly waiting for more features like Customizable Workflow notifications and custom CRM fields populated via Webforms. I'd love for us to work on adding those features BUT for the record our focus has to be kept strictly on BC V3 for now and the medium term, we really need to get the core of our new platform built as quickly as possible. 2011 is all about BC V3 and our primary goal is upgrade core functionality for BC. Every time we divert resources away to do a small feature here or a small feature there we slow this process down.

A Sneak Peak at BC V3

I thought I'd sign off these release notes with a sneak peak of the preliminary UI design for the new dashboard - click below to enlarge. BC V3 is going to have more of a 'desktop' feel where each module or feature is contained within an App that is launched from the BC Dashboard. For example, to manage your blogs, you will open the Blog App, for your photos you will have a Galleries App, ecommerce gets a Store App, the CRM gets a Customers App and well, you get the idea. The aim of this approach is to provide for all of your end-to-end workflows within individual apps rather than trying to make you skip around the system. You would only turn on the Apps that your customers needed to run their Online Business to keep the system easy for them and the side dashboard navigation menu uncluttered.

BC Dashboard Preliminary UI Design

Furthermore we will be building the whole UI in HTML not Flex (turning BC into an Air App) as some have feared so it will work in all your favorite browsers. One of our primary UI requirements is to be accessible from iOS devices as well so you and your clients will be able to use BC from an iPad! As the team builds more and more of the App we'll be able to sneak more previews and details over the coming releases. Until next time, Happy Thanksgiving!

View Comments

New Community Forums

Hello everyone, your friendly forum moderator here.  I'm very happy to share with you something we've been working on and thinking about for some time.

Today, along with the release of our latest version, we've also completely reworked the Community Forums. The old forums are still available and will continue to be for a few weeks (after which they will become "read only"), however we ask that you start posting new threads in the new forums. If there are particular old posts which were missed and need to be answered or you think are particularly valuable in terms of information, please *bump* them and we'll consider moving them over. While a valuable resource, the old forums have become a bit long in the tooth to moderate and often people will bump threads that are years old and have nothing to do with their current issue. This makes it hard to have a conversation and also provides lots of conflicting information.

Our new forum listing is more than doubled and much more specific in name, which should make them that much more browse-able. Additionally, new forums exist for discussions that obviously needed to happen, but weren't necessarily pertinent to any specific system area. Some examples of these are:

  • HTML/CSS/JS Forum - The idea here is to provide a place to talk shop, show off tutorials you find interesting, provide resources for awesome new libraries, etc.
  • Marketplace - Partners are finding themselves in more and more situations that involve  taking on work that beyond their areas of expertise. Luckily we have a great community of partners with expertise in a myriad of competencies.
  • API & Third Party Integration - We find more and more people wanting to extend BC or complement it with another service. Up till now, there really wasn't any area to discuss this fully and we really want to foster more conversations about methodology and availability of solutions.
  • General Discussion - This is an area to talk about... well we're not really sure. To begin, we plan on having a thread of Show & Tell so you can show off your work.
  • Newbie Corner - No question is a stupid question here, if you feel truly lost in the BC well of knowledge post here and someone can help you along. This will be a great spot for free partners to get their wings and old partners to offer a helping hand.

We want you to talk shop, to have conversations about the reasons behind your design concepts, show off your slick AJAX hackery, etc.

We hope our new layout will enable a more conversational approach to the forums, while maintaining them as the educational resource they have become. We will continue to moderate the forums and jump in as necessary when we can provide an answer unique to our abilities. And don't forget our BC secret agents who prefer to remain anonymous.

However, at the end of the day its all about enabling you and providing a way to pass along your experience. I would like to personally thank Liam, Matthew, Vincent , and all of the other regulars I am forgetting for contributing so much to our community.

Cheers,

Justin Price - Adobe BC Forum Moderator

View Comments