A May Full of Drupal Commerce Releases

May was one of our most productive months to date. It was full of releases for the core Commerce modules, our standalone PHP libraries, and essential contributed modules that all work together to comprise Drupal Commerce. While I outlined the highlights in the roadmap issue on drupal.org, these wins are worth sharing more broadly to keep the rest of the Drupal community in the loop.

The biggest release of the month was Drupal Commerce 2.7, which included new features for currency formatting, address form configuration, and stored payment methods. It also fixed a handful of bugs that unblocked other module releases and updated core in response to improvements in our libraries and dependent modules.

We've long discussed how our standalone PHP libraries are exporting expertise off the Drupal island. Addressing and Internationalization, which have each been downloaded over one million times, are our two shining stars. We rolled new releases for each of them in May, improving even further Drupal Commerce's ability to solve the hardest parts of address entry / validation / formatting and currency localization. Refer to the price formatting change record from the 2.7 release to see how the new API is more flexible and performant as a result.

Additionally, we released Address 1.4 and Inline Entity Form 1.0 RC1. The latest Address release unlocks the customer profile’s address field to support collecting less detailed billing addresses. The Inline Entity Form release includes new product information management features, letting you duplicate product variations for faster product data entry.

Inline Entity Form product variation duplication

Thanks to generous sponsorship from Authorize.Net themselves, we've been able to dedicate several weeks to improving their integration this year. The resulting Authorize.Net RC1 release now supports eCheck, Visa Checkout, and 3DSecure payments! We also included several bug fixes related to duplicate customer and payment profiles that appear when migrating from an old system to Drupal Commerce, for example.

While not fully released yet, our Technology Partner integration for Avalara's AvaTax is nearing beta. Jace Bennest from Acro Media contributed heavily by refactoring the module to properly use a TaxType plugin while my co-maintainer Matt Glaman contributed additional fixes to our port from the Drupal 7 integration to prepare it for certification. Thanks, Jace / Acro Media!

When Matt wasn't working on the above contribs, he was collaborating with Lisa Streeter from Commerce Guys to bring Commerce Reports to its first beta release for Drupal 8. The new version takes a completely different approach from the Drupal 7 using lessons we learned developing Lean Commerce Reports. It denormalizes transaction data when an order is placed to support reports generation with or without the Views module, providing a better developer experience and much better performance. Check it out below! (Click to expand.)

Commerce Reports usage demo

We've also been hard at work improving the evaluator experience. The big release for that is Commerce Demo's beta1, which showcases what Drupal Commerce provides out of the box. It creates products and scaffolds out a full product catalog (pictured below). To get the full effect, try it out with our default store theme, Belgrade. The new demo module gets us closer to something like we had with Kickstart 2.x on Drupal 7 - a learning resource for site builders and a way for agencies to more easily demo and sell Drupal Commerce.

Demo product catalog in the Belgrade theme

Finally, I'm very excited to announce that Lisa Streeter is our new documentation lead! Expect some great things to come. She has already done fantastic work with the Commerce Recurring documentation and is working on revising our getting started, installation, and update docs.

Looking at June, we plan on finalizing the query level entity access API, which will allow us to better support marketplace and multi-store Drupal Commerce implementations. We expect to merge user registration after checkout completion, and we will also be focusing on address reuse / copying, Buy One Get One promotion offers, and more product management experience enhancements.


Source: Reposted from: drupalcommerce.org


7 Topics that Should be Covered During a Digital Discovery Workshop (including 70+ Specific Questions You Should Ask)

Discovery Workshops play an important role in the success of any integrationproject. If a Discovery Workshop is not conducted the right manner, its value can be lost.
At the beginning of a project, Discovery Workshops are the part of the “Discovery Phase,” which can be considered as the courtship period, during which a strategic partner usually collaborates with his client to understand the project’s requirements and functional specifications, and to discuss content modelling, solution architecture and so on. The aim is to define the project’s business goals by fitting the pieces together.
This is the foundation of any project.
However, a successful Discovery Workshop is only achieved when the right set of questions are asked. Here is my list of questions that I consider are important to ask while you are onsite with client, discussing the details of his or her project.
For me, the right set of questions inspires the client to think about what he or she needs out of the whole engagement. It also ensures that there are no surprises and unwritten assumptions.
I’ve grouped my questions (more than 70 of them!) into seven topics.
Strategy

What is the end goal of this engagement?
What is the client proposition around it?
How, as partners, shall we together actively evaluate the success of the project?
How will we ensure that the business goals are met at the end of engagement?
How does this whole engagement fit into the client’s vision and overall strategy?
How does this project stack up against competition?
What will this solution create a “unique selling proposition” for the client?
User Experience

Who is the target audience?
What is the demographic of audience the client is targeting?
What are the different needs of the users who will be coming to the project for a solution?
Is there any specific timing during which users will use the application?
Why will they want to come back, or refer it to others?
As a service provider, what does the client want the user of the solution to do?
What are the current challenges?
What is the expected “user journey?”
How can customer satisfaction be improved?
How can desired conversions be achieved?
How is the competition doing it differently?
What devices will the application be supporting?
What are the usability cases that the client is expecting?
What platform are we building the application for?
Is accessibility compliance a goal?
Content

What is our primary content type?
Are we planning to migrate old content?
If so, what content should be moved, specifically?
How will the content, old and new, relate to each other?
What will be our user permissions and workflows?
Is content strategy part of the scope?
How frequently will different pages be updated?
Will there be personalization/localization of content? If yes, what are the APIs that the client has thought of?
Will the product be designed for different, specific markets? If yes, what differences will be expected?
Will the solution be multilingual? If so, what is the default language, and how will language-selector needs be changed with regard to the user journey?
Are there any specific requirements with regard to different markets?
Visual/User Experience/User Interface

What are the style guidelines?
How well are brand guidelines defined?
Do brand assets -- logos etc. -- exist?
How rigid is the existing style guide? As the solution partner, do we have some flexibility?
Are there any designs that are already in the client’s mind?
Any existing creative insights in the minds of stakeholders?
Are there emotional end states that the client wants to engender in customers?
Functionality
What functionality is expected?

Are there any expected integrations with social networks?
Are there any third-party integrations that the client is expecting?
Is the client expecting any of the solutions to be multilingual?
Most importantly, how are these functionalities supposed to help the client achieve the project’s business goals?
Is data capture required?
Are there any requirements for e-commerce, store locators, or any Google API integrations?
Technical

What level of security checks/compliances is the client expecting?
Is encryption required?
Does the client have a legacy system that needs to be integrated?
If change in an existing system is required, where are current databases located? Does the client want to change them? Do they have any preferences around this process?
Where will the solution be hosted?
What backup mechanism is expected?
Is client expecting CDNs, AWS, or Akamai to handle spikes in traffic?
Is there any integrationframework the client wants us to follow?
Does client expect a tracking mechanism? If yes, which tool: for example, Webtrends, Adobe Site Catalyst, or Google Analytics?
Project Management & Governance

What is the client’s expectation with regard to a Project Plan?
Who are the stakeholders? Who shall be the client Point of Contact for all communication during the project execution?
How comfortable is the client with agile methodology?
What is the preferred communication mode? What tools will be used to collaborate?
Who needs to be involved in day-to-day communication?
Who will manage the Project Management process?
What does the project’s RACI (Responsible, Accountable, Consulted, and Informed) look like?
What will be the change-management process?
What is the tentative live date? How are we arriving this live date via business goals? What would be the impact, if the “live” date is not met?
What are the potential risks associated with the “live” date?
When these questions are answered, a Discovery Report should be shared with the delivery team. This will not only help with the smooth execution of project, but it will also reduce surprises down the road.
Although these workshops are usually an added expense in the project’s budget, they are well worth it. As a strategic partner/consultant to the client, it makes sense to encourage these workshops -- to ensure better understanding and a smoother collaboration ahead.
Source: http://dev.acquia.com/


Localization Framework Developer - eBay - San Jose, CA

Experience with 3rd party systems that the framework will interact with, such as SDL WorldServer, DrupalCoin Blockchain, InQuira, or similar is highly desirable....
From eBay - Thu, 17 Nov 2016 05:08:07 GMT - View all San Jose jobs
Source: http://rss.indeed.com/rss?q=DrupalCoin Blockchain+Developer


DrupalCoin Blockchain Development - Creating a Multilingual Site in DrupalCoin Blockchain

If you've never created a multilingual site for a client before, it can seem like a daunting task. Even if you speak geek it's still easy to get lost in a sea of code, strings, files and acronyms. Thankfully, DrupalCoin Blockchain 7 makes this task a little easier. In this article we decode the secrets to Developing a multilingual site in DrupalCoin Blockchain.

The first two items you need to become best friends with are internationalization (i18n) and localization (l10n). Internationalization and localization are means of adapting computer software to different languages and regional differences. Here's how they're broken down:

Internationalization is the process of designing a software application so that it can be adapted to various languages and regions without engineering changes. The application will give you the ability to replace your English content with German (or whatever language you want). In other words, internationalization gives you the framework to create your "About Us" page in 17 languages and then have them displayed to your site visitors according to their selected locale. Read more