Documentation should reflect new project name
See original GitHub issueIn the README, there are a bunch of stale references to blockstack-portal
when the repository at some point was renamed blockstack-browser
. GitHub will do all the redirects properly, so the difference doesn’t seem to have technical problems, but it is a reflection of out of date documentation. Out of date docs can be confusing to new users and generally “smells”.
I’m happy to go through and make the updates if you all agree that this should be done.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
How to Manage Project Documentation Throughout Your Project
Project documentation can be a major pain point for teams. Find out how you can manage project documentation better with a dedicated software....
Read more >SWA URLs reflect PackageId, not project name #26055 - GitHub
According the documentation path should be: _content/[LIBRARY NAME]/[PATH UNDER WWWROOT] . Which looks good to me and was working before. But ...
Read more >18. Project Completion – Project Management – 2nd Edition
The key activities in project completion are gathering project records; disseminating information to formalize acceptance of the product, service, or project; ...
Read more ><Project Name> Change Management plan - DoIT
<Project Name> ... The Change Management Plan documents how changes will be proposed, ... the Project Scope Statement should reflect the updated scope....
Read more >Solved You will use your previous programming project as a
Be sure to copy and rename your file from that project and edit the internal documentation to reflect the new name and date....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Closing this thanks to @freethejazz 's pull request which updated the old name references. This will ship in 0.16.
👍 In that case, the PR is ready to merge. Good luck on the rest of your prep work for the release, and I’m happy to help out on chores or front-end stuff if you need a hand.