I've been bouncing around a bit trying to define an efficient workflow for working on power pages (PP).
I would like to know what the Best Practice for developers working env and workflow.
Here are some scenarios I have been trying:
Scenario |
Thoughts |
Working directly in Power Pages Design Studio (PPDS) |
Insufficient |
Working in VS Code for the web > then sync/preview inside PPDS |
Very slow process (sync/preview). Many Extensions disabled. No in-editor preview, no github or github copilot. |
VS Code Desktop > using pac CLI to up/down > PPDS to preview with Liquid rendered. |
Benefit from preview and live Server, many more Extensions . Preview liquid in PPDS for liquid render. |
VS Code for web > github repo > PPDS sync/preview |
Still missing local preview, extensions, but now have version control |
VS Code desktop > github repo > PPDS |
Get preview (fast), version control, automate upload, liquid preview in PPDS |
Not exactly sure where power pages management app (PPMA) fits in. I figure to use it for admin actions. Like switching page templates to try different web templates.
NOTE: A consideration is filename naming conventions. I noticed that VS Code for the web does not accept underscores. That should be taken into account for env setup.
I would like to here from developers. What have you found to be the best developer workflow environment.
This will definitely be beneficial to new dev's.
Doug