Skip to content

Add GitHub Actions workflow for Nuxt deployment - #3356

Closed
lanewreachoutinc-boop wants to merge 1 commit into
vinta:masterfrom
lanewreachoutinc-boop:master
Closed

lanewreachoutinc-boop wants to merge 1 commit into
vinta:masterfrom
lanewreachoutinc-boop:master

Conversation

@lanewreachoutinc-boop

@lanewreachoutinc-boop lanewreachoutinc-boop commented Sep 25, 2026 •

Copy link
Copy Markdown

This workflow automates the build and deployment of a Nuxt site to GitHub Pages, including steps for detecting the package manager, setting up Node.js, and generating static HTML.

Project

project-name

Checklist

  • I read CONTRIBUTING.md - awesome-python is a shortlist, not a catalog
  • One project per PR
  • PR title format: Add project-name
  • Entry format: - [pypi-name](https://github.com/owner/repo) - Description ending with period.
  • Display name is the PyPI package name
  • Placed in an existing use case (new sections and subcategories are maintainer-only)
  • Meets all Quality Requirements: active, stable, documented, at least 1 month old

Which Tier

Pick one:

  • Obvious choice - a tool an experienced Python developer would name when asked "what do I use for this?"
  • Challenger - not yet the obvious choice, but a credible successor to one. Give adoption-trajectory evidence, not popularity alone.

Explain:

Displacement

If the use case is at its cap, name the entry your project replaces and argue that yours does that entry's job better. One in, one out.

This workflow automates the build and deployment of a Nuxt site to GitHub Pages, including steps for detecting the package manager, setting up Node.js, and generating static HTML.
@vinta vinta closed this Sep 25, 2026
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.

2 participants