Skip to content

Commit b82fc1a

Browse files
ToolboxAidToolboxAid
committed
Add Build Play Share no-code platform vision copy - PR_26152_018-build-play-share-vision-copy
1 parent 6bbdd7a commit b82fc1a

11 files changed

Lines changed: 160 additions & 62 deletions

‎GameFoundryStudio/about.html‎

Lines changed: 19 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
<meta charset="utf-8">
66
<meta name="viewport" content="width=device-width, initial-scale=1">
77
<title>About - Game Foundry Studio</title>
8-
<meta name="description" content="Game Foundry Studio: creator tools, playable games, marketplace assets, tutorials, cloud saves and community discovery.">
8+
<meta name="description" content="Game Foundry Studio is a no-code, config-driven path from game design documents to manifests and open-web games.">
99
<link rel="icon" href="assets/images/favicon.svg" type="image/svg+xml">
1010
<link rel="stylesheet" href="assets/css/styles.css">
1111
</head>
@@ -16,45 +16,47 @@
1616
<section class="about-hero">
1717
<div class="container about-hero__content">
1818
<div class="kicker">About Game Foundry Studio</div>
19-
<h1>Build the game. Ship the world. Bring the players.</h1>
20-
<p class="lede">Game Foundry Studio is a creator destination for the open web: creator tools, playable
21-
games, marketplace assets, tutorials, cloud saves and community discovery in one foundry-bright
22-
workspace.</p>
19+
<h1>Build, play and share open-web games without writing code.</h1>
20+
<p class="lede">Game Foundry Studio is a no-code, configuration-driven creator destination where game
21+
ideas move from GDD to manifest to engine. Creators shape content, rules, worlds and publishing
22+
plans through composition instead of custom user code.</p>
2323
</div>
2424
</section>
2525
<section class="section">
2626
<div class="container grid cols-3">
2727
<article class="card">
2828
<div class="card-body">
29-
<h2>Create</h2>
30-
<p>Forge sprites, sounds, scenes, input maps and prototypes with web-native tools built for fast
31-
iteration.</p>
29+
<h2>Build</h2>
30+
<p>Create games through configuration, content and composition: scenes, sprites, rules, inputs,
31+
objectives and templates that the engine can understand.</p>
3232
</div>
3333
</article>
3434
<article class="card">
3535
<div class="card-body">
3636
<h2>Play</h2>
37-
<p>Discover playable experiments, arcade releases and creator showcases without leaving the
38-
browser.</p>
37+
<p>Test, preview, run, discover and enjoy games and examples in the browser while the same
38+
manifest-driven engine powers each experience.</p>
3939
</div>
4040
</article>
4141
<article class="card">
4242
<div class="card-body">
4343
<h2>Share</h2>
44-
<p>Package assets, publish updates, learn from tutorials and grow a community around every
45-
finished build.</p>
44+
<p>Publish games, assets, templates, tutorials, ratings and community knowledge so every
45+
useful pattern can help the next creator move faster.</p>
4646
</div>
4747
</article>
4848
</div>
4949
</section>
5050
<section class="section">
5151
<div class="container card">
5252
<div class="card-body">
53-
<div class="kicker">Open-web game studio</div>
54-
<h2>A creator playground with production instincts.</h2>
55-
<p class="lede">The direction is simple: make the browser feel like a living game foundry. Tools,
56-
games, tutorials, marketplace assets, saves and discovery should feel connected, energetic and
57-
ready for creators who want to move from idea to playable world without ceremony.</p>
53+
<div class="kicker">GDD &rarr; Manifest &rarr; Engine</div>
54+
<h2>A config-driven engine for anyone with a game idea.</h2>
55+
<p class="lede">The long-term mission is to enable anyone to create games for the open web without
56+
writing code. Game Foundry Studio turns a design plan into structured manifests, then lets the
57+
engine run behavior from configuration instead of custom scripts.</p>
58+
<p>The engine goal is zero user code: all gameplay behavior, content, presentation and publishing
59+
intent should be described through manifests, reusable templates and clear creator controls.</p>
5860
</div>
5961
</div>
6062
</section>

‎GameFoundryStudio/assets/css/pages.css‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -469,6 +469,10 @@
469469
margin-top: 4px
470470
}
471471

472+
.version-item span {
473+
text-transform: none
474+
}
475+
472476
.version-item.is-current {
473477
border-color: var(--gold);
474478
background: var(--orange-soft)

GameFoundryStudio/assets/images/forge-bot.png renamed to GameFoundryStudio/assets/images/forge-bot-single.png

File renamed without changes.

‎GameFoundryStudio/assets/images/icons/localization.png‎

4.95 KB
Loading

‎GameFoundryStudio/assets/images/tools/localizaton.png‎

1.8 MB
Loading

‎GameFoundryStudio/mission.html‎

Lines changed: 19 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
<meta charset="utf-8">
66
<meta name="viewport" content="width=device-width, initial-scale=1">
77
<title>Mission - Game Foundry Studio</title>
8-
<meta name="description" content="Plan the product mission page for Game Foundry Studio.">
8+
<meta name="description" content="Game Foundry Studio mission: help anyone create open-web games through no-code configuration and manifests.">
99
<link rel="icon" href="assets/images/favicon.svg" type="image/svg+xml">
1010
<link rel="stylesheet" href="assets/css/styles.css">
1111
</head>
@@ -17,34 +17,40 @@
1717
<div class="container">
1818
<div class="kicker">Company</div>
1919
<h1>Mission</h1>
20-
<p class="lede">A planning page for the practical creator promise behind Build, Play, and Share.</p>
20+
<p class="lede">The practical creator promise behind Build, Play and Share: make open-web game creation possible without writing code.</p>
2121
</div>
2222
</section>
2323
<section class="section">
2424
<div class="container card">
2525
<div class="card-body">
26-
<div class="kicker">Status = Planning</div>
26+
<div class="kicker">No-code creator mission</div>
2727
<div class="grid cols-3">
2828
<article class="callout">
29-
<h2>Purpose</h2>
30-
<p>State how Game Foundry Studio helps creators move from idea to playable web game.</p>
29+
<h2>Build</h2>
30+
<p>Give creators clear configuration, content and composition tools so a game idea can become structured data the engine can run.</p>
3131
</article>
3232
<article class="callout">
33-
<h2>Future Scope</h2>
34-
<p>Clarify support for tools, tutorials, asset reuse, publishing readiness, and community discovery.</p>
33+
<h2>Play</h2>
34+
<p>Make testing, previewing, running, discovering and enjoying games part of the same workflow, from first prototype to published example.</p>
3535
</article>
3636
<article class="callout">
37-
<h2>Planned Sections</h2>
38-
<ul>
39-
<li>Build promise</li>
40-
<li>Play promise</li>
41-
<li>Share promise</li>
42-
</ul>
37+
<h2>Share</h2>
38+
<p>Support publishing for games, assets, templates, tutorials, ratings and community knowledge so creators can learn from each other.</p>
4339
</article>
4440
</div>
4541
</div>
4642
</div>
4743
</section>
44+
<section class="section">
45+
<div class="container card">
46+
<div class="card-body">
47+
<div class="kicker">GDD &rarr; Manifest &rarr; Engine</div>
48+
<h2>Turn design intent into playable behavior.</h2>
49+
<p class="lede">The long-term mission is to let anyone describe a game in plain terms, refine it into a manifest and run it through a config-driven engine.</p>
50+
<p>Game Foundry Studio is aiming for zero user code. Creators should configure systems, compose content and choose templates while the engine handles behavior from manifest data.</p>
51+
</div>
52+
</div>
53+
</section>
4854
</main>
4955
<div data-partial="footer"></div>
5056
<script src="assets/js/gamefoundry-partials.js" defer></script>

‎GameFoundryStudio/release-notes.html‎

Lines changed: 28 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
<meta charset="utf-8">
66
<meta name="viewport" content="width=device-width, initial-scale=1">
77
<title>Release Notes - Game Foundry Studio</title>
8-
<meta name="description" content="Platform status, milestone progression and release notes for Game Foundry Studio.">
8+
<meta name="description" content="Platform status, milestone progression and release notes for the no-code Game Foundry Studio engine direction.">
99
<link rel="icon" href="assets/images/favicon.svg" type="image/svg+xml">
1010
<link rel="stylesheet" href="assets/css/styles.css">
1111
</head>
@@ -17,16 +17,16 @@
1717
<div class="container">
1818
<div class="kicker">Company</div>
1919
<h1>Release Notes</h1>
20-
<p class="lede">Platform status and milestone notes for the Game Foundry Studio creator destination.</p>
20+
<p class="lede">Platform status and milestone notes for the Build, Play and Share no-code engine direction.</p>
2121
</div>
2222
</section>
2323
<section class="section">
2424
<div class="container release-overview">
2525
<article class="release-intro">
2626
<div class="kicker">Build &middot; Play &middot; Share</div>
2727
<h2>The platform is in Developer Preview.</h2>
28-
<p class="lede">Game Foundry Studio is shaping the connected loop between creator tools, playable games, tutorials, assets, cloud saves and community discovery.</p>
29-
<p>These notes track platform-level milestones and public-facing direction. They are informational planning markers, not software build numbers or compatibility promises.</p>
28+
<p class="lede">Game Foundry Studio is shaping the connected loop between configuration tools, playable games, tutorials, assets, templates, ratings and community discovery.</p>
29+
<p>These notes track platform-level milestones and public-facing direction toward GDD &rarr; Manifest &rarr; Engine. They are informational planning markers, not software build numbers or compatibility promises.</p>
3030
</article>
3131
<div class="release-stat-grid" aria-label="Current platform status">
3232
<article class="release-stat">
@@ -44,6 +44,29 @@ <h2>The platform is in Developer Preview.</h2>
4444
</div>
4545
</div>
4646
</section>
47+
<section class="section">
48+
<div class="container card">
49+
<div class="card-body">
50+
<div class="kicker">No-code engine direction</div>
51+
<h2>Zero user code, all config and manifest-driven behavior.</h2>
52+
<p class="lede">The long-term mission is to enable anyone to create games for the open web without writing code.</p>
53+
<div class="grid cols-3">
54+
<article class="callout">
55+
<h3>Build</h3>
56+
<p>Create games through configuration, content and composition.</p>
57+
</article>
58+
<article class="callout">
59+
<h3>Play</h3>
60+
<p>Test, preview, run, discover and enjoy games and examples.</p>
61+
</article>
62+
<article class="callout">
63+
<h3>Share</h3>
64+
<p>Publish games, assets, templates, tutorials, ratings and community knowledge.</p>
65+
</article>
66+
</div>
67+
</div>
68+
</div>
69+
</section>
4770
<section class="section">
4871
<div class="container">
4972
<div class="section-head">
@@ -89,7 +112,7 @@ <h2>From early foundations to launch readiness.</h2>
89112
<div class="kicker">Platform Version History</div>
90113
<h2>Milestones, not software build numbers.</h2>
91114
</div>
92-
<p>Version labels describe product milestones across Build, Play and Share. They do not map to internal code builds.</p>
115+
<p>Version labels describe product milestones across Build, Play and Share, including the path from game design documents to manifests to the engine. They do not map to internal code builds.</p>
93116
</div>
94117
<div class="version-columns">
95118
<section aria-labelledby="released-platform-versions">

‎GameFoundryStudio/roadmap.html‎

Lines changed: 19 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
<meta charset="utf-8">
66
<meta name="viewport" content="width=device-width, initial-scale=1">
77
<title>Roadmap - Game Foundry Studio</title>
8-
<meta name="description" content="Plan the product roadmap page for Game Foundry Studio.">
8+
<meta name="description" content="Game Foundry Studio roadmap for Build, Play, Share and no-code manifest-driven game creation.">
99
<link rel="icon" href="assets/images/favicon.svg" type="image/svg+xml">
1010
<link rel="stylesheet" href="assets/css/styles.css">
1111
</head>
@@ -17,34 +17,40 @@
1717
<div class="container">
1818
<div class="kicker">Company</div>
1919
<h1>Roadmap</h1>
20-
<p class="lede">A planning page for product direction, upcoming milestones and release themes.</p>
20+
<p class="lede">A roadmap for moving from creator tools toward a zero-code, manifest-driven engine for open-web games.</p>
2121
</div>
2222
</section>
2323
<section class="section">
2424
<div class="container card">
2525
<div class="card-body">
26-
<div class="kicker">Status = Planning</div>
26+
<div class="kicker">Platform direction</div>
2727
<div class="grid cols-3">
2828
<article class="callout">
29-
<h2>Purpose</h2>
30-
<p>Provide a footer destination for future roadmap communication.</p>
29+
<h2>Build</h2>
30+
<p>Grow the authoring path around configuration, content and composition so creators can assemble game systems without code.</p>
3131
</article>
3232
<article class="callout">
33-
<h2>Future Scope</h2>
34-
<p>Add milestones, release themes and community feedback summaries.</p>
33+
<h2>Play</h2>
34+
<p>Improve testing, previewing, running and discovery so games and examples become the fastest way to understand what the platform can make.</p>
3535
</article>
3636
<article class="callout">
37-
<h2>Planned Sections</h2>
38-
<ul>
39-
<li>Now and next</li>
40-
<li>Release themes</li>
41-
<li>Feedback notes</li>
42-
</ul>
37+
<h2>Share</h2>
38+
<p>Expand publishing paths for games, assets, templates, tutorials, ratings and community knowledge as the creator loop matures.</p>
4339
</article>
4440
</div>
4541
</div>
4642
</div>
4743
</section>
44+
<section class="section">
45+
<div class="container card">
46+
<div class="card-body">
47+
<div class="kicker">GDD &rarr; Manifest &rarr; Engine</div>
48+
<h2>The roadmap is organized around manifest-driven creation.</h2>
49+
<p class="lede">The long-term path is to move from plain-English game design documents into structured manifests that the engine can execute.</p>
50+
<p>Future roadmap themes should push toward zero user code: game behavior, content rules, presentation, progression and sharing metadata all expressed through configuration instead of custom scripts.</p>
51+
</div>
52+
</div>
53+
</section>
4854
</main>
4955
<div data-partial="footer"></div>
5056
<script src="assets/js/gamefoundry-partials.js" defer></script>

0 commit comments

Comments
 (0)