Find out how Content Security Policy can protect your websites from malicious attacks. Cross-Site Scripting exploits vulnerabilities in CMS architecture—but with the right security policy, you can keep your websites safe.
b13 Blog
Sharing what we’ve learned while delivering client projects online for more than 20 years and being leading contributors to TYPO3 is part of who we are.
We choose widely-adopted open-source technologies because we can fix, extend, and improve them while building on the experience and support of thousands of our peers. In our blog, we share with you the knowledge we’ve gained along the way for you to build on.
Read on!
Categories TYPO3
Unlock TYPO3 v12’s enhanced TCA types. Improvements to the Table Configuration Array introduce streamlined code and simply work for integrators and extension authors.
Choosing an agency is difficult, but once you’ve gone through your project’s concept document, and gained an understanding of your agency’s technical expertise and proposals, the process becomes more straightforward. At that point, you’ve kicked off your partnership and are looking forward to shared success. Before getting too deep into the details, however, you should have a work plan for what gets tackled first. And while it’s natural to get caught up in the excitement of a new project, a thorough agency will take care of the basics first: important housework tends to be critical to the success of any project.
Whether you’re launching a brand new project or upgrading your decades-old multisite website, you need to make sure your agency fully understands your project goals and your current suite of technology. In our recent post, “How we kick off TYPO3 projects for enterprises,” we explained why you should expect a Concept Document before your agency begins writing a single line of code. But say your agency has come to you with a set of suggestions for your CMS, integrations, and extensions—at that point, an obvious question comes up: how do I know that this is the right technology?
TYPO3 is an open source CMS used widely across Europe, but it is still surprisingly little known in some regions. Built for international, multiregional, distributed, and multilingual organizations, TYPO3 is an accessible CMS for users around the world. In this article, we’ll walk you through the strengths of this CMS and why you should consider it alongside other popular solutions like Sitecore, Drupal, and WordPress.
While external teams will upgrade your ability to make updates and extend functionality for your customers, integrating them effectively is a challenge because code can quickly become opaque, buggy, and brittle. Our standard processes leverage automation, version control tools, virtualization, and standardized best practices to make sure everyone not only tugs on the same rope, but—crucially—in the same direction.
In an ever-evolving technological landscape, keeping your brand and technology up-to-date and competitive can feel like a full-time job. Whether you’re working on a website relaunch, a brand refresh, or a system-wide version update, it’s going to be time-consuming and expensive, not to mention repetitive. When your focus turns instead to future-proofing your website, you ensure your design and technology are ready for anything, now and for the long-term.
Enterprises now have many software delivery channel options to choose from. With software-as-a-service (SaaS) and cloud-based implementation models on the rise, you might be trying to figure out the best software delivery channel to support your enterprise’s digital strategy. If you don’t have an internal IT department, SaaS can be tempting, but when you also have stringent data compliance needs, an on-premises (or on-prem for short) solution is your best bet.
TYPO3’s separation of content and code is one of its major strengths. TYPO3 saves content in containers called content elements, which you can stack in content areas on a page record to create pages. The different parts of this highly configurable setup include “page types” (defined by the “doktype” field value in the pages database table record), a “backend layout” configuration, and possibly a third, separate “frontend layout” configuration value. We combine these components in various ways to enable different scenarios and desired outcomes.
In previous installments of our TYPO3 v11 series, we covered some of the great UX improvements that are making editors‘ lives easier. In this final post of the series, we’ve got something special for all the developers and site administrators: new TCA types. Using these dedicated types will reduce and simplify the TCA configuration required for special fields. They also allow auto-configuration and auto-creation of database fields.