Здравей Гост ! Регистрирай се и влез .

Навигация на книгата

Последни коментари

Кой е онлайн

В момента са 0 потребители и 0 гости online.

Гласуване

Колко тестови Друпал сайта имате?
1-5 бр.
61%
5-10 бр.
16%
10-15 бр.
8%
15-20 бр.
3%
20-30 бр.
3%
30-40 бр.
3%
40-50 бр.
3%
над 50 бр.
5%
Общо гласове: 38

Разпространи

Разпространи съдържание

Агрегатор на източници

Agiledrop.com Blog: AGILEDROP: The quality of life and the effect it has on work performance

Planet Drupal - 30 Януари, 2018 - 05:00
The way we work is constantly changing. The possibility to work remotely or distributed is something that has been with us for a long time. Even before the industrial revolution people tended to work at home. All professions we knew back in the time were working from their home. With the advent of the industrial revolution that has begun to change. Our ancestors were starting to work in organisations. The divide between what is home and what is workplace was getting deeper. As we developed more and more, our needs were bigger and bigger.    From shoes to cars  It may sound a little bit… READ MORE
Категории: Planet Drupal

Oliver Davies: DrupalCamp Bristol 2018 Statement

Planet Drupal - 30 Януари, 2018 - 03:00
Категории: Planet Drupal

Drupal Association blog: 2016 990 and Audit

Planet Drupal - 30 Януари, 2018 - 00:46

Last year, the Drupal Association committed to not only providing more transparency into our financials, but also more clarity about where our funds come from and what they fund.

We completed our 2016 Audit and official financial reporting at the end of 2017. This post gives insight into 1) the audit 2) the 990s (our official financial report for the year) and 3) a new financial report called the “Weather Report”. 990s provide a one-year snapshot of program financials, but some of our programs have two years of expenses, like DrupalCon, so just looking at the 990s never gives the exact insight into how our events perform. The weather report provides this clarity. It will expand over time to provide clarity for more of our programs as well.

We did a financial audit for 2016

Audits are a good thing. In fact, our operations department welcomes them and appreciates the feedback.

To assist our board in their fiduciary obligations, we strive to conduct audits every other year. In the years that we don’t do an audit, we contract with our CPA firm, McDonald Jacobs, to do a financial review.

We conduct an audit for several reasons:

  • to demonstrate our commitment to financial transparency.
  • to assure our community that we follow appropriate procedures to ensure that the community funds are being handled with care.
  • to give our board of directors outside assurance that the financial statements are free of material misstatements.

For our 2016 audit, our auditors focused on three points:

  • Proper recording of income and expense: our auditors ensure that our financial statements are an accurate representation of the business we have conducted. Did we record transactions on the right date, to the right account, and the right class? In other words, if we said that 2016 revenue was a certain amount, is that really true?
  • Financial controls: preventing fraud is an important part of the audit. It is important to put the kinds of controls in place that can prevent common types of fraud, such as forged checks and payroll changes. Our auditors looked to see that there are two sets of eyes on every transaction, and that documentation is provided to verify expenses and check requests.
  • Policies and procedures: there are laws and regulations that require we have certain policies in place at our organization. Our auditors looked at our current policies to ensure they were in place and, in some cases, had been reviewed by the board and staff.

The primary goal of this audit is for our auditor to express an opinion on two aspects of the financial statements of the Association: the financial statements are fairly presented, and they are in accordance with generally accepted accounting principles (GAAP). Generally accepted accounting principles are the accepted body of accounting rules and policies established by the accounting profession. The purpose of these rules is to promote consistency and fairness in financial reporting throughout the business community. These principles provide comparability of financial information.

Our audit for 2016 is complete and has been reviewed and approved by the board. The results of our audit can be found here

In short, we received a clean bill of health with one recommendation from our Auditors (which is VERY good).  It is in how we open and deposit incoming checks:

"Controls over Checks Received
With the elimination of our physical office during 2016, the control of segregating certain duties has been eliminated. The Accountant now processes checks received in the mail. In this situation where the Accountant has access to the physical asset and the accounting records, there is an opportunity to misappropriate a check and void or delete the invoice billing in the accounting system. To mitigate the risk of this occurring without detection, the following recommendations can provide additional control:

  • As part of the monthly reconciliation process performed by the outside CPA firm, a review of voided and/or deleted invoices can be done with appropriate follow up and resolution.
  • Consider using a lockbox with your bank."

While our security checks are tight, adding the bank lock box process was suggested by our auditors to add an additional layer of security to prevent potential fraudulent activity.

A lockbox is a physical post office box controlled by the bank.  Checks are directed to this post office box, or “lockbox”, and checks are opened and scanned by bank employees.  Those checks are deposited into our account, and scans of the checks are uploaded and recorded in our banking portal.  This can be accessed and seen by all members of our accounting team.  Checks are now recorded into our accounting system by a different team member, since checks are now digitized and deposited by the bank - and are no longer physically deposited by only one team member.

Tax filing: The IRS Form 990

Once the audit is finished, our CPA can complete the 990 tax return for the year.

All U.S.-based 501c3 exempt organizations are required to file a 990 each year. Additionally, this form is also filed with state tax departments as well. The 990 is used by the IRS and state regulators to ensure that non-profits continue to serve their stated charitable activities. The 990 can be helpful when you are reviewing our programs and finances, but know this is only a “snapshot” of our year.  

You can find our past 990s here.

Here are some general points, when reviewing our 990:

FORM 990, PART I—REVENUES, EXPENSES, AND CHANGES IN NET ASSETS OR FUND BALANCES

Lines 8-12 indicates our yearly revenue. Not only how much total revenue (line 12), but also where we have earned our income, broken out into four groups. Line 12 is the most important: total income for the year which ended at $5.1 million.

Lines 13-18 shows expenses for the year which totaled $6.1 million for the year.

Cash Reserves are noted on line 20 of page 1.  Our year ended with 186k in net assets. The 990 has a comparison of the net assets from last year (or the beginning of the year) and the end of the current year, as well as illustrates the total assets and liabilities of the Association.  We ended 2015 with -$92K, and with our refocus in 2016 we closed the year up, at $185k in net assets.

FORM 990, PART II—SIGNATURE BLOCK

Sign off on our 990 by our Treasurer Tiffany Farriss & CPA Representative McDonald Jacobs partner Sang Ahn.

FORM 990, PART III—STATEMENT OF PROGRAM SERVICE ACCOMPLISHMENTS

In Part III, we describe the activities performed in the previous year that adhere to our 501c3 designation.  You can see here that Drupal.org, DrupalCon and our Fiscal Sponsorship programs are highlighted noting the expenses and income for each program.  Keep in mind that this is only a year snapshot, as DrupalCons span a couple of years, ramping up and winding down.

FORM 990, PART IV -  CHECKLIST OF REQUIRED SCHEDULES

This is a checklist of schedules that must be completed and accompany the 990 filing.  Any “yes” answers checked here will produce a schedule to explain the “yes” answer in detail.

FORM 990, PART V - STATEMENTS REGARDING OTHER IRS FILINGS AND TAX COMPLIANCE

This is a place for statements about other IRS filings and tax compliance such as receiving tax deductible contributions, and noting that we have provided donors with required substantiation for their donations.

FORM 990, PART VI - GOVERNANCE, MANAGEMENT AND DISCLOSURE

This is for us to note detailed information regarding our governing body, management, and policies of our organization.

FORM 990, PART VII - LIST OF OFFICERS, DIRECTORS, TRUSTEES AND KEY EMPLOYEES

Part VII lists our board and staff who are responsible in whole or in part for the operations of an organization. These entries do include titles and compensation of key employees.

Section B—Compensation of the Five Highest Paid Independent Contractors for Professional Services
We list any of our contractors, if we have paid them more than $50,000, on this schedule.

FORM 990, PART VIII - Statement of Revenue

This is a snapshot of where our revenue comes from, what is exempt or not exempt as taxable income. For 2016, $573,247 was considered taxable.

FORM 990, Part IX Statement of Functional Expenses

This section classifies the total amount earned for the year into three different buckets; fundraising, general, and program expense. These are expenses related to running those three different types of programs.

FORM 990, Part X, XI and XII Balance Sheet

This is a comparison of our 2016 balance sheet from beginning of the year to the end of the year, along with notes about the account method we use (accrual) and independent auditor and who is responsible for oversight.

Additional Filing to the 990, Schedule A — Public Charity Status and Public Support

A tax exempt organization must meet certain public support tests in order to maintain its status as a public charity. Schedule A provides an opportunity to see the various sources of revenue have increased or declined over the last four or five years. Please be aware that the definitions of revenue for the purposes of the support schedule are not directly comparable to Part I of the Form 990.

Additional various schedules following the 990, show large contributions (5k +), activities outside of the United States (ie grants given outside of the US), assets depreciation and other various activities.

Now that our 2016 990 has been reviewed by the board and approved, we have filed it. From there we are required to post the return publicly, which we do here on our website. 

Weather Report — Review of 2016

As part of our work to ensure financial health, our virtual CPA firm Summit compiles a “weather report” monthly so we can compare particular data points and see if we are reaching to our set KPIs. 

In closing the year 2016, Summit prepared this report for the year.

Revenue —the Drupal Association creates income in four different ways:

  • Advertising, which consists of ad sales on Drupal.org.
  • Events - DrupalCon income
  • Fundraising consisting of any donations or membership sales
  • Other Income, which comprises income from digital sponsors, Supporting Partner sales and time and material projects.

The graph below shows the breakdown of revenue for 2016.

Expenses — The Drupal Association has expenses which are categorized in the following ways:

  • Production Expense:These are the costs associated directly with earning revenue (for example: paying employees who work directly with the revenue streams described above, direct event costs, marketing event costs, IT costs, etc.)
  • Administrative Costs: These are general costs associated with running the organization (for example: administrative employees, accounting fees, insurance, professional fees, etc)
  • Sales and Marketing Costs: These are costs for marketing the Drupal organization (mostly Marketing employees)
  • Facility Costs: These are costs associated with the physical office space employees work. (Drupal moved a distributed workforce in the end of 2016, so these costs will be minimal going forward.)

KPI Goals — Moving into 2017, we set the following goals for Drupal.org.

  • Cash Reserve – Have 30% of forecasted YTD revenue in the bank.  As of the end of 2016 we have $397K (27% of the goal) in the bank.
  • Net Income – Have a Year End Net Income greater than 10%.  In 2016 we achieved a Net Income margin of -1%.

Event Summary — The graphs below present the 2016 and 2015 DrupalCon events

2016 results show us in the middle of our financial recovery.  As we moved into 2017, we took deep looks into our operations and programs to ensure financial health and growth. We will have a 2017 update after we close our financial review and 990 filing for the year.

We are thankful for the great team work that went into new financial reporting process and the resulting data to help us push towards our financial goals. Additionally, and as always, we are truly thankful to our financial contributors who provide the financial fuel for us to do our mission work.

Категории: Planet Drupal

MTech, LLC: Two Down, One to Go

Planet Drupal - 29 Януари, 2018 - 19:02
Two Down, One to Go

Today, the final blocker for Migrate Drupal UI was committed. That leaves only a series of complicated internationalization (i18n) issues to get resolved for Migrate Drupal before all of migrate in all of Drupal core can be considered stable. Lots of effort by lots of people have gone into the UI. Thanks to each one of them.

If you have been on the fence, waiting to upgrade, now is the time to do that. 80 percent of all Drupal 6 and Drupal 7 sites do not use i18n features. If you are in that large camp, just waiting to upgrade, then the upgrade path for you is fully stable NOW.

Lucas Hedding Mon, 01/29/2018 - 10:02
Категории: Planet Drupal

Chapter Three: Dreditor Refresh: A New User Style for Dreditor

Planet Drupal - 29 Януари, 2018 - 17:26

Dreditor is a beloved and indispensable tool, in the form of a browser extension, that enhances project issue pages on Drupal.org. When it comes to reviewing patches, it turns what would just be a plain text file into a feature rich interface for reviewing patches, allowing users to easily select and comment on lines of code, which then get pasted into the comment form, as properly formatted HTML.

I've been lucky to have some extra community time here at Chapter Three over the past couple of weeks. While perusing the core issue queue, I decided to resurrect an old User Style I created for Dreditor back in 2009, and give Dreditor a little refresh. You can install the Dreditor Refresh style with Stylish here. Make sure you also have Dreditor installed, and have logged into Drupal.org.

Категории: Planet Drupal

DrupalEasy: DrupalEasy Podcast 204 - Tim Lehnen and Neil Drumm - Drupal.org tooling

Planet Drupal - 29 Януари, 2018 - 15:41

Direct .mp3 file download.

Tim Lehnen, (hestenet), Director of Engineering for the Drupal Association and Neil Drumm (Drumm, Senior Technologist at the Drupal Association join Mike Anello to take a bit of a deep dive into the continuing evolution of Drupal.org tooling - specifically the modernization of the issue queue, patch process, code reviews, and more. Along the way, we try to figure out where (when?) the phrase "feather in your cap" comes from, exactly what Neil does in his free time, and why Mike isn't nearly as cool as he thinks.

Interview DrupalEasy News Sponsors
  • Drupal Aid - Drupal support and maintenance services. Get unlimited support, monthly maintenance, and unlimited small jobs starting at $99/mo.
  • WebEnabled.com - devPanel.
Follow us on Twitter Subscribe

Subscribe to our podcast on iTunes, Google Play or Miro. Listen to our podcast on Stitcher.

If you'd like to leave us a voicemail, call 321-396-2340. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or corrections. If you'd rather just send us an email, please use our contact page.

Категории: Planet Drupal

Amazee Labs: GraphQL for Drupalers - part 4 - fetching the entities

Planet Drupal - 29 Януари, 2018 - 12:47
GraphQL for Drupalers - part 4 - fetching the entities

GraphQL is becoming more and more popular every day. Now that we have a beta release of the GraphQL module (mainly sponsored and developed by Amazee Labs) it's easy to turn Drupal into a first-class GraphQL server. In this series, we'll try to provide an overview of its features and see how they translate to Drupal.

Blazej Owczarczyk Mon, 01/29/2018 - 10:47

In the last post we talked about the basic building blocks of every GraphQL query - the fields. We've discussed their types and traits as well as described the rules according to which Drupal fields turn into GraphQL fields. This week we were going to expand the topic further and cover field creation, but Daniel Noyola asked an interesting question in the comment below one of the recent articles:

How can I filter the results in a nodeQuery? Like I would in a normal View or with the "where" clause in a SQL Statement. I noticed that it receives a NodeQueryFilterInput but I don't see how to use it.

Fetching entities based on a filter or a set of filters is a common use case, so let's focus on that first.

TL;DR

There are two ways to query the entity repository. First one would be through the entityQuery fields which are shipped with the core module but are limited in functionality. They only allow us to filter by base fields and there's no way to use an operator other than equals to. The other approach is much more powerful, as it's based on Views. It requires an additional module - graphql_views - to be installed though. Let's start with the built-in way.

The nodeQuery

Each entity type in the system gets its own query field. Let's see in the explorer how it looks like for nodes:

So it's a field (blue) with 3 arguments: offset, limit and filter (purple) which returns a value of type EntityQueryResult (all types are in yellow).

The first two arguments, offset and limit, are for paging and they work the same way as in SQL. Both are integers and both have default values of 0 and 10 respectively (green). Arguments that have default values can be omitted. We'll use this feature in a while.

The last argument - filter - is of a complex type NodeQueryFilterInput. Let's click it:

So it comprises all the base fields of the entity type that is being queried. It's not enough to issue arbitrary queries but it will suffice for a simple use case. This is how we could fetch a list of articles created by a given user:

We haven't specified the offset nor the limit, so they'll get their default values. It means that the output will contain at most 10 results, starting from the result number 0.

That's cool, but what if we wanted to order the articles by node id (nid) to only show the latest articles? Or filter by tags? Or fetch the title text of an image that is attached to a media entity that is connected with the first event that starts after the article's release date?

Use The Views

The answer is: we can do it like we'd normally do it in Drupal - with a view. Views integration has been moved to a separate project, so it has to be downloaded with composer (composer require drupal/graphql_views), from drupal.org or from github.

With graphql_views enabled we can add a GraphQL display to any view in the system.

Now we can sort the results, filter based on content fields and add relationships. We also have the option to return either the full entities, just a selection of fields, or even search results taken straight from a search server.

Contextual filters set in the view will automatically turn into the arguments of the GraphQL field. Let's see an example:

This field represents a simple view showing nodes. It has one contextual filter - Content: Authored by - so the corresponding input type consists of just one field:

and its row type is set to Entity (as pictured on the screenshot above), so the result will be of type NodeArticle:

We can use the filed like this:

Views integration is a pretty broad topic, so in the next post we might try to cover it in more detail. There are quite a few more interesting aspects like sorting, exposed filters, and attaching views to entities, so we'll focus on that in an attempt to fully answer Daniel's question. For those interested in the back-end side of things I'd recommend the great Extending GraphQL series by Philipp Melab. The first post that explains how to create fields is here: Extending GraphQL: Part 1 - Fields.

P.S. GraphQL Views is not stable yet. In fact, two issues were spotted and fixed in the process of writing this article. If you spot a bug please report it on github  or let us know in the #graphql channel at Drupal slack.

Other posts in the series
Категории: Planet Drupal

Promet Source: How to Setup and Run Automated Accessibility Testing using Windows 10 OS

Planet Drupal - 29 Януари, 2018 - 12:36
Tools Needed: Step 1: Install Python then setup in Environment Variables
Категории: Planet Drupal

Gizra.com: We Don't Need an Intro Tune

Planet Drupal - 29 Януари, 2018 - 09:00

Amitai and Adam discuss a 1.6 million dollar stamp sale, skill set mastery and technological decision making, and the value of slowing down. Along the way Amitai explains his indifference to Drupal 8 and why Gizra’s Drupal-Elm Starter Kit uses Drupal 7 and Restful 1.x.

Continue reading…

Категории: Planet Drupal

OSTraining: Give Your Drupal Articles More Visual Appeal with Boxout

Planet Drupal - 29 Януари, 2018 - 08:10

A boxout is a design element used mainly in magazines to enclose related information to the main article while retaining some type of connection. You can use it to add extra links related to your content or a small bio.

The "Boxout" contrib module helps you add this design element to your content directly in CKEditor. In this tutorial, you will learn how to do just that. Let’s start!

Категории: Planet Drupal

DrupalEasy: Setting up Xdebug with Lando and PhpStorm

Planet Drupal - 27 Януари, 2018 - 21:05

Over the past few months, I've been test-driving various Docker-based local development environments with two goals in mind. First, as my "daily driver" for consulting work - I've been a long-time MAMP Pro user and I've been feeling for a long time that I need to modernize my local development tools. Second, I'm trying to figure out what is the most ideal local development environment for students of both our 12-week Drupal Career Online class (starts March 19) and our 6-week Mastering Professional Drupal Development Workflows with Pantheon (starts February 26) courses. 

One of the necessary skills for a professional Drupal developer (one who codes either modules or themes) is to be able run a solid debugging tool. As part of my evaluation of Lando, I decided to figure out how to set up local PHP debugging with Xdebug and PhpStorm on Mac OS X.

This process described below is largely based on a comment in an issue thread in the Lando issue queue by David Hunt - thanks, David!

My local setup includes:

  • Mac OS X Sierra 10.12.6  
  • Lando v3.0.0-beta.21  
  • Google Chrome with the Xdebug helper extension 
  • PhpStorm 2016.1.1  
Starting point

This tutorial assumes that you have a local Drupal site up-and-running in Lando and set up as a project in PhpStorm. In this example, my local site is using the Lando "Pantheon" recipe, but as you'll see in a bit, any recipe can be used. Also - my local site is based on the standard Drupal project composer template (with a nested docroot).

Enable Xdebug in Lando

The first step is to enable Xdebug in Lando - this is easily done by modifying the local site's .lando.yml file. In my case, I added the following:
 

 

If your .lando.yml file is defining a custom appserver service, then you should be able to just add the "xdebug: true" bit to the appserver definition. 

Once added, you'll need to perform a "lando rebuild" - this will rebuild your environment based on your .lando.yml, including adding Xdebug. The documentation page for the "rebuild" command includes a caution about how there's no guarantee that data will persist between rebuilds. In my experience, I haven't had any issues with losing my database. If you're concerned, then you may want to perform a "lando db-export" prior to rebuilding.  

Configuring PhpStorm

Here's where some magic comes in. Admittedly, I don't fully understand the details of some of the configuration necessary in PhpStorm to get debugging working, but I can confirm that following these steps, it has worked every time for me so far.

The first step is to add the Lando recipe folder as an "Include path" in your PhpStorm project. Open Preferences > Languages & Frameworks > PHP, click the "+" button at the bottom of the list, and manually type in the name of the folder of the Lando recipe you're using. On my machine it is: /Users/michael/.lando/services/config/pantheon. If you're using the standard "Drupal8" recipe, then it would be: /Users/michael/.lando/services/config/drupal8. Unless your username is also "michael", you'll want to update the path.
 

 

Then, go to Preferences > Languages & Frameworks > PHP > Servers

If no server for your project exists (it might be called “appserver”), then enable PhpStorm to listen for Xdebug connections, load a page from your local site in your browser and PhpStorm will prompt you to accept the incoming connection. In my case, it didn’t matter if the Xdebug helper is set to debugging or disabled at this point.
 

 

 

Then, once a server for your local site exists (remember, it might be called "appserver”), select it and ensure that "Use path mappings" is checked, and ensure that your project folder is mapped to "/app" for the "Absolute path on server". Also ensure that the "Absolute path for the server" for the “include path” is "/srv/includes".

 

Give it a try!

At this point, we should be ready for debugging! As a test, open up the site's index.php in PhpStorm and place a breakpoint.

Then, using the Xdebug Helper extension, enable debugging. Also ensure that PhpStorm is still set to listen to incoming Xdebug connections. 

Finally, load your local site's home and watch how PhpStorm will pause code execution at your breakpoint in the index.php file.
 

Warning - performance will suffer

While Xdebug is a powerful tool and will absolutely save you loads of time, there's a dark side. Performance will suffer. I recommend disabling Xdebug in your .lando.yml - by setting "xdebug: false" - (and rebuilding) when you're not using it. You can leave it enabled and gain back some (but not all) performance by disabling PhpStorm's listener as well. 

Final thoughts

In case you're wondering where some of the configuration settings come from, here's what I've figured out so far:

  • "appserver" is the name of the Lando service that contains the codebase. 
  • "/app" is the absolute path of the codebase in the "appserver" Docker container. 
  • "/srv/includes" is the absolute path to a Lando-provided "prepend.php" file in the "appserver" Docker container. As far as I can tell, this file defines and sets a bunch of environment variables depending on the recipe used.
     
Категории: Planet Drupal

fluffy.pro. Drupal Developer's blog: PHP Netflix Eureka client

Planet Drupal - 27 Януари, 2018 - 21:05
Netflix Eureka is a REST service that is primarily used in the AWS cloud for locating services. It comes with a Java-based client. But if you need a PHP-based client - welcome under the cut.
Read more »
Категории: Planet Drupal

Lullabot: Tom Grandy on Backdrop, Drupal, and Education

Planet Drupal - 27 Януари, 2018 - 19:04
In this episode, Matthew Tift talks with Tom Grandy, who oversees websites for 23 school districts. Tom describes himself as a journalist, a teacher, and a non-coder who helps out with documentation and marketing for Backdrop. He describes his experiences using proprietary software, finding Drupal, his involvement with Backdrop, and the challenges of using free software in K-12 education. Tom shares why people working in schools make decisions about technology most often based on cost, but that he believes we should also considers software licenses, communities, and other more philosophical factors.
Категории: Planet Drupal

Frederic Marand: Tip of the day: how to debug Composer scripts with XDebug and PhpStorm

Planet Drupal - 27 Януари, 2018 - 13:51
The problem: XDebug doesn't work for Composer scripts

PhpStorm is quite convenient to debug scripts with XDebug (do you support Derick for giving us XDebug ?): just add a "Run/Debug configuration", choosing the "PHP Script" type, give a few parameters, and you can start debugging your PHP CLI scripts, using breakpoints, evaluations, etc.

Wonderful. So now, let's define such a configuration to debug a Composer script, say a Behat configuration generator from site settings for some current Drupal 8 project. Apply the configuration, run it in debug mode, and ....

...PhpStorm doesn't stop, the script runs and ends, and all breakpoints were ignored. How to actually use breakpoints in the IDE ?

read more

Категории: Planet Drupal

TIP Solutions: Adding social media feed to website - or not?

Planet Drupal - 26 Януари, 2018 - 16:04

When adding a social media (SoMe) feed or "some wall" like here on the right bottom corner to your webpage the big question is: Why would you put it to your site? Why is it there?

If the answer is something like "to get some content to your site." - consider again. The SoMe feed might benefit you or harm you depending how you manage it.

Here are some points to consider:

Social media SoMe Drupal 8 SoMe wall Planet Drupal
Категории: Planet Drupal

Love Huria: Emboss your footprints in the Drupal Sand - Drupal Camp Goa 2018, Call for sessions

Planet Drupal - 26 Януари, 2018 - 03:00

We are thrilled to bring you the most exciting event of this year Drupal Camp Goa 2018! You would be ecstatic to be a part of something really big that’s happening in India’s most sought-after destination, Goa. It’s a shoutout for all of you who love developing and would like to extend their immense support to the web’s leading content management system (CMS), Drupal!

Why should Drupalers have all the fun!

This time it is not just Drupal, we are exploring beyond it. Join us to share your knowledge on topics like...

Категории: Planet Drupal

Lullabot: Rock and a Hard Place: Changing Drupal.org Tooling

Planet Drupal - 26 Януари, 2018 - 02:17
Matt and Mike talk with the Drupal Association's Tim Lehnen and Neil Drumm about the changes to Drupal.org's tooling.
Категории: Planet Drupal

Platform.sh: HHVM deploys off into the sunset

Planet Drupal - 25 Януари, 2018 - 23:58
HHVM deploys off into the sunset Crell Thu, 01/25/2018 - 20:58 Blog

We always aim to offer our customers the best experience possible, with the tools they want to use. Usually that means expanding the platforms and languages we support (which now stands at six languages and counting), but occasionally it means dropping tools that are not being used so that we can focus resources on those that are.

For that reason, we will be dropping support for the HHVM runtime on 1 March 2018.

HHVM began life at Facebook as a faster, more robust PHP runtime. Although it never quite reached 100% PHP compatibility it got extremely close, and did see some success and buy-in outside of Facebook itself. Its most notable achievement, however, was providing PHP itself with much-needed competition, which in turn spurred the work that resulted in the massive performance improvements of PHP 7.

Similarly, Facebook's "PHP extended" language, Hack (which ran on HHVM), has seen only limited use outside of Facebook itself but served as a test bed and proving ground for many improvements and features that have since made their way into PHP itself. Like HHVM itself, though, Hack never achieved critical mass in the marketplace outside of Facebook.

Back in September, Facebook announced that they would be continuing development of Hack as its own language, and not aiming for PHP compatibility. Essentially Hack/HHVM will be a "full fork" of the PHP language and go its own way, and no longer try to be a drop-in replacement for PHP.

Platform.sh has offered HHVM support as a PHP alternative for several years, although as in the broader market it didn't see much use and with the release of PHP 7 the performance advantage of HHVM basically disappeared, leading people to migrate back to vanilla PHP 7. Looking at our own statistics, in fact, we recently found that HHVM was virtually unused on our system.

"Give the people what they want" also means not giving them what they clearly don't want, and the PHP market clearly doesn't want HHVM at this point. We will therefore be dropping support for it on 1 March. If Hack/HHVM develops its own market in the future and there's demand for it we may look into re-adding it at that time, but we'll wait and see.

Good night, sweet HHVM, and may a herd of ElePHPants sing thee to they REST!

Larry Garfield 30 Jan, 2018
Категории: Planet Drupal

Promet Source: How to Set Up Responsive Images in Drupal 8

Planet Drupal - 25 Януари, 2018 - 21:56
Responsive images are great! If I wanted to quickly introduce what responsive images are to some, I would say: On mobile? Small images. Tablet? Medium images. Desktop? Large images. This article is a complete "how to" in setting up responsive images in Drupal 8.  If you are using Drupal 7, check out my previous article here: Picture Module: Building Responsive Images in Drupal 7.
Категории: Planet Drupal

Phase2: Decoupled Drupal: A Guide for Marketers

Planet Drupal - 25 Януари, 2018 - 20:58

If you are considering a move to Drupal 8, or upgrading your current Drupal platform, it’s likely that you’ve come across the term “decoupled Drupal”, aka “headless Drupal”. But do you know what it means and what the implications of decoupled Drupal are for marketers? In this guide we will define decoupled Drupal and share three reasons why marketers should consider a decoupled architecture as they evolve their digital experience platforms.

Категории: Planet Drupal