We're proud to announce that Prismic has raised $20 million to change the way everyone builds websites.
This is a transcript of an (extremely technical but nonetheless interesting) conversation about Gatsby, Next.js, speed, SEO, caching, and other things between Sadek (the CEO of Prismic) and Gabe (a core engineer – at Prismic, too). Watch the video, or scan through the highlights below, or read the entire thing – or do none of these things. Do as you please.
Last week, our product designer, Renaud, sent some questions to our users asking for their help in planning our backlog. The results were amazing! I personally didn't expect these levels of quantity, quality and details in the feedback.
Companies and startups still fail at placing their website in the center of their communication and marketing. Despite their huge efforts to integrate unique up-to-date design and technology, their websites suffer from one fundamental problem: they are stagnant, right on the day of their release!
Ever wanted to know, for sure, whether short titles are more efficient than long ones? A data visualisation is more relevant than a funny kitten photo? Or whether you should use first, second or third person for a blog post or page? And while we're on it, do these vary with different types audiences and domains?
We started our journey with prismic.io to challenge the traditional content management approach. prismic.io is an entirely new way to bring websites or apps' content alive.
With prismic.io we want to achieve a product that helps every developer integrate content into their websites and apps, and every content writer experiment with and optimize their content ideas. We'll help adopting cutting edge technologies and designs in these websites and apps while presenting optimal, carefully crafted and updated content.
Content writers' experience with Content Management Systems has mostly varied from crossing their fingers any time they edit or publish content, to avoiding and minimizing the use of the CMS at any price, replacing it with more trustworthy tools, like word processors and even plain paper!
One of the challenges of creating a service for Content Management (Content Query API) is achieving and guaranteeing very low latency. Content is very central to an application or website. Basically you can't show the website if you have no content, and any latency in fetching content means a slow website.
A quick exploration of the world of Content Management reveals obvious limitations in current classical solutions — the disdained Content Management System. These limitations certainly present a great opportunity to fix things up, and reshape what modern Content Management should look like.
Last week, we successfully launched prismic.io, introducing several new concepts into the cluttered Content Management world (and breaking a bunch of assumptions about how to manage content). In the last few days since then, we've received loads of positive feedback, we're glad lots of hackers have a good grasp of the concepts. We've also been receiving plenty of very interesting questions.
Content is everywhere. When you are creating a website, a web application, a game or a native mobile app - big or small, you have to deal with content at some point. Which inevitably has you asking questions: where do I store content? How can I modify texts? Fix typos, evolve and expand my work?