adobe / adobe/aem-project-archetype
Frontend module - automate fetching HTML for static dev server
- Dominant language
- JavaScript
- Stars
- 596
- Forks
- 431
- Avg merge
- 10d 6h
- Merged PRs (30d)
- 1
Description
Currently the FE development flow looks like this:
1. Author page you want to use for styling
3. Open that page in view as publish mode
4. Save page html in _index.html_
5. Run local web server to work on the given page
This could be automated a bit by a simple script that will update the content of the static html files, so the flow would look like
1. Author page you want to use for styling
2. Run something like `npm run syncStaticContent`
3. Run local web server
Contributor guide
Research direction
The issue names no implementation files. Start by locating the frontend module’s existing npm scripts and static HTML files, then confirm how the local web server consumes them. Done means a command such as npm run syncStaticContent fetches or updates the static HTML so the server can run without manually saving page HTML.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100