Drupal News

Quick question: is Drupal 8 supports writing post in MarkDown?

Drupal 7 - block_filter module troubles

  • I'm trying to output a bean I created in specific locations in certain tpl files, but all that is getting output is the string '[block:bean:calculator-block]'. The module page says that the format should be '[block:{module}:{delta}]'. I grabbed the delta by navigating to the edit page and checking the url. I also tried to use their example of '[block:system:0]' as a test to see if it was the bean module but that didn't print the block either.

    I was wondering if anyone knew what the issue might be.

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

    3 days 3 hours ago

Lullabot: A Software Developer’s Guide to Project Communication: Part 1

  • The key to a successful project is good communication.  Honesty and directness about timelines and scopes of work go a long way to relieve pressure from the development team and avoid frustration from stakeholders, but what about the day-to-day information exchanged between developers, designers, and project managers? This is the grease that keeps the project running smoothly and should not be overlooked.

    As teams vary in size, so do the roles and responsibilities of individual team members.  Smaller teams have fewer communication channels, so you may need to switch between your developer hat and project manager hat frequently.  On larger teams your hat rack may be quite sparse, but the number of communication channels, and thus the possibility of miscommunication, is far greater.

    Regardless of the size of your team, information about the project must be communicated and documented effectively.  From very large teams to projects where it's just me, I've learned how damaging even minor miscommunication can be.  Conversely, you look like a hero when you get it right.  Stakeholders, project managers, and developers work in very different realms. In this article I'll discuss a few overarching principles that I've learned to help navigate the monsoon of information blustering through a project.  They will help you regain control of your time and create a more productive and successful project.

    What is Communication?

    Existentialism aside, what do we really mean when we talk about communication?  Communication is an exchange of information between parties.  The parties may be people, but they may also be project management tools.  From video conferences to GitHub notifications, these are all part of the project communication landscape and require different levels of attention.

    Forms of Communication

    Here are some of the most common methods of communication I've dealt with on projects:

    • In-Person Meetings
    • Voice conference
    • Video conference
    • Chat
    • Text message
    • Direct Email
    • Email Notifications
    • Project Management Tools
    • RSS Feeds
    • Twitter
    • Mobile Notifications

    All these types of communication serve a unique role. We wouldn't use them if they weren't helpful, but the question we really should be asking is, "are they necessary?"  Gone unchecked, many of these tools can overrun each other and tangle the workflow.

    For example, Slack is a great tool for team members to quickly exchange information between each other, but numerous tools can also post updates into Slack.  A few may be helpful, but too many can dilute the conversation and the effectiveness of the tool.  So how do you find the balance between effective and over-communication?  We can start by categorizing these forms of communication into two groups: active and passive.

    Active vs Passive Communication

    I find it helpful to group all communication into two categories: active and passive.

    Active communication is a two way street.  The sender is expecting a direct response.  Google hangouts, Slack discussions, and phone calls are all forms of active communication.  There is an immediate reciprocation between the parties involved.  You wouldn't invite someone to a conversation just to read them the backlog of tickets, would you?

    Passive communication, on the other hand, does not require a direct reply.  This is not as easily definable as active communication.  Let's take a look at email as an example.

    If Stakeholder Sarah emails you a question about the next deadline, that is active communication.  She is expecting a response from you in a timely manner.  When a Github notification shows up in your inbox informing you that your pull request has been merged, no follow up is required.  This is passive.  Now, if you receive an email from Jira Notifications because the client asked a question on one of your tickets, which category does that fall under?  It's a notification email, so you shouldn't respond to it directly, but the client is expecting an answer.  Ultimately it depends on the ground rules for communication you set for your project.

    Setting Expectations

    I tend to follow this order of urgency for response, from most urgent to least.  It's important to agree on a set of communication guidelines at the beginning of a project so everyone on the team follows the same expectations.

    1. Live Communication If you ask me a question face-to-face, of course I will respond to you right away.
    2. Chat Chances are that unless I've set my away message, I'm receiving chat messages in real time.  However, I might be neck-deep in some code or preoccupied in another conversation, so I will respond as soon as I can, but maybe not be right away. 
    3. Mentions in Comments Comments in Jira tickets or GitHub pull requests will likely go unread even if they show up in my inbox unless I am specifically mentioned in them.  I get a lot.  The convention to use the @ symbol to mention another person links their account in the ticket and generates more specific notifications for that person.  It the difference between saying something needs to be done and asking someone to do something about it.
    4. Email I use a couple of email addresses to keep my interests separate so I use an email client to aggregate them into one management space.  However, I find constant email notifications and alerts distracting, so I don't keep my email client open when I don't need to (more on this later).  If you email me, I will probably get back to you within the day, but don't rely on me standing by my inbox waiting to reply to you.  This rule is so important to us that we actually wrote it into the Lullabot Employee Handbook along with a few other tips.
    5. Unmentioned Comments I will likely still get email notifications about activity on repositories, projects or tickets I'm watching or otherwise related to, but if you don't mention me in the comment, it will disappear into tornado of notifications and chances are I won't see it unless I'm reading the backscroll on the ticket.

    These are just my rules, but they have worked well for me so far.

    Understanding the communication landscape of your project is a necessary foundation.  Setting the proper expectations will prevent miscommunication and keep the project running smoothly.  So far we've identified some of the most common pitfalls and laid the groundwork for a fluid project.  In the next two articles of the series I'll provide advice for managers and stakeholders on how to communicate effectively with the development team and also offer some recommendations and tricks for handling the number one offender when it comes to communication overload: email.

    3 days 5 hours ago

How can I solve Writable (public download method) error in Drupal 8 without 777-ed the directory?

  • I have this error:

    FILE SYSTEM

    Writable (public download method)

    The directory sites/default/files does not exist. An automated attempt to create this directory failed, possibly due to a permissions problem. To proceed with the installation, either create the directory and modify its permissions manually or ensure that the installer has the permissions to create it automatically. For more information, see INSTALL.txt or the online handbook.

    How can I solve this problem without give 777 permission to whole directory?

    Note:

    • I moved Apache root from /var/www to ~/www
    • I am using 16.04 Xubuntu
    • I am using PHP7
    submitted by /u/reddit_lonely
    [link] [comments]

    3 days 8 hours ago

Drupal 8 Lessons From the Field pt 2: Enhancing Front End Drupal Development

Weekly useful Drupal things to know thread

InternetDevels: Spice up your Drupal 8 menus with the Superfish module

  • Let’s talk about secret ingredients in menus. Like the right spices, they create special flavours that your guests really enjoy. When it comes to your Drupal website menus, the recipe is simple: just add some jQuery! Using the Superfish Drupal module, which integrates the jQuery Superfish menu plugin, you can create interactive multi-level menus with exceptional usability features. Let’s see how it works on Drupal 8’s example.

    Read more

    3 days 10 hours ago

Deeson: Deeson at DrupalCon Vienna 2017: Becoming an Agile agency

  • Last month a few of us in the team attended DrupalCon Vienna with fellow Drupal enthusiasts and developers from across Europe and further afield.

    Over the three days, my teammates and I hosted several Birds of a Feather (BoF) sessions between us. The format is more participatory than a traditional talk, so it’s a great opportunity to engage in discussion and hear other perspectives from within the community. 

    Deeson has been delivering digital projects since 2001, refining our agile delivery process over the years from the DSDM Agile Project Framework in combination with other agile practices particularly suitable for an agency environment.

    My first BoF session invited other conference attendees to share their experiences (the highs and lows), tips and best practices for making Agile work in an agency. The following is a roundup of what we discussed over the hour.

    Starting slow.

    We identified that the typical journey sees agencies start off being ‘agile’ with a small a. They have begun to implement some of the process tools around agile, such as SCRUM, standups, sprints and so on, but aren’t yet living by the core elements of the Agile Manifesto.

    Individuals and interactions over processes and tools. Working software over comprehensive documentation. Customer collaboration over contract negotiation. Responding to change over following a plan.

    Agile Manifesto

    Including the client.

    We talked about whether the client should be an integral part of the delivery team or should be kept at arm’s length. Those who believed they had an Agile workflow suggested that the client should be part of the team and involved throughout. The benefit being that – as part of the team delivering the product – they share the risk with delivery.

    Those who felt they still had some way to go in becoming Agile were more wary of this approach, believing the client either couldn’t take on these roles or wouldn’t want to. These agencies were more likely to retain full control of the project and client, and accept all the risk as a result.

    Handling changing requirements.

    There was a discussion about the time taken up with dealing with change, and how clients don’t always appreciate the efforts involved in managing their changing requirements. I described how we deal with this at Deeson with our Dual board in Jira.

    This process separates new ideas neatly from refined and signed off units of work ready for development. The client can see their backlog of new ideas and what state each is in, and knows that effort will be involved in taking those ideas from concept to ready for development.

    We also considered the need for developers to be able to highlight to a client when an idea is completely new, and to prevent them from trying to squeeze additional functionality into a sprint which already had been signed off.

    It’s good to have a SCRUM master or some level of leadership position in the team so developers don’t have to make these decisions themselves and can defer to someone else if they are unsure.

    Questioning sprints.

    Someone raised the idea that sprints were a waste of time in a truly agile project. They suggested that nirvana could be achieved with Kanban alone; there is only work in progress and with an engaged client and team you would be constantly refining the backlog so new work could constantly be pulled in and worked on. This works well in a model where the client has you on retainer as their technical team for a long period of time (rather than to deliver a specific thing, like a website). 

    So there’s always a finite amount of WIP (work in progress). If stories are always refined to the point that they are about half a day's effort for one person, and are complete (finishing them can be tested and, in theory, released) then you can calculate the velocity and the time remaining on sections of work fairly accurately.

    We invest heavily in agile training for our staff and clients, and we’re currently hiring for multiple roles including a Delivery Manager.

    3 days 11 hours ago

Does anyone know of any ways to link drupal blog posts to a facebook page?

Pages