All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
We use Slack to communicate internally as well as with our clients, but we also make use of it in different ways that help us deliver a better service to both groups of stakeholders.Fran Garcia-Linares Fri, 05/04/2018 - 14:19
Slack vs Email
Whilst we still use emails when the situation requires, we always try to move the communication related to our projects to slack. Most of our clients are in slack in their own dedicated channel, which happens to be the same one that all designers, developers, project managers, etc. use for communications related to the project.
This way, everybody involved in the project is aware of what’s going on. Information gets passed easily across the team and we avoid multiple “broken telephone” situations. Also, if the person who is usually responsible for something happens to be sick or on holiday, the rest of the team can assist instead of getting an unhelpful “Out of Office” reply.
Slack and its bots are part of our Global Maintenance team too (I guess they can be considered remote workers). They help us with our day to day tasks in a myriad of ways.
- Activity Channel: we use slack integrations that will pull any message or activity related to the tickets that the team is taking care of in the current sprint. This can get a bit noisy sometimes but it’s a wonderful way to stay informed of what’s going on on our team board. No more email and Jira issue watching.
- Think about Blaize: it’s not just a reminder to think about Blaize (which we also do) who lives in New Zealand, it’s also a reminder for the UTC timezone team to starting wrapping up the day, commit everything not yet committed, update tickets not yet updated and leave things ready for Blaize, who will tell us “Good morning” at our 8~9pm (his 7~8am).
- Information about important events: we have multiple integrations for regular but important events on certain projects, for peace of mind, and to make people aware that something has happened. The following examples are to inform everyone that an automatic Mailchimp list was created (this is crucial for the client) and to inform developers that a deployment has happened (and whether it went well or not - red vs green).
- Instant bug reporting: this is probably the most important one and the one that is making the biggest difference to our Global Maintenance team. We use it whenever there are bug reports that we can’t replicate because the data changed, or when we don’t have enough information to take an action. If we can’t fully resolve a ticket request, we’re very likely to create an integration that will “spot” a problem and give us useful realtime information so that we can debug knowing further information about the issue. Over the past few months we’ve done this in multiple projects and it not only gives us instant feedback, it also informs everyone on the channel that something is happening, so we can be alert and take an action if needed. Below are two examples of those situations, again on critical parts of our clients’ systems, that allowed us to take quick action.
These are just a few samples of the multiple integrations we have. If you want to know a bit more about the technical part, just keep reading.
How to do the integration?
Create the slack webhook: here.
Use the Drupal slack module (recommended) or code your own function, which could be as simple as:
Call the desired function:
Using slack module:
Using custom module:
That’s it really, as you can see it’s not too complex but it adds huge value to our day to day work.
With Visma Sign you can sign documents digitally. Simply upload your document and send the invitation to sign via email. https://allekirjoitus.visma.fi/digital-signature/
A super quick blast from the past today; a Drupal 7 based article!
I had some work recently to create a new "setting" variable for one our Drupal 7 multilingual sites, which meant creating multilingual versions of those variables. I soon found out that there is very much a correct way - or order - to achieve this as I got this one very wrong (I had to re-instate my DB!). So here I am writing a very quick guide to help those from my wrong doings.
(This guide assumes you have a multilingual site setup with i18n's Variable translation module.)
Four simple steps to achieve a multilingual variable:
- Declare your new variables via hook_variable_info
The options you can set in this hook are well documented - start reading from the Variable module's project page.
- Flush the variable cache and get your new variables registered using an update hook. The meat of the update hook is below -- note that this assumes you want all all of the possibly-localizable variables to be made translatable:
- Create or alter your settings form (I'm assuming it uses system_settings_form() or is already recognised by the i18n/variable systems as a form containing translatable variables) and add your new form elements. Make sure the element(s) are the same as your newly created variable(s) - I use a $key variable to avoid any mistakes there!
Head over to /admin/config/regional/i18n/variable or your settings form to see your new multilingual variable in all it's glory!
The demand for Voice technology is rising and it is likely to revolutionize the way publishing websites engage with their audience. The Internet-connected virtual assistant is seeing a significant rise, but the question is how publishers can use this tech to grow their audience base and ultimately increase revenue? Here, we will explore how to use Actions on Google for a new project and an existing one followed up by an integration with Drupal 8 website.
Let’s have a look.Integrating Actions on Google with a device
Integrating Actions on Google with an electronic gadget or smart speakers allow us to trigger voice command to control various Drupal commands such as:
- Clearing cache
- Count number of node
This is a module to do the electronic billing for Costa Rican regulations only.
It solves the signature process, it lets us to create electronic documents and
send them to the verifications API, generates the XML documents,
email integrations, customer management, and taxes management.
----------------- PARA LOS TICOS ------------------
Desde el 15 de enero del 2018, todos los contribuyentes de Costa Rica, sean personas físicas o jurídicas, del sector salud deben utilizar de forma obligatoria comprobantes electrónicos como método de facturación, tal y como lo establece la resolución DGT-R-51-2016.
Con esto en mente ParallelDevs desarrolló este módulo como una Solución OpenSource para que cualquier empresa pueda montar su plataforma de facturación de manera gratuita o bien ofrecer ese servicio a sus clientes.
Si usted necesita alguna solución a la medida puede contactarnos a info[at]paralleldevs.com
You might have noticed that Wikipedia recently started enabling link previews; when you hover over a link, it displays a card with more information about the linked page.
My first reaction was: what took them so long? Link previews help to solve an important usability problem of having to open many articles, often in multiple browser tabs. However, after I started to read more about how Wikipedia implemented the link previews, I was reminded of how hard it is to do things at the scale Wikipedia requires.
Nirzar Pangarka, who works as a designer at the Wikimedia Foundation, shared that more than 10,000 links get hovered each second across Wikipedia. In another post, David Lyall, an engineering manager at the Wikimedia Foundation, shared that they are seeing up to half a million hits every minute on the API that serves the link preview cards.
I have a great appreciation for Wikipedia's seemingly straightforward link previews. Delivering a feature at this scale is an impressive achievement.
Contributing editor Katherine Cross celebrates the ways in which Blizzard's latest WoW expansion tells a tale of 'tragedy, diminishment, and the brutality of war without appearing wanton or childish.' ...