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

blog wordpress-wpengine (PR from TinaCMS) #2365

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

tina-cloud-app[bot]
Copy link
Contributor

No description provided.

Copy link

vercel bot commented Oct 24, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
tina-io ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 24, 2024 5:34am

@landonmaxwell landonmaxwell marked this pull request as ready for review October 24, 2024 05:35
Comment on lines +34 to +38
***

#### How to Migrate from WordPress to TinaCMS

Transitioning from WordPress to TinaCMS doesn’t have to be complicated. With TinaCMS’s headless and Git-first approach, migrating your content and code can be done in a few steps. To learn more about the migration process, check out our step-by-step guide on how to migrate from WordPress to TinaCMS.
Copy link
Member

@bradystroud bradystroud Oct 28, 2024

Choose a reason for hiding this comment

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

Feels like this should link somewhere...
For now we could comment it out and get this blog live without it

Copy link
Contributor

Choose a reason for hiding this comment

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

Afaik that guide doesn't exist?

Copy link
Member

Choose a reason for hiding this comment

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

Does this exist now?

Comment on lines +24 to +28
1. Git-First Content Management: In WordPress, content is typically stored in a database, while TinaCMS keeps everything in sync with your Git repository. This means you always own your own content - it will never be stuck in a database you can't access! This makes it easy to version control your content alongside your code, bringing transparency and simplifying collaboration. If you're currently using WordPress or hosting your site with WP Engine, TinaCMS’s Git-first approach offers a more developer-friendly experience.
2. Headless CMS for Flexibility: TinaCMS gives you full control over how your content is displayed. This headless architecture allows you to integrate your CMS with any frontend framework, whether it's React, Vue, or Next.js. For those moving from WordPress or a managed WordPress host like WP Engine, this gives you to better performance, scalability, and frontend customization.
3. A Better Developer Experience: While WordPress relies on PHP, TinaCMS leverages modern JavaScript frameworks like React. This provides a more intuitive development experience for teams that prefer working within the JavaScript ecosystem. If you’re developing on platforms like WP Engine but want to shift to a more JavaScript-focused stack, TinaCMS offers a modern approach without the complexities often associated with traditional CMS platforms.
4. Simplified Content Management: WordPress offers a vast array of plugins and features, but this can sometimes lead to site bloat and maintenance overhead. TinaCMS, on the other hand, provides a streamlined, lightweight solution that keeps your setup clean and focused. This is particularly attractive for developers looking to avoid the complexity of managing plugins and customizations on platforms like WP Engine. TinaCMS also uses Markdown, which is easy to use and great for quick formatting and documentation.
5. Freedom from Platform Lock-in: Unlike WordPress, which is often tied to specific hosting solutions like WP Engine, TinaCMS is fully hosting-agnostic. Its Git-backed architecture ensures that your content and code remain portable, giving you the freedom to choose the best infrastructure for your project without being locked into a particular platform.
Copy link
Member

Choose a reason for hiding this comment

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

I feel like all these should be links to feature pages

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants