https://vrm.dev/en/blog/ VRM Blog 2024-07-03T00:00:00.000Z https://github.com/jpmonette/feed VRM Blog https://vrm.dev/en/favicon.ico <![CDATA[202407]]> https://vrm.dev/en/blog/2024/07/03/ 2024-07-03T00:00:00.000Z blog と site をまとめてサイト管理に。

  • VRM-1.0 を UniVRM-1.0 に変更。一部 VRM 下に移動。
  • VRM Animation を VRM 下に移動。
  • VRM-1.0 の SpringBone の記事
]]> VRM consortium https://vrm.dev <![CDATA[開発ドキュメントの移動]]> https://vrm.dev/en/blog/2024/02/19/api/ 2024-02-19T00:00:00.000Z https://vrm-c.github.io/UniVRM/ のドキュメントを本サイトに移動しました。 おもに /api/ フォルダー配下になります。

今後はこちらで更新していきます。

]]> VRM consortium https://vrm.dev <![CDATA[About the English version URL]]> https://vrm.dev/en/blog/2024/01/17/english-url/ 2024-01-17T00:00:00.000Z We are working on updating the site from 2024-01-15.

A broken link occurred due to a change in the URL of the English version. We have modified it to use the original URL. You can now access it at the original URL.

vrm.dev.en

English version repository . English version will be deployed to https://vrm.dev/en/

The problem

Please let us know here

https://github.com/vrm-c/vrm.dev/issues

]]> VRM consortium https://vrm.dev <![CDATA[We have updated the site]]> https://vrm.dev/en/blog/2024/01/12/blog-post/ 2024-01-12T00:00:00.000Z We are working on updating the site from 2024-01-15.

The problem

Please let us know here

https://github.com/vrm-c/vrm.dev/issues

sphinx to docusaurus​

We changed the Document tool from sphinx to docusaurus.

https://github.com/vrm-c/vrm.dev/issues/315

updated: 2024-01-15​

  • We restore the order of sphinx toc articles
  • We recovered sphinx figure (screenshots etc.)
  • We restored sphinx admonition(info, warning...)

updated: 2024-01-16​

Updated list of applications that support VRM.

showcase

The registration method is here. We accept issues even if it is not a PullReq. If you have already registered, please feel free to change the wording.

updated: 2024-01-17​

Work on the change from Sphinx to Docusaurus is currently scheduled to be completed.

updated: 2024-01-19​

  • tailingSlash (Fixed URL compatibility)
]]> VRM consortium https://vrm.dev <![CDATA[対応Applicationの登録]]> https://vrm.dev/en/blog/2024/01/05/vrm_application/ 2024-01-05T00:00:00.000Z こちら

]]> <![CDATA[Site structure]]> https://vrm.dev/en/blog/2024/01/04/system/ 2024-01-04T00:00:00.000Z documents​
Inheriting sphinx markdown

It is inherited from the previous sphinx and previous hugo markdown articles.

/docs/**/*.md

pages​

/

React

/src/pages/index.ts

/showcase/​

VRM-enabled applications

React

/src/pages/showcase/index.tsx /src/data/tags.tsx /src/data/users.tsx

customize​

The language switching menu has been modified.

Swizzling | Docusaurus

https://github.com/vrm-c/vrm.dev/blob/master/src/theme/NavbarItem/LocaleDropdownNavbarItem/index.js

meta​

info

check English translation

title​

hard coding

  • /src/pages/index.tsx
`${metaTitle} | ${config.title} `;
  • /docusaurus.config.ts

(template)

description​

hard coding

  • /src/pages/index.tsx

image​

https://docusaurus.io/docs/api/themes/configuration#meta-image

docusaurus.config.js
epport default {
  themeConfig: {
    image: 'img/docusaurus.png',
  }
}
]]> <![CDATA[Build the site]]> https://vrm.dev/en/blog/2024/01/03/build/ 2024-01-03T00:00:00.000Z We are building with github-action.

https://github.com/vrm-c/vrm.dev/blob/master/.github/workflows/docusaurus.yml

  • build is triggered on master update of vrm.dev
  • TODO: How to trigger build if vrm.dev.en is updated

build sequence​

  • Build the vrm.dev => /build
  • Buidl the vrm.dev.en => build/en(master head)
  • Deploy the /build to gh-pages
]]> <![CDATA[Translation]]> https://vrm.dev/en/blog/2024/01/02/translation/ 2024-01-02T00:00:00.000Z We maintain separate docusaurus repositories for each language. The Japanese version is the original, and the English version is forked.

Changed sphinx's gettext method to fork method

Reference GitHub as an open source document translation platform (React Japanese documentation example)

Japnanese​

https://github.com/vrm-c/vrm.dev

Deploy the Japanese version to https://vrm.dev as the base site.

English​

https://github.com/vrm-c/vrm.dev.en

Deploy the English version to https://vrm.dev/en.

Build all at once with github-action

When building a Japanese site It is built in the /en directory.

英語版の反映方法

英語版を merge した 次回の日本語版 の github action でビルドされます。 即座に反映したい場合は、日本語版の reposity の Actions - Docusaurus - Run workflow ボタンを 手動で押してください(緑のボタン)。

action

Translation sequence​

  • The contents of vrm.dev are updated
  • Reflect updates in vrm.dev to vrm.dev.en (fetch merge and push). This task is performed regularly (weekly?) by the vrm.dev administrator.
    • Untranslated parts will increase
    • There may be a conflict, but if the docusaurus build passes, you can just commit. TODO: Automate
  • Translate untranslated parts into English or send an English update PullReq to vrm.dev.en

Example (on the github website)​

TODO:

Example (Local)​

Start preview​

$ git clone https://github.com/vrm-c/vrm.dev.en.git
$ git switch -c fix/EN_TOPIC # Please give a suitable and unique branch name
$ cd vrm.dev.en
$ npm install
$ npm run dev

# Access https://localhost:3000. View translated article.

Translate with editor​

Push pull request

Example (For administrators. Follow-up to Japanese)​

TODO: bot automation.

$ git clone https://github.com/vrm-c/vrm.dev.en.git
$ cd vrm.dev.en
$ git remote add ja https://github.com/vrm-c/vrm.dev

$ git switch -c merge/topic
$ git fetch ja master
$ git merge ja master
$ npm run build

# If there is an error, resolve the conflict and proceed with the build.
# If the build is transparent, you can commit the merge and proceed.

$ git commit
$ git push
]]> <![CDATA[Update articles]]> https://vrm.dev/en/blog/2024/01/01/contributing/ 2024-01-01T00:00:00.000Z How to send a pull request to vrm.dev​

Please submit a pull request for the markdown article here.

https://github.com/vrm-c/vrm.dev/pulls

How to send a pull request to vrm.dev.en​

Please submit a pull request here for an English translation of the markdown article.

https://github.com/vrm-c/vrm.dev.en/pulls

If you are confused between vrm.dev and vrm.dev.en, Please send it to vrm.dev.

]]>