* Deleting an account or org, new topic to replace a support article
Signed-off-by: Lena Larionova <lena.larionova@docker.com>
* Removed steps for deleting repos
Fixed everything from comments
* renamed topic from delete to deactivate
Signed-off-by: Lena Larionova <lena.larionova@docker.com>
* Access token doc (#1323)
Doc for personal access tokens on Hub
* release note for access tokens
Signed-off-by: Lena Larionova <lena.larionova@docker.com>
* Updates to the billing UI for personal plans
Signed-off-by: Lena Larionova <lena.larionova@docker.com>
* Changing a link to the billing page
Signed-off-by: Lena Larionova <lena.larionova@docker.com>
* Updating the Docker Hub screenshots to current version of Hub and various page cleanup
Signed-off-by: Lena Larionova <lena.larionova@docker.com>
* Missed one instance of unnecessary capitalization
https://github.com/docker/docs-private/issues/1151
* Docker Store references
* Incorrect DCI references
* Docker Enterprise Edition references
* Removing "Private repo" requirement which is _not actually true and has mislead / frustrated many partners_
* Removing SLA - This has never been enforced, to the extent that we don't even have Certification requirements around resolving the CVE's anymore!
* Deleted DCI reference, because it is wildly inaccurate :)
* Program Guide URL
* Listing fee is a lie.. we've kept that up for 3+ years, time to let it go!
* Removing old versioning which is irrelevant 2 years later..
Just a note... much of this look extremely redundant with the Publisher FAQ's. Also, there's no link to this page at all within the doc's tree. There's only a lone link to it at the end of another doc's section.. not sure if this page was intended to be shut down? If not, we ought to get it pulled back into the tree again.
* Update customer_faq.md
Quick hit edits to User FAQ
* Remove Docker EE references
* Added Community vs. Verified profile Question
* Q1 2018 product teaser removed.
* Buy / purchase references adjusted to "Subscription" / "subscribe"
* Removed "How can I become a Publisher" because it was redundant with Publisher FAQ, Publisher onboarding, etc. other pages...
* Payment details -> I'm moving this entire section over to the "Upgrade your Plan" section. Pay via Docker deprecation means that content is _not purchased_ via Hub any longer. Additionally, for some time Docker Enterprise has _not been sold_ through Hub. Don't see any reason to keep this whole section here. _If anything, this would need to be a part of Digital / SaaS documentation._ I'm assuming that's tracked elsewhere and there's no dependency. Given all that, I think "Upgrade your Plan" is the only other sensible place for this content to live.. as it is the only other current place where payments are being made, and I don't see any similar references to billing in that section.
* Make headings consistent
* Moving Billing FAQs from Customer FAQ section
This whole section is completely out of place under customer FAQ. Seems to only be relevant to this Plan upgrade page, given this is the only current place in Hub where I can make a payment for anything.
https://github.com/docker/docs-private/pull/1155 for more context
* Update upgrade.md
* Adding Release Notes commentary
Per HUB-1827, we discovered a Hub feature which is *very valuable* to partners & customers, but was not previously documented. Given that we only discovered this because _one partner_ was made aware by _one partner manager_, it is a great example of tribal knowledge we can disseminate via proactive documentation.
Adding to the FAQ's now so it will not be lost / forgotten. In a more comprehensive revision, this could easily be situated in a dedicated "Publisher Portal Usage Docs" section.
* Minor edit
As noted in issue #6684 `CACHE_TAG` environment variable is actually empty in the builds, turns out the documented value is represented by a `DOCKER_TAG` variable instead.
Hub backend dose not support `Create multiple Docker tags from a single build`. Take it off from the docs. Already received several issues asking about why it is not working according to the doc.
