Skip to content

Conversation

@mtgr18977
Copy link
Collaborator

Moved existing documentation to backup-old-docs/ to archive previous versions. Added new introduction and supported platforms documentation under introduction/, and updated .gitignore to include Vale linter and GitBook development files.

Moved existing documentation to backup-old-docs/ to archive previous versions. Added new introduction and supported platforms documentation under introduction/, and updated .gitignore to include Vale linter and GitBook development files.
@Fishbowler
Copy link
Collaborator

We don't want this merging yet, right?
It'd destroy the current docs site.

@mtgr18977
Copy link
Collaborator Author

@Fishbowler no, this is the staging new documentation site.
Don't merge at all.

@mtgr18977
Copy link
Collaborator Author

We will work only on this branch, separated from the main documentation site.

@Fishbowler
Copy link
Collaborator

@mtgr18977 Mind if I kick the PR into draft, just in case someone gets clicky?

@Fishbowler
Copy link
Collaborator

Also, let me know when you want reviews

@mtgr18977
Copy link
Collaborator Author

@mtgr18977 Mind if I kick the PR into draft, just in case someone gets clicky?

Not at all. Just kick it.

@mtgr18977
Copy link
Collaborator Author

Also, let me know when you want reviews

You can start reviewing any time you want.
In fact, this is better for us, since we can ensure the right tone and address any technical issue regarding our docs.

@mtgr18977 mtgr18977 marked this pull request as draft December 19, 2025 16:56
@mtgr18977
Copy link
Collaborator Author

@Fishbowler
Already converted to draft :)

Copy link
Collaborator

@Fishbowler Fishbowler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A quick pass of the first couple of files

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Maestro cloud" => "Maestro Cloud" throughout this one.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will put this on out linter to avoid new errors.

mtgr18977 and others added 16 commits December 22, 2025 10:46
Reorganized SUMMARY.md to group content under new sections such as Introduction, Maestro Studio, Maestro CLI, Cloud, Flows, Command Reference, Best Practices, Javascript With Maestro, Use Cases, Troubleshooting, and Community. This update streamlines navigation and reflects a more logical documentation structure.
Removed front matter from README.md and reformatted the strategic note in cloud.md to use a hint block for improved clarity and consistency in documentation.
Revised README.md for improved clarity, grammar, and branding consistency. Updated cloud infrastructure references and reworded feature descriptions for readability. Changed SUMMARY.md to rename the main documentation link to 'What is Maestro?'.
Replaced plain note text with styled hint blocks in Maestro MCP, Maestro Studio, repository config, and web browser support documentation for improved readability and consistency.
Changed hint styles in several documentation files for consistency (e.g., 'info' to 'warning' or 'success'). Added clarification on UI interaction patterns in Jetpack Compose support documentation. Improved formatting and accuracy in installation and configuration instructions.
Updated headings for clarity in CLI and cloud documentation, improved link formatting in Maestro MCP introduction, and restructured feature descriptions in Maestro Studio documentation for better readability.
Corrected and reorganized links for Android Native and Web Browsers in the supported platforms section to improve navigation and accuracy.
Reordered 'What is Maestro?' in SUMMARY.md for better navigation. Enhanced formatting in maestro-studio.md by bolding feature headings for clarity. Streamlined section titles in uikit.md to improve readability and consistency.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants