refresh landing, branding, and docs for trading focus (#46) (#47)

* docs(landing): refresh contribution and project guidance



* build(tradinggoose): adjust dev and image settings



* feat(tradinggoose): rebrand metadata and AI reference content



* fix(landing): tighten responsive layout and preview hydration



* feat(tradinggoose): clarify llms reference canonical repo



* chore(public): remove obsolete assets



* docs(readme): retitle google ai badge



* feat(landing): refresh hero ai prompt copy



---------

Co-authored-by: Codex <codex@openai.com>

Author: Bruz

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,91 @@
+# TradingGoose Studio Code of Conduct
+
+## Our Commitment
+
+TradingGoose Studio is an open-source project for technical LLM trading workflows.
+We want the project to be a professional, respectful, and useful place for
+developers, researchers, traders, designers, and contributors of all experience
+levels.
+
+Maintainers and contributors commit to making participation in the TradingGoose
+community harassment-free for everyone, regardless of age, body size,
+disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Expected Behavior
+
+Examples of behavior that strengthen the TradingGoose community include:
+
+- Treating other contributors with respect, patience, and professionalism
+- Critiquing ideas, code, and decisions without attacking people
+- Giving clear, actionable feedback in issues, pull requests, discussions, and chat
+- Sharing context, reproduction steps, and evidence when reporting bugs or disagreements
+- Assuming good intent first and asking clarifying questions before escalating
+- Respecting user privacy, project security, and confidential information
+- Helping keep discussion focused, technically useful, and welcoming to newcomers
+
+## Unacceptable Behavior
+
+Examples of unacceptable behavior include:
+
+- Harassment, intimidation, threats, discrimination, or hate speech
+- Trolling, personal attacks, dogpiling, or deliberately inflammatory behavior
+- Sexualized language, imagery, or unwanted sexual attention
+- Publishing another person's private information without explicit permission
+- Sharing credentials, API keys, tokens, account access, or sensitive financial data
+- Abusive behavior in code review, issue triage, support channels, or community chat
+- Impersonation, spam, or repeated off-topic disruption of community spaces
+
+## Maintainer Responsibilities
+
+Project maintainers are responsible for clarifying and enforcing this Code of
+Conduct. They may remove, edit, or reject comments, commits, code, wiki edits,
+issues, pull requests, discussions, or other contributions that are not aligned
+with this policy.
+
+Maintainers will aim to act fairly, consistently, and proportionally. When
+appropriate, they will communicate moderation decisions and next steps.
+
+## Scope
+
+This Code of Conduct applies across TradingGoose community spaces, including:
+
+- This GitHub repository and related repositories
+- Issues, pull requests, discussions, and code review
+- Documentation sites and examples maintained by the project
+- Official Discord, social accounts, and other project-managed communication channels
+- Events, demos, livestreams, or public conversations where someone is representing TradingGoose
+
+## Reporting
+
+If you experience or witness behavior that violates this Code of Conduct, report
+it to the maintainers at <bruzzz@tradinggoose.ai>.
+
+Please include relevant context when possible:
+
+- What happened
+- Where it happened
+- Links, screenshots, or logs if available
+- Whether there is any immediate safety or security concern
+
+Reports will be reviewed promptly and handled as confidentially as practical.
+We will prioritize the safety and privacy of the reporter and affected parties.
+
+## Enforcement Guidelines
+
+Maintainers may respond with any action they consider appropriate, including:
+
+1. Private clarification or warning
+2. Request to stop specific behavior
+3. Removal of content or comments
+4. Temporary restriction from project spaces
+5. Permanent ban from some or all project spaces
+
+The response will depend on severity, pattern of behavior, impact on the
+community, and any security or privacy implications.
+
+## Attribution
+
+This policy is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/),
+version [2.1](https://www.contributor-covenant.org/version/2/1/code_of_conduct/).

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,25 +1,47 @@
 ## Summary
-Brief description of what this PR does and why.
+<!-- What changed? Keep this concrete. -->
 
-Fixes #(issue)
+## Why
+<!-- Why is this change needed? What problem does it solve? -->
 
-## Type of Change
-- [ ] Bug fix
-- [ ] New feature  
-- [ ] Breaking change
-- [ ] Documentation
-- [ ] Other: ___________
+## Affected Areas
+<!-- Check all that apply. -->
+- [ ] `apps/tradinggoose`
+- [ ] `apps/docs`
+- [ ] `packages/*`
+- [ ] Workflows / execution
+- [ ] Realtime / sockets
+- [ ] Market data / charting
+- [ ] Dev tooling / CI / infra
+- [ ] Documentation only
+- [ ] Other:
 
-## Testing
-How has this been tested? What should reviewers focus on?
+## Issue Links( if any )
+<!-- Example: Fixes #123 -->
+
+## Validation
+<!-- List the exact commands you ran and the result. -->
+```bash
+# example
+bun run test
+bun run type-check
+```
+
+## Risk / Rollout Notes
+<!-- Call out breaking changes, rollout concerns, follow-up work, or backout plan. -->
+
+## Config / Data Changes
+<!-- Delete lines that do not apply. -->
+- Env vars added or changed:
+- Database schema or migration impact:
+- External services or provider behavior changed:
+
+## Screenshots / Video
+<!-- Required for visible UI changes. Include before/after when useful. -->
 
 ## Checklist
-- [ ] Code follows project style guidelines
-- [ ] Self-reviewed my changes
-- [ ] Tests added/updated and passing
-- [ ] No new warnings introduced
-- [ ] I confirm that I have read and agree to the terms outlined in the [Contributor License Agreement (CLA)](./CONTRIBUTING.md#contributor-license-agreement-cla)
-
-## Screenshots/Videos
-<!-- If applicable, add screenshots or videos to help explain your changes -->
-<!-- For UI changes, before/after screenshots are especially helpful -->
+- [ ] I kept the change focused and reviewed my own diff
+- [ ] I validated the change locally and documented the results above
+- [ ] I updated docs, examples, or copy if behavior/user-facing flows changed
+- [ ] I called out any env, schema, provider, or rollout impact
+- [ ] I did not include secrets, tokens, or private credentials in this PR

README.md

@@ -9,7 +9,7 @@
 </p>
 
 <p align='center'>
-  <a href="https://google.com/ai?q=I+am+using+TradingGoose-Studio+from+https%3A%2F%2Fgithub.qkg1.top%2FTradingGoose%2FTradingGoose-Studio.+How+do+I+automate+a+strategy+using+this+library" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/ASK%20google%20gemini-8E75B2?style=for-the-badge&logo=google%20gemini&logoColor=white" alt="Gemini"></a>
+  <a href="https://google.com/ai?q=I+am+using+TradingGoose-Studio+from+https%3A%2F%2Fgithub.qkg1.top%2FTradingGoose%2FTradingGoose-Studio.+How+do+I+automate+a+strategy+using+this+library" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/ASK%20google%20AI-8E75B2?style=for-the-badge&logo=google%20gemini&logoColor=white" alt="Gemini"></a>
 <a href="https://perplexity.ai?q=I+am+using+TradingGoose-Studio+from+https%3A%2F%2Fgithub.qkg1.top%2FTradingGoose%2FTradingGoose-Studio.+How+do+I+automate+a+strategy+using+this+library" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/ASK%20perplexity-088F8F?style=for-the-badge&logo=perplexity&logoColor=000000" alt="Perplexity"></a>
 </p>
 
@@ -29,6 +29,13 @@
 TradingGoose Studio is an **AI workflow platform for technical LLM trading**, it combines both technical + LLM analysis for your trading decision.
 It is built for analytics, research, charting, monitoring, and workflow automation. 
 
+> **Early Stage Notice**
+>
+> TradingGoose Studio is still in a very early development stage.
+> You should expect rough edges, incomplete features, and a meaningful number of bugs.
+> Breaking changes are normal at this stage and may happen very frequently, including on a near-weekly basis.
+> If you are building on top of the project, expect to update your setup, workflows, and integrations often.
+
 
 
 <picture>
@@ -46,7 +53,7 @@ It is built for analytics, research, charting, monitoring, and workflow automati
 
 ### Requirements
 
-- **Bun** v1.2+
+- **Bun** v1.3+
 - **Docker** (for PostgreSQL)
 - **Colima** or **Docker Desktop** (macOS)
 
@@ -82,6 +89,23 @@ bunx drizzle-kit migrate --config=./drizzle.config.ts
 cd ../..
 bun run dev:full
 ```
+
+## Contributing
+
+Pull requests are welcome.
+
+If you want to improve TradingGoose Studio, fix a bug, tighten the docs, or ship
+an idea that makes the platform better for traders and builders, open a PR.
+Small, focused changes are preferred and easier to review.
+
+This project is moving quickly and is expected to have bugs and frequent breaking
+changes. Contributors should expect the codebase, interfaces, and workflows to
+change often, sometimes week to week.
+
+- Read the [Contributing Guide](.github/CONTRIBUTING.md) for setup, workflow, and PR expectations
+- Review the [Code of Conduct](.github/CODE_OF_CONDUCT.md) before participating in project spaces
+- Open an issue first if you want feedback on larger changes or architecture work
+
 | Tech Stack       |                                                                                                                                                                                                                                                                                                                                                                                                                           |
 | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Framework        | <a href="https://nextjs.org/" target="_blank" rel="noopener noreferrer"><img src="https://img.shields.io/badge/Next-black?style=for-the-badge&logo=next.js&logoColor=white" alt="Next.JS"></a>                                                                                                                                                                                                                                |
@@ -130,5 +154,5 @@ terms that continue to apply to that directory.
 ---
 
 <p align="center">
-  Built with ❤️ by the TradingGoose Team
+  <b>HONK !</b>
 </p>

apps/tradinggoose/app/(landing)/components/feature/components/landing-canvas/landing-flow.tsx

@@ -8,13 +8,13 @@ import { LandingNode } from './landing-block/landing-node'
 import { CARD_WIDTH, type LandingCanvasProps } from './landing-canvas'
 import { LandingEdge } from './landing-edge/landing-edge'
 
-const nodeTypes = {
+const landingNodeTypes = {
   landing: LandingNode,
   landingLoop: LandingLoopNode,
   group: LandingLoopNode,
 }
 
-const edgeTypes = { landingEdge: LandingEdge }
+const landingEdgeTypes = { landingEdge: LandingEdge }
 
 /**
  * Props for the LandingFlow component
@@ -41,6 +41,9 @@ export function LandingFlow({
   const { setViewport, getViewport } = useReactFlow()
   const [rfReady, setRfReady] = React.useState(false)
   const [localNodes, setLocalNodes] = React.useState(nodes)
+  // Stabilize across HMR re-evaluations — React Flow warns on ref change.
+  const nodeTypes = React.useMemo(() => landingNodeTypes, [])
+  const edgeTypes = React.useMemo(() => landingEdgeTypes, [])
 
   // Update local nodes when props change
   React.useEffect(() => {

apps/tradinggoose/app/(landing)/components/feature/components/workflow-preview/workflow-preview-canvas.tsx

@@ -28,8 +28,14 @@ import {
 import { resizeContainerNodes } from '@/widgets/widgets/editor_workflow/components/workflow-editor/canvas/node-position-utils'
 import { WorkflowRouteProvider } from '@/widgets/widgets/editor_workflow/context/workflow-route-context'
 
-const nodeTypes = importedNodeTypes
-const edgeTypes = importedEdgeTypes
+// importedNodeTypes / importedEdgeTypes are module-level constants in
+// block-registry.ts. In dev, Turbopack HMR re-evaluates that module on any
+// edit to its transitive imports, producing a new object identity which
+// trips React Flow's nodeTypes-changed warning. In production these remain
+// stable. Kept aliased for call-site readability; actual stabilization
+// happens via useMemo inside WorkflowPreviewFlow.
+const nodeTypesImport = importedNodeTypes
+const edgeTypesImport = importedEdgeTypes
 
 const LANDING_WORKSPACE_ID = 'landing-preview'
 const LANDING_WORKFLOW_ID = 'landing-workflow'
@@ -253,6 +259,11 @@ type WorkflowPreviewCanvasProps = {
 type WorkflowPreviewFlowProps = Omit<WorkflowPreviewCanvasProps, 'workflowKey'>
 
 function WorkflowPreviewFlow({ workflowState, className }: WorkflowPreviewFlowProps) {
+  // Capture types once per mount so the ref stays identical across re-renders
+  // even if HMR rebuilds block-registry and swaps the imported object.
+  const nodeTypes = useMemo(() => nodeTypesImport, [])
+  const edgeTypes = useMemo(() => edgeTypesImport, [])
+
   const previewSeed = useMemo(() => {
     const initialBlocks = workflowState.blocks
     const initialNodes = buildPreviewNodes(workflowState)

apps/tradinggoose/app/(landing)/components/feature/feature.tsx

@@ -106,8 +106,14 @@ function FeatureRowSection({
           'card group group/feature relative isolate m-1 overflow-hidden rounded-lg bg-foreground/10 p-px transition-all duration-300 ease-in-out lg:col-span-2',
           contentOrder
         )}
+        // useCardGlow() mutates --shine-x/--shine-y on this .card node
+        // imperatively on every mousemove, and Framer Motion renders
+        // initial `opacity: 0` as a string in SSR vs number on the client.
+        // Both are known-benign mismatches; skip hydration diffing here.
+        motionProps={{ suppressHydrationWarning: true }}
       >
         <div
+          suppressHydrationWarning
           className='blob absolute top-0 left-0 h-[120px] w-[120px] rounded-full opacity-0 blur-xl transition-all duration-300 ease-in-out'
           style={{ backgroundColor: 'hsl(var(--primary) / 0.7)' }}
         />
@@ -162,7 +168,7 @@ function FeatureRowSection({
         transition={{ duration: 0.75 }}
         delay={index * 0.12 + 0.15}
         className={cn(
-          'flex min-h-[40vh] w-full lg:col-span-3 lg:h-full lg:min-h-0',
+          'flex h-[60vh] min-h-[560px] w-full lg:col-span-3 lg:h-full lg:min-h-0',
           previewOrder,
           previewIsLeft ? 'lg:justify-start' : 'lg:justify-end'
         )}
@@ -202,7 +208,7 @@ export default function Feature() {
         />
       </div>
 
-      <div className='mx-auto px-12 sm:px-6 lg:px-20 xl:px-24'>
+      <div className='px-4 sm:px-6 lg:px-20 xl:px-24'>
         <div className='mx-auto max-w-3xl text-center'>
           <MotionPreset
             fade

apps/tradinggoose/app/(landing)/components/footer/footer.tsx

@@ -1,6 +1,6 @@
 import Image from 'next/image'
 import Link from 'next/link'
-import { DiscordIcon, GithubIcon, LinkedInIcon, xIcon as XIcon } from '@/components/icons/icons'
+import { DiscordIcon, GithubIcon } from '@/components/icons/icons'
 import FooterHoverText from '@/app/(landing)/components/footer/footer-hover-text'
 import { soehne } from '@/app/fonts/soehne/soehne'
 
@@ -72,24 +72,6 @@ export default function Footer({ fullWidth = false }: FooterProps) {
               >
                 <DiscordIcon className='h-5 w-5' aria-hidden='true' />
               </a>
-              <a
-                href='https://x.com/simdotai'
-                target='_blank'
-                rel='noopener noreferrer'
-                aria-label='X (Twitter)'
-                className='transition-colors duration-300 hover:text-foreground'
-              >
-                <XIcon className='h-[18px] w-[18px]' aria-hidden='true' />
-              </a>
-              <a
-                href='https://www.linkedin.com/company/tradinggoose/'
-                target='_blank'
-                rel='noopener noreferrer'
-                aria-label='LinkedIn'
-                className='transition-colors duration-300 hover:text-foreground'
-              >
-                <LinkedInIcon className='h-[18px] w-[18px]' aria-hidden='true' />
-              </a>
               <a
                 href='https://github.com/TradingGoose/TradingGoose-Studio'
                 target='_blank'
@@ -119,8 +101,8 @@ export default function Footer({ fullWidth = false }: FooterProps) {
             </div>
           </div>
 
-          <div className='text-sm sm:max-w-[28rem] sm:self-start lg:items-end'>
-            <div className='grid grid-cols-4 gap-x-8 gap-y-3 sm:gap-x-12'>
+          <div className='order-first text-sm max-sm:text-center sm:max-w-[28rem] sm:self-start lg:order-none lg:items-end'>
+            <div className='grid grid-cols-3 gap-x-8 gap-y-3 sm:grid-cols-4 sm:gap-x-12'>
               {productLinks.map((link) =>
                 link.external ? (
                   <a
@@ -149,7 +131,7 @@ export default function Footer({ fullWidth = false }: FooterProps) {
 
         <div
           aria-hidden='true'
-          className='-translate-x-1/2 -translate-y-8 -pt-8 sm:-pt-16 absolute left-1/2 z-0 w-full max-w-70 overflow-hidden'
+          className='-translate-x-1/2 -translate-y-8 -pt-8 sm:-pt-16 absolute left-1/2 z-0 hidden w-full max-w-70 overflow-hidden sm:block'
         >
           <FooterHoverText text='HONK!' />
           <div