Drupal Planet

Subscribe to canal de noticias Drupal Planet
Drupal.org - aggregated feeds in category Planet Drupal
Actualizado: hace 11 horas 15 mins

Amazee Labs: Recap Pt.2: Drupal Dev Days Lisbon 2018

Jue, 07/19/2018 - 05:49
Recap Pt.2: Drupal Dev Days Lisbon 2018 Vijay Dubb Thu, 07/19/2018 - 10:49

Day three Today, my friends, we’re going to Change the World...

Rachel Lawson presented day three’s keynote. It was a really good session as it showed how everyone who attended, has contributed in some way to Drupal, as well as how “Drupal changes the world”. It started by “Meeting Sami”, a 10-year-old boy from Mosul, Iraq, who was captured (along with his brother) by ISIS. He was held captive for three and a half years, after which he was sent to a refugee camp. While in the camp, it was the Warchild charity that provided support, activities, education, and most importantly, ended up reuniting Sami and his brother with his family.

Now, you’re probably wondering what any of this has to do with Drupal? I know, I also did, but it became apparent that Warchild recently switched to using Drupal, making use of several modules. Rachel asked the audience to stand up, if they had made a contribution to modules used by Warchild, including paragraph and media. Almost half the room did, but I didn’t. She then went on to ask about other contributions that people in the audience had made. This time, it related to anything from documentation, to hosting meetups, and even attending camps.

By the end of the session, everyone in the room was standing, including me. It felt good to know that I had contributed in some way. During the question and answer session, the issue of becoming a member of the Drupal Association was raised, as well as the importance of doing so. Membership empowers the Drupal community to be able to do more things that are requested by users, which in turn makes a transformational difference.


“If you don’t push yourself and just go with things, then you’ll never get the amazing things.” - Rachel Lawson

Watch session

Drupal 9: Decoupled by design?

Both Preston So and Lauri Eskola gave a session on decoupling Drupal, as well as the direction in which it is going. Anyone who has been working with Drupal should know that the idea of decoupling Drupal has been around for some time. Among the reasons for doing this, is that developers are free to choose any technology they want for the frontend. It’s clear that Drupal 9 will continue to use Twig, but with support client-side rendering with an API first approach. Another point was that editors prefer the non-decoupled approach, which raises the questions, “Who is requesting this? Is it the clients or developers?”

Watch session

The future of Drupal in numbers

One of the most interesting and debatable sessions I attended was presented by Nemanja Drobnjak. Similar to the first keynote session, this session was about comparing Drupal from 18 months ago, with its current state. This presentation could have been perceived as very pessimistic, especially when seeing the numbers compared to other major CMS’s like WordPress. He also referred to the compare PHP frameworks blog.

All the data in the presentation had clearly been researched, so it was rather shocking to hear Nemanja predict that Drupal could go out of use within 15 years if the current trends continue. A few suggestions to prevent this were made. From improving documentation to Drupal directly targeting the education sector. This session drew a lot of questions. Firstly, “Why compare Drupal to Wordpress?”. I agree completely. It's about who is using it and benefiting from it. It reminded me of the blog post I read in which Vue.js passed React.js in the number of people who have 'starred' it on Github. Basically, it doesn’t mean that React is dying and Vue is now the norm. Both have different purposes and uses, just like, for example, Drupal and Wordpress.

Another question raised was, with Decoupled sites becoming more popular, “Can a crawler detect the backend?”. Maybe the data wasn't 100% correct.

Day four An update on Drupal 8.6

The day four keynote session was presented by Gábor Hojtsy, who gave a short speech about the upcoming Drupal update. He then moved onto how we could help with several initiatives, both at Drupal Dev Days and in general, including helping with Admin UI and documentation.

Watch session

Contribute, contribute, contribute! Yes!!!

Having put my Windows issues on the back burner, it was time to get the admin UI demo to work. I went over to the Admin UI innovation table where I met Lauri Eskola, Daniel Wehner, and Volker Killesreiter, all of whom helped me try to get the site working. Turns out it was because of an outdated module, so I updated the module, created a pull request and boom, my first ever contribution to Drupal was made. I then spent the rest of the day looking at the code and getting to grips with how it worked.

I was then assigned my first issue, which took some time to complete as I was still getting used to the code base. But nonetheless, I was able to fix the issue and contribute some more to the initiative. I really like how everything is broken into small issues, meaning that a single person isn't completing a large issue by themselves. It is clear that Drupal can only be maintained if people contribute back to the project and/or community.

It is never too late to contribute! Even though Drupal has been around for almost 20 years, it still relies heavily on people to contribute and come up with innovative ideas. If you are looking to contribute, but don’t know how I can suggest you take a look at the Drupal development and strategic initiatives.

Having heard the word “contribute” several times, it would have been great to hear someone repeatedly say the word, as Steve Balmer did - "developers".

Day five Quo Vadis, Free Software?

The final keynote session, by Rui Seabra, was about free software. He shared thoughts on how we should have the freedom to run software as we wish, make changes to the software to make it fit for your purpose, and distribute both the original and modified version. It was clear that as users of so-called “free software”, we have a misconception about what we think is free. Rui also went on to talk about how we can help protect the internet, especially from the EU’s copyright directive. I did find the joke about the “[fill in] sucks” reference to Windows, very amusing.

Free software is everywhere, and people are forgetting that the freedom of sharing is a quintessential part of the evolution and moving forward together. “If we didn't share we wouldn't have knowledge, technology, and hardware we use today.” - Rui Seabra

Watch session

Progressive decoupling - the why and the how

The final session I attended was my colleague Blazej Owczarczyk’s talk, where he explained everything about progressive decoupling. One of his key points was that you should only decouple where it makes sense. Blazej showed some cool and interesting new features available in EcmaScript 6/7. We also learnt about the new await/async function in EcmaScript 8, which I found to very cool and cannot wait to start using. It was then time to move on and discuss how we could use these new features in our current Drupal sites.

By installing dependencies, defining a dynamic library and running a web server, you are able to create a decoupled environment for any technology of your choice. Two things I really liked about the session was 1) Blazej asking the audience to tweet a thanks to our very own Philipp Melab for the GraphQL module, and 2) the bonus question, which resulted in more questions from the audience. Way to go Blazej, we’re very proud of you here at Amazee Labs.


 

Watch session

The rest of the day I spent contributing more to the Admin UI initiative.

Many thanks

I would like to take this opportunity to thank:

Ruben Teijeiro for being so helpful throughout the week and introducing me to several people.

Christophe Jossart for not only helping me with my installation issue but for being great company and showing me around Lisbon.

Lauri Eskola, Daniel Wehner, and Volker Killesreiter for the introduction to Admin UI, which helped me find the issue as to why I couldn’t set up the site on my machine and finally allowing me to help contribute to the great initiative.

Finally, to all the sponsors, speakers, organiser, and volunteers, a huge thank you for a spectacular week, great evening social events, and for making my first ever Dev Days an amazing one. I hope to see you all at the next one.

Links

Mediacurrent: Is Drupal Right for Universities? A Strategic Perspective

Mié, 07/18/2018 - 17:15

Selecting a CMS for a university can be a challenging decision. There are so many needs and nuances to consider - costs of implementation and maintenance, a wide-range of technical ability among site administrators, developers and content editors, a variety of end users looking for different information and the list goes on and on. While your answer likely isn’t as easy as, “let’s just do what everyone else is doing,” by better understanding why other universities made the choice they did can shed light into your decision-making process. 

Drupal is far and above the most used CMS in higher education - 26% of all .edu domain sites are in Drupal, including 71 of the top 100 universities. 

So why are universities like MIT, Georgia Tech, Louisiana State University, Butler, Stanford, Harvard and the rest of the Ivy League universities choosing Drupal? 

Simply put, Drupal makes good business sense, especially with the added benefits of Drupal 8. At Mediacurrent, we believe your website is your greatest digital asset and can be leveraged to accomplish organizational-wide goals. Drupal makes that possible. Here’s how:  

Communicate With All Students - Prospective, Current, and Alumni 

If you want to reach your full recruiting and fundraising potential, you need to communicate with your entire audience. There are a variety of Drupal features that ease the stress of common communication challenges. 

Language:  Not only are their multiple languages spoken within the U.S., but our country hosts over a million international students. Drupal makes creating a multilingual digital experience simpler. Native language handling is built directly into Drupal 8’s core APIs, giving you over 100 languages to choose from. With that functionality it is easier than ever to engage with prospective students across the globe in a meaningful way.

Accessibility: The CDC estimates that 20% of U.S. adults identify as having a disability. These disabilities often hinder people’s ability to interact with the average website. Drupal is an inclusive community and has committed to ensuring that all features of Drupal conform with w3C and WCAG 2.0. Pair that with a strong higher-education focused accessibility strategy and your potential audience could grow by 20%. 

Technology: According to the 2017 College Explorer Market Research Study, the average college student owns 5.6 devices and spends 137+ hours on them! This may seem like common sense now, but if you want to engage with students, you need to account for a variety of screen sizes. Thankfully, Drupal 8 is designed with a mobile-first mentality and includes out-of-the-box responsive functionality. 

Personalization: Universities face added complexity when it comes to digital strategy due to the broad audiences they appeal to. With so many unique people coming to the same pages, content strategy, conversion path mapping and optimization, and defining strong call to actions can be a struggle. By incorporating personalization into your content strategy, whether that is personalized based on user authentication or by integrating tools like Acquia Lift or Salesforce Marketing Cloud, you can speak to the masses but make them feel like you’re speaking specifically to them. 

Reduce Overhead Costs + Increase Operational Efficiencies with Drupal

Drupal can have a dramatic impact on reducing overhead costs and increasing operational efficiency. Universities have a big need for multiple websites: departments, colleges, libraries, and student organizations all want their own website. The direct cost of supporting this many sites along with resourcing the training and support is expensive and encourages unnecessary technology sprawl. As an open source technology (no licensing fees!) along with the multisite feature, creating sites for these different groups is exponentially easier, more cost effective, and ensures brand consistency. 

You can also increase efficiency, ensure content consistency and improve the user experience by creating a “source of truth”.

Write content once and publish it anywhere it’s relevant.

Having to update content such as curriculum or an academic calendar on multiple pages is inefficient and unnecessary. Write once, publish everywhere, save time. 

Improve Brand Equity + Amplify Digital Strategy

As a university, your brand is a powerful asset. You spend significant energy and resources on building loyalty to bolster several organizational goals from recruiting efforts, engaging current students on campus and fundraising among alumni.

With your website being the hub of your marketing strategy, it is critical for your CMS of choice to play nice with your marketing efforts.

Drupal happens to be very SEO friendly out of the box, but there are also advanced configuration options available to support a more sophisticated SEO strategy. You can amplify your digital strategy by integrating your marketing tools and communication platforms directly with Drupal. And the 26% percent of other .edu sites using Drupal make integrating your university-specific tools to your website easier. 

Reduce Risk

I’d be remiss without mentioning security and GDPR compliance. As a university, you hold sensitive information about the students who have attended your school and they are trusting you to keep that secure.

The Drupal community is passionate about security and has an industry leading global security team to ensure your site is protected.

Additionally, as the landscape of privacy rights changes around the world (most recently, GDPR), it’s in your best interest to stay on top of it and reduce the risk of being penalized for data collection practices. 

Have questions about how Drupal can benefit your university? Let us know. We’d be happy to chat. 

myDropWizard.com: Drupal 6 security update for XML sitemap (6.x-2.x only)

Mié, 07/18/2018 - 16:42

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 Moderately Critical security release for the XML sitemap module (version 6.x-2.x only) to fix an Information Disclosure vulnerability.

The XML sitemap module enables you to generate XML sitemaps and it helps search engines to more intelligently crawl a website and keep their results up to date.

The module doesn't sufficiently handle access rights under the scenario of updating contents from cron execution.

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 XML sitemap 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).

Ashday's Digital Ecosystem and Development Tips: Upgrading from Drupal 7 to Drupal 8

Mié, 07/18/2018 - 16:00

Now that Drupal 8 has gained some momentum, it is time to start planning out your upgrade strategy. You want to upgrade to get the latest benefits and take advantage of the future stability that comes with the direction that Drupal will be taking from here on out. Before upgrading you will want to consider some things about what your current site has. In this article we will be covering some of those questions with some context to assist in the decision making process. Let’s determine if you website is adequately serving the current needs of your business and which content will need to be brought over to the new Drupal 8 site. There may be a difficulty in the switch, but being prepared will put you in position to handle whatever comes up.

Drupal Association blog: Features and the future

Mié, 07/18/2018 - 12:17

Drupal.org has been in existence since 2001. That's a long time for a website to serve an ever changing community! We're doing this work thanks to the support of our members, supporters, and partners. As time goes on needs change, technology evolves, and features are deployed to improve the experiences of site visitors.

As a web professional, you know how delivering small feature requests can have a big impact. To ensure people take notice of the improvements the Engineering Team makes on all of the *Drupal.org sites, we share frequent updates with the community. You can read a monthly what's new on Drupal.org blog, watch for change notifications, and follow on Twitter to know what's on the horizon.

Recently, these improvements were deployed:

  • More maintainers can now grant issue credit

  • Security Advisory nodes are now included in the /news feed

  • Project page screenshots will display in a lightbox

  • DrupalCI.yml Documented

We'll continue to make Drupal.org better every day, with your help. Find out more about what we do and become a member today. Thank you!

 Follow Drupal.org on Twitter: news and updates, infrastructure announcements, commits (and deployments).

InternetDevels: Drupal 8 Modules you should have

Mié, 07/18/2018 - 11:00

Each Drupal release makes it more refined and up-to-date. The latest one offers better architecture, fresh functionality, improved security and other benefits of Drupal 8. It is considered to be innovative and progressive due to new functions such as multilingual applications, advanced mobile-friendly options or HTML5 for better site management.

Read more

Droptica: Working with a team that is spread out over many locations can be comfortable and pleasant, just like working in a team working at a single office. See how we do it at Droptica.

Mié, 07/18/2018 - 09:59
At Droptica, remote work is something ordinary. From the very first day, we had two offices in Wrocław and Gdańsk. Recently, we also opened our third office in Rzeszów. Every day, developers, testers, graphic designers and other specialists work together in each of these locations. In addition, 90% of our clients come from abroad, like in the case of most software houses. Throughout several years, we have developed methods of effective and efficient cooperation in a dispersed team. We are constantly improving our work model, testing new tools and ways of working. In this article, you will learn how our system works today.

Droptica: Models of cooperation of the development team and the client based on the examples used at Droptica

Mié, 07/18/2018 - 09:28
Droptica helps clients from all over the world to complete and implement their projects. Each of these clients has already developed their way of working. Everyone is different. In this article, I have collected the most common ways and systems of cooperation between Droptica and our clients. Why do we work a little differently with every client? We are Agile. We always want to maximise the results of our work, so our development team always adjusts and adapts their way of working to the client’s needs. The elements that are adapted and changed the most often include:

Drupal Association blog: The Values & Principles Committee

Mié, 07/18/2018 - 08:00

In a previous blog post, I wrote that Dries asked for help in continuing the development of the Values & Principles and that a Values & Principles Committee will be formed to facilitate this. Well, we are at the point where we can explain how the committee will be formed, its purpose and how it will achieve its goals.

Purpose

The Values & Principles Committee will exist to focus on specific Values & Principles to see where continual improvements can be made and to propose those to the Project Lead for approval. For example, in meetings at DrupalCon Nashville, Dries expressed a desire to focus on Principle 8: “Every person is welcome; every behavior is not” because it is both critically important, in need of work, and requires more input.

Formation

To learn more about how the Values and Principle Committee will work, please read the charter, which is attached.

We have been giving thought to how we can facilitate a better, more open, process for appointing members to this Committee and we have come up with the following:

We will be posting role descriptions for the volunteer committee roles on jobs.drupal.org. The Values & Principles Committee Member voluntary role description will describe the:

  • Expectations of the role

  • The specific jobs the role will require

  • An indication of the time commitment of the role

  • The attributes that would be expected of a successful candidate

  • How to apply

The Committee Member role will be advertised from today until 3 August 2018 at https://jobs.drupal.org/drupal-community/job/15126 and then I will take the applications to Dries Buytaert and Megan Sanicki to select candidates based on the membership requirements outlined in the charter and role description.

This work matters to them personally and through their roles:  Dries as Drupal Project Lead and Megan as Drupal Association Executive Director. In addition to their different experiences and perspectives, they bring a wealth of experience in enterprise leadership, organizational culture and community building.  They hope to assemble a group that is inspired by this work, diverse, and representative of the values and principles we hope to inspire in the community. After the initial membership is selected, the membership will help recruit new members going forward.

Once the committee is selected, it can then begin work, in consultation with subject matter experts, on updating the values and principles.

My call to action for you is to consider whether volunteering as a Member of this Values & Principles Committee is a way that you can contribute to the Drupal Community and, if so, to submit your application.

I’m really keen to ensure that the Values & Principles Committee has membership from many places, with a diverse background and representing many a wide understanding of what makes Drupal - Drupal. It is even baked into the Values & Principles Committee Charter, attached.

File attachments:  Values Committee Charter.pdf

OPTASY: How to Add Autocomplete to Text Fields in Drupal 8: Defining a Custom Route

Mié, 07/18/2018 - 07:15
How to Add Autocomplete to Text Fields in Drupal 8: Defining a Custom Route radu.simileanu Wed, 07/18/2018 - 10:15

Let's say that it's a WhatsApp-like, a decoupled, Drupal 8-backed, real-time chat platform that you're building. One using Node.js. In this case, implementing field autocomplete functionality becomes a must, doesn't it? But how do you add autocomplete to text fields in Drupal 8?

Needless to add that such otherwise "basic" functionality — implemented on fields such as node reference and user/tags — would instantly:
 

  1. improve the user experience 
  2. increase the level of user interactivity and engagement
     

Users would group around different "channels" and be able to easily add new members. The auto-complete text fields will make the whole “new member coopting” process conveniently easy:

Agiledrop.com Blog: AGILEDROP: Drupal events in 3th quarter of the year

Mar, 07/17/2018 - 21:09
We've made a list of Drupal camps and summits that you can attend in the third quarter of the year. Drupal events are bringing together Drupal developers, site builders, themers, end users and those interested in learning more about Drupal. We are attending Drupal events because of sessions and collaborative discussions.   DrupalCamp LA 2018 The United States, Irvine, CA School of Engineering of the University of California 21-22. July 2018 DrupalCamp LA is an unconference-style Drupal training. They are planning to have 5 sessions proposed by community volunteers and BoFs. Sessions are… READ MORE

Tandem's Drupal Blog: Changing a Content Type Name During a Drupal 8 Migration

Mar, 07/17/2018 - 21:00
July 18, 2018 Changing a content type machine name during a Drupal Migration requires a little bit of migration knowledge, but is fairly straight forward to do. The Use Case It is a typical occurrence when a Drupal site has its content types named one way when it is built. Then, later on it is changed to better reflect what that type currently ...

mark.ie: Getting Value (URI) of a Drupal Media (File) Field from within a Twig Template

Mar, 07/17/2018 - 13:07
Getting Value (URI) of a Drupal Media (File) Field from within a Twig Template

To the future or to the past, to a time when thought is free, to the next time when I need to get the value of file field to use as a variable in Drupal 8 with Twig.

markconroy Tue, 07/17/2018 - 17:07

Working my way down through one of Drupal's render arrays of doom to try to get the URI of a file in a media field (in a paragraph type), I came up with this. If you can improve it, feel free to drop a note in the comments:

{% set slide_url = file_url(content.field_p_ei_speaker_slides[0]['#media'].field_m_file_file.entity.uri.value) %}

In steps:

  1. Get the {{ content }} variable
  2. Drill down into the media field (Speaker Slides - pdf, ppt, etc)
  3. Get the first element (0 - it's not a multi-value field in this case)
  4. Load up the #media object
  5. Interrogate the field on the media entity that has the file attached (the File field)
  6. Load this entity (entity here is not presented as an item in the {{ dpm() }} but it's very handy to know
  7. Get the uri.value from here
  8. Wrap it all in a file_url() function

For clarity, here's what I had in PatternLab:

  {# Begin Slides Download #}
  {% if event_slide_download %}
   
     
        {% include '@basic-elements/icons/_svg.twig'
          with {
            svgpath : '@basic-elements/icons/svg/download.svg'
          }
        %}
     

   
  {% endif %}
  {# End Slides Download #}

And here's what I have in the corresponding Drupal paragraph.html.twig tempate:

{% if paragraph.field_p_ei_speaker_slides.value %}
  {% set event_slide_download = true %}
  {% set slide_url = file_url(content.field_p_ei_speaker_slides[0]['#media'].field_m_file_file.entity.uri.value) %}
  {% set event_slide_download_link = slide_url %}
{% endif %}

{% include "@building-blocks/event-section/event-item.twig" %}

So now, my future self, you will know where to find this next time.

Phase2: Decoupled Drupal 8 + GatsbyJS: a quickstart guide

Mar, 07/17/2018 - 12:07

If you're not familiar with GatsbyJS, then you owe it to yourself to check it out. It's an up and coming static site generator with React and GraphQL baked in, and it prides itself on being really easy to integrate with common CMS'es like Drupal.

OpenSense Labs: Approach your Mobile-First Design with This Guide

Mar, 07/17/2018 - 10:51
Approach your Mobile-First Design with This Guide Harshit Tue, 07/17/2018 - 19:21

It’s always a battle when planning a website design. Your end goals, target audience, content, user experience, everything must align. It’s like a cloud of thoughts right inside your team’s head. It’s critical to optimize your website experience for the devices your audience is or will be using. 

Emarketer forecasts, approximately 83% of internet users will use a mobile phone to go online by 2021. 

Since now that we’ve established the fact that mobile is where the future lies, a mobile-first redesign is a way to go. We’ll dive into what a mobile-first approach entails, including tips for creating a seamless experience for visitors from mobile devices. 

In 2018, it is critical to analyze what’s the right way to go about it. 

1. Shoot for the least 

Without compromising the functionalities, it is definitely a challenge to pull everything into such a limited real estate. The difference in the screen space of various devices should tell you the varied approach to design. 

Minimalism begins by removing every element one by one.

After listing down all the elements, prioritizing is key. Sort out the cruciality of every element and how would they hierarchically sit in the interface. This should be in a way that the most important elements are displayed prominently. 

If after this exercise there’s still space for more, carefully add some elements in order of importance without overdoing it. Doing this would make sure every inch is utilised to the fullest. 

Content Repository 

The approach to this should be by drafting a document or a spreadsheet containing all the content elements you want the interface to entail. 

List down the page titles, navigation titles and be open to comments from peers. An example is given below:

An example of a content repository2. Analyse the Important Interaction Points

Comparing smartphones from 2008 to the ones in 2018,  a lot has changed since then. The user experience is no more frustrating. Earlier you had to touch the exact alphabet in the keyboard now the smart devices can read your movement through sensors. Keyboards differ according to the smartphone size, button space and overall sensitivity. And so your mobile design should be approached in the same manner. 

Unfortunately, many websites are still lagging behind when it comes to the user experience which leads to weak engagement, poor sessions and doubled bounce rates. 
Make sure the important elements are not missed. 

This includes: 

  • Make button more clickable
  • Make CTAs more appealing and responsive
  • Choose the right color combination for the user to read on the sunny noon
  • Give hyperlinks plenty of space
  • Keep the tabs in the drop down manner
Good vs Bad UX design The number of mobile phone users in the world is expected to pass the five billion mark by 2019, according to Statista.  3. Optimize Your Images

When it comes to loading size, images make up nearly 64% of an average web page. Outlining the “why”, it is now important to know how you can optimize your images to deliver an optimum and engaging experience to your user, without hogging on those extra kilobytes of data. 

Hacks to Optimize Images
  • Use correct image dimensions for faster loading
  • Use the correct image format. JPEG image would be a lot lighter than the PNG.
  • Compress your image with lossless compression
  • Use Lazy loader to keep the user engaged
4. Content is all that matters

Devising content around mobile is time-consuming as it requires due thinking and goes through numerous iterations along the course of finalizing the content itself. 

Taking the limited space aside for a while, there are more added difficulties when it comes to mobile web development. 

There comes screen rotation, device to device compatibility, text and image overlaps and what not. These factors have everything to make your content look very less appealing. What do you do for cutting these hurdles off? 

Think from an app perspective

Mobile users are accustomed to motion and a modicum of control in their experience. Think about off-canvas navigation, expandable widgets, AJAX calls, or other elements on the screen with which users can interact without refreshing the page. This would help you always maintain the right threshold for user experience. 

Screen and remove all the distracting elements, make the content as precise as possible while catering to actual product or service display. 

Landscape photos and complex graphics don't show well when your screen is reduced by half. Take into account the mobile user with pictures that are comprehensible on handheld screens.

5. Be a User, Before Presenting to the User

Our industry standard for approaching design is devising wireframes first. During wireframing or prototyping, use adaptive breakpoints reference. It streamlines the process of moving to different screen sizes, starting with the least real estate. 

Hover is off the table

Interactive interfaces from 2018 mostly utilize hover effects. UX designers go bonkers over them. But that’s a desktop only thing as we do not have the finger-hover technology in town. You will have to forget hover' existence when going mobile. 

Having trouble configuring your site? Check out services by OpenSense Labs.

6. Opt for Accelerated Mobile Pages

Your users are likely to bounce off your website if it doesn’t load within 3 seconds. With mobile, the standard has been set high (or rather less). Since the internet has been taken for granted, people have become second sensitive these days. 

AMP does bring you speedy pages and is a great way to boost your SEO and stop losing out of potential customers. It’s important to note that Google has gone lengths to identify and promote AMP pages.

If your web pages follow AMP standards, it becomes eligible to be cached by Google and appear in the search results and carousels with the AMP logo, indicating that they offer a fast experience. 

A standard built on top of existing technologies to speed up the loading of web pages on mobile devices.

How to go about it?

Configure AMP in your website

7. Make engagement on Mobile Simple 

Whether it’s deciding between a “hamburger” style menu or a more visible-style on the front end or how to display forms on specific pages, don’t make engagement paths more abstract than they need to be. Engagement should be extremely crisp and effective in nature.


Set the Display Order

Now, after listing down all the elements, prioritizing is key. Sort out the cruciality of every element and how would they hierarchically sit in the interface. This should be in a way that the most important elements are displayed prominently. 

8. Test It Before You Sell It

Even after having the final product in your hands, recommendations and tweaks will keep flowing in. Change is evergreen. With changes being made, you need to be testing them as soon as they are deployed. 

Nothing beats discovering for yourself how usable a website is (or isn’t). Step away from your computer desktops and load up your product on a real phone or tablet. 

Test it in a real devices 

Using testing tools, you can conduct A/B tests. Some tests may be like, an orange CTA vs a Yellow CTA, Button size changes, block layout tweaks and etc. Tests can range from regular functionality checks to user experience tests.

Tap through pages. Is the site easy to navigate? Does it load in a timely fashion? Are the text and graphics easy to read?

It's as clear as the skies that the future of the internet is dependent on mobile experiences. Responsive web design is a must if you run your business online or attend to your customers for any purpose. 

The tips above will help you build what you are looking at while making the least possible amount of mistakes. 

If you need any further recommendations, we are here. Hook with us at hello@opensenselabs.com or tweet us at @OpenSenseLabs and our mobile development team will save you the trouble.

blog banner blog image Mobile first Mobile friendly  User experience Drupal Web Redesign Drupal websites Mobile approach Websites Mobile first approach Webpages Design Ideas Design Ideology Design Blog Type Articles Is it a good read ? On

Web Wash: Live Training: Managing Media Assets using Core Media in Drupal 8

Mar, 07/17/2018 - 10:30

In the video above, you'll learn how to build powerful media management functionality using Drupal 8.5. I start the webinar with a review of what's new in Drupal 8 and then jump right into a live demo.

If you prefer text, then read our tutorial on "Managing Media Assets using Core Media in Drupal 8".

Blair Wadman: How to add page templates for content types in Drupal 8

Mar, 07/17/2018 - 04:49

This weeks tutorial will dive into how you can add page templates for a specific content type in Drupal 8. Sometimes you need to create a page template for a specific content type so that you can customise it. Drupal allows you to create content types for node templates out of the box by following the naming convention node--content-type.html.twig. But things aren’t so simple for page templates. Drupal does not automatically detect page templates for content types purely based on the naming convention. Fortunately it just takes a few lines of code and you can create a page template for any content type you choose....

Dx Experts: Drupal core: Now with less than 100 Simpletests

Mar, 07/17/2018 - 03:34
Drupal core now has less than 100 Simpletests

Mark Shropshire: Demystifying Decoupled Drupal with Contenta CMS Presentation at Drupal Camp Asheville

Lun, 07/16/2018 - 23:24

It was a pleasure to present "Demystifying Decoupled Drupal with Contenta CMS" with Bayo Fodeke at Drupal Camp Asheville 2018 on July 14th, 2018. I want to thank the organizers, volunteers, attendees, presenters, and sponsors for making another awesome year in the beautiful North Carolina mountains. This is one great camp that gets better and better each year. Below you will find the video for my talk and slide deck::

"Demystifying Decoupled Drupal with Contenta CMS".

Blog Category: 

Drupal core announcements: Drupal 8.6.0 will be released September 5; alpha begins week of July 16

Lun, 07/16/2018 - 12:20
Drupal 8.6.0-alpha1 will be released the week of July 16

In preparation for the minor release, Drupal 8.6.x will enter the alpha phase the week of July 16, 2018. Core developers should plan to complete changes that are only allowed in minor releases prior to the alpha release. (More information on alpha and beta releases.)

  • Developers and site owners can begin testing the alpha next week.

  • The 8.7.x branch of core has been created, and future feature and API additions will be targeted against that branch instead of 8.6.x. All outstanding issues filed against 8.6.x will be automatically migrated to 8.7.

  • All issues filed against 8.5.x will then be migrated to 8.6.x, and subsequent bug reports should be targeted against the 8.6.x branch.

  • During the alpha phase, core issues will be committed according to the following policy:

    1. Most issues that are allowed for patch releases will be committed to 8.6.x and 8.7.x.

    2. Drupal 8.5.x will receive only critical bugfixes in preparation for its final patch release window on August 1. (Drupal 8.4.x and older versions are not supported anymore and changes are not made to those branches.)

    3. Most issues that are only allowed in minor releases will be committed to 8.7.x only. A few strategic issues may be backported to 8.7.x, but only at committer discretion after the issue is fixed in 8.7.x (so leave them set to 8.7.x unless you are a committer), and only up until the beta deadline.

Drupal 8.6.0-beta1 will be released the week of July 29

Roughly two weeks after the alpha release, the first beta release will be created. All the restrictions of the alpha release apply to beta releases as well. The release of the first beta is a firm deadline for all feature and API additions. Even if an issue is pending in the Reviewed & Tested by the Community (RTBC) queue when the commit freeze for the beta begins, it will be committed to the next minor release only.

The release candidate phase will begin the week of August 13, and we will post further details at that time. See the summarized key dates in the release cycle, allowed changes during the Drupal 8 release cycle, and Drupal 8 backwards compatibility and internal API policy for more information.

Páginas