-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
Before launch
- Review the approach to redirects ie 301 vs 302
- Address FIXMEs in the code
- Validate rendered HTML / CSS
- Test accessibility further (Lighthouse, manual testing)
- CHANGELOG.md with API changes
- Analytics (Matomo)
- Decide how to handle 'RFC Link Previews' with regard to analytics... will this feature —although useful— affect RFC page view stats because fewer people don't open the RFC page anymore? ie should RFC Link Previews just trigger a page view count for that RFC?
- Will URL changes (ie trailing slash) affect analytics? ie RFC page view count before and after would be nice to compare. Is there anything to do here?
- Ensure HTTP headers allow for long cache times
- JSON-LD?
- Ensure eg https://www.rfc-editor.org/rfc/rfc1234.html has canonical HTTP header
Infra
- Nuxt prod w/ CDN in front, envs for Red API server URL
- CDN reverse proxy of
/rpc/wiki/
- CDN reverse proxy of
- Red API server
- static.rfc-editor.org bucket/store and CDN
- Staging environment?
Metadata
Metadata
Assignees
Labels
No labels