docs(paas-native): restructure and expand the FAQ - #2518
Open
Sandor Akszenovics (axasanya) wants to merge 6 commits into
Open
Sandor Akszenovics (axasanya) wants to merge 6 commits into
Sandor Akszenovics (axasanya) wants to merge 6 commits into
Conversation
Group the questions into 12 thematic sections and add coverage for the topics that currently drive support tickets and RFP questions: backups and recovery, availability and maintenance, resource overage, security and data protection, migration, rollback, build-versus-deploy, extension removal and Shopware upgrades. Also corrects answers that were wrong or incomplete, including zero-downtime deployments, custom domain DNS and Tideways support, and aligns the availability and overage answers with the published PaaS Native Supplementary Agreement.
Developer Docs healthcheckStatus: Waiting for approval from someone with write access. Fork PRs need approval from a maintainer with write access before the healthcheck can run. GitHub approves only the latest commit, so every new commit pushed after approval needs another approval. |
Reword six terms aspell does not recognise, and add the domain acronyms to .wordlist.txt (sorted).
Tideways setup is now documented, so replace the placeholder with the actual configuration, note the shop-application-only restriction, and cover the Blackfire/Tideways/tracing exclusivity in one answer.
…rite # Conflicts: # products/paas/shopware/faq.md
stabilise -> stabilize, unauthorised -> unauthorized, and reword two constructions the dictionary does not recognise.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reworks the PaaS Native FAQ from a flat list into 12 thematic sections, and expands it from 29 to 84 questions. The additions cover topics that currently come in through support tickets, security questionnaires and RFPs but had no documented answer.
New topic areas
Corrections to existing answers
Alignment with the contract
The availability and overage answers follow the published PaaS Native Supplementary Agreement, including the Clause 2.3 exclusion of developer tooling from the uptime target and the three-month evaluation period for overage.
Where a topic has no guide yet — CI/CD pipeline examples, migration, automated rollback, Tideways setup — the FAQ says so in an
:::infocallout rather than leaving the gap silent.Related links
Checklist
PageRefreferences where relevant..gitbook.yamlif pages were moved, renamed, or deleted. — n/a, no pages moved.wordlist.txt(and sorted it) if spellcheck flags new legitimate terms. — no new termsNotes
Single file, no pages added or moved. All 24 relative links and 3 internal anchors resolve.
Question headings moved from
##to###so the new section headings can use##. Deep links to individual question anchors are unaffected where the question wording is unchanged.Two answers restate commitments that are not in the public Supplementary Agreement and need sign-off before merge: the RTO/RPO of 24 hours, and the "CVSS above 9.0, mitigation begins within one working day" patching statement. Happy to drop both if they should not be public.