DOCSLIB.ORG

481 Access Token, 125–126 Acquia Dev Desktop, 72 Admin UI And

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
481 Access Token, 125–126 Acquia Dev Desktop, 72 Admin UI And Index A Angular CLI, 356 installation, 356 Access token, 125–126 API Blueprint, 449 Acquia Dev Desktop, 72 API design, 449 Admin UI and JavaScript Modernization API-first distributions, 269–281, 283 Initiative, 466–467 Contenta (see Contenta) advantages, decoupled Drupal, 45 Headless Lightning (see Headless content syndication, 45–46 Lightning) front-end developer experience, 47 Reservoir (see Reservoir) pipelined development, 48 variations, 269 separation of concerns, 46 API-first Drupal, 18 user-centered user API-first initiative, 18 experience, 46–47 API specifications, 449 Angular, 355, 466 Apple Watch, 470 AngularJS, 355 Application programming components, 358, 361, 363–364 interface (API), 15 dependency injection, 372 Asynchronous JavaScript and directives, 359, 365–369 XML (Ajax), 22–23 ngFor directive, 365 Atom, 28 ngIf directive, 367 Augmented reality (AR), 468 two-way data binding, 365 Authentication, 113 HttpClient, 375 basic authentication (see Basic observables, 375–376, 379 authentication) retrieving data from Drupal, cookie-based authentication 375–377, 379 (see Cookie-based authentication) reusable and nestable components, 358 OAuth2 Bearer Token authentication scaffolding, 356, 358 (see OAuth 2.0 Bearer token services, 370–372, 374–375 authentication) subscribe() method, 379 Authorization code grant, 121 subscribing to observables, 378–379 Authorization header, 115, 116 two-way data binding, 359–360 Axios, 285, 327, 329, 391 481 © Preston So 2018 P. So, Decoupled Drupal in Practice, https://doi.org/10.1007/978-1-4842-4072-4 INDEX B Surrogate-Keys header, 461 time-to-live (TTL), 463 Basic authentication, 113, 204 use cases, decoupled access tokens, 125–127 Drupal, 455–456 authorization header, 115, 116 personalization, 455 generating keys, 122 security, 455 grants, 121 VCL, 462 handling expired tokens, 128–129 X-Drupal-Cache-Tags header, 461 HTTP Basic protocol, 114 Cascading Style Sheets (CSS), 4 installation, 122 Chatbots, 7 scopes, 123 Client credentials grant, 121 scopes are permissions, 123 Client-side validation, 289, 446 session cookie, 117–119 Composer, 69 Simple OAuth installation (see Simple downloading Drupal and OAuth module) dependencies, 70–72 user roles, 123–125 installation, 69 BigPipe, 52 Conference Organizing Distribution Black box problem, 50 (COD), 269 Block placement, 472–473 Consumer Electronics Show (CES), 8 Bluetooth Low Energy (BLE), 8 Content AR and VR, 7–8 channels, 9 C conversational, 7 Cacheability metadata, 52 responsive web design (RWD), 5 Cache invalidation, 52 situational, 8–9 Cache tags, 52, 456–457 Contenta, 270, 303 Caching, 455, 458 Contenta.js, 308 cache indexing, 461 installation, 272–273 cache invalidation, 462–463 mission, 271 cache tags, 457 reference builds content delivery networks (CDNs), 457 contenta_angular, 303–304 hard purges, 463 contenta_ember, 304 incoherency, 459 contenta_react, 305–306 monolithic Drupal architectures, 455 contenta_vue_nuxt, 307 personalization, 455 contenta_angular, 303–304 purge requests, 462 Contenta ecosystem, 303 reverse proxies, 458, 460 contenta_ember, 304 soft purges, 463 Contenta.js, 308, 455 482 INDEX contenta_react, 305–306 X-CSRF-Token request Content as a service (CaaS), 19, 284 header, 145, 148 contenta_vue_nuxt, 307 CouchDB, 92–93, 203, 206 Content delivery networks (CDNs), 382, databases, 206 391, 432, 457–458, 460–462 documents, 206 purge APIs, 462 Cross-origin resource sharing (CORS), 77 Contentful, 284 configuration in Drupal, 77, 79 Content management system (CMS), 11 Cross-site content staging, 92 Content modeling, 168 Cross-site request forgery (CSRF), 145 Content staging, 91, 94, 96–97 Cross-site scripting (XSS) Content syndication, 45 attacks, 50 Contextual administration, 53 CSV Serialization module, 63 Contextual links, 50, 477 Custom modules, 419–420 Contextual tools, 53 .info.yml file, 419 Conversational content, 7 Cookie-based authentication, 116, 117 Cordova, 6 D Core REST, 73 Decoupled Blocks, 472–473 configuration, 74–76 Decoupled CMS architectures, 12–14 content entities Decoupled content management, 13, 19 creation, 148–150, 152 Decoupled Drupal, 29, 468 deletion, 158, 160 caching (see Caching) retrieval, 146–147 choosing architectures, 42 updating, 153, 157 definition, 29 DELETE requests, 158, 160 disadvantages (see disadvantages, GET requests, 146–147 decoupled Drupal) HTTP verbs (request methods), 144 Drupal as site and repository, 38–39 issuing HTTP requests, Drupal core flowchart for decision makers, 43 safe and unsafe methods, 144 fully decoupled Drupal, 31–32 serialization formats, 145 JavaScript developer experience, 471 X-CSRF-Token request performance (see also Caching), 435, 441 header, 145 preview, 471 modules, 73 progressive decoupling PATCH requests, 153, 157 (see Progressive decoupling) POST requests, 147, 152 pseudo-decoupled Drupal, 32–34 safe and unsafe methods, 144 security, 50 serialization formats, 145, 151 use cases, 40, 468 Views REST exports, 161 site-and-repository, 270, 468 483 INDEX Decoupled Router, 442 personas, 467 DELETE requests, 158 user experience, 465 core REST, 158, 160 Drupal 8, 82 JSON API, 200 cache tags, 457 Derived schemas, see Schemas cache tag system, 455–456 Devel module, 73, 185 Form API, 477 content generation, 73 plug-ins, 420 Devel Generate submodule, 73 Typed Data system, 446 Digital signage, 468 web services, 82 disadvantages, decoupled Drupal, 49 Drupal-aware decoupled Drupal, 32 additional point of failure, 49 Drupal Console, 420 lack of content workflows, 51 scaffolding custom modules, 420 lack of contextualized tools, 50 Drupal 8 core lack of layout and display entity access system, 67 management, 51 Hypertext Application Language (HAL) lack of security and input module, 68 sanitization, 50 OAuth module, 67 lack of system notifications, 51 serialize() and deserialize() need for accessibility and usability, 53 methods, 63 performance drawbacks, 52 web services, 82 Display Suite, 51 Drupal Deploy ecosystem, 91–92, 203 Distributed denial-of-service (DDoS) Drupal ecosystem, 81 attacks, 77 Drupal front end Document object model (DOM), 24 decoupled blocks, 471–473 Drupal, 12, 467 progressive decoupling, 471 administrative interface, 478 shared rendering, 474 community, 12 shared routing, 474 custom modules (see Custom modules) shared templating, 474 decoupling by design, 476–478 universal editing, 470 distributions, 269 Drupal iOS SDK, 299 editorial experience, 469 Drupalisms, 12 end-user experience, 469 Drupal-powered interface, 471 front end, 468 drupalSettings, 38 preprocess functions, 468 Drupal web services ecosystem, 81 shared routing, 475–476 dummy APIs, 449 installation profiles, 477 Dynamic HTML (DHTML), 4 new incongruity, 468 dynamic pages, 22 484 INDEX E Flux, 314 Flux architectural approach, 314 ECMAScript 6 (ES6), 27, 472 Fully decoupled Drupal, 31–32, 40 Electron, 28 Elm, 466 Ember, 399, 466 G adapters, 411–412 Generated API documentation, 449 customization, 413 Generated code, 452 JSONAPIAdapter, 411, 415 GET request, 146 components, 406–409 core REST, 146–147 ecosystem, 400–401 GraphQL, 239 JSONAPIAdapter, 412 JSON API, 184 launching a local server, 403 JSON-RPC, 432–433 models, 410–411 RELAXed Web Services, 207 retrieving data from Drupal, 412–413 Schemata module, 447 route handlers, 404, 412–413 Subrequests, 437 routes, 404–406 Views REST exports, 178 scaffolding, 401, 403 Graphical user interface (GUI), 14 templates, 403–404 GraphiQL, 108, 239 Ember CLI, 400 keyboard shortcuts, 240 installation, 401 GraphQL, 18, 98, 239 Ember Data, 400, 410 aliases, 243–244 ember-drupal-waterwheel, 300 condition groups, 256, 262–263 installation, 301 directives, 105–106 Ember FastBoot, 300, 401 filter operators, 255 Ember Inspector, 401 fragments, 103–105, 244 Entity Access system, 67 GET requests, 239 Entity Query API module, 285 limitations in typical RESTful Entity resolvers, 64 architectures, 98, 100 Expo CLI, 336 module, 107–108 installation, 336 motivations, 98, 100 Extensible Markup Language (XML), 15 mutations, 106–107, 263–264 permissions, 239 queries and mutations, 101 F retrieving entities, 239 Fielding constraints, 16–18 entity collections, 247–249 File Transfer Protocol (FTP), 4 entityLabel field, 240 Filtering entity collections, 255 entityOwner field, 243 485 INDEX GraphQL (cont.) Installation profiles, 477 filtering entity collections, 252 Internal Page Cache, 458 individual entities, 240 Internet of Things (IoT), 9 individual entities with Isomorphic JavaScript, see Universal relationships, 243 JavaScript sorting entity collections, 249, 251 J, K selection sets and fields, 101–103 JavaScript, 5, 23 variables, 105–106 JavaScript renaissance, 5–6 single-page applications (SPAs), 466 H universal JavaScript, 5 HAL+JSON format, 59 JavaScript Object Notation (JSON), 15 HAL+JSON normalization, 64 JavaScript renaissance, 23–24, 28 HAL module, 59 JavaScript-to-native frameworks, 6 HAL+JSON format, 59 jQuery, 24, 467 normalize() implementation, 64 JSON API, 18 Serialization API, 59 condition groups, 189 Handlebars, 403 creating resources, 195–198 Headless Lightning, 270, 279 DELETE requests, 200 installation, 280 deleting resources, 200 mission, 280 Drupal 8 implementation, 84 Headless software, 14 GET requests, 184 Hoodie, 97 JSON API, 200 HTTP Basic protocol, 114 module, 83, 88 authorization field, 114 module API HTTP/2 server push, 304 request headers and response Hydrant, see Waterwheel.js codes, 90–91 Hypermedia as the engine of application types, 89 state (HATEOAS), 17 URLs, 89–90 Hypertext Application pagination links and definitions, 186
Load more

Recommended publications
  • Joomla Vs Drupal - Website Content Management Systems]
    [JOOMLA VS DRUPAL - WEBSITE CONTENT MANAGEMENT SYSTEMS] Joomla or Drupal? CMS’s are generally used to manage and control a large, dynamic collection of Web material (HTML documents and their associated images). And yes, they can take the web maintenance person out of the picture, as clients can update their own content, as and when required There are numerous Web CMS (Content Management Systems), and each one can ether fall into Open Source or proprietary. The ones that tend to stand out from the crowd, or should I say those that are more commonly used by small website design agencies are Word Press, Joomla and Drupal. So which one do you choose as a customer, or do you leave this to your web developer? Generally speaking, Joomla has a cleaner and smoother user interface; on the other hand Drupal is more flexible. Drupal and Joomla developers could argue all day,, so I’m going to go in as a bipartisan developer. • For starters both are easy to install and deploy, and many hosting companies have a one click install for these. • Both have plenty of modules and extensions you can use. • Joomla has a lighter learning curve than Drupal. • Joomla support SSL logins and SSL pages. Drupal not known to support it. • Server resources utilization is more compared to drupal © 2009 www.visualwebz.com Seattle Web Development Company [JOOMLA VS DRUPAL - WEBSITE CONTENT MANAGEMENT SYSTEMS] Summary of Joomla & Drupal Features • Limited technical knowledge need to get started. • Short learning curve • Cannot integrate other scripts etc. to your site • Generally you cannot create high-end sites, without additional investment of time.
    [Show full text]
  • Building Online Content and Community with Drupal
    Collaborative Librarianship Volume 1 Issue 4 Article 10 2009 Building Online Content and Community with Drupal Gabrielle Wiersma University of Colorado at Boulder, [email protected] Follow this and additional works at: https://digitalcommons.du.edu/collaborativelibrarianship Part of the Collection Development and Management Commons Recommended Citation Wiersma, Gabrielle (2009) "Building Online Content and Community with Drupal," Collaborative Librarianship: Vol. 1 : Iss. 4 , Article 10. DOI: https://doi.org/10.29087/2009.1.4.10 Available at: https://digitalcommons.du.edu/collaborativelibrarianship/vol1/iss4/10 This Review is brought to you for free and open access by Digital Commons @ DU. It has been accepted for inclusion in Collaborative Librarianship by an authorized editor of Digital Commons @ DU. For more information, please contact [email protected],[email protected]. Wiersma: Building Online Content and Community with Drupal Building Online Content and Community with Drupal Gabrielle Wiersma ([email protected]) Engineering Research and Instruction Librarian, University of Colorado at Boulder Libraries use content management systems Additionally, all users are allowed to post in order to create, manage, edit, and publish content without using code, which enables content on the Web more efficiently. Drupal less tech savvy users to contribute content (drupal.org), one such Web-based content just as easily as their more proficient coun- management system, is unique because it terparts. For example, a library could use employs a bottom-up strategy for Web de- Drupal to allow library staff to view and sign that separates the content of the site edit the library Web site, blog, and staff from the formatting which means that “you intranet.
    [Show full text]
  • Program Details
    Home Program Hotel Be an Exhibitor Be a Sponsor Review Committee Press Room Past Events Contact Us Program Details Monday, November 3, 2014 08:30-10:00 MORNING TUTORIALS Track 1: An Introduction to Writing Systems & Unicode Presenter: This tutorial will provide you with a good understanding of the many unique characteristics of non-Latin Richard Ishida writing systems, and illustrate the problems involved in implementing such scripts in products. It does not Internationalization provide detailed coding advice, but does provide the essential background information you need to Activity Lead, W3C understand the fundamental issues related to Unicode deployment, across a wide range of scripts. It has proved to be an excellent orientation for newcomers to the conference, providing the background needed to assist understanding of the other talks! The tutorial goes beyond encoding issues to discuss characteristics related to input of ideographs, combining characters, context-dependent shape variation, text direction, vowel signs, ligatures, punctuation, wrapping and editing, font issues, sorting and indexing, keyboards, and more. The concepts are introduced through the use of examples from Chinese, Japanese, Korean, Arabic, Hebrew, Thai, Hindi/Tamil, Russian and Greek. While the tutorial is perfectly accessible to beginners, it has also attracted very good reviews from people at an intermediate and advanced level, due to the breadth of scripts discussed. No prior knowledge is needed. Presenters: Track 2: Localization Workshop Daniel Goldschmidt Two highly experienced industry experts will illuminate the basics of localization for session participants Sr. International over the course of three one-hour blocks. This instruction is particularly oriented to participants who are Program Manager, new to localization.
    [Show full text]
  • Desarrollo De Una Aplicación Web De Gestión Colaborativa Para Un Club De Triatlón
    Escola Tècnica Superior d’Enginyeria Informàtica Universitat Politècnica de València Desarrollo de una aplicación web de gestión colaborativa para un club de triatlón Trabajo Fin de Grado Grado en Ingeniería Informática Autor: Jose Enrique Pérez Rubio Tutor/a: Manuela Albert Albiol Victoria Torres Bosch 2016 - 2017 Desarrollo de una aplicación web de gestión colaborativa para un club de triatlón 2 Resumen Se ha desarrollado una intranet para sustituir el actual método de contacto y navegación de los usuarios el cual es un foro. La nueva aplicación cuenta con más funcionalidades que no estaban disponibles anteriormente. La página web está desarrollada en web2py, un framework de Python. Como patrón de diseño para la implementación se utilizará el conocido Modelo Vista Controlador (MVC), arquitectura estándar hoy en día el cual separa los datos y la lógica de las vistas del usuario. Este diseño facilita el desarrollo y mantenimiento de las aplicaciones. Palabras clave: triatlón, intranet, web2py, framework, Python. MCV Abstract This Intranet has been developed to replace the current users contact and navigation method, nowadays it is a forum. The new application has more functionality than previously available. This web page is developed in Python web2py’s framework. As design for the implementation we'll be using the Model View Controller (MVC), standard architecture because it separates the data and the logic from user's view. This design improves the development and maintenance of applications. Keywords: triathlon, intranet, web2py, framework, Python, MVC 3 Desarrollo de una aplicación web de gestión colaborativa para un club de triatlón Agradecimientos Antes de nada, me gustaría dar las gracias a: Mis padres, por alentarme a continuar mi educación y han trabajado siempre muy duro para poder brindarme la oportunidad que ellos nunca tuvieron para poder continuar mis estudios.
    [Show full text]
  • Dotnetnuke Remote Code Execution Vulnerability Cve®1-2017-9822
    DOTNETNUKE REMOTE CODE EXECUTION VULNERABILITY CVE®1-2017-9822 DISCUSSION DotNetNuke®2 (DNN), also known as DNN Evoq and DNN Evoq Engage, is a web-based Content Management System (CMS) developed on the Microsoft®3 .NET framework. DNN is a web application commonly deployed on local or cloud Microsoft Internet Information Service (IIS) servers. On July 7, 2017, security researchers revealed a vulnerability within DNN versions 5.2.0 through 9.1.0 that allows an attacker to forge valid DNN credentials and execute arbitrary commands on DNN web servers. Web-based applications, such as DNN, can be overlooked in routine patching since vulnerability scans may be unaware of their presence. Furthermore, administrators often postpone major version updates to web applications due to the frequent user impact and incompatibility with customized features. Web applications are a frequent target for attackers and vulnerabilities can be exploited days or even hours after their release. For this reason, configuring web applications to update automatically is imperative to secure web application servers. There are many web-based CMSs similar to DNN. Other common CMS’s are WordPress®4, Drupal®5 and Joomla®6. Organizations should be aware of CMS instances within their purview (i.e., blog, wiki, etc.) and ensure adequate processes are in place for timely updates. MITIGATION ACTIONS The most effective mitigation action is to update to the latest version of DNN, version 9.1.1, which is not vulnerable. A hotfix is available at dnnsoftware.com for older versions of DNN, but NSA recommends to only use the hotfix as a temporary measure while migrating to the latest version.
    [Show full text]
  • The Drupal Decision
    The Drupal Decision Stephen Sanzo | Director of Marketing and Business Development | Isovera [email protected] www.isovera.com Agenda 6 Open Source 6 The Big Three 6 Why Drupal? 6 Overview 6 Features 6 Examples 6 Under the Hood 6 Questions (non-technical, please) Open Source Software “Let the code be available to all!” 6 Software that is available in source code form for which the source code and certain other rights normally reserved for copyright holders are provided under a software license that permits users to study, change, and improve the software. 6 Adoption of open-source software models has resulted in savings of about $60 billion per year to consumers. http://en.wikipedia.org/wiki/Open-source_software www.isovera.com Open Source Software However… Open source doesn't just mean access to the source code. The distribution terms of open-source software must comply criteria established by the Open Source Initiative. http://www.opensource.org/docs/osd www.isovera.com Open Source Software Free as in… Not this… www.isovera.com Open Source CMS Advantages for Open Source CMS 6 No licensing fees - allows you to obtain enterprise quality software at little to no cost 6 Vendor flexibility - you can choose whether or not you want to hire a vendor to help you customize, implement, and support it, or do this internally. If at any point along the way you decide you don’t like your vendor, you are free to find another. 6 Software flexibility – in many cases, proprietary software is slow to react to the markets needs.
    [Show full text]
  • Open Source Content Management Software's Joomla and Drupal
    Open Source Content Management Software’s Joomla and Drupal: A Comparative Study Subhankar Ray Chowdhury Abstract: Content management is an effective tool for creating, collecting, organising and retrieving electronic document as well as web resources. Content management system can provide us various types’ web-based information service. At present open source is a popular choice in the field of Library and Information science. This paper covers two open source content management software i.e. Joomla and Drupal with their technical requirements, features, functions, service, importance etc. This paper will also give a complete overview about content management system with its advantage and need in organisation and dissemination of information in the library. Key Words: Content Management Software’s, Joomla, Drupal, comparative study Introduction: In today’s world library users are became more web savvy for the availability of internet. For that user expectations have also changed from traditional document to web based or e-documents. Now user’s wants training videos, presentations, white paper, scholarly article and much more. Blogs, wikis, social networking sites, twitter, RSS and other tools included as web 2.0 technologies have transformed the way content is created, developed, managed and shared. In recent time information in any form is typically referred to as content or digital content. Content management system is an effective tool for content or resource sharing. Libraries have also adopted these new technologies to provide services among all user groups. With the help of these content management systems libraries can collaboratively produce, share and disseminate information to the users. Along with that libraries can also create and develop a web site for their own.
    [Show full text]
  • Magento Vs Drupal Vs Joomla Vs Wordpress: a Comparison Here, We Are Going to Compare 4 Major Content Management Systems Available in the Market for Free
    Magento vs Drupal vs Joomla vs WordPress: A Comparison Here, we are going to compare 4 major content Management Systems available in the market for free. Now, since we are in the market ourselves and our team is also one that has a lot of experience in many different technologies, we think that the key point is that there is no one CMS that is better than another. It just depends on your situation and what is that you are trying to do with your website. And if you are looking for a Content Management System (CMS) to build your website, it’s highly possible that you have come across WordPress, Joomla, Drupal and Magento along with a few others during your due diligence. These are the four main software programs used to create websites and all have their pros and cons. But again, it all comes down to what your goals are and what kind of features you are trying to implement in your website. In this post, we’ll compare the programs to give you a stronger idea. What is a CMS? CMS is just an acronym for Content Management System. A Content Management System is a program that helps you manage a lot of content. For an instance, if you want to create a blog or just a website to showcase your products or services, you could use a CMS without having any extensive knowledge about coding and still be able to give the general public a user friendly and an easy-to-use website. Magento, Drupal, Joomla and WordPress are a clean fit to these needs.
    [Show full text]
  • Drupal 8 User Guide Drupal 8 User Guide Table of Contents I
    Drupal 8 User Guide Drupal 8 User Guide Table of Contents i. Preface ...................................................................................................................................... vi i.1. Copyright ....................................................................................................................... vi i.2. Audience and Goal ....................................................................................................... vi i.3. Organization ................................................................................................................. vii i.4. Reporting Problems .................................................................................................... viii i.5. Conventions of the Guide ............................................................................................ ix i.6. Guiding Scenario ........................................................................................................... xi 1. Understanding Drupal ............................................................................................................ 1 1.1. Concept: Drupal as a Content Management System ............................................... 1 1.2. Concept: Modules ......................................................................................................... 3 1.3. Concept: Themes .......................................................................................................... 4 1.4. Concept: Distributions ................................................................................................
    [Show full text]
  • How to Do a Performance Audit of Your .NET Website
    WEB CMS MIGRATION HANDBOOK Of all the tasks that make up a content management system (CMS) implementation, there’s one that’s invariably underestimated, under budgeted, unscheduled, or even outright forgotten: content migration. If you’re implementing a new CMS, then you often have content—text and files—in your existing CMS system which has to be moved before you can launch. When someone builds a new house, they never forget that they have to move all their furniture from their existing house. However, when an organization builds a new website, it’s somehow all too easy to think that the content magically makes its way to the new CMS. Sadly, it’s never that simple. When planning for a migration, the content manager has to answer three fundamental questions: The Editorial Question: what content needs to migrate? 3 The Functional Question: how will content 5 in the existing system be managed in the new system? The Technical Question: how will the actual bytes 8 of content be exported from the existing system and imported to the new system? Answering these three questions are the core of any successful migration. 2 Web CMS Migration Handbook THE EDITORIAL QUESTION: WHAT CONTENT TO MIGRATE? Fundamental to any migration project is to determine what content is migrating. Remember, the easiest content to migrate is content you discard. That may seem flippant, but there’s almost invariably a chunk of content in any CMS that’s no longer necessary. This is content that’s redundant, outdated, or trivial. Any content migration should start with a comprehensive audit of what content exists on the current site.
    [Show full text]
  • Web Design and Implementation
    Web design and implementation Web design • It’s another type of publishing – Your web site is you shop window –people will judge your company on it – Web publishing is no different from other types of publishing – Spelling, grammar, point size, broken links, incorrect captions – Social networking sites make this available to all • Get the domain name right – Inventive: business.com vs PlentyOfFish (dating site) • Design is important – But functionality more so – Integrate good design with backend databases • http://www.webpagesthatsuck.com – http://www.dokimos.org/ajff/ 2/14 Web design mistakes • Ego: Believing people care about you and your website – Why are they looking at your site? – What are they trying to do? – Do you help then achieve THEIR goals? • Can't figure out what your website is about in less than four seconds – http://www.genicap.com/Site/ • Contrast Contrast Contrast • Mystery Meat – Navigation you have to roll over – Zero intelligible content – http://www.osbrinkagency.com/ • Too much stuff – http://www.arngren.net/ 3/14 More Common mistakes • Huge images Useless Title Zero intelligible content • Distracting colour schemes Refuses to work with IE • Flashing gifs, scrolling text Only works with IE • Music Requires Flash • Unclear navigation Assumes screen size • Unreadable Assumes font size • Cluttered Contains errors www.webpagesthatsuck.com 4/14 Navigation • Navigation is important – Make the navigation clear – Three clicks maximum to get anywhere – Hard when Sainsbury’s have 25,000 line items – Consistent position/action
    [Show full text]
  • Technical Expertise
    www.ultantechnologies.com Technical Expertise Subject: Ultan Technologies Technical Expertise Author: Cathal Brady Date Published: 01/03/2016 Version Number: Version 1 www.ultantechnologies.com Contents 1 INTRODUCTION ..................................................................................................................... 1 2 .NET ....................................................................................................................................... 1 3 DATABASES ........................................................................................................................... 2 4 BIG DATA ............................................................................................................................... 2 5 JAVA ...................................................................................................................................... 3 6 PHP, RUBY, PYTHON .............................................................................................................. 3 7 FRONT END............................................................................................................................ 4 8 3RD PARTY INTEGRATION, APIs, PLUGINS ............................................................................. 4 9 CONTINUOUS INTEGRATION / BUILD AUTOMATION / VERSION CONTROL .......................... 4 10 MOBILE DEVELOPMENT ........................................................................................................ 5 11 CRM CUSTOMISATION .........................................................................................................
    [Show full text]