24 Matching Annotations
  1. Oct 2022
  2. Sep 2022
    1. For information architects and designers — The content model helps information architects and designers make sure that the page designs accommodate all the content types for the site and provides guidance on the bits of text and media that will be available for the page. At the same time, the content model needs to support the content, layout, and functionality portrayed in the designs. If captions are included in the layout, that must be captured in the model for an Image. If events must be sorted by date on a calendar, then Date has to be captured in a separate field and it has to be sortable data, not just text. Depending on the complexity of the site, a high-to-medium level of detail is usually sufficient for designers.

      question: What skills of information architecture are important for developers to learn?

    1. No-more Shopify theme editorNo “plug-and-play" install of Shopify appsDependency on developers or development agency

      cons of headless eComm - mostly focused on the shopify aspect, but goes inline with increased complexity

    1. Here are some of the major benefits associated with headless: Speed. Rolling out any new changes, new features, UI changes, business logic changes, promotions, cosmetic changes, is faster with headless. With a traditional architecture, small adjustments and minor tweaks to anything require testing major parts of the back-end to make sure everything is working properly. More customization and personalization. Headless grants maximum customization freedom across the board, which allows the freedom to create industry-leading, personalized brand experiences.The front-end is more accessible. Since front-end updates don’t have to be optimized for the back-end, they take less time to build and are cheaper to implement. Accessing, using, and updating the front-end no longer requires any advanced IT skills, so it’s easier to find people to do the job. You also no longer have to write JSPs to make cosmetic edits. You still can, but you can also use React and several other systems that are not usable under a traditional eCommerce model. Integration of non-web channels. Through the focused use of APIs, brands can create a coordinated, seamless, and personalized brand experience across all channels. Future platform changes are easy as well. If Google Glass takes off, or Tik Tok comes out with a shopping feature, a shopping experience can be quickly created and implemented without changing the back end. Just plug it into an API and start selling.  Saved time and money across IT. Front-end changes no longer require significant IT support, so you save developers time on cosmetic adjustments. Commerce apps can be created and implemented faster than monolithic eCommerce platforms. Quick changes to be made to the front or back-end, without disturbing your taking resources away from the other side. Room for experimentation. A headless structure allows your system to become much more open to experimentation. Marketers can test new designs without affecting the back-end. Developers can make changes and tests while customers are still making purchases. Brands can phase in innovations and prevent front-end errors in production environments.Performance. When you control the front-end, you control performance. Shopify not loading fast enough? Tough cookies. They own the front-end and the servers. Your headless React code not loading fast enough? Just write better code and boost server performance.Time to market. Businesses can swiftly introduce any and all front-end experiences with no back-end development required. Whether it’s reacting to a new trend, entering into a new device or channel, or adjusting to events like COVID-19, headless makes it as easy as possible. 
    1. The Cons of Headless Commerce While diversity and flexibility are great, there are a few cons to consider with headless commerce as well: Complexity: With headless, you’ll be responsible for more infrastructure, so it will be more complex. This isn’t quite like it used to be in the pre-Shopify era when you needed a large team to build and maintain the website. But it is not as simple as setting things up on one platform. That means you’ll need strong partners or a larger in-house tech team. Cost: A headless site will cost more to build, manage, and maintain. You will have multiple platforms playing different roles for the store. This increases platform costs as well as the effort to build and manage it. Growing Pains: Since this is a new development in the ecommerce world, there will naturally be growing pains attached to jumping into this type of solution. Integrations: Integrations are required for platforms to play nicely together on a headless site. As more tech platforms adopt this concept, this will become less of an issue. But for now, you will be limited to the platforms that currently support headless sites.
  3. Mar 2022
  4. Jan 2022
  5. Sep 2021
  6. Jun 2021
  7. May 2021
    1. When you separate your content repository “body” from its presentation layer “head,” it becomes a headless CMS. What truly makes a headless CMS better than a traditional CMS is its content-first approach with full APIs to access and display content in any way desired.
  8. Jan 2021
  9. Oct 2020
    1. I am going to start getting serious about headless WordPress development for my new website at jimgroom.net, inspired by Tom Woodward’s talk for #HeyPresstoConf20

      A lot of the posts I make to my WordPress site are done in a headless manner using the Micropub spec and the Micropub plugin with a huge wealth of Micropub clients.

  10. May 2020
    1. A pure headless CMS is different, because it offers no front-end capabilities at all, giving you full control of your customer experience via APIs. The CMS typically provides content managers with a presentation and channel agnostic way of managing content. It requires a front-end development team to manage the rest with the frameworks and tools they prefer: The content can be loaded by external applications which handle the content delivery to the client, meaning that the content can be (re-)used by multiple applications and channels (web, mobile app, audio guides, IOT).
    1. There is some confusion around what makes a headless CMS truly “headless”, as vendors use the term somewhat loosely to label their decoupled or hybrid CMS systems. But a true headless CMS is one that was built from the ground up to be API-first, not a full monolith CMS with APIs attached afterwards.