Blog to JAMStart
I reached a point in my blog site development PennockProjects.com where the specific content and customizations made it a poor starter template for the additional content-specific sites I envisioned. With that, the JAMStart project was born. I forked my blog repo, turned it private, and created a new public repo called 'JAMStart'. JAM is an acronym for JavaScript API Markup.
What follows are issues and choices I made in creating JAMStart.
Philosophy - Copy Not Linked
The JAMStart project is a starter template project for a new Nuxt Markdown site. It is not intended for a long-term sync/upstream relationship. You own this code going forward, warts 😦 and wonders 😍 both. I do intend to keep JAMStart up to date and will blog about migration issues and new features, but if you want to include any of the new stuff after you have copied, you will have to upgrade manually.
Simplification
Git Repos
My plan to fork my blog repo to JAMstart was:
- Make a new repo on GitHub, GitLab, etc. SecondProject
- Locally clone your original project FirstProject (or a single branch) Then use git pull on the FirstProject branches you need to move to the second repo.
git remote set-url origin git@github.com:yourname/SecondProject.git- Push it
Files Separation
Blog Files
Blog Articles
- I removed
FigureCaption ComponentandMonkInset Componentarticles and left them in JAMStart
Blog Content Components
FigureCaptionMonkInset
JamStart Files
JAMStart Blog
JAMStart Articles
- I kept
FigureCaption ComponentandMonkInset Componentarticles as the two 'base' articles and to remind anyone who uses JAMStart what custom components are included.
JAMStart Content Components
FigureCaptionMonkInset