SSWConsulting / SSWConsulting/SSW.Website
📄 Migration - Track Migrated Pages
Open
Nobody has claimed this yet.
v3-Migration
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
As we migrate pages from the old website, they should be zz'ed in a duplicate/separate branch of the v1 website. This way we can track whats been migrated and what is left
### Tasks
- [x] zz consulting pages
- [x] zz offices pages
- [x] zz any other pages we have migrated
- [x] Create issues for pages that haven't been migrated (check that they dont already exist)
- [x] Create Excel spreadsheet with pages migrated + to migrate
- [ ] Reply done to "Re: SSW Web API - Where it should be used"
If there are any pages that dont look relevant to migrate, check with @wicksipedia then zz them if he agrees
Acceptance Criteria
- Every page has been
- migrated then zz'ed
- The PO's have agreed to not migrate it, then zz'ed
- moved to a new issue (and linked)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.