MMOframework
Why AI Playground Libraries Documentation Search Agency
FR EN
MMOframework · made by Hydra Agency Documentation · MCP
The search an agent runs

Search the documentation

Every document of every library, and their agent skills, searched by the MCP server's own search_documentation: a match holds every word, on one line or on 3 lines in a row.

20 matches, the best first

  1. php/Theme.md mmo.client · line 35 | ▪ | 🔐 | [`pages`](#theme-pages) | |
  2. php/Theme.md mmo.client · line 128 <a id="theme-pages"></a>
  3. php/monitoring/HubScaffold.md mmo.admin · line 178 | `$pages` | [`array`](https://www.php.net/manual/fr/language.types.array.php) | the theme's pages the project has (`{Oviepro}/pages`): kept first |
  4. Pages.md mmo.client · line 92 so a `category.phtml` at the root of one of the theme's `pages` folders replaces it; with none, the package's
  5. monitoring.md mmo.admin · line 183 An application of your own can show the same pages: `{MMO\admin}/monitoring/pages` in its theme's `pages`,
  6. checklists.md mmo.admin · line 71 "MMO\\client\\Theme": {"pages": ["{root}/src/pages", "{MMO\\admin}/pages"]}
  7. monitoring.md mmo.admin · line 67 and `{MMO\admin}/monitoring/pages` after its theme's own pages. The pages are then `<site>/hub`, `hub/servers`,
  8. mmoframework/references/gotchas.md mmo.core · agent skill · line 272 thrown by a route made `Application::handle()` throw instead of answering; mmo.client's `Theme` error pages had the same
  9. Pages.md mmo.client · line 62 | `css` | the class of the `<mmo-app>` shell on its pages (`admin`, `landing`, `blog`, ...), instead of the theme's. Its pages inherit it |
  10. php/monitoring/HubScaffold.md mmo.admin · line 51 | ƒ | 🔓 | [`EmbeddedConfig($pages)`](#hubscaffold-embeddedconfig) `static` | What the project's `configs/dev.json` gets for its hub: HubController routed and reading its `hub.json` (collections left to cron: the web server has no ssh agent), the hub's pages in its theme. |
  11. php/monitoring/HubScaffold.md mmo.admin · line 170 left to cron: the web server has no ssh agent), the hub's pages in its theme.
  12. Pages.md mmo.client · line 265 `import()` looks relative names up on the document's import path -- every `pages` folder of the theme, then
  13. SASS_FIX_PLAN.md mmo.client · line 69 and [addingTheme.md](demo/www/contents/pages/guides/frontEnd/themes/addingTheme.md) instructs
  14. SASS_FIX_PLAN.md mmo.client · line 83 demo/www/contents/pages/guides/frontEnd/themes/addingTheme.md
  15. SASS_ARCHITECTURE_REVIEW.md mmo.client · line 396 `demo/www/contents/pages/sass/*.phtml` (11 pages), `guides/frontEnd/themes/addingTheme.md`,
  16. PLAN.md www.mmoframework · line 41 | mmo.core, mmo.client | the application, the pages, the `.jhs` elements, the theme |
  17. mmo-client/SKILL.md mmo.client · agent skill · line 65 A page (`src/pages/**.phtml`) is plain html the theme already styles: write the elements and these classes, no
  18. php.md mmo.doc · line 204 so a theme switch reaches the documentation pages like any other page.
  19. PLAN.md www.mmoframework · line 60 one-line note on the French pages. **Theme.** `src/styles/app.scs` on top of mmo.client's design system: the Blueprint tokens (`$color.*`, the grid
  20. monitoring.md mmo.admin · line 42 | `hub.php`, `www/index.php`, `bootstrap.php` | the command line, the pages, what both load | | `www/bin/` | the theme mmo.client compiles the first time a page is asked for |

Connect your agent