Presentation
Surely people are not sure what the word architecture combined with a process of agile development and deployment.
I will try to highlight the architectural complexity of the model and mention anything that may be involved in a portal architecture.
The product of choice is Drupal, but Drupal is not the center of architecture, but a spot in it.
A good architecture should be adaptable to another product without excessive complexity and keeping his footing.
To do this we will go from the system moving towards development and ending with a community of portals.
Five keys
- g.- Architectural Keys: The presentation and composition of these architectural components is also architecture
- q.- Architectural Keys: The relationship of these needs with the component architecture to use is architecture
- e.- Architectural Keys: The choice of components is architecture
- p.- Architectural Keys: The decision to minimize the documentation and group common needs is architecture
- k.- Architectural Keys: The management and control components of the portals is architecture
g.- Architectural Keys: The presentation and composition of these architectural components is also architecture
By default Drupal presents the components in a list format.
At the same time provides Blocks, Views and other objects to display the information on this site.
The decision of how to do this deployment and the ability to modify it relates to an architecture appropriate content presentation.
Since there are these products, since the time of Php Nuke and similar distinction is made between a reduced format of the component, called Drupal Teaser, and an extended format which displays all of its contents, known as Body, Body, Full House, Complete, etc.
Have input from at least three variants of the presentation:
- Titles
- Teasers
- Full
The idea is to customize these parts according to the information we want to show at any time.
Drupal by default to cut number of characters, whether there are modules that create a separate field for teasers.
But the form that gives us that flexibility is Content Templates.
This module allows us to customize the output of the components.
This module allows you to create templates and systems and most importantly, they are stored on databases, therefore we speak of components that can be shared among multiple portals with the same types of user.
The decision of when to use a template or not is an important factor in architecture.
In turn, own types of Drupal can be related, both with links and inclusions, you can create complex hierarchies that make more advanced components.
This composition is a determinant of the architecture of the portal.
Therefore, the appearance of the portal not only can be modeled with the same objects themselves but also with components created by us.
I believe this ability to create custom components is one of the most powerful aspects of Drupal.
The module components and further the field and matched between taxonomy module provided by another fantastic Taxonomy Content will go directly into the core of Drupal 7.
It is direct evidence that informs us of the importance of developing this form of writing or portals.
q.- Architectural Keys: The relationship of these needs with the component architecture to use is architecture
When we value a project, we must consider to what extent it is important to one of the requirements.
The relationship of this requirement caused by the requirement and a course component that will satisfy a very important architectural aspect to balance the process of creating the site.
There may be instances where the component fill those needs perfectly.
Will be important to compare potential candidates who also come to fill.
It is time to analyze the established or existing component to decide if you need a new component in the system.
And if you get that case, we must analyze the cost of implementation due to the importance of that requirement.
Therefore not all needs are the same and not always the best option to get to try to solve them.
It is very necessary to make a study of existing components, the current state of the art and future changes will entail.
You can be the best option for a postponement of that functionality before engaging in a development whose benefits are dubious.
And if you really need, no doubt will never be the option to develop independently, but join the community, closer to the creators of such components or that can really provide the needed and either request services or collaborate with to achieve collaboration solution that allows the requirement.
This should be the line of action.
This was the largest that has made free software collaboration and is what allows us to anticipate problems and compatibility that enhances the product and focused on quality system whose sole purpose is to improve the company itself.
e.- Architectural Keys: The choice of components is architecture
It is essential to a correct study of the modules required before deciding on any further development.
It is a multi portal transcendent in terms of modules and components selected.
It will be very important to the valuation of common components, not only those provided by Drupal, but categories, views, data types defined to simplify future developments.
For all these reasons, an approach component-oriented architecture is one of the keys to the success of the product.
The peace of knowing that this functionality is already solved by the X component, for addressing development as if it were a big Lego, to know what parts are available and have direct example of how those pieces interrelate.
Therefore the approach to a portal should be a part of architecture.
We must not isolate the development of the portal of the implementation of all the portals.
Therefore there will be common components and specific components for this portal.
These components may be physical and logical.
Physical components are all provided by Drupal therefore attributable physically, such as modules, themes, templates, etc.
And software components generated by the product from them, such as blocks, views and the same modules, themes and templates.
A good architecture must consider the existing common components to minimize further developments and to join efforts in fighting for the final product quality.
Therefore, the continued study of modules and the daily documentation of selected components and developed is considered crucial for the successful architecture is deployed properly and enjoy the benefits of the product.
As you can see, this method of components is beyond Drupal
Let this be a product, but the philosophy of documentary and art studio continued deployment possibilities is and shall apply to any products that are focused on how components, so bazaar, as is often phrased as always being free.
p.- Architectural Keys: The decision to minimize the documentation and group common needs is architecture
How we get closer to the problems so that the documents are speedy and simple to interpret.
We must simplify the system.
We forget all the methodologies such as UML or others that they have only managed to complicate their representation and closer to the programmer or not so, but emphasize the need for an intermediate position to interpret it.
We must make simplicity to the case, betting on a new air into a single system of components.
This methodology has been a party of architecture defended before the independent entity Red.es of the Ministry of Industry of Spain.
I present a documentation system out of the ordinary:
Agile Methodologies - System Documentation.
We have succeeded in loosening the document all the components, auto components associate requirements and focus exclusively on business customers.
We simplify the model.
And this simplification is architecture
k.- Architectural Keys: The management and control components of the portals is architecture
We talked about relations between components, but we must also note the organization of the same.
Getting a simple system that allows localization of components and easy integration into an environment of that component or functionality, linking a range of components is a credit to good architecture.
No doubt a structural level a system of symbolic links facilitate this work.
We discuss below the recommended structure to Vector SF and other partners to Red.es and that is being used on servers Brqx.
The structure has an unmistakable character fit in any system.
The initial word "brqx" whatever that is identifying, serves two purposes:
1 . - Do not be confused with a directory where you install any systems (Unix, Mac, Windows).
2. - Do not be confused with any definite plan, it never made any plans that call brqx.
The second string defines the word level:
- Base : Product Level (Products level)
- Lnk : Level of links (link level)
- Proy : Project level (here, English is different: Project Level)
- Pers : Customizations
- www : Final level of sites (site level)
The third term of the string defines the product.
We start with Drupal, but the structure is designed to suit any product.
/brqx/base/drupal
The fourth word defines the version of the product.
It puts a letter because many systems have problems if a folder starts with number.
- v50
- v60
- v70
Once you have selected the version defined three levels:
- core - 'Core' unchanged for Drupal
- modules - 'Modules' Drupal Modules
- themes - ' Themes' Drupal Themes
For now we will not delve further into the structure.
We're just going to indicate an example of it:
/core
/core/v612
/core/v615
/modules/abc/c/captcha/captcha_2_1
Now about the level 2.
At this level indicate the components that are certified and / or final versions being used.
The initial path is similar:
/brqx/lnk/drupal/v60/modules/abc/c/captcha
Here we specify the functional cores formed with links (already certified versions)
We can see the core bas (base module) that defines the basic functionality required for all sites of architecture.
The path of this common functionality is:
/brqx/proy/drupal/v60/base
The modules that form:
a/ajax ' /brqx/lnk/drupal/v60/modules/abc/a/ajax
c/cck ' /brqx/lnk/drupal/v60/modules/abc/c/cck
This information is now obsolete, but certainly one way to teach when organizing a complete and complex architectural approach applies to a multi site development system with a philosophy of simplicity.
The advantage of using a homogeneous structure is that the processes can be automated, therefore Drush applications as well as our scripting architecture allows us flexibility in developing out of the común.
Althought sites functions are not completely updated, this architecture is downloadable from the internet:
Policies allow scripts to an agility that can not get in a web process.
Drupal knows. The Drupalers know.I invite you to learn how to create shell scripts to automate processes, customize settings.
There is so much to be learned that enhances the final product.
Drupal Arquitect: Ricardo Cabello Torres
I am available for work job as Agile Architect Drupal or offer my design services portals Portals Professionals .
I invite you to learn to turn a revolutionary approach to architecture-based positioning Your best location - Brqx
It is a pleasure to share with you my concerns in society and my fight unanimously for a better world.
I invite you to meet current social customs - Brqx.
Also if you like quality collectibles, I invite you to participate in projects like My chopsticks or My presentations .
Without further also, thank you for your visit.
Facets of Drupal - Keys to Success
