Whether text is centered, right-aligned, or justified on Strapi, it's right aligned once published on the website. This makes it very difficult to add captions to images in the content.

(Enhancement) Being able to pin 3 posts to the top row on our blog pages would be helpful to highlight important content, such as our new Whitepapers.

To improve our SEO

The story.xyz is missing a robots.txt and sitemap.xml - let's add those to improve SEO

• https://story.xyz/robots.txt
• https://story.xyz/sitemap.xml

use values provided on Story.xyz - Page SEO CMS data for SEO and social share data on index and /blog pages.

A table of contents on Story and OP blogs will help us hit Keywords again within H2s/H3s.

Here's an example on the staging site: https://staging.ousd.com/litepaper

If this can automatically pick up H2s for headers and H3s as subheaders within the ToC that would be perfect. Alternatively I can manually add these sections in the CMS.

H3s show extremely similar to normal text. Prior to the font size being small, I still opted for H2s due to the spacing of H3s. Spacing between body text and H3s can be reduced for better readability and the size needs to be increased.

Example: https://www.story.xyz/how-to-value-NFTs

Fix on all 3 sites:

• story.xyz
• ousd.com
• originprotocol.com

The August token holder update in vietnamese is only viewable from the direct URL:
https://www.originprotocol.com/vi/bao-cao-thang-8-origin-protocol

The blog card shows here, but doesn't load when you click on it: https://www.originprotocol.com/vi/blog

• Edit “Latest Stories” to “NFT News” and switch from H3 to H1 on https://www.story.xyz/blog
• Add HSTS support

Google PageSpeed tool reports a low score for story.xyz on mobile.

It provides the following recommendation: "Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Use the next/image component instead of <img> to automatically lazy-load images."

Interestingly we are already using next/image and all images should be returned as webp and lazy loading is the default.
I confirmed it works on desktop. Perhaps there is something specific about mobile?

It would be good to try to run the exact same configuration as used by PageSpeed for their mobile testing to see if we can reproduce. Or perhaps the tool provides an incorrect performance optimization recommendation?

We need to add support for Twitter embeds and Youtube embeds. Some of our legacy Medium content is mostly just the embeds, so we're blocked on fully bringing that content over until we can support these embeds.

examples:

https://www.originprotocol.com/paypal-co-founder-discusses-strengths

https://www.originprotocol.com/ryan-kim-from-hashed-on-why-they-invested-in-origin