tinacms / tinasaurus Goto Github PK

Home Page: https://tinasaurus.vercel.app

JavaScript 80.28% CSS 3.98% MDX 15.74%

tinasaurus's Introduction

Quickstart With Tina

$ npm install && npm run tina

$ yarn && yarn tina

This will install dependencies and open the website in your browser.

Visit the CMS at http://localhost:3000/admin to start editing.

About

This website is built using Docusaurus 3 and TinaCMS.

Watch an overview of this project on YouTube.

Installation

$ npm install

$ yarn

Local Development

$ npm run tina

$ yarn tina

This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server. Go to the Tina Admin to start editing.

Build

$ npm run build

$ yarn build

This command generates static content into the build directory and can be served using any static contents hosting service.

Deployment

To deploy to production and support editing on your live website (at your-domain.com/admin), you can follow the steps from Tina's docs to get it running on TinaCloud.

tinasaurus's People

Contributors

Stargazers

Watchers

Forkers

thecoryroberts a-hest yarardogukan nahidtanvir atechadventurer ancoruby jsantiago611 vangalilea anastasiiaxfr beqa777 dbemakers zakirzhan maleksandrovgreencode markusahlstrand mouadbahri morris-mao tommyearly bjenhamin4alfredolvchenki mahmoud-mohasseb wiwa32 annitannenbaum holiber frankjmb mcuello17 kjeevan14 milantorok francois-dbag fazi-gondal ziigur nwesterlaken 1202design son923 camerastuffdevelopment facundobarquet fabiensabatie somfist geobehr emiluzelac karipuso et0and kyle-atienza julrichkieffer thejon07 ec25p5e ibrammanggara rajivsingha dakshika nowis808 hzz780 sriramsadineni tadhgconnolly om-gg ericx20 yongenaelf pouchlabs namnguyenthanhwork beni20 patrickkoevoetssogeti bnapora

tinasaurus's Issues

full detailed guide

i am making an aready template and i deleted the the default md files but tine repo not saying how to add tina step by step please add it
a guide for adding tinacms to exiting project

Error when building using next

Lemme start by saying this is a great project and thank you for the effort put forward!

However, was wondering if it's possible to build it using next build, and start it using next start? the reason being it allows an active server that keeps it in sync with the updated data on github etc... The current setup serves the docusaurus files, however it does not integrate instant syncing to updated content on github (because of lack of running server).

I attempted to do it however I received multiple type errors:

next build

 ▲ Next.js 14.2.5
  - Environments: .env

 ✓ Linting and checking validity of types
   Creating an optimized production build ...
   Disabled SWC as replacement for Babel because of custom Babel configuration "babel.config.js" https://nextjs.org/docs/messages/swc-disabled
Failed to compile.

./src/components/Hero/index.js
Module not found: Can't resolve '@docusaurus/Link'

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./src/components/Blocks/index.jsx
./src/pages/index.js

./src/components/Hero/index.js
Module not found: Can't resolve '@docusaurus/useDocusaurusContext'

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./src/components/Blocks/index.jsx
./src/pages/index.js

./src/pages/index.js
Module not found: Can't resolve '@theme/Layout'

https://nextjs.org/docs/messages/module-not-found

./src/pages/index.js
Module not found: Can't resolve '@docusaurus/useDocusaurusContext'

https://nextjs.org/docs/messages/module-not-found


> Build failed because of webpack errors```

Bug: Date picker field is broken and crashes (Tinasaurus)

Describe the issue that you're seeing. Any Loom videos or screenshots usually help a lot!

I'm using the base tinasaurus project. When editing a post of the blog and changing the Date field, behaviour is as follows:

When selecting a date, it shows required and Save is disabled:
When deleting the field content (Ctrl+A and Delete) and typing (e.g. s for september), the whole page crashes and we get a date value is not finite in DateTimeFormat.format():

Reproduction

https://github.com/tinacms/tinasaurus

Steps to reproduce

Clone the tinasaurus project, start it and edit the date field of a blog post (see above on what errors to expect).

System Info

System:
    OS: Windows 10 10.0.22621
    CPU: (16) x64 12th Gen Intel(R) Core(TM) i7-1260P
    Memory: 4.24 GB / 15.62 GB
  Binaries:
    Node: 18.16.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\_Source\docs\node_modules\.bin\yarn.CMD
    npm: 9.5.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22621.2215.0), Chromium (116.0.1938.62)
    Internet Explorer: 11.0.22621.1

Validations

Follow our Code of Conduct
Read the docs.
Check that there isn't already an issue that reports the same bug.

Bug - Adding tab component to rich text results in React error

Screenity.video.-.Jun.4.2024.3-53-07.PM.webm

how to add truncate marker using TinaCMS

I have been using truncate marker with Forestry and other CMS like below, Unfortunately, Tina does not allow saving

Tab is not showing rich text editor

Current behaviour:

Tabs Component is showing a rich text toolbar (can result in errors - tab components are expected as children)
Tab Component has only a text input

Expected behaviour:

Tabs Component is showing a text input with a Embed+ Button only
Tab Component shows a rich text toolbar, inclusive the Embed+ Button

Aufzeichnung.2023-05-02.134720.mp4

Bug: Cannot edit Tabs without crash

Hi, if I create a document, add a Tabs component, edit that, add a Tab component and click it, it crashes with the following error:

See the video attached:

2023-10-10.10-01-07.mp4

Docusaurus 3.0 + TinaCMS 1.5.28 not working

Hi, guys!

I'm struggling to create a build of Tinasaurus with the following setup:

Gitlab as git provider
MongoDB as database adapter
NextJS as backend
Self-hosted

After I run yarn build I get the following errors:

...
--------------------------

Module not found: Error: Can't resolve 'querystring' in '/home/julio/workspace/pt/mikado/decap-mikado-docs/node_modules/openid-client/lib/helpers'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "querystring": require.resolve("querystring-es3") }'
	- install 'querystring-es3'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "querystring": false }

--------------------------

Module not found: Error: Can't resolve 'http' in '/home/julio/workspace/pt/mikado/decap-mikado-docs/node_modules/openid-client/lib/helpers'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "http": require.resolve("stream-http") }'
	- install 'stream-http'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "http": false }

--------------------------

Module not found: Error: Can't resolve 'https' in '/home/julio/workspace/pt/mikado/decap-mikado-docs/node_modules/openid-client/lib/helpers'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "https": require.resolve("https-browserify") }'
	- install 'https-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "https": false }

--------------------------

Module not found: Error: Can't resolve 'crypto' in '/home/julio/workspace/pt/mikado/decap-mikado-docs/node_modules/scmp'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }'
	- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "crypto": false }

--------------------------

Module not found: Error: Can't resolve 'stream' in '/home/julio/workspace/pt/mikado/decap-mikado-docs/node_modules/socks/build/common'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
	- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "stream": false }

--------------------------

Module not found: Error: Can't resolve 'crypto' in '/home/julio/workspace/pt/mikado/decap-mikado-docs/node_modules/@tinacms/graphql/dist'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }'
	- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "crypto": false }

--------------------------

Attempted import error: 'fileURLToPath' is not exported from 'url' (imported as 'fileURLToPath').
error Command failed with exit code 1.

So, I solved this using a polyfill with Webpack, like this one (tinacms build works after this)

const webpack = require("webpack");
const NodePolyfillPlugin = require("node-polyfill-webpack-plugin");

module.exports = function (context, options) {
  return {
    name: "custom-docusaurus-webpack-config-plugin",
    configureWebpack(config, isServer, utils) {
      return {
        resolve: {
          fallback: {
            fs: isServer ? "fs" : false,
            dns: isServer ? "dns" : false,
            net: isServer ? "net" : false,
            tls: isServer ? "tls" : false,
            url: isServer ? "node:url" : "url",
          },
        },
        plugins: [
          new webpack.DefinePlugin({
            "process.versions.node": JSON.stringify(
              process.versions.node || "0.0.0"
            ),
          }),
          new NodePolyfillPlugin(),
        ],
      };
    },
  };
};

However, I have not been able to solve the last error:

Attempted import error: 'fileURLToPath' is not exported from 'url' (imported as 'fileURLToPath').
error Command failed with exit code 1.

Steps to reproduce:

Download tinasaurus project
Configure it with the setup given above
run yarn build

Do you guys have any idea? Please, let me know if you need more info. Thanks

docker

Looks like I am too stupid to create the most simple Docker.
Maybe you can help me somehow?

I would just like to run it to have a look

FROM node:20-bookworm

WORKDIR /app

COPY . .

RUN npm install

EXPOSE 3000
EXPOSE 80

CMD ["npm", "run", "tina"]

I run it with -p "80:80" -p "3000:3000" but nothing happens at localhost:3000, why is that?

Cannot open /admin page

I integrated the code on the repository in my existing docusaurus project.

Though i can build locally and serve and i get /admin page but when i go on to deploy on gh-page it does not work and shows 404 page. Help please.