Turning complexity into clarity.

Sales Page Re-design in leadpages - Upwork

WordPress Work From UpWork - Wed, 12/05/2018 - 23:51
Hi there!

I'm looking to transform my sales page- I will have the copy and content but want to pretty it up and make it look more professional including adding some features like sliding images for my testimonials and q&a section. Here's what my current page looks like http://www.lindsaypleskot.com/3-2-1-method  (I'm updating it for a new program but this is the general idea of current layout) and I want it to look more like this https://listtolaunch.jennakutcher.com/ type of style


Posted On: December 06, 2018 08:41 UTC
Category: Web, Mobile & Software Dev > Web & Mobile Design
Skills: Graphic Design, LeadPages, WordPress
Country: Canada
click to apply

AWS Consultant - New Value Solutions - Vancouver, BC

NodeJS jobs - Wed, 12/05/2018 - 22:39
Exposure to NodeJS. New Value Solutions, a national IT consulting company, is seeking a AWS Consultant to help our multiple clients assess, design and implement...
From Indeed - Wed, 05 Dec 2018 22:39:25 GMT - View all Vancouver, BC jobs
Categories: NodeJS

Lullabot: Diving Into The Deep End: Tips for UX Designers When Joining an Ongoing Project

News from Planet Drupal - Wed, 12/05/2018 - 21:18

It's never too late to start thinking about user experience design when working on a project. To help ensure the project is a success, it's best to have a UX designer involved in the project as early as possible. However, circumstances may not always be ideal, and User Experience may become an afterthought. Sometimes it isn't until the project is already well on its way when questions around user experience start popping up, and a decision is made to bring in a professional to help craft the necessary solutions. 

What’s the best way for a UX designer to join a project that is well on its way? In this article, we will discuss some actions that UX designers can take to help create a smooth process when joining a project already in progress.

General Onboarding

Planning and implementing an onboarding process can help set the tone for the remainder of the project. If it’s disorganized and not well planned out, you can feel underprepared for the first task, which can lead to a longer design process. It’s helpful to designate a project team member to help with on-boarding. It should be someone who knows the project well and can help answer questions about the project and process. This is usually a product owner or a project manager but isn’t limited to either. If you haven’t been assigned someone to help you with the on-boarding process, reach out to help identify which team member would be best for this role. During the on-boarding process, discuss what user experience issues the team is hoping to solve, and also review the background of significant decisions that were made. This will help you to evaluate the current state of the project as well as the history of the decision-making process. You should also make sure you understand the project goals and the intended audience. Ask for any documentation around usability testing, acceptance criteria, competitive reviews, or notes for meetings that discuss essential features. Don’t be afraid ask questions to help you fully grasp the project itself. And don’t forget to ask why. Sometimes entertaining the mindset of a five-year-old when trying to understand will help you find the answers you’re seeking.

Process Evaluation How you climb a mountain is more important than reaching the top. - Yvon Chouinard

Processes help ensure that the project goes smoothly, is on time, and on budget. They can also be a checkpoint for all those involved.  If a process doesn't already exist that includes UX Design, work together with the team to establish a process to discuss, track and review work. If you feel that a process step is missing or a current system isn't working, speak up and work with the team to revise it. Make sure to include any critical process that the team may be lacking. You also may want to make sure that discussions around any important features include a UX Designer. Ask if there are any product meetings that you should be joining to help give input as early as possible.

Schedule Weekly Design Reviews

One example of improving the process to include UX Design is scheduling weekly meetings to review design work that’s in progress. This also gives project members an opportunity to ask questions and discuss upcoming features and acceptance criteria.

Incorporate Usability Testing

Another suggestion is to include usability tests on a few completed important features before moving ahead. The results of the usability tests may help give direction or answer questions the product team has been struggling with. It can also help prioritize upcoming features or feature changes. The most important thing to remember is that usability testing can help improve the product, so it’s tailored to your specific users, and this should be communicated to the project team.

Collect General User Feedback

Establishing early on the best way to collect and give feedback on a design or feature can help streamline the design process. Should it be written feedback? Or would a meeting work better where everyone can speak up? Sometimes, when multiple people are reviewing and giving feedback, it’s best to appoint one person to collect and aggregate the input before it filters down to you.

Track Project Progress

You also want to discuss the best way to track work in progress. If your team is using an agile process, one idea is to include design tickets in the same software that you’re using to keep track of sprints such as Jira [link] or Trello [link]. Discuss the best way for summarizing features, adding acceptance criteria and tracking input in whatever system you decide to use.

Prioritization of Work Efficiency is doing things right; effectiveness is doing the right things. - Peter Drucker

The team should be clear on priorities when it comes to work, features, and feedback. Joining a team that’s in progress can be very overwhelming to both the designers and stakeholders and creating clear priorities can help set expectations and make it clear to both sides on what the team should focus on first. If a list of priorities doesn't already exist, create one. It doesn't have to be fancy. A simple excel sheet or Google Sheets will do. You can create separate priority lists for things like upcoming features that need design, QA, or user feedback. You can also combine everything into a single list if that works better for your team. Just make sure that it links to or includes as much detail as possible. In the example below, a feature that has completed acceptance criteria is linked to a ticket in Jira that explains all of the details.

undefined

It’s also helpful to group related features together, even though they may have different priorities. This will help you think about how to approach a feature without needing to reworking it later down the line. Be proactive. Ask questions around the priority of items if something doesn't make sense to you. If needed, volunteer to help prioritize features based on what makes sense for a holistic finished product or feature. Creating diagrams and flowcharts can help get everyone to understand how separate features can be connected and what makes the most sense to tackle first. Make sure that QA and user feedback is also part of the priority process.

undefined Summary

Having any team member join a project mid-process can be intimidating for all parties involved, but it’s important to be open and understanding. Improving the process and the end result is in everyone's interest, and giving and accepting feedback with an open mind can play an important role in ensuring that the project runs smoothly for everyone involved.

For User Experience Designers, it’s important to respect what’s already been accomplished and established with the idea that you should tread lightly to make small improvements at first. This will help gain confidence from the team, while also giving you time to learn about the project and understand the decisions that lead up to where it’s at today. For stakeholders involved, it’s important to listen with an open mind and take a small step back to reevaluate the best way to include UX in the process moving forward. The above suggestions can help both parties understand what actions they can take to help make the onboarding process for a UX Designer a smooth transition.

Categories: Drupal

Front-end Wordpress designer to help implement WP theme - Upwork

WordPress Work From UpWork - Wed, 12/05/2018 - 20:21
Looking for front-end developer/designer who can help implement a Wordpress theme I purchased and want to tailor to need - primarily CSS possibly some html.

The site will have appx 4-5 pages, including homepage, 3 of which will be blog/content archive and one of which will be contact page.

Most of the work is tweaking homepage to purpose.


Posted On: December 05, 2018 21:11 UTC
Category: Web, Mobile & Software Dev > Web Development
Skills: HTML, WordPress
Country: United States
click to apply

myDropWizard.com: Drupal 6 security update for Password Policy module

News from Planet Drupal - Wed, 12/05/2018 - 19:59

As you may know, Drupal 6 has reached End-of-Life (EOL) which means the Drupal Security Team is no longer doing Security Advisories or working on security patches for Drupal 6 core or contrib modules - but the Drupal 6 LTS vendors are and we're one of them!

Today, there is a Less Critical security release for the Password Policy  module to fix a Denial of Service (DoS) vulnerability.

The Password Policy module makes it possible to set constraints on user passwords.

The "digit placement" constraint is vulnerable to Denial of Service attacks if an attacker submits specially crafted passwords.

See the security advisory for Drupal 7 for more information.

Here you can download the Drupal 6 patch.

If you have a Drupal 6 site using the Password Policy module, we recommend you update immediately! We have already deployed the patch for all of our Drupal 6 Long-Term Support clients. :-)

If you'd like all your Drupal 6 modules to receive security updates and have the fixes deployed the same day they're released, please check out our D6LTS plans.

Note: if you use the myDropWizard module (totally free!), you'll be alerted to these and any future security updates, and will be able to use drush to install them (even though they won't necessarily have a release on Drupal.org).

Categories: Drupal

Drupal blog: Drupal's commitment to accessibility

News from Planet Drupal - Wed, 12/05/2018 - 19:58

This blog has been re-posted and edited with permission from Dries Buytaert's blog. Please leave your comments on the original post.

Last week, WordPress Tavern picked up my blog post about Drupal 8's upcoming Layout Builder.

While I'm grateful that WordPress Tavern covered Drupal's Layout Builder, it is not surprising that the majority of WordPress Tavern's blog post alludes to the potential challenges with accessibility. After all, Gutenberg's lack of accessibility has been a big topic of debate, and a point of frustration in the WordPress community.

I understand why organizations might be tempted to de-prioritize accessibility. Making a complex web application accessible can be a lot of work, and the pressure to ship early can be high.

In the past, I've been tempted to skip accessibility features myself. I believed that because accessibility features benefited a small group of people only, they could come in a follow-up release.

Today, I've come to believe that accessibility is not something you do for a small group of people. Accessibility is about promoting inclusion. When the product you use daily is accessible, it means that we all get to work with a greater number and a greater variety of colleagues. Accessibility benefits everyone.

As you can see in Drupal's Values and Principles, we are committed to building software that everyone can use. Accessibility should always be a priority. Making capabilities like the Layout Builder accessible is core to Drupal's DNA.

Drupal's Values and Principles translate into our development process, as what we call an accessibility gate, where we set a clearly defined "must-have bar." Prioritizing accessibility also means that we commit to trying to iteratively improve accessibility beyond that minimum over time.

Together with the accessibility maintainers, we jointly agreed that:

  1. Our first priority is WCAG 2.0 AA conformance. This means that in order to be released as a stable system, the Layout Builder must reach Level AA conformance with WCAG. Without WCAG 2.0 AA conformance, we won't release a stable version of Layout Builder.
  2. Our next priority is WCAG 2.1 AA conformance. We're thrilled at the greater inclusion provided by these new guidelines, and will strive to achieve as much of it as we can before release. Because these guidelines are still new (formally approved in June 2018), we won't hold up releasing the stable version of Layout Builder on them, but are committed to implementing them as quickly as we're able to, even if some of the items are after initial release.
  3. While WCAG AAA conformance is not something currently being pursued, there are aspects of AAA that we are discussing adopting in the future. For example, the new 2.1 AAA "Animations from Interactions", which can be framed as an achievable design constraint: anywhere an animation is used, we must ensure designs are understandable/operable for those who cannot or choose not to use animations.

Drupal's commitment to accessibility is one of the things that makes Drupal's upcoming Layout Builder special: it will not only bring tremendous and new capabilities to Drupal, it will also do so without excluding a large portion of current and potential users. We all benefit from that!

Categories: Drupal

Drupal blog: Pilot Program: Help us improve reliability of minor updates

News from Planet Drupal - Wed, 12/05/2018 - 18:50

The Drupal Association seeks volunteer organizations from Agency and Drupal site owners running production Drupal 8 sites for the creation of an official minor-release beta-testers program.

Since Drupal 8.0's release in November 2015, the Drupal community has successfully transitioned to a scheduled release process whereby two minor releases are made every year.

The most recent of these releases was Drupal 8.6, released in September 2018.

In a significant change from Drupal 7, these minor releases may contain new features and maintain backwards compatibility. This means that every six months there are new features in Drupal core, instead of waiting for the next major release.

This rapid acceleration in feature development has resulted in the need for greater real-world testing of upgrade paths and backwards compatibility. Drupal core has a vast automated test-suite comprising almost 25,000 tests—however, these can be greatly complemented by real-world testing of production sites. There are an infinite number of ways to put Drupal together that cannot always be handled in automated tests.

In order to improve the reliability of the minor-releases, the Drupal community—in conjunction with the Drupal Association—aims to develop a minor-release beta testers panel comprised of agencies and site-owners who maintain complex Drupal 8 production sites.

Many companies and Drupal users are looking to help with core development but aren't always sure where to start. Membership in this panel presents a new way to help the development of software that powers their website.

Who should apply?

Agencies and site owners who maintain large and complex Drupal 8 production sites. In particular, sites that use a wide range of contributed and custom modules or have large volumes of content.

What is involved?

When the beta release becomes available, the Drupal core committers will work in conjunction with the Drupal Association to contact the members of the beta-testing panel to advise that the next minor release is ready for testing.

Members of the panel will be asked to attempt updating to the beta using a staging version of their site (not straight-on production) and report back any issues found. New issues will be opened to track and resolve reported issues. If a predetermined percentage of the program participants have not yet reported back their results, a decision may be made to delay releasing subsequent beta versions or a release-candidate. Participants whose participation lapses may be removed from the program.

At the moment, testing of the new release occurs in a largely ad-hoc fashion, but once the program is established, this will become more structured and maintainers will have access to statistics regarding the breadth of testing. This will then inform release management decisions in regards to release preparedness.

What's in it for participants?
  • Updating early helps find issues beforehand, rather than after the release is out.

  • Reporting issues encountered lets you tap the wealth of experience of the Drupal core contributors that you'd not have the same level of access to if you update on your own after the release.

  • All organizations and individuals taking part in the testing will receive issue credits for both testing the update and fixing any issues that arise.

  • Satisfaction in the knowledge that you helped shape the next minor release of Drupal core.

  • Advanced preview of upcoming features in Drupal core.

Apply to participate in the program

Categories: Drupal

Wordpress Installation, server management, optimisation and overall administration - Upwork

WordPress Work From UpWork - Wed, 12/05/2018 - 18:27
Looking for a candidate that understands the business requirements rather than just a Wordpress installation.

Have an AWS server using cPanel and need someone to:

1. Create an account on cPanel, manage its permissions
2. Install Wordpress
3. Install the theme/s
4. Work with our designs and customisation of the theme to make it work with all the content
5. Help with installation of custom or available plugins to achieve what we need
6. Keep the website up to date in terms of updates, code and general upkeep
7. Optimise for speed
8. Assist with SEO and advise on what will work and what will not
9. Be my website guru to advise on what is good and what is not


Posted On: December 05, 2018 21:11 UTC
Category: IT & Networking > Network & System Administration
Skills: Amazon Web Services, CPanel, CSS3, HTML, PHP, System Administration, Website Development, WordPress
Country: United Arab Emirates
click to apply

[Discussion] Google maps plugin suggestions?

Talk about plugins - Wed, 12/05/2018 - 17:41

I have been using what I think is a pretty old plugin called Google Maps Ready! which seems to no longer be supported. I'd like to replace it with something effective but simple, and easy to configure the two markers for my business locations. Any suggestions?

Thanks in advance.

submitted by /u/First_Proof
[link] [comments]

IDENTIFY AND FIX ISSUES WITHIN A WORDPRESS WEBSITE TO IMPROVE FUNCTIONALITY AND RANK ON GOOGLE - Upwork

WordPress Work From UpWork - Wed, 12/05/2018 - 14:22
Hi there, I used a Themify Ultra builder to create a Wordpress Website from scratch. I had very clear ideas of how I wanted the site to look.
However there are some issues that prevented it from being listed and scrawled by Google bots. The site is aesthetic and very functional otherwise.
The freelancer would ideally be:
- an expert in Wordpress web development
- some background in relating Page content and structure that can help the site rank on google
- have some imagination and adaptive towards the Aesthetic and feel of the website, I'm very open to changing the way it looks in areas if it serves Ranking/functionality purposes etc
- should be able to develop the site without hosting access - been asked this before and not prepared to give out personal passwords for the Hosting manager. PHP and other access is fine of course! :)

https://www.drmajidshah.com


Posted On: December 05, 2018 21:11 UTC
Category: Web, Mobile & Software Dev > Web Development
Skills: PHP, Search Engine Optimization (SEO), Website Development, WordPress, Yoast SEO
Country: United Kingdom
click to apply

Community: Values & Principles Committee Update - November 2018

News from Planet Drupal - Wed, 12/05/2018 - 12:00

The Values & Principles Committee has formed and has started its work. It has started by looking at Principle 8.

Why are we doing this?

As Dries said, when announcing the first iteration of the Drupal Values & Principles, the Drupal project has had a set of Values & Principles for a very long time. Historically, they were mostly communicated by word of mouth and this meant that some in our community were more aware of them than others.

Writing down the Values & Principles was a great first step. What we need to do now is continually refine the common understanding of these Values & Principles across our whole community and ensure that they are built-in to everything we do.

How will we work?

The Values & Principles are held very closely to the heart of the members of our community and we absolutely recognise that any work on them must be inclusive, clear, structured and accountable.

We are, therefore, going to be open about the work we are doing. While there are members of a committee that will focus on this task, it is not the committee’s job to make decisions “behind closed doors”. Instead, the committee is responsible for enabling the whole community to refine and communicate our common Values & Principles.

We will record actions and progress in the Drupal Governance Project so that all in our community will be able to have the necessary input.

How will we communicate?

We will continue to post updates on the Drupal Community Blog and, as already mentioned, you will always be able to see and, most importantly, participate in issues in the Governance Project. We even have a board on ContribKanban!

Who is on the committee?

Hussain Abbas (hussainweb) works as an Engineering Manager at Axelerant. He started writing programs in 1997 for school competitions and never stopped. His work focus is helping people architect solutions using Drupal and enforcing best practices. He also participates in the local developer community meetup for PHP in general and Drupal in particular. He often speaks at these events and camps in other cities.

Alex Burrows (aburrows), from UK, is the Technical Director of Digidrop and has over 10 years working in Drupal, as well as an avid contributor and a member of the Drupal Community Working Group. As well as this he is a DrupalCamp London Director and Organizer and the author of Drupal 8 Blueprints book.

Jordana Fung (jordana) is a freelance, full-stack Drupal developer from Suriname, a culturally diverse country where the main language is Dutch. She has been steadily increasing her participation in the Drupal community over the past few years and currently has a role on the Drupal Community Working Group. She loves to spend her time learning new things, meeting new people and sharing knowledge and ideas.

Suchi Garg (gargsuchi), living in Melbourne Australia is a Tech Lead at Salsa Digital. She has been a part of the Drupal community for more than 12 years as a site builder, developer, contributor, mentor, speaker and trainer. She had been a part of the Indian community before moving to Australia and is now an active Drupal community down under.

John Kennedy (johnkennedy), lives in Boston, works as a Product Manager for AWS. Over 10 years in Drupal as a site-builder, developer, speaker and on the business side. Co-organiser of Drupal Camp London 2012-2015. PM for Acquia Lightning and the Drupal 8 Module Acceleration Program.

Rachel Lawson (rachel_norfolk), UK and the Community Liaison at the Drupal Association will finally be providing logistical support to the committee and helping wherever she can. Having been in the Drupal community for 11 years as a site builder, a contributor and a mentor, she has had opportunity to experience how the community understands its collective Values & Principles.

In order to be as transparent and forthcoming as possible we wanted to address the fact that there are currently 2 CWG members on the committee. The initial call for people to join the Values & Principles committee happened at the same time as the Community Working Group was calling for new members and, as luck would have it, Alex Burrows applied for both.

In October 2018 a current member of the CWG, Jordana Fung joined the Values & Principles committee and at same time he was being vetted for potential membership to the CWG, Alex joined the Values & Principles committee as well. After the vetting process, Alex officially became a member of the CWG in November. So as it stands now, there are 2 CWG members on the V&P committee.

There are a few possible options going forward, some are:

  • Both CWG members continue for now (whilst the V&P committee is in the very early formation stages) and then possibly:
    • One member drops off
    • They act as a team and only one member (whichever is available) participates in meetings
  • The CWG decides which member is on the VP committee
    • We may need to add another member to the VP committee to take the place of the member that will no longer attend.
So, what’s next?

We have started by compiling a summary of feedback from the community so far that relates to the project’s Values & Principles from such places as the Whitney Hess Interviews, community-led conversations around governance and some anonymized feedback from the Governance Taskforce. We will be adding this summary to an issue in the project.

Call to action

We recognize, though, that what we really want to understand is how you understand what we already have written in Principle 8. THis is how we intend to do that…

The members of the committee have each written stories from their own memories of the Drupal community that demonstrate Principle 8 in action.

We invite you all to write your own stories, from your memories of the Drupal community, other tech communities or indeed any other aspect of life, that demonstrate Principle 8 to you. You should add your story to this issue we have created:

Add my story about Principle 8

One thing we do ask, though, is that you only add your own stories (as many as you like!) and NOT comment or question others’ stories. All stories are valid.

By the end of the year, we hope to have a rich set of stories that show how we, as a global community, interpret Principle 8 and we can then look to see if any changes need to be made to the words or, maybe, it is more a case of linking the Principle to the stories or providing other statements supporting Principle 8.

Categories: Drupal

Kristof De Jaeger: Send me a webmention with Drupal!

News from Planet Drupal - Wed, 12/05/2018 - 11:07

After months of reading, experimenting and a lot of coding, I'm happy that the first release candidate of the Drupal IndieWeb module is out. I guess this makes the perfect time to try it out for yourself, no? There are a lot of concepts within the IndieWeb universe, and many are supported by the module. In fact, there are 8 submodules, so it might be daunting to start figuring out which ones to enable and what they exactly allow you to do. To kick start anyone interested, I'll publish a couple of articles detailing how to set up several concepts using the Drupal module. The first one will explain in a few steps how you can send a webmention to this page. Can you mention me?

Step 1: enabling modules

After you downloaded the module and installed the required composer packages, enable following modules: IndieWeb, Webmention and Microformats2. In case you are not authenticated as user 1, also toggle the following permissions: 'Administer IndieWeb configuration' and 'Send webmention'.

Step 2: expose author information

To discover the author of a website after receiving a webmention, your homepage, or the canonical url of a post needs author information. The module comes with an Author block so you can quickly expose a block where you can configure your name. Your real name or nickname is fine, as long as there's something. The minimal markup should look like something like this:

Your name


Note: this can be anywhere in your HTML, even hidden. Step 3: configure webmention module

All configuration exposed by the modules lives under 'Web services' > 'IndieWeb' at /admin/config/services/indieweb. To configure sending webmentions go to /admin/config/services/indieweb/webmention/send. Ignore the ' Syndication targets' fieldset and scroll down to ' Custom URL's for content' and toggle the 'Expose textfield' checkbox.

Scroll down a bit more and configure how you want to send webmentions, either by cron or drush (webmentions are stored in a queue first for performance reasons)

Step 4: configure Microformats module

When sending a webmention to me, it would be nice to be able to figure out what exactly your post is. To achieve this, we need to add markup to the HTML by using CSS classes. Let's configure the minimal markup at /admin/config/services/indieweb/microformats by toggling following checkboxes:

  • h-entry on node wrappers
  • e-content on standard body fields. In case your node type does not use the standard body field, enter the field name in the 'e-content on other textarea fields' textarea.
  • dt-published, p-name, u-author and u-url in a hidden span element on nodes.
Now create a post!

Create a post with a title and body. Your body needs to contain a link with a class so that when I receive your webmention, I know that this page is valid. As an example, we're going to write a reply:

Hi swentel! I just read your article and it's awesome!

Save the post and verify the markup more or less looks like underneath. Make sure you see following classes: h-entry, u-url, p-name, dt-published, e-content, u-author.


 
    
       
          Published on Tue, 04/12/2018 - 22:39
       
       
         
            Test send!
            2018-12-04T22:39:57+01:00
         

         
       
     
     
 
  Hi swentel! I just read your article and it's awesome!
 

If everything looks fine, go to the node form again. Open the 'Publish to' fieldset where you can enter 'https://realize.be/blog/send-me-webmention-drupal' in the custom URL textfield. Save again and check the send list at /admin/content/webmention/send-list. It should tell that there is one item in the queue. As a final step, run cron or the 'indieweb-send-webmentions' drush command. After that the queue should be empty and one entry will be in the send list and I should have received your webmention!

Note: You can vary between the 'u-in-reply-to', 'u-like-of' or 'u-repost-of' class. Basically, the class determines your response type. The first class will create a comment on this post. The other two classes will be a mention in the sidebar.

What's next?

Well, a lot of course. But the next step should be receiving webmentions no? If you go to /admin/config/services/indieweb/webmention, you can enable receiving webmentions by using the built-in endpoint. Make sure you expose the link tag so I know where to mention you!

I tried it, and it didn't work!

Maybe I missed something in the tutorial. Or you have found a bug :) Feel free to ping me on irc.freenode.net on #indieweb-dev or #drupal-contribute. You may also open an issue at https://github.com/swentel/indieweb

Categories: Drupal

Senior Front-end Developer - MetaOptima Technology - Vancouver, BC

NodeJS jobs - Wed, 12/05/2018 - 10:56
Python/Django, NodeJS, JSON, RESTful APIs, Git, Linux, Gulp, PostgreSQL/MySQL, SocketIO. We are one of Vancouver’s fastest growing startups looking for a highly...
From MetaOptima Technology - Wed, 05 Dec 2018 10:56:37 GMT - View all Vancouver, BC jobs
Categories: NodeJS

Dries Buytaert: Drupal's commitment to accessibility

News from Planet Drupal - Wed, 12/05/2018 - 10:56

Last week, WordPress Tavern picked up my blog post about Drupal 8's upcoming Layout Builder.

While I'm grateful that WordPress Tavern covered Drupal's Layout Builder, it is not surprising that the majority of WordPress Tavern's blog post alludes to the potential challenges with accessibility. After all, Gutenberg's lack of accessibility has been a big topic of debate, and a point of frustration in the WordPress community.

I understand why organizations might be tempted to de-prioritize accessibility. Making a complex web application accessible can be a lot of work, and the pressure to ship early can be high.

In the past, I've been tempted to skip accessibility features myself. I believed that because accessibility features benefited a small group of people only, they could come in a follow-up release.

Today, I've come to believe that accessibility is not something you do for a small group of people. Accessibility is about promoting inclusion. When the product you use daily is accessible, it means that we all get to work with a greater number and a greater variety of colleagues. Accessibility benefits everyone.

As you can see in Drupal's Values and Principles, we are committed to building software that everyone can use. Accessibility should always be a priority. Making capabilities like the Layout Builder accessible is core to Drupal's DNA.

Drupal's Values and Principles translate into our development process, as what we call an accessibility gate, where we set a clearly defined "must-have bar". Prioritizing accessibility also means that we commit to trying to iteratively improve accessibility beyond that minimum over time.

Together with the accessibility maintainers, we jointly agreed that:

  1. Our first priority is WCAG 2.0 AA conformance. This means that in order to be released as a stable system, the Layout Builder must reach Level AA conformance with WCAG. Without WCAG 2.0 AA conformance, we won't release a stable version of Layout Builder.
  2. Our next priority is WCAG 2.1 AA conformance. We're thrilled at the greater inclusion provided by these new guidelines, and will strive to achieve as much of it as we can before release. Because these guidelines are still new (formally approved in June 2018), we won't hold up releasing the stable version of Layout Builder on them, but are committed to implementing them as quickly as we're able to, even if some of the items are after initial release.
  3. While WCAG AAA conformance is not something currently being pursued, there are aspects of AAA that we are discussing adopting in the future. For example, the new 2.1 AAA "Animations from Interactions", which can be framed as an achievable design constraint: anywhere an animation is used, we must ensure designs are understandable/operable for those who cannot or choose not to use animations.

Drupal's commitment to accessibility is one of the things that makes Drupal's upcoming Layout Builder special: it will not only bring tremendous and new capabilities to Drupal, it will also do so without excluding a large portion of current and potential users. We all benefit from that!

Categories: Drupal

Senior Software Developer - Adacado.com - Vancouver, BC

NodeJS jobs - Wed, 12/05/2018 - 09:59
Kubernetes, Golang, Maven, Git, Tomcat, Nginx, MySQL/MariaDB, Redis, ElasticSearch, ActiveMQ, Akka, ReactJS, NodeJS, Webpack, Python, Hibernate, Spring,...
From Adacado.com - Wed, 05 Dec 2018 09:59:45 GMT - View all Vancouver, BC jobs
Categories: NodeJS

Senior Software Architect - Adacado.com - Vancouver, BC

NodeJS jobs - Wed, 12/05/2018 - 09:59
Kubernetes, Golang, Maven, Java, Tomcat, Nginx, MySQL/MariaDB, Redis, ElasticSearch, ActiveMQ, Akka, NodeJS, Python, Hibernate, Spring, Aerospike, Apache Spark,...
From Adacado.com - Wed, 05 Dec 2018 09:59:45 GMT - View all Vancouver, BC jobs
Categories: NodeJS

Online Course Creation Advisory and Partial Manual Help To Set up All Technology - Upwork

WordPress Work From UpWork - Wed, 12/05/2018 - 08:10
THE CONTEXT

I am a serial tech entrepreneur who has built several websites and managed several teams.
https://www.linkedin.com/in/paolo-messina/

THE PROBLEM
I am starting an online class on "become a Machine learning manager" for managers worldwide.
Although I know how ot create a wordpress site, I have an account on teachable and I know how to set up an email marketig system etc... putting the pieces together is wasting me lot of time.

THE GOAL
In less than a week I want to create all the website, marketing content and marketing funnel to start the PRE-LAUNCH. Basically, I want to sell the course even before I have it to my linkedin connections.

THE POTENTIAL HELP NEEDED( TASK DEFINITION)

1) Consulting on how to integrate Wordpress and Teachable
2) Consulting on How to integrate the funnel software with Teachable , this is being a pain.
3) Optimize the funnel for the specific objective we have now e.g. pre-enroll students like 6 weeks before the course launches. For example, I have a dilemma whether going with a Webinar approach or a multiple emails with several videos.
4) I am undecided on how much time invest on the traditional funnel given that I want to use my linkedin network to sell the pre-sale. So some guidance on linkedin network marketing and how to decide maybe very helpful.
5) Potentially if the cost is not too high I may outsource the creation of all website/funnel/plugins and I may focus on creating the marketing content e.g. lead magnet, top of the funnel free content, potential linkedin ads.  


WHAT I ASK

1) Define very specifically how you can address all of the 4 points above, if you can not do all the 4 define how you could source the missing piece and what would be the indicative cost.
2) Make a clear offer on the estimated total cost and delivery time
3) Specifically, discuss only the elements of your experience that are relevant to my pain points. DO not overwhelm me with material about everything.  

Some Info the course is:
https://innodemia.teachable.com/

My competitors are:
https://executive.mit.edu/openenrollment/program/artificial-intelligence-implications-for-business-strategy-self-paced-online/#.XAd1hWhKiUk

https://www.getsmarter.com/courses/us/mit-artificial-intelligence-online-short-course

https://www.getsmarter.com/search?utf8=%E2%9C%93&query=Deep+Learning%3A+A+Critical+Appraisal+&category=no-results


Posted On: December 05, 2018 11:11 UTC
Category: Design & Creative > Other - Design & Creative
Skills: aWeber, ClickFunnels, Email Marketing, Internet Marketing, LinkedIn Development, Social Media Marketing, Teachable, Web Design, Website Development, WordPress
Country: United States
click to apply

[DISCUSSION] tinyShield - a new security plugin for WordPress

Talk about plugins - Wed, 12/05/2018 - 04:02

Hi WordPressPlugins - I'm looking for feedback on a plugin that I've been working on for the past several months.

The plugin is called tinyShield and is a security plugin for WordPress. It's not a Web Application Firewall per se, it's not a malware scanner or file integrity checker or anything else similar. tinyShield focuses directly on the traffic that is coming to a WordPress site and compares the originating IP with blacklists.

The blacklists are comprised of several sources; one that we're particularly excited about is generated directly from users of tinyShield. We're using tinyShield to generate a blacklist that takes each failed login attempt from a site using tinyShield and sends it over to us to compare with other failed login attempts. If it meets our criteria, it goes in the blacklist where it will stay for 24 hours and then the process starts over again. This is a sort of herd immunity concept.

The plugin consists of a whitelist, blacklist and permanent whitelist. Each visitor that attempts to connect to the site is sent over to our servers for verification against the blacklist and if deemed ok, it will be added to your sites whitelist and it will stay for 24 hours before being rechecked on their next visit. The blacklist is exactly the same but only if IP is deemed malicious.

In the tests we've ran on live sites ranging from little to no traffic to sites with ~20k hits a day, we have seen about a 90% drop in brute force attempts and a notable decline in bots trying to exploit known vulnerabilities. This is also coming with no noticeable lag or decline in site performance.

One other thing to note, we encourage you to use other security plugins along side tinyShield, we play nice with others with the exception of wp-spamshield - it has some conflicts.

The goal of this plugin is to add an additional layer of security through blacklists while focusing ONLY on that avenue. We are not out to become a full fledged WAF or end all security plugin. tinyShield is just focused on simple, fast, and reliable blacklists.

This plugin does run off of a subscription model with two tiers of feeds. The community feed is and always will be free, one just has to register the site to generate a key. The second is a professional feed which includes additional blacklist sources as well as our own crowd sourced blacklist, which includes a manual human review process when our automated processes can not determine if a failed login or traffic is malicious.

If you'd like to read up more, visit our website at https://tinyshield.me or in the plugin repo https://wordpress.org/plugins/tinyshield/

I'd love any feedback on the project!

submitted by /u/tinyShield
[link] [comments]

Website Design - Insects and Organic Gardening - Upwork

WordPress Work From UpWork - Wed, 12/05/2018 - 02:50
I am looking for a web designer for a website I need to build about insects and organic gardening.

Here are some comments:

Pages:  
We’re envisioning around 5 different type pages.  I am attaching a content map and have only marked the pages that I think need design.  The rest can be adapted from these.

- Home
- Blog
- Content pages (they talk about different subjects like soil, plants, planting, pest control, etc)
- Insect pages (like a wiki page of each insect)
- Insect Gallery (photos of all insects with buttons to filter)

Photographs
They will use mostly their own photographs as they are very specialised and they are part of their own collection. (insect database and photos of different projects)
These photos are not great, but they have been collected on the field for many years, so we can’t do much about this.
We might need a few nice stock ones for home page and banners (maybe?).  If we use good stock photos for home page we could create a good first impression (although I realise this might not work well as it will increase the contrast with the other photos that are not great).

Brand
They are farmers and they don’t have a brand as such.  So we will need to come up with a nice logo for the website as well.   

Web Development
We already have a developer who will create the website using Wordpress / Oxygen builder.  So we are only looking for a designer at this stage.

Purpose of website / Design
A bit more insight of what we’re after.  We're after a design that is earthy, organic, tidy, relaxing, pleasant to the eye and easy to read.  Something that connect people to earth, to nature.

The purpose of this website is more idealistic rather than a business.  They want to help people that want to grow their food organically.


-----
Please send me a quote and ONLY RELEVANT samples of your designs
(this means, designs related to nature, farming, etc).  

Please do not send designs of other types of websites as your proposal will be deleted.


Posted On: December 05, 2018 11:11 UTC
Category: Web, Mobile & Software Dev > Web & Mobile Design
Skills: Graphic Design, UX Design, Web Design
Country: Australia
click to apply

Lead Data Scientist - Invoice Simple - Vancouver, BC

NodeJS jobs - Wed, 12/05/2018 - 00:44
Written Typecript and/or Javascript on the backend with NodeJS. Invoice Simple's mission is to build the world's simplest way to run and grow a small business....
From GlassDoor.com - Wed, 05 Dec 2018 00:44:30 GMT - View all Vancouver, BC jobs
Categories: NodeJS

Navigation

Let's Talk


Let's talk about your website:
250-661-4834

My LinkedIn profile



LocalSolo Freelance