Skip to content

Create Code Push guide for Flutter applications - #616

Open
dawn-ducky wants to merge 6 commits into
mainfrom
dawn-ducky-patch-2
Open

Create Code Push guide for Flutter applications#616
dawn-ducky wants to merge 6 commits into
mainfrom
dawn-ducky-patch-2

Conversation

@dawn-ducky

Copy link
Copy Markdown
Contributor

Added a comprehensive guide for implementing Code Push in Flutter applications, covering setup, patching, and compliance with app store guidelines.

Status

READY/IN DEVELOPMENT/HOLD

Description

Added a comprehensive guide for implementing Code Push in Flutter applications, covering setup, patching, and compliance with app store guidelines.
Updated headings for consistency and improved clarity. Added import statements for Image and LinkCard components.
@dawn-ducky
dawn-ducky marked this pull request as ready for review August 11, 2026 14:46
- Fix Prettier formatting in code-push-guide.mdx
- Fix Vale style errors: lowercase 'flutter' → 'Flutter', remove
  exclamation mark, convert first-person to second-person voice,
  fix heading to sentence case, fix 'code push' → 'Code Push'
- Add 'wagus' and 'gallego' to cspell allowed words
@AbhishekDoshi26

Copy link
Copy Markdown
Member

The PR had failing CI and the assets were not loading. Have fixed both of the issues

@AbhishekDoshi26 AbhishekDoshi26 added the documentation Improvements or additions to documentation label Aug 12, 2026
@tomarra

tomarra commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

I think content and everything looks good, just questioning where it should go in the sidebar. Its kind of a mix of a lot of the pages we already have so not sure what the answer is but where it currently sits also feels buried.

CleanShot 2026-08-12 at 08 30 08@2x

@AbhishekDoshi26

Copy link
Copy Markdown
Member

How about moving it under Guides section?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants