Changes between Initial Version and Version 1 of Ticket #4814, comment 23
- Timestamp:
- 04/02/2020 12:33:58 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #4814, comment 23
initial v1 1 1 We can't move (further) away from server-side rendering unless we have a pre-rendering/isomorphic solution in place. Given that's unlikely to happen (and that it'd be an equivalent amount of effort just to do this right), then we need to make this crawlable, indexable and accessible. Relying on fudges and no-js hacks isn't a viable option. We need the behaviour to be correct and optimal without JS, and then to layer in progressive enhancement. Anything else will (continue to) damage our discoverability, market share, reputation, etc. 2 2 3 An oedotally, we're already seeing examples where the current approach causes unforeseen issues because it's over-engineered. E.g., our recent addition of lazy loading for images was ineffectual, because we load theme tiles in an unnecessarily complex manner. We're likely to unearth ''hundreds'' of such issues as we try and get best practices in place for SEO and accessibility.3 Anecdotally, we're already seeing examples where the current approach causes unforeseen issues because it's over-engineered. E.g., our recent addition of lazy loading for images was ineffectual, because we load theme tiles in an unnecessarily complex manner. We're likely to unearth ''hundreds'' of such issues as we try and get best practices in place for SEO and accessibility. 4 4 5 5 Our simplest option is to use a server-side solution which behaves like a conventional WordPress archive (posts per page, pagination, adaptive metadata, etc). On top of that, we can add a JS solution for lazy-loading additional pages as the user scrolls.