Squashed commit of the following:

commit 4aaa79a Author: SASAKI Kaoru <[email protected]> Date: Mon Jan 20 17:07:28 2025 +0900 Miyabi の追加他 (#1371) * Miyabi 追加他 (#1368) * Miyabi 追加他 (#68) * サポートに Mecrosoft Cpilot を追加：Update index.mdx * Miyabi の追加と Wisteria の修正：Update index.mdx * Update mdx/index.mdx * 少し修正：Update index.mdx --------- Co-authored-by: Shigeru Chiba <[email protected]> * 東大初かどうかは不明なので削除 (#1370) * Miyabi 追加他 (#68) * サポートに Mecrosoft Cpilot を追加：Update index.mdx * Miyabi の追加と Wisteria の修正：Update index.mdx * Update mdx/index.mdx * 少し修正：Update index.mdx * + タ：Update index.mdx * 東大初かどうかは不明なので削除：Update index.mdx --------- Co-authored-by: Shigeru Chiba <[email protected]> --------- Co-authored-by: Shigeru Chiba <[email protected]> commit abe8c58 Author: SASAKI Kaoru <[email protected]> Date: Mon Jan 20 14:46:16 2025 +0900 タ (#1369) * Miyabi 追加他 (#68) * サポートに Mecrosoft Cpilot を追加：Update index.mdx * Miyabi の追加と Wisteria の修正：Update index.mdx * Update mdx/index.mdx * 少し修正：Update index.mdx * + タ：Update index.mdx --------- Co-authored-by: Shigeru Chiba <[email protected]> commit d75cc60 Author: 並木　登美幸 <[email protected]> Date: Fri Jan 17 14:49:52 2025 +0900 Update index.md slide replacement commit b77d7fc Author: 並木　登美幸 <[email protected]> Date: Fri Jan 17 13:59:00 2025 +0900 Update index.md slide replacement commit 1fd0895 Author: 並木　登美幸 <[email protected]> Date: Fri Jan 17 13:46:00 2025 +0900 Add files via upload commit 0b1baca Author: riktake <[email protected]> Date: Fri Jan 17 09:25:50 2025 +0900 Update notice.yml 2025Sセメスターコモンサポータ募集のお知らせを追加 commit 2664261 Merge: 367342a 62e8bd3 Author: utsakai <[email protected]> Date: Thu Jan 16 16:30:43 2025 +0900 Merge pull request #1363 from utelecon/course-application-form-update Update course application form url commit 367342a Author: riktake <[email protected]> Date: Thu Jan 16 13:05:59 2025 +0900 Create 0117-cs.md　2025Sセメスター募集要項掲載のためファイルとフォルダを追加 commit ddfb7ea Merge: 5d77f66 b84a747 Author: jtamatsukuri <[email protected]> Date: Thu Jan 16 12:37:14 2025 +0900 Merge pull request #1362 from utelecon/printing Add printing css commit 62e8bd3 Author: femshima <[email protected]> Date: Thu Jan 16 09:24:19 2025 +0900 update course application form url commit b84a747 Author: femshima <[email protected]> Date: Thu Jan 16 07:13:49 2025 +0900 add printing css commit 5d77f66 Author: SASAKI Kaoru <[email protected]> Date: Tue Jan 14 17:08:28 2025 +0900 （英）複数人グループの更新他 (#1360) (#1361) * 英：年末年始休業お知らせの削除：Update index.mdx * 年末年始休業お知らせの削除：Update index.mdx * AIサービスを利用終了した際のVM停止や削除 (#64) * 申請後のステータスに承認待ちがあるので追加：date subscription.mdx * 利用終了時の停止や削除について：Update azureai.mdx * Update index.mdx * Update deploy.mdx * Update index.mdx * （英）複数人グループの更新 (#67) * Rename index.mdx to _index.mdx * （英）複数人グループの更新：Create index.mdx * 画像リンク修正：Update index.mdx * Update index.mdx * Update index.mdx * タイトル追加：Update index.mdx * タイトル修正：Update python.mdx * タイトル修正：Update quota.mdx --------- Co-authored-by: Shigeru Chiba <[email protected]> commit 5b0a007 Author: jtamatsukuri <[email protected]> Date: Tue Jan 14 09:32:53 2025 +0900 Update index.md commit f95967c Author: SASAKI Kaoru <[email protected]> Date: Fri Jan 10 15:07:04 2025 +0900 AIサービスを利用終了した際のVM停止や削除 (#1356) (#1357) * 英：年末年始休業お知らせの削除：Update index.mdx * 年末年始休業お知らせの削除：Update index.mdx * AIサービスを利用終了した際のVM停止や削除 (#64) * 申請後のステータスに承認待ちがあるので追加：date subscription.mdx * 利用終了時の停止や削除について：Update azureai.mdx commit 0a519b2 Merge: e91fd90 b0b9864 Author: nninomiya <[email protected]> Date: Thu Jan 9 08:58:41 2025 +0900 Merge pull request #1336 from utelecon/202412-utol-assignments-en add: `/en/utol/lecturers/assignments/` commit e91fd90 Merge: a7fdcc6 a862a64 Author: riktake <[email protected]> Date: Tue Jan 7 19:51:39 2025 +0900 Merge pull request #1355 from utelecon/20250107-fix-open-hour fix: 20250107 サポート窓口年末年始休業日の表示を削除 commit a862a64 Author: Masaya Takahashi <[email protected]> Date: Tue Jan 7 19:08:50 2025 +0900 fix: restore open hour commit 3741eed Author: Masaya Takahashi <[email protected]> Date: Tue Jan 7 19:07:41 2025 +0900 fix: restore standard open hour commit a7fdcc6 Merge: 61f84f4 86ef30e Author: jtamatsukuri <[email protected]> Date: Tue Jan 7 08:36:00 2025 +0900 Merge pull request #1352 from utelecon/202501-docs-sns add sns-policy to /docs/ commit 61f84f4 Merge: f52e85a f329919 Author: utsakai <[email protected]> Date: Mon Jan 6 10:31:29 2025 +0900 Merge pull request #1349 from utelecon/202412-utol-assignments-fix Update: `/utol/lecturers/assignments` commit f52e85a Author: SASAKI Kaoru <[email protected]> Date: Mon Jan 6 09:18:23 2025 +0900 年末年始休業お知らせの削除 (#1353) (#1354) * 英：年末年始休業お知らせの削除：Update index.mdx * 年末年始休業お知らせの削除：Update index.mdx commit 86ef30e Author: syobonpastel <[email protected]> Date: Sun Jan 5 15:44:15 2025 +0900 add commit f329919 Author: syobonpastel <[email protected]> Date: Sat Jan 4 21:41:18 2025 +0900 fix commit b0b9864 Author: syobonpastel <[email protected]> Date: Sat Jan 4 21:11:27 2025 +0900 fix commit a2780be Author: syobon <[email protected]> Date: Sat Jan 4 21:09:48 2025 +0900 Update src/pages/en/utol/lecturers/assignments/index.mdx Co-authored-by: phenylshima <[email protected]> commit d2c8a05 Author: syobon <[email protected]> Date: Sat Jan 4 21:06:42 2025 +0900 Apply suggestions from code review Co-authored-by: phenylshima <[email protected]> commit 76ba6e8 Author: syobonpastel <[email protected]> Date: Sat Dec 28 21:22:48 2024 +0900 fix image commit 51bfe5b Author: syobonpastel <[email protected]> Date: Sat Dec 28 21:21:28 2024 +0900 fix images commit 4d41fd4 Author: syobonpastel <[email protected]> Date: Sat Dec 28 21:18:00 2024 +0900 minor fix commit 2bbee75 Author: syobonpastel <[email protected]> Date: Sat Dec 28 21:07:22 2024 +0900 resize images commit 203fb28 Author: syobonpastel <[email protected]> Date: Sat Dec 28 18:56:48 2024 +0900 add commit 70a098b Author: syobonpastel <[email protected]> Date: Sat Dec 28 18:33:32 2024 +0900 add commit 6811bf1 Author: syobon <[email protected]> Date: Sat Dec 28 18:18:16 2024 +0900 fix place of the screenshot commit 40bd6f7 Author: syobon <[email protected]> Date: Sat Dec 28 17:56:19 2024 +0900 minor fix commit 2b44b31 Author: syobon <[email protected]> Date: Sat Dec 28 17:39:22 2024 +0900 minor fix commit 6f7b19a Author: syobonpastel <[email protected]> Date: Sat Dec 28 17:24:51 2024 +0900 minor fix commit d2cc1c1 Author: syobonpastel <[email protected]> Date: Sat Dec 28 17:22:13 2024 +0900 add commit 2008b36 Author: syobon <[email protected]> Date: Sat Dec 28 17:17:08 2024 +0900 Update index.mdx commit a8d44ec Author: syobon <[email protected]> Date: Sat Dec 28 16:57:42 2024 +0900 Update: `/utol/lecturers/assignments` commit 44ba9a7 Merge: 837719e b69e804 Author: jtamatsukuri <[email protected]> Date: Fri Dec 27 18:08:43 2024 +0900 Merge pull request #1334 from utelecon/20241123-sns-en add /en/notice/2024/1227-rss-sns & /en/notice/rss commit 837719e Merge: 2fbef66 dba574e Author: jtamatsukuri <[email protected]> Date: Fri Dec 27 15:31:02 2024 +0900 Merge pull request #1347 from utelecon/revert-1346-revert-1228-20241016-sns Revert "Revert "add notice and policy document about SNS"" commit dba574e Author: phenylshima <[email protected]> Date: Fri Dec 27 15:27:29 2024 +0900 Revert "Revert "add notice and policy document about SNS"" commit 2fbef66 Merge: dc86fa4 52e4156 Author: jtamatsukuri <[email protected]> Date: Fri Dec 27 15:10:37 2024 +0900 Merge pull request #1346 from utelecon/revert-1228-20241016-sns Revert "add notice and policy document about SNS" commit 52e4156 Author: phenylshima <[email protected]> Date: Fri Dec 27 15:09:39 2024 +0900 Revert "add notice and policy document about SNS" commit dc86fa4 Merge: acab6c4 a807368 Author: jtamatsukuri <[email protected]> Date: Fri Dec 27 15:05:24 2024 +0900 Merge pull request #1228 from utelecon/20241016-sns add notice and policy document about SNS commit acab6c4 Merge: 078927d be43533 Author: jtamatsukuri <[email protected]> Date: Fri Dec 27 13:45:34 2024 +0900 Merge pull request #1337 from utelecon/20241224-support 「サポート窓口ページ」の注意事項の追加 commit a807368 Author: Ryocat <[email protected]> Date: Thu Dec 26 19:48:54 2024 +0900 update notice.yml commit cb7a6f4 Merge: 6d3d961 078927d Author: Ryocat <[email protected]> Date: Thu Dec 26 19:46:02 2024 +0900 Merge branch 'master' into 20241016-sns commit 078927d Author: SASAKI Kaoru <[email protected]> Date: Thu Dec 26 17:10:34 2024 +0900 fontタグの代替更新他 (#1341) (#1342) * fontタグを代替タグに変更：Update index.mdx * （英）fontタグを代替タグに更新：Update index.mdx * （英）FAQ項目の追加：Update index.mdx * FAQ項目の追加：Update index.mdx commit 6d3d961 Author: Ryotai <[email protected]> Date: Thu Dec 26 17:00:28 2024 +0900 Apply suggestion from code review Co-authored-by: syobon <[email protected]> commit b69e804 Author: Ryotai <[email protected]> Date: Thu Dec 26 16:59:41 2024 +0900 Apply suggestion from code review Co-authored-by: syobon <[email protected]> commit 1516836 Author: arima kazumi <[email protected]> Date: Thu Dec 26 16:37:04 2024 +0900 Update index.mdx リンクの文言を「こちら」からリンク先ページ名称に修正 commit 24f7ecf Author: SASAKI Kaoru <[email protected]> Date: Thu Dec 26 11:33:09 2024 +0900 複数人グループ利用ページの内容更新、年末年始休業のお知らせ他：20241227 utokyo azure (#1340) * Create mdx/index.mdx * Update research_computing/index.mdx * Update index.mdx * 推奨されるロール割り当ての追加：Update index.mdx * 微修正：Update index.mdx * （英）ロール割り当ての推奨を追加：Update index.mdx * Azure AI Studio が Azure AI Foundry に更新されたことに伴う更新 (#54) * Azure AI Studio > Foundry：Update azureai.mdx サービスの名称と利用手順が更新されているので修正 * Add files via upload * Update azureai.mdx * Update azureai.mdx * Update azureai.mdx * Update azureai.mdx * Azure AI Foundry に更新されたことによる修正：Update python.mdx * Add files via upload * Delete src/pages/research_computing/utokyo_azure/ai/img/02_aistudiopython2.png * Add files via upload * Update python.mdx * Azure OpenAI の手順が更新されたので修正：Update openai.mdx * Update openai.mdx * Delete src/pages/research_computing/utokyo_azure/ai/img/05_openai5.png * Add files via upload * Update openai.mdx * Update openai.mdx * Update openai.mdx * AI サービスの名称変更：Update index.mdx * Update index.mdx Adds how to update an ACL. * Update mdx/index.mdx * 複数人グループページの内容構成を変更 (#56) * 複数人グループページの更新下書き：Create _index.mdx * Update _index.mdx * Update _index.mdx * Add files via upload * Rename index.mdx to __index.mdx * Rename _index.mdx to index.mdx * Update index.mdx * Update index.mdx * Update index.mdx * Update index.mdx * Update index.mdx * Update index.mdx * Update index.mdx * Update index.mdx * Update mdx/index.mdx * Update index.mdx * Create mdx/deploy.mdx * Update mdx/index.mdx add a link to mdx/deploy.mdx * Update mdx/index.mdx * Update mdx/deploy.mdx * 複数人グループページの更新 (#59) * 複数人グループページの更新下書き：Create _index.mdx * Update _index.mdx * Update _index.mdx * Add files via upload * Rename index.mdx to __index.mdx * Rename _index.mdx to index.mdx * Update index.mdx * Update index.mdx * Update index.mdx * Update index.mdx * Update index.mdx * Update index.mdx * Update index.mdx * Update index.mdx * Azure Portal 上も Foundry の名称修正入ったようなので更新：Update azureai.mdx * 「対象」「Time bound」はライセンスが必要な可能性があるので回避いただく内容に更新 (#60) * 「対象」「Time bound」はライセンスが必要な可能性があるので回避いただく内容に更新：Update index.mdx * Add files via upload * 年末年始休業の広報 (#61) * テスト：Update index.mdx * 年末年始休業のお知らせ記載：Update index.mdx 1/6 に削除予定 * 修正：Update index.mdx * 休業のお知らせ修正他 (#62) * Azure Portl や AI Foundry の仕様変更によりこのページは不要になったので削除：Delete src/pages/research_computing/utokyo_azure/faq/subscriptionid.mdx * 微修正：Update subscription.mdx * 微修正：Update index.mdx * 文法修正：Update index.mdx * 微修正：Update index.mdx * 微修正：Update index.mdx * （英）年末年始休業のお知らせ：Update index.mdx 1/6 削除予定 * 微修正：Update index.mdx --------- Co-authored-by: Shigeru Chiba <[email protected]> Co-authored-by: arima kazumi <[email protected]> commit 6950c59 Author: syobonpastel <[email protected]> Date: Wed Dec 25 21:18:47 2024 +0900 add commit be43533 Author: Aozora Dokko <[email protected]> Date: Wed Dec 25 15:42:06 2024 +0900 Update email-form.md(en) commit 0289d1c Author: Aozora Dokko <[email protected]> Date: Wed Dec 25 15:41:35 2024 +0900 Update chat.md(en) commit 8ca4a1c Author: Aozora Dokko <[email protected]> Date: Tue Dec 24 18:10:03 2024 +0900 Update email-form.md commit 2bd6f2a Author: Aozora Dokko <[email protected]> Date: Tue Dec 24 16:41:03 2024 +0900 Update chat.md commit 424a716 Author: syobonpastel <[email protected]> Date: Mon Dec 23 21:57:16 2024 +0900 add commit 5cfd3a0 Author: syobonpastel <[email protected]> Date: Mon Dec 23 21:50:23 2024 +0900 add commit e7c0353 Merge: 3c83a76 8f1f8b4 Author: Ryotai <[email protected]> Date: Mon Dec 23 20:17:03 2024 +0900 Merge pull request #1335 from utelecon/20241101-rss-link 中途半端に作ってしまった#1251の後始末 commit 8f1f8b4 Merge: f167eb8 3c83a76 Author: Ryotai <[email protected]> Date: Mon Dec 23 20:16:45 2024 +0900 Merge branch '20241123-sns-en' into 20241101-rss-link commit 3c83a76 Author: Ryocat <[email protected]> Date: Mon Dec 23 20:05:34 2024 +0900 fix translation commit 7d09888 Author: Ryocat <[email protected]> Date: Mon Dec 23 20:04:48 2024 +0900 fix file name commit 7fe41d9 Author: Ryocat <[email protected]> Date: Mon Dec 23 20:03:13 2024 +0900 add en link into notice.yml commit a30d877 Author: Ryocat <[email protected]> Date: Mon Dec 23 20:00:07 2024 +0900 update publish date commit 7066b6b Author: Ryocat <[email protected]> Date: Mon Dec 23 19:53:18 2024 +0900 create pages commit f16343e Merge: fb99389 40ce6c6 Author: arima kazumi <[email protected]> Date: Mon Dec 23 15:01:09 2024 +0900 Merge pull request #1332 from utelecon/20241223-mdx mdxの説明ページをuteleconに新規作成 commit 40ce6c6 Author: arima kazumi <[email protected]> Date: Mon Dec 23 14:51:14 2024 +0900 mdxのuteleconページを作成したことによる修正 commit cc2c321 Author: arima kazumi <[email protected]> Date: Mon Dec 23 14:49:37 2024 +0900 仮想マシンのデプロイ方法説明ページを新規作成 commit 49eb92b Author: arima kazumi <[email protected]> Date: Mon Dec 23 14:47:40 2024 +0900 mdxのページをuteleconに新規作成 commit f167eb8 Author: Ryocat <[email protected]> Date: Fri Nov 1 17:13:42 2024 +0900 create en RSS links commit 88d164c Merge: 55868b6 d84d8e3 Author: Ryotai <[email protected]> Date: Thu Oct 17 18:58:52 2024 +0900 Merge branch 'master' into 20241016-sns commit 55868b6 Author: Ryocat <[email protected]> Date: Wed Oct 16 12:15:59 2024 +0900 add policy doc commit c289654 Author: Ryocat <[email protected]> Date: Wed Oct 16 12:02:18 2024 +0900 add notice
utelecon · Jan 20, 2025 · 0baf891 · 0baf891
1 parent 7a08209
commit 0baf891
Show file tree

Hide file tree

Showing 75 changed files with 1,193 additions and 187 deletions.
diff --git a/src/data/notice.yml b/src/data/notice.yml
@@ -12,6 +12,15 @@
 #   c. 右上の「Cancel workflow」ボタンを押してください．
 #   参考：https://docs.github.com/ja/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/canceling-a-workflow
 # 2. もしキャンセルが間に合わず，投稿されてしまった場合は，Slackでご連絡ください．
+-
+  date: 2025-01-17
+  content:
+    ja: "[2025年度Sセメスター「コモンサポーター」募集のお知らせ](/notice/2025/0117-cs) （2月10日13時締切）"
+-
+  date: 2024-12-27
+  content:
+    ja: "[最新情報をRSSとSNS（X；旧Twitter）で便利に受け取れるようになりました](/notice/2024/1227-rss-sns)"
+    en: "[Now you can conveniently receive the latest information via RSS and SNS (X; formerly Twitter)](/en/notice/2024/1227-rss-sns)"
 -
   date: 2024-11-29
   content:

diff --git a/src/layouts/Footer/index.astro b/src/layouts/Footer/index.astro
@@ -83,5 +83,9 @@ const topUrl = {
         }
       }
     }
+
+    @media print {
+      display: none;
+    }
   }
 </style>
diff --git a/src/layouts/Header/index.astro b/src/layouts/Header/index.astro
@@ -250,4 +250,26 @@ const theOtherLangUrl = canonicalUrl.pathname.startsWith("/en/")
       padding: 1em;
     }
   }
+
+  @media print {
+    header.header {
+      background-color: inherit;
+      background-image: none;
+    }
+    .hamburger-button,
+    .hamburger-contents {
+      display: none;
+    }
+    .links {
+      display: none;
+    }
+    .title span {
+      &:nth-child(1) {
+        color: $header-background-color-secondary;
+      }
+      &:nth-child(2) {
+        color: $header-background-color-primary;
+      }
+    }
+  }
 </style>
diff --git a/src/layouts/Toc.astro b/src/layouts/Toc.astro
@@ -264,6 +264,12 @@ for (const heading of Astro.props.headings) {
       display: block;
     }
   }
+
+  @media print {
+    #sidebar {
+      display: none;
+    }
+  }
 </style>
 
 <script>

diff --git a/src/pages/docs/index.md b/src/pages/docs/index.md
@@ -18,3 +18,4 @@ breadcrumb:
     - [東京大学の学生の皆さんへ：AIツールの授業における利用について](/docs/ai-tools-in-classes-students)
     - [AIツールの授業における利用について](/docs/ai-tools-in-classes)
     - [生成系AI(ChatGPT, BingAI, Bard, Midjourney, Stable Diffusion等)について](/docs/20230403-generative-ai)
+- [uteleconのソーシャルメディアポリシー](./sns-policy)
diff --git a/src/pages/docs/sns-policy.md b/src/pages/docs/sns-policy.md
@@ -0,0 +1,41 @@
+---
+title: uteleconのソーシャルメディアポリシー
+toc: false
+---
+
+<div style="text-align: right;">2024年10月31日 情報システム本部</div>
+
+情報システム本部では，東京大学の情報システムに関連する情報を発信するためのソーシャルメディア公式アカウント（「utelecon公式SNS」）を保有しています．情報システム本部は，utelecon公式SNSを，本ポリシーの方針に沿って管理・運用しています．
+
+## アカウント一覧
+
+以下のアカウントを保有しています．
+- X（旧Twitter）（日本語）：[utelecon お知らせ](https://x.com/utelecon_pr)
+- X（旧Twitter）（英語）：[utelecon notice](https://x.com/utelecon_pr_en)
+- YouTube：[utelecon](https://www.youtube.com/@utelecon/videos)
+
+## utelecon公式SNSの運用
+
+### 発信内容について
+utelecon公式SNSでは，東京大学の情報システムに関連する情報を発信します．その際，他者の権利を不当に侵害することのないよう細心の注意を払い，関連する法令等を遵守します．
+
+### 返信・コメントについて
+
+利用者の発言・投稿に対する返信・コメント等は原則として行いません．utelecon公式SNSの投稿内容等について返信が必要な場合は，[uteleconサポート窓口のメールフォーム](/support/#email-form)からお願いします．なお，利用者による発言・投稿の中に不適切と思われるものがあった場合は，利用者の承諾を得ずに非表示にしまたは削除する場合があります．
+
+### シェア・リポスト・いいね・フォロー等について
+
+シェア・リポスト・いいね・フォロー等は原則として行いませんが，情報システム本部の判断によりこれらを行う場合もあります．
+
+## 知的財産権等について
+
+utelecon公式SNSに掲載される写真・イラスト・音声・動画及び記事等の知的財産権は，東京大学または正当な権利を有する者に帰属します．
+
+
+## 免責事項について
+
+情報システム本部は，utelecon公式SNSで発信する情報の正確性には万全を期すものの，利用者がこの情報を用いて行う一切の行為について，何ら責任を負うものではありません．また，利用者により投稿されたコメントやutelecon公式SNSに関連して，利用者間または利用者と第三者間でトラブルや紛争が発生した場合であっても，情報システム本部は何ら責任を負いません．情報システム本部は，ソーシャルメディアを利用したこと，または利用できなかったことによって被った損害について一切責任を負いません．utelecon公式SNSに掲載されたコンテンツは，予告なく変更，移転，削除等が行われることがあります．
+
+## その他
+
+本ポリシーは随時更新されます．
diff --git a/src/pages/en/events/2024-12-20-genai-sympo-ws/index.md b/src/pages/en/events/2024-12-20-genai-sympo-ws/index.md
@@ -17,7 +17,7 @@ In the first part (the symposium, open to all), Associate Professor Koji Yatani
 * Date: Friday, December 20, 2024, 13:00–16:00
 * Location: Online (Zoom)
 * Symposium (First Half): (13:00–14:00) Open to all
-  * Special Lecture by Associate Professor Koji Yatani (Graduate School of Engineering): _"What Do People Feel When Working with Generative AI? --- Perspectives from Human-AI Interaction Research"_ (in English) [slide deck](/events/2024-12-20-genai-sympo-ws/slides/yatani-lecture-slides.pdf)
+  * Special Lecture by Associate Professor Koji Yatani (Graduate School of Engineering): _"What Do People Feel When Working with Generative AI? --- Perspectives from Human-AI Interaction Research"_ (in English) [slide deck](/events/2024-12-20-genai-sympo-ws/slides/1-slide-genAI-koji.pdf)
   * Report by Organizing Committee, Presented by Professor Toshihiko Yamazaki (Graduate School of Information Science and Technology): _"Trends and Cases from Japan and Overseas"_
 * Workshop (Second Half): (14:00–16:00) For UTokyo faculty and staff only
   * Breakout Room Discussions: Group discussions categorized by courses being taught (subjects and formats); further details below

diff --git a/src/pages/en/index.mdx b/src/pages/en/index.mdx
@@ -8,6 +8,7 @@ sitemap: false
 ---
 
 import "@styles/top.scss";
+import "@styles/rss_icon.scss";
 
 import Emergency from '@components/Emergency.mdx'
 import Notice from '@components/pages/Notice.astro'
@@ -37,7 +38,7 @@ import Events from '@components/pages/Events.astro'
 <div class="container">
 <div class="container__column">
 
-## Notice
+## Notice <a href="/en/notice/rss" class="rss_icon" title="RSS">rss_feed</a>
 
 {/* To add notice here, edit `src/data/notice.yml` */}
 

diff --git a/src/pages/en/notice/2024/1227-rss-sns.md b/src/pages/en/notice/2024/1227-rss-sns.md
@@ -0,0 +1,40 @@
+---
+title: Now you can conveniently receive the latest information via RSS and SNS (X; formerly Twitter)
+---
+<div style="text-align: right;">December 27, 2024</div>
+
+The utelecon portal site has provided a variety of information on using ICT at the University of Tokyo. We would like to announce that we have introduced two new ways for users to access the latest information posted on utelecon easily. We would also like to take this time to introduce a similar existing tool that makes it easier to access the latest information.
+
+## We will start providing RSS (really simple syndication)
+
+The latest information published in [the “Notice” section](/en/#notice) of the top page of utelecon is distributed as an RSS feed. RSS is a method for distributing new information on websites. By subscribing to this RSS feed, you can quickly and easily receive the latest information on the “Notice”. For details on how to use it, please see [the explanation page for RSS](/en/notice/rss).
+
+Please note that not all updates to the portal site are distributed via RSS. You can check the latest information on pages other than “Notice” by referring to them as needed.
+
+## We will start sharing information on SNS (social networking service)
+
+We will also share the latest information posted on the utelecon portal site via our official X (formerly Twitter) accounts. In addition to the content of the “Notice” section, we will also introduce new and important articles from utelecon, and we plan to deliver information on major system failures at the University of Tokyo as needed. Please follow the account and check the latest information in a timely manner.
+
+- [uteleconお知らせ](https://x.com/utelecon_pr) (in Japanese)
+- [utelecon notice](https://x.com/utelecon_pr_en) (in English)
+
+Note that this account does not respond to inquiries from users. If you need a reply, please contact us using [the email form on the support desk page](/en/support/#email-form). For other detailed usage policies, please refer to the [“utelecon Social Media Policy”](/docs/sns-policy).
+
+In addition, you can also follow this account and turn on notifications for new posts from this account to find out about the latest posts immediately. Please make use of these functions as well.
+
+## We are sending out emails about “System Failures and Maintenance Information”
+
+Since August 2023, utelecon has been providing [a page where you can view a list of system failures and maintenance information](https://univtokyo.sharepoint.com/sites/utokyoaccount/SitePages/en/service-status.aspx) (sign-in with your UTokyo Account is required) (cf. “[「システムの障害・メンテナンス情報」ページ作成のお知らせ](/notice/2023/08-service-status),” only in Japanese). In addition, we are also sending out emails about the information on this page to ECCS Cloud Email using Google Groups. If you would like to receive notifications by email, please log in to ECCS Cloud Email and click the “Join Group” button on the “System Outages and Maintenance Information” group page to register.
+
+As of now, the following systems are listed.
+
+- UTOL, ECCS Cloud Email, ECCS Terminals
+  - This information was previously posted on the ECCS website.
+- UTokyo Wi-Fi, UTokyo VPN
+  - This information was previously posted in the Notices section of the utelecon portal site.
+- Office Work Terminals, Email System for Staff
+  - This information was previously sent by email to the PC Equipment Manager of each department.
+- UTNET (Campus Network)
+  - This information was previously posted on the UTNET website.
+- Databases, e-journals, OPAC, etc.
+  - This information was previously posted on the “[Failure information on databases, e-journals, OPAC, etc.](https://www.lib.u-tokyo.ac.jp/en/library/literacy/user-guide/servicestatus)” page (for the time being, it will be posted on both pages).
diff --git a/src/pages/en/notice/index.mdx b/src/pages/en/notice/index.mdx
@@ -1,6 +1,10 @@
 ---
 title: Notice
+h1: Notice <a href="/en/notice/rss" class="rss_icon" title="RSS">rss_feed</a>
+breadcrumb:
+  title: Notice
 ---
+import "@styles/rss_icon.scss";
 import Notice from '@components/pages/Notice.astro';
 
 {/* To add notice here, edit `src/data/notice.yml` */}

diff --git a/src/pages/en/notice/rss.mdx b/src/pages/en/notice/rss.mdx
@@ -0,0 +1,27 @@
+---
+title: About RSS for “Notice”
+breadcrumb:
+  title: RSS
+toc: false
+---
+
+The latest information published in the Notice section of the top page of utelecon is distributed via RSS. RSS is a method for distributing new information on websites. 
+
+Please note that this does not mean that all updates to the portal site are distributed via RSS. For pages other than the Notice section, please check those pages for the latest information as needed.
+
+## How to use RSS
+
+To receive website update information using RSS, you need to set the URL of the RSS feed (a file that contains updates in RSS format) in a dedicated tool or app.
+
+The URL for the RSS feed of utelecon's Notice is as follows.
+
+<b class="box center">
+`https://utelecon.adm.u-tokyo.ac.jp/en/notice/rss.xml`
+</b>
+
+The following are some examples of how to use RSS.
+- Receive notifications from an RSS reader: Enter the RSS feed URL in a dedicated app known as an “RSS reader” to receive updates in the form of smartphone notifications, etc.
+- Automatically post to a Slack channel: Using the “RSS” app for Slack, you can automatically post updates to the channels in your workspace.
+    - Reference information: [Add RSS feeds to Slack](https://slack.com/help/articles/218688467-Add-RSS-feeds-to-Slack) (slack help center)
+
+You can also use other ways to receive updates by using tools and apps that support RSS.
diff --git a/src/pages/en/research_computing/utokyo_azure/faq/index.mdx b/src/pages/en/research_computing/utokyo_azure/faq/index.mdx
@@ -94,6 +94,11 @@ However, for example, login authentication to the OS running on a virtual machin
   <Fragment slot="solution">You can check your subscription ID on the subscription details screen.</Fragment>
 </HelpItem>
 
+<HelpItem lang="en" type="details">
+  <Fragment slot="problem">Can I recover my service and data if I accidentally cancel my subscription?</Fragment>
+  <Fragment slot="solution">Subscriptions and data cannot be restored. If you wish to continue using the service for a certain period of time or longer, please be sure to turn off the Auto Suspension function from the subscription management page on the Utokyo Azure:New application page.</Fragment>
+</HelpItem>
+
 **Free Tier and Guaranteed Free Tier**
 
 <HelpItem lang="en" type="details">

diff --git a/src/pages/en/research_computing/utokyo_azure/group/_index.mdx b/src/pages/en/research_computing/utokyo_azure/group/_index.mdx
@@ -0,0 +1,92 @@
+---
+title: "Group Use"
+breadcrumb:
+  title: Group Use
+---
+import HelpItem from "@components/utils/HelpItem.astro";
+
+If you want to share **subscriptions** or **resources** (scopes) with members of your laboratory or collaborators, the representative can apply for a subscription and add members to that subscription with the appropriate permissions (roles) to make it possible to share.
+
+Also, what a sharer can do will depend on which resource they are assigned to, who they are assigned to, and what role they are assigned to.
+
+Please refer to this link for instructions on assigning permissions.
+- [Steps to assign an Azure role to subscriptions and resources](/en/research_computing/utokyo_azure/faq/addrole)
+
+<div class="box">
+If you're not sure what to do, we recommend assigning the following:
+- **Sharing with faculty**: For sharing that includes costs, assign to the subscription with the **Owner** role. For sharing that does not include costs, assign to the subscription with the **Contributor** role.
+- **Sharing with students**: If you want them to manage resources including creating new resources, assign to the subscription with the **Contributor** role. If you only want them to manage existing services, assign to the resource or resource group with **Contributor**.
+- **Use only**: If you only want to use the service without managing it, assign the account and permissions to the service, but do not assign roles to the subscription or resources. In this case, the way accounts and permissions are assigned varies depending on the service, so please refer to the help for each service for details.
+</div>
+
+## Roles and Members (Role-Based Access Control: RBAC)
+
+In Microsoft Azure, you can grant permissions to other accounts to access each scope by setting which permissions (roles) to assign to whom (members). This is called role-based access control (RBAC), and you can use this function to share subscriptions and resources you create.
+
+## Permission Inheritance
+
+Microsoft Azure inherits permissions from higher scopes to lower scopes. Specifically, in the diagram below, inner scopes inherit permissions from outer scopes. Permissions are irreversible and are not inherited to outer scopes. The top-level scope is a subscription.
+
+<div class="box">
+- Deployed services such as virtual machines may be an exception to privilege inheritance. (described later)
+- There are cases where permissions are not necessarily inherited. If it is important that permissions are inherited, be sure to check that they are, and if they are not, assign the necessary permissions individually.
+</div>
+
+![](img/01_iam_en.png){:.medium.center}
+
+
+## Assign a member with the **Owner** role to the subscription.
+
+The **Owner** has the authority to assign all roles (with some exceptions) and is assigned to the applicant's UTokyo Account by default. The main privileges are as follows.
+
+- Assign other members and roles to the subscription.
+  - However, depending on the conditions when assigning the owner role to a member, that member may not have some privileges.
+- View the details of your subscription on the `Subscription Management page` of the **UTokyo Azure:New Application page**.
+  - The current of limit the Free Tier and Guaranteed Free Tier can only be viewed on the subscription management page of the UTokyo Azure New Application page.
+  - Billing information will also be displayed, so be careful not to give owner privileges to the wrong member.
+- Use that subscription to create resources for the new service.
+
+
+Unless you want to completely transfer the subscription to another member, please do not assign other members the privileges of the **Owner who can assign all roles**. If you want to assign the owner role to that member for sharing purposes, make sure to make a conditional selection.
+
+## Assign a member with the **Contributor** role to the subscription.
+
+**Contributor** role has the same permissions as the Owner role, except that permissions cannot be assigned to other members. Normally, if you want to share your subscription with other members, please grant this privileges.
+
+- **have privileges**
+  - Use that subscription to create resources for the new service.
+  - Check resource usage from the Azure Portal.
+- **have no privileges**
+  - Assign roles to other members to each scope.
+  - View the subscription details on the Subscription Management page of the **UTokyo Azure:New Application page**.
+
+
+## Assign a member with the **Owner** role to a resource or resource group.
+
+You will be given privileges to assign all roles to that resource.
+
+- **have privileges**
+  - Assign other members and roles to the resource or resource groups.
+    - However, depending on the conditions when assigning the owner role to a member, that member may not have some privileges.
+  - Create a new resource in the resource group.
+    - For example, adding a new interface to a virtual machine, adding a new subnetwork resources, etc.
+- **have no privileges**
+  - Create a resource or resource group for the new Azure service.
+
+## Assign a member with the **Contributor** role to the resource or resource groups.
+
+Has the same privileges as the Owner, except that the role cannot be granted to other members.
+
+- **have privileges**
+  - Create a new resource in the resource group.
+    - For example, adding a new interface to a virtual machine, adding a new subnetwork resources, etc.
+- **have no privileges**
+  - Assign roles to other members to the resource or resource group.
+  - Create a resource for the new Azure service.
+
+## About permissions for deployed services
+
+Deployed services may not be subject to Azure permission inheritance.
+
+- For example, when a virtual machine is deployed, the system account and administrative privileges for that OS will not be inherited from the Azure service and will be managed separately.
+- For such services, if you want to add members only to the service, set the accounts and permissions only in the deployed service, not in Azure.