Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add mobile performance post #9106

Merged
merged 5 commits into from
Oct 16, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 12 additions & 4 deletions docs/blog/2018-10-10-unbundling-of-the-cms/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ tags: ["content-mesh"]

_This is Part 2 of a series. You may want to read Part 1:_ [Delivering Modern Website Experiences: The Journey to a Content Mesh](/blog/2018-10-04-journey-to-the-content-mesh).

Web users’ expectations follow a simple law: they always increase over time.
Web users’ expectations follow a simple law: they always increase over time.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe

User expectations follow a simple law: they always increase over time.

(The apostrophe is correct, I just don't usually like using it like that 😅 )

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also should've commented on this way sooner!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll probably leave this as is now :) I like using "Web" in this sentence.


Creating compelling web content experiences has become _crucial_ in the battlefield for customer loyalty. But you can’t get _fresh_, _novel_, and _engaging_, without up-to-date content and development architectures.

Expand All @@ -25,7 +25,7 @@ But creating compelling experiences is challenging:

When compared with purpose-built CMSs like Shopify for e-commerce or Wordpress for blogging, enterprise CMS applications like Sitecore, Evoq or Adobe Experience Manager (AEM) provide generic content modules.

The enterprise CMS core development experience experiences are based in C#, ASP.NET, and J2EE -- languages and frameworks a decade out of date for frontend development. Add-ons are expensive and are difficult-to-use compared to pure-play alternatives.
The enterprise CMS core development experiences are based in C#, ASP.NET, and J2EE -- languages and frameworks a decade out of date for frontend development. Add-ons are expensive and are difficult-to-use compared to pure-play alternatives.

Best-of-breed products have emerged to provide top-notch alternatives in each of these areas, but have been difficult to integrate.

Expand All @@ -48,11 +48,19 @@ With these solutions available, customers can pick vendors _à la carte_. The co

Enterprises who have purchased these CMS solutions are left asking themselves one of the oldest questions in corporate IT: should they stick with their single-vendor application suite, with inferior but integrated modules? Or, unlock a way to integrate the best-of-breed solutions?

Over the next three posts, we’ll discuss the rise of a content mesh that makes integration _feasible_ for most digital agencies and enterprise customers.

<figure>
<img alt="The modularization of the CMS" height="400" src="./headless-cms-landscape.png" />
<figcaption>
The headless CMS landscape
</figcaption>
</figure>

## Making integration feasible via a content mesh

Over the next three posts, we’ll discuss the rise of a content mesh that makes integration _feasible_ for most digital agencies and enterprise customers.

The next post, [The Rise of Modern Web Development](/blog/2018-10-11-rise-of-modern-web-development), discusses the development side -- how frameworks that increase development speed and reduce bugs have become ubiquitous.

After that, [Why Mobile Performance is Crucial](/blog/2018-10-16-why-mobile-performance-is-crucial) discusses the rise of e-commerce on smartphones, why the average site haven't been getting any faster on mobile, and existing technology that can make sites fast _by default_.

Finally, in our conclusion, Creating Compelling Experiences, we’ll discuss a step-by-step approach for choosing a content architecture, modern development environment, a performance strategy -- and most importantly, choosing an "content mesh" that makes all the other choices easy.
6 changes: 3 additions & 3 deletions docs/blog/2018-10-11-rise-of-modern-web-development/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,8 +55,8 @@ React and Angular, along with mature ES2015+ JavaScript, and stable dependency/b
While React and Angular were originally created as web _app_ solutions, with the rise of the headless CMS, usage of React and Angular on _websites_ has skyrocketed, growing 5-10X since early 2017.

<date-chart
title="React and Angular usage"
y-axis-label="% of top 10,000 sites"
title="React and Angular usage among top 10k sites"
y-axis-label="% of top 10k sites"
series-data='[{ "name": "React", "data": [{ "date": "2017/01", "value": "0.0170"}, { "date": "2017/04", "value": "0.0223"}, { "date": "2017/06", "value": "0.0251"}, { "date": "2017/08", "value": "0.0283"}, { "date": "2018/01", "value": "0.0538"}, { "date": "2018/08", "value": "0.0738"}] },{ "name": "Angular", "data": [{ "date": "2017/06", "value": "0.0001"}, { "date": "2017/08", "value": "0.0007"}, { "date": "2018/01", "value": "0.0018"}, { "date": "2018/08", "value": "0.0184"}] }]'>
</date-chart>

Expand All @@ -82,6 +82,6 @@ Modern web development frameworks like React and Angular are the latest step tra
</figcaption>
</figure>

In the next blog post, Why Mobile Performance is Crucial, we’ll move on to the final piece of the changing content landscape puzzle.
In the next blog post, [Why Mobile Performance is Crucial](/blog/2018-10-16-why-mobile-performance-is-crucial), we’ll move on to the final piece of the changing content landscape puzzle.

We'll discuss how growing smartphone usage both in the US and globally has made mobile performance crucial -- as well as suddenly easier to optimize in the Headless CMS world. We’ll also explore two modern, complementary trends for improving web performance and how website teams can get the best of both out of the box.
Loading