Empieza con Drupal
Nos encanta presentar a los principiantes los conceptos básicos de Drupal. Ofrecemos seminarios introductorios cortos para grupos pequeños según demanda para la construcción del sitio, la creación de plantillas y el desarrollo de extensiones. Cada seminario incorpora, cuando corresponde, la arquitectura de la información, las pruebas de experiencia del usuario y las técnicas de liderazgo y colaboración necesarias para que cualquier proyecto que no sea solo sea un éxito.
Desarrolla tus Habilidades
Enseñamos equipos de desarrollo y programadores en solitario en nuestro lugar de trabajo o en el suyo, con el programa adaptado a los problemas que está tratando de resolver. Hemos proporcionado tal capacidad en programación Drupal, temática y plantillas, migración de datos y Backbone.js, pero siempre estamos mejorando nuestras habilidades tecnológicas, así que háganos saber lo que está buscando y es posible que estemos justo delante de Estás en la curva de aprendizaje y listo para tirar una cuerda - y listo para tirar una cuerda.
Inscribirse en un Curso
We offer courses with a defined curriculum on building, theming and developing a site. This is great for intermediate trainings of groups. We also offer decision-maker seminars for leaders who need a better understanding of the technology underlying their projects.
¿Por qué Agaric?
Aprenda Drupal 8 de expertos profesionales, con énfasis en los profesionales: Tenemos la experiencia práctica en el desarrollo de sitios web para impartir las habilidades necesarias para realizar el trabajo y hacerlo bien.
Como desarrolladores, Agaric es conocido por asumir las tareas difíciles cuando colaboramos en equipos más grandes. Estamos encantados de capacitarlo, porque siempre hay algo difícil que querrá contratarnos para hacer. En serio, desde nuestros primeros proyectos hace diez años, nuestro objetivo ha sido hacer que nuestros clientes nos necesiten lo menos posible, para poner todo el poder posible en las manos de nuestros clientes. Es por eso que comenzamos a utilizar los sistemas de administración de contenido en primer lugar, y es una tradición que continuamos desarrollando con Software Libre, escribiendo documentación y brindando capacitación.
Agaric participa activamente en la comunidad Drupal en general y se ha presentado en varios Campamentos Drupal, así como en la organización de Jornadas Mundiales de Capacitación en Nicaragua desde 2013.
Solicitar un Entrenamiento
In this installment of our case study about working with long term projects I will explain the architectural decisions made by our client, ZEIT ONLINE, regarding the relaunch of their digital subscription platform. Please refer to part 1 of this series for basic information about the project and a discussion of how to deal with the evolution of programming languages and operating systems.
Early on our client had decided to split up the platform into separate services that communicate via HTTP. This would allow them to develop those components using the most suitable technology for each, as well as allowing the services to progress more independently. The existing platform already used a separate service for authentication and storing user profile information. We took it from there and worked with the client to take it a step further.
First we identified the major logical components of the platform:
- User accounts
- Product presentation
- Checkout
- Order management (including data exchange with fulfillment provider)
- Content delivery (via HTTP and E-Mail)
When considering how to divide the whole into services, we found it helpful to elaborate on the interfaces between them. The overall idea here is similar to what is accomplished by writing tests first: by grasping how you will consume an interface, it helps define the implementation more succinctly. In order to keep it simple we imposed a constraint on communications between services: When responding to any request, a service must not depend upon another HTTP request to a third party. That way developers would not have to deal with complex dependencies in their development environment and errors would be easy to locate.
Another important consideration was not to do too many things at the same time. Drupal 6 was fulfilling the roles of delivering content and product presentation to the client's satisfaction and the functionality was provided by a small amount of modules. As an upgrade of those parts to Drupal 7 would be straight forward, that was the direction taken for those items. A new client side order form had been developed already and was in experimental use as an alternative to the Ubercart checkout process.
That left the order management as a candidate for a new service. It needs to take orders from the client side order forms, store them, and send them to the fulfillment provider. It would also need to receive updates about the states of an order from the fulfillment provider. Agaric was asked to develop that component and picked Flask as a framework. That was a subjective choice, any other technology for building web applications could have been employed as well.
In upcoming posts I will cover the individual components and how they fulfill the goals of the overall architecture. ZEIT ONLINE is happy with the architecture and is currently moving further along those lines.
Clayton speaks at events around the world on topics including Free Software, Platform Cooperatives and Cooperative Business Structures.
It's great to be here, and there, and there.
Thanks Indieweb module for Drupal!
There is an important correction to be made to the top-selling Drupal book, the Definitive Guide to Drupal 7.
The slogan printed on the cover is incorrect. The book does not contain "Everything you need to know about Drupal"— rather, a central goal of the book is to show how to keep learning and growing within the Drupal community. Everything to know about Drupal could never fit in one book or set of books.
Admittedly, that point is probably made in 20 pages. The other thousand-plus pages are a solid effort to give a whole lot of information to help everyone (at every level) succeed with Drupal:
The Definitive Guide to Drupal 7 accelerates people along the Drupal learning curve by covering all aspects of building web sites with Drupal: architecture and configuration; module development; front end development; running projects sustainably; and contributing to Drupal's code, documentation, and community.
Which brings us to the actual slogan for the book: Configuration, Code, and Community. This broad sweep of what it takes to do Drupal right comes in these pages from the perspective (and blood, sweat, and tears) of thirty-four contributing authors, including top Drupal contributors. The talent and effort in this book is humbling, and inspiring.
The book site, DefinitiveDrupal.org, is lagging behind what the community of readers needs for updates and discussion, but i could not put aside telling people about the book any longer just because that site (or Agaric's, for that matter) has been neglected. You, your friends, and the cousin looking for work should know you can buy this book for cheaper than i can photocopy it for you. And the publisher, Apress, did a great job with the layout and production, despite the slogan slip-up.
Note: E-book versions will come; it seems we have to wait on Amazon and Apple, but we will also pursue the ePub format. Sign up to learn about new formats and new material (so very rare updates only when there's something definitely worth knowing about).
Thank you for your kind attention!
benjamin melançon
Agaric is not hiring! As a worker-owned-and-run collective, we don't have bosses or employees. We do need to add to our team to keep up with our opportunities, and if we have to we'll make an exception and hire someone with strong administrative skills, willingness and ability to lead projects, and knowledge or willingness to learn finances. Front end development skills a bonus. We believe in cross-training! Especially if you can see becoming a Principal at a go-great-and-do-good cooperative technology shop,
Photo courtesy of Women of Color in Tech stock images. CC Attribution License
Numquam eos enim voluptatem beatae doloribus. Ea provident dolor repellendus dolores adipisci laborum illo. Quas iusto vel architecto totam voluptas assumenda. Excepturi est inventore et architecto velit ratione.
Eum sed quisquam vel voluptatum enim nisi optio nobis. Deleniti corporis magnam dolore quia. Perferendis voluptatum dignissimos cum atque quasi quis est asperiores.
Practical individual resources for opting out of surveillance
Things you can do personally and without too much difficulty to get a little more free from Nineteen Eighty-Four style government oppression and surveillance capitalism. (But remember, the most important and impactful things will require collective action!)
- PRISM Break
- Electronic Frontier Foundation's Surveillance Self-Defense
- Micky's blog post on daily business operations using (privacy-protecting) free software
Sign up to be notified when Agaric gives a migration training:
Getting an audio player to show on your content nodes only takes a few steps. However, like many things in Drupal, knowing what those few steps are can be a bit of a challenge. This short guide will provide a basic introduction for anyone looking to use this core functionality on their site.
Step 1: Enable the Media module
The media module is available in Drupal core, and just needs to be enabled.
Step 2: Create a new Media type
In the admin toolbar, navigate to Structure > Media types > Add media type
You may or may not have specific needs that determine how you name your media type. I simply named mine Audio file, and then selected Audio file for the Media source selection field. Don't forget to click save.
Step 3: Create an entity reference field on the entity type that should contain your audio player
In the most basic case, you will add a field to the content type where you want an audio player. When you get to the field type drop-down, select Media (under Reference). Of course, label your field according to your needs.
note: If you are using the paragraphs module, you might choose to create a new paragraph type and add a field there instead.
Click Save and continue
Click Save field settings
Now you will be directed to the Edit tab for your new field. Select your desired settings. The important bit here is that you scroll to the REFERENCE TYPE field set, and click the checkbox next to your new media type (Audio file in my case).
Scroll to the bottom and click Save settings
If you added this field directly to your content type, then you should be all set.
If you are using paragraphs, don't forget to enable your new paragraph type on the paragraph field of your content type.
Being able to share an article via a social network is a common request on a project.
Fortunately for Drupal 8 there is a module for that called Social Simple. This module allows you to display a share button on a node for the most popular social media networks:
You have been successfully signed up to learn about data migration training opportunities.
