Best Practice for developer working environment and workflow

Like (0) Share

Report

Posted on 10 Oct 2024 16:11:52 by dgray304

150

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

Categories:

General

All responses (2)

Answers (1)

Verified answer

dgray304 150 on 19 Oct 2024 at 15:46:21

Like (1)

Report

Best Practice for developer working environment and workflow

SaiRT14,

Great! Thanks. That is what I settled on as well, after many different attempts at workflow.

I will also try to set up a github action to push to PPDS/PPMA automatically when it receives a push from vscd.

My hope is we hear from more dev's and this will be a good working document for dev workflow, as a "Best Practice" for developers.

It is really frustrating when your new and things don't work the way you expect. So having some guidance is great for newb's. I wasted a lot of time trying to figure it out.

I really appreciate it SaiRT14.

Now we need to figure out the best way to keep all things in SYNC (vscd, github repo, PPMA, PPDS).

So what we do in VS Code Desktop (vscd) is implemented and is reflected in our PPDS Preview in near realtime, so we can be efficient.

Thanks again,

Doug

P.S. I FORGOT TO SET SaiRT14 POST as "ANSWERED", BUT I CAN'T EDIT HIS POST TO MARK "ANSWERED". SO I AM MARKING THIS ONE SO DEVELOPERS WILL LOOK AT IT.
Suggested answer

SaiRT14 1,966 Super User 2025 Season 1 on 19 Oct 2024 at 13:42:32

Like (0)

Report

Best Practice for developer working environment and workflow

Good question - here what i know are the best practices:

-- VS Code Desktop + GitHub Repo + PAC CLI + PPDS for Liquid Preview

--Code Locally in VS Code Desktop

--Push to GitHub

--Sync with Power Pages using PAC CLI

--Preview in PPDS

--Preview in PPDA/Power Pages Management App

Community site session details

Best Practice for developer working environment and workflow

Helpful resources

News and Announcements

Quick Links

Announcing the Engage with the Community forum!

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Warren Belz – Community Spotlight

Leaderboard > Power Pages - General Discussions

Featured topics

Product updates

Community site session details

Best Practice for developer working environment and workflow

Helpful resources

News and Announcements

Quick Links

Announcing the Engage with the Community forum!

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Warren Belz – Community Spotlight

Subscribe to this forum!

Select categories

Leaderboard > Power Pages - General Discussions

Featured topics

Product updates