v0.10.1

コンポーネントのJavaScriptは使用するページのHTMLに埋め込まれます。単独のJavaScriptファイルはメディアから読み込めます。

mikanBox Cloud v0.10.0

mikanBox Cloud 0.10.0 remains a development edition. It follows mikanBox PHP 2.20.0.

• The admin page list's default order now matches the public lists: pending, then index, then display order, then the newest update, then ID. (Before, pages with the same display order were ordered by ID.)
• A sort selector right of the output-format filter: Display order, Newest update, Oldest update, ID, Title (sort= in the URL). Title order uses Japanese collation, and an empty title is ordered by its ID. index is always first; pending pages come first only in Display order.
• Sorting happens before paging. The order is kept with the filters, search and paging, and after opening and closing an editor. The selector's tooltip explains what the Update date means.

After updating, check: open the page list and try each order (the list should reorder without a reload and the URL should show sort=); go to page 2 of a sorted list, open a page and close it (you should return to the same page and order); combine an order with the output-format filter and with a search.

Validation: TypeScript checks and all 279 Cloud tests pass. In headless Chrome each order produced the expected sequence (Title: Data, Zeta, あ, い, う, えび), and paging, the format filter, editor open/close and search kept sort=.

mikanBox Cloud v0.9.4

mikanBox Cloud 0.9.4 remains a development edition. It follows mikanBox PHP 2.19.3.

• Closing an editor (page and design) in a new order: it fades out in place (about 200 ms, the height does not change), the screen scrolls smoothly to the top of the list (300-600 ms by distance), and only after the scroll ends is the editor removed. With reduced motion it closes at once. This replaces 0.9.3's "scroll, then shrink".

After updating, check: open a page far down the list and press "一覧へ戻る": the editor should fade where it is, then the screen should glide up to the list top. Do the same with a component in the design section.

Validation: TypeScript checks and all 276 Cloud tests pass. In headless Chrome I sampled a real close every 40 ms. Page editor: opacity 1 to 0 over about 200 ms at a constant height of 1969 px; then scrollY fell step by step (2334, 2224, 1646, 607, 190, 138) over about 400 ms; then the editor was gone and the list top was at 0. Design editor: opacity 1 to 0 at a constant 1711 px; scrollY 4286, 4179, 3643, 3306, 3275; then removed.

mikanBox Cloud v0.9.3

mikanBox Cloud 0.9.3 remains a development edition. It follows mikanBox PHP 2.19.2.

• Closing an editor shrinks visibly. Closing a page or design editor first scrolls smoothly to the top of the list, then the editor shrinks away in 260 ms (opening takes 320 ms). It used to look instant. The scroll back to the edited row is gone.
• Unsaved changes ask like the PHP edition: Save and close / Discard and close / Cancel, when closing an editor, opening another, or switching revision. If the save fails, the prompt stays open. Unsaved changes are counted separately for the page and design editors, and "Save and close" saves the editor you are leaving. The media rename confirmation looks like PHP's too.
• Delete buttons ask for confirmation even when a required field (such as the title) is empty.
• The data-migration screen (/admin?view=import) is unchanged.

After updating, check: open a page far down the list, press "一覧へ戻る" and watch the editor shrink after the scroll; make an edit and close (three choices); make an edit and press delete with the title emptied (the confirmation appears).

Validation: TypeScript checks and all 276 Cloud tests pass. In headless Chrome the collapse animation was paused and measured (260 ms, forwards; height 1969, 1503, 442, 80, 0 px at 0, 65, 130, 195, 259 ms), and every operation rewritten in 0.9.0 was pressed again.

mikanBox Cloud v0.9.2

mikanBox Cloud 0.9.2 remains a development edition.

• Page search filters as you type, like the media search: the list changes 250 ms after you type, the search term stays in the URL, and clearing it with the browser's own × shows every page at once. (Before, you pressed Enter.) There was no technical reason for the difference.
• README features now mention Markdown output and the other output formats (JSON, XML, CSV, text, JavaScript, CSS and mikanBox DB).

Includes 0.9.1 (the fix for the failed update to 0.9.0). Run the update from the admin screen.

Validation: TypeScript checks and all 273 Cloud tests pass. The live search was checked in headless Chrome against a local dev server (typing filters in place, the URL keeps q, no reload, no dialog).

mikanBox Cloud v0.9.1

mikanBox Cloud 0.9.1 remains a development edition.

• Fixes the update to 0.9.0. The GitHub update workflow failed because the shared admin-ui.js was copied from a shared/ folder outside the repository, which does not exist there. Without shared/, the committed public/mikanbox/admin-ui.js is now used as it is. Checked in a clean clone without shared/: npm ci, the type check, all 273 tests and the build pass and leave no changed files. Run the update from the admin screen.
• Two in-place operations fixed. Changing the language now switches the screen, and issuing a device code now shows the code. Both were found by pressing every operation rewritten in 0.9.0 in a development environment (see the manuals for the list of operations that still reload on purpose).

Everything in 0.9.0 is included (no browser dialogs, no reload, editor motion, preview of the content being edited, preview_page; update needs migration 0018, applied by the workflow).

mikanBox Cloud v0.9.0

mikanBox Cloud 0.9.0 remains a development edition. It follows mikanBox PHP 2.19.0.

• Operation basics. The browser's alert, confirm and prompt are gone from the admin screen (a test fails if one returns). Results go to the toast at the bottom right; confirmations are asked in the screen.
• No reload. Saving and deleting pages and components, memo, site settings, update source, devices and users, publishing, and choosing or adding a category run in the current screen. A new page or component becomes an existing editor after its first save.
• Opening and closing editors. Page and design editors grow and shrink in, scroll to the top of the editor when opened and back to the edited row when closed, keep the filters, and ask in the screen about unsaved changes.
• Preview shows the content being edited (unsaved changes and new pages included). It is not saved; the display stays isolated. The edited content is kept for 30 minutes (at most four per user, readable only by that user), in a new D1 table (migration 0018, applied by the update workflow).
• MCP. New read-only preview_page (an ID alone previews the saved page; fields preview unsaved content, also for a new ID). get_site_info reports version; the connection guidance says to re-read the tool list when it changes; get_ai_context ends with a built-in output-formats document.
• Full reloads remain only where the screen's premise changes: language change, restoring a backup, switching media storage (and cancelling its migration), restoring D1 to a time, stopping your own device, saving the connection settings, and file downloads. They are listed in the manuals.

After updating, check: open and close a page editor (no reload, back to the edited row), delete a page (an in-screen confirmation, a message at the bottom right), change the editor text without saving and press Preview, and confirm that no browser dialog appears anywhere. Publishing again is only needed if you have not published since 0.8.1 or later.

Validation: TypeScript checks and all 273 Cloud tests pass. Open/close, delete, in-place save, unsaved preview and the design editor were also driven in headless Chrome against a local dev server (no reload, no browser dialogs). Not yet checked on a real Cloudflare deployment.

mikanBox Cloud v0.8.3

mikanBox Cloud 0.8.3 remains a development edition.

• Times in your time zone. "Last published", revision times and the Added / Last used / Expires columns under Devices and users were shown in UTC (04:30 for 13:30 in Japan). They now appear in the viewer's own time zone.
• Sign-in page. It receives only the site name instead of the whole settings record; its tab title is "🍊site name - Sign in", as in the PHP editions.

The public-site header settings of 0.8.1 are unchanged. Publishing once more is only needed if you have not published since updating to 0.8.1 or later.

Validation: TypeScript checks and all 264 Cloud tests pass. The time conversion was checked in headless Chrome (04:35 UTC shows as 13:35 in Asia/Tokyo and 4:35 in UTC).

mikanBox Cloud v0.8.2

mikanBox Cloud 0.8.2 remains a development edition.

The admin screens follow mikanBox PHP 2.18.2:

• Title: the browser tab shows "🍊site name" (sign-in: "🍊site name - Sign in"); a site name that already starts with 🍊 keeps one.
• Page list: an output-format filter right of Help (all / HTML / HTML + Markdown / Markdown / data / mikanBox DB). It combines with the category and the search, stays in the URL, and is kept when the page editor is opened and closed.
• Row actions: edit, visual editing and the globe icon, which opens the page on the public site. Drafts, pending pages and pages never published show the globe grey and unclickable. Check saved content with the page editor's preview, which now says "Shows the saved content." beside the button.
• Media: the type filter and a live filename search sit in the heading row, and the supported formats are explained inside Upload options.
• Searches: one clear button (the browser's).
• Drops: files can be dropped only on the media section; elsewhere the pointer shows "no drop" (previously a file dropped on the data-migration screen looked accepted but did nothing).
• Selects: room right of the arrow, as on date inputs (including the "HTML file structure" select next to "Download static ZIP").
• MCP: the connection instructions and get_ai_context explain that a page is made readable as Markdown by setting output_format to html_md or md; there is no site-wide switch.
• Japanese and English Cloud manuals updated.

After updating, publish once more, especially if you are coming from 0.8.0, so that the 0.8.1 header settings reach the public site.

Validation: TypeScript checks and all 263 Cloud tests pass. The page list, page editor, media section and data-migration screen were compared with a local PHP 2.18.2 admin.

mikanBox Cloud v0.8.1

mikanBox Cloud 0.8.1 remains a development edition.

Fixes found on a real Cloudflare deployment of 0.8.0:

• Garbled text on the public site. Cloudflare's delivery typed .md, .txt, .csv, .js and .css by extension without a charset, so Japanese text opened from the globe icon in the page list was garbled. _headers now sets charset=utf-8 with one wildcard rule per text extension (/*.md and so on), plus exact rules for the /id and /id/ aliases of Markdown-only pages and /api/ID of mikanBox DB, because Cloudflare matches the requested path, not the rewrite target. XML files keep exact rules so the sitemap and feeds keep their own types.
• CORS for Markdown and data outputs. Markdown versions, data formats (.json, .xml, .csv, .txt, .js, .css) and mikanBox DB are served with Access-Control-Allow-Origin: *, as in the PHP editions, so Markdown viewers and scripts on other sites can read them. HTML, the sitemap and the feeds do not get it.
• Page list filter. Opening the page editor from a page list filtered by category no longer clears the filter (the search and list page are kept too), and a new page starts with the filtered category, as in the PHP editions.

After updating, publish once more so the new _headers takes effect.

Validation: TypeScript checks and all 262 Cloud tests pass. The generated _headers was served by wrangler's local asset server: every Markdown, text, XML and DB path, aliases included, returned charset=utf-8 and a single Access-Control-Allow-Origin: *, and HTML returned no CORS header. The fix has not yet been checked on the real public site, which needs this update and a re-publish.