Change Details

#### Description The Wikistories MediaWiki extension introduces visual stories as a new contribution format in a new namespace. A story is a list of frames, each with an image, text, references, and metadata. They are stored as page/revisions using a new StoryContent/StoryContentHandler. Stories are created, curated, and viewed using Vuejs apps with minimal no-js fallbacks. #### Preview environment On the beta cluster * Story builder: https://en.m.wikipedia.beta.wmflabs.org/wiki/Special:StoryBuilder/Apollo_12 * Story Viewer on article: https://en.m.wikipedia.beta.wmflabs.org/wiki/Apollo_12?wikistories=1#/story/274929 #### Which code to review The extension repo is https://gerrit.wikimedia.org/r/admin/repos/mediawiki/extensions/Wikistories #### Performance assessment Please initiate the performance assessment by answering the below: - What work has been done to ensure the best possible performance of the feature? -- Tried to keep the 'discover' module as light as possible since it runs on article views. Building HTML using jquery instead of loading Vuejs. Load the 'viewer' module dynamically later. -- Cache the rendered stories for each article in one bundle so the rest API return as quickly as possible. - What are likely to be the weak areas (e.g. bottlenecks) of the code in terms of performance? -- RL modules breakdown and content. -- Interaction with the Commons image search API - Are there potential optimisations that haven't been performed yet? -- We plan on caching the image search results and article content in the Story Builder so they don't reload every time the user navigates to those pages. -- We talked about a smarter cache invalidation approach when a new story is associated to an article but we don't have any plan about it. - Please list which performance measurements are in place for the feature and/or what you've measured ad-hoc so far. If you are unsure what to measure, ask the Performance Team for advice: [[ mailto:performance-team@wikimedia.org | performance-team@wikimedia.org ]]. -- There's no measurement in place but we are quite concerned about the time it takes to load the stories thumbnails below the title on article pages. We would welcome ideas to track that time and hopefully speed it up.

#### Description The Wikistories MediaWiki extension introduces visual stories as a new contribution format in a new namespace. A story is a list of frames, each with an image, text, references, and metadata. They are stored as page/revisions using a new StoryContent/StoryContentHandler. Stories are created, curated, and viewed using Vuejs apps with minimal no-js fallbacks. #### Preview environment On the beta cluster * Story builder: https://en.m.wikipedia.beta.wmflabs.org/wiki/Special:StoryBuilder/Apollo_12 * Story Viewer on article: https://en.m.wikipedia.beta.wmflabs.org/wiki/Apollo_12?wikistories=1#/story/274929 #### Which code to review The extension repo is https://gerrit.wikimedia.org/r/q/project:mediawiki%252Fextensions%252FWikistories #### Performance assessment Please initiate the performance assessment by answering the below: - What work has been done to ensure the best possible performance of the feature? -- Tried to keep the 'discover' module as light as possible since it runs on article views. Building HTML using jquery instead of loading Vuejs. Load the 'viewer' module dynamically later. -- Cache the rendered stories for each article in one bundle so the rest API return as quickly as possible. - What are likely to be the weak areas (e.g. bottlenecks) of the code in terms of performance? -- RL modules breakdown and content. -- Interaction with the Commons image search API - Are there potential optimisations that haven't been performed yet? -- We plan on caching the image search results and article content in the Story Builder so they don't reload every time the user navigates to those pages. -- We talked about a smarter cache invalidation approach when a new story is associated to an article but we don't have any plan about it. - Please list which performance measurements are in place for the feature and/or what you've measured ad-hoc so far. If you are unsure what to measure, ask the Performance Team for advice: [[ mailto:performance-team@wikimedia.org | performance-team@wikimedia.org ]]. -- There's no measurement in place but we are quite concerned about the time it takes to load the stories thumbnails below the title on article pages. We would welcome ideas to track that time and hopefully speed it up.

#### Description The Wikistories MediaWiki extension introduces visual stories as a new contribution format in a new namespace. A story is a list of frames, each with an image, text, references, and metadata. They are stored as page/revisions using a new StoryContent/StoryContentHandler. Stories are created, curated, and viewed using Vuejs apps with minimal no-js fallbacks. #### Preview environment On the beta cluster * Story builder: https://en.m.wikipedia.beta.wmflabs.org/wiki/Special:StoryBuilder/Apollo_12 * Story Viewer on article: https://en.m.wikipedia.beta.wmflabs.org/wiki/Apollo_12?wikistories=1#/story/274929 #### Which code to review The extension repo is https://gerrit.wikimedia.org/r/admin/repos/q/project:mediawiki/%252Fextensions/%252FWikistories #### Performance assessment Please initiate the performance assessment by answering the below: - What work has been done to ensure the best possible performance of the feature? -- Tried to keep the 'discover' module as light as possible since it runs on article views. Building HTML using jquery instead of loading Vuejs. Load the 'viewer' module dynamically later. -- Cache the rendered stories for each article in one bundle so the rest API return as quickly as possible. - What are likely to be the weak areas (e.g. bottlenecks) of the code in terms of performance? -- RL modules breakdown and content. -- Interaction with the Commons image search API - Are there potential optimisations that haven't been performed yet? -- We plan on caching the image search results and article content in the Story Builder so they don't reload every time the user navigates to those pages. -- We talked about a smarter cache invalidation approach when a new story is associated to an article but we don't have any plan about it. - Please list which performance measurements are in place for the feature and/or what you've measured ad-hoc so far. If you are unsure what to measure, ask the Performance Team for advice: [[ mailto:performance-team@wikimedia.org | performance-team@wikimedia.org ]]. -- There's no measurement in place but we are quite concerned about the time it takes to load the stories thumbnails below the title on article pages. We would welcome ideas to track that time and hopefully speed it up.