Requirements

• Submission ("resource") must have a title, active link and description
• You must be an author or someone authorized to submit the resource for consideration
• Submission must be related to Azure Static Web Apps and related technologies
• Submission adheres to Code of Conduct (no offensive language, non-inclusive narratives)
• Submission resource can be an article, a project (repo), or an event (meetup or conference)

Process

• Fill in the sections below and submit the issue
• Track issue to know when it gets scheduled - might not always be in the next roundup

Resource Title

Simple Library Management

Resource Link

Repository: Simple Library Management Website: Online Library

Resource Description

A simple library management project that is easy to use and helps learners understand the basic concept of JS. You will learn how to implement add, remove/delete, search, and save functionalities & how to deploy, or publish, your website to Azure so that you can show it off to your friends.

Submitter Name and Github Profile

Muhammad Samiullah (Microsoft Learn Student Ambassador) GitHub profile: samipak458

(Optional) Your Twitter profile

Twitter profile: samipak458

(Optional) Expiry Date

N/A

Split the playwright workflow into 2 separate workflows, one that runs on demand and the other that runs every night. Also updating reporter in playwright config file to store html and json reports in pw-report folder (and turned trace on).

Created a playwright test harness and 2 github actions that runs the tests on push and pull requests to the main branch and at midnight. Tests can be run with npm run playwright_test.

when following the link https://staticwebdev.github.io/30DaysOfSWA/#

the site gives error Your Docusaurus site did not load properly.

And some of the links on the page does not work (this might be due to docusaurus?)

Fills in the September roundup.

Primary focus on students, highlighting the current SWA bug bash to see if we can encourage more students to participate.

What

• Additional call out to Septermber roundup section to appeal to students.
• Added Developer resource link from Academic Cloud Advocate
• Added Community resource link from professor in Hong Kong
• Added some additional spacing bewtween sections

Please submit this issue only if YOU are the author (or one of the authors) on the associated article or code sample AND/OR have the authority to give us permission to share that resource in our roundup.

Article Title

SWA in Python (Should be the same as in the original blog post)

Article Link

(Working link to where the canonical post lives)

Article Tags

3-5 topics tags that best reflect your project.

• Pick 1 tag for the coding language used
• Pick 1 or more tags to identify technologies or frameworks used
• Look at GitHub Topics for examples of valid tags

Your Name and GitHub profile

(used to provide attribution)

(Optional) Your Twitter profile

(if specified, we may tag you in any tweets that highlight your project in Showcase)

(Optional) Anything else we need to know

(use this to provide any information to help us in evaluating the submission for Showcase)

Blog Post Author

(Your name and GitHub profile link for attribution)

Explore analytics support and usage

Note: Analytics/Tag support is built into preset-classic theme - no need to install plugin, just configure it. (See Issue 7221 on docusaurus repo for updates on support for Google Analytics 4 now that UA is being sunsetted)

See: https://docusaurus.io/docs/api/plugins/@docusaurus/plugin-sitemap

Note: Classic theme has this plugin in presets, so no need to add plugin again - just configure it

1. Will improve SEO
2. Can be useful for running tests for validating links later

Playwright test actions are tied to a nightly-builds testing project (summer intern). Currently pausing the workflows since they are erroring out on access issues Re-enable when the project goes public (access restrictions fixed)

Test with Twitter validator: https://cards-dev.twitter.com/validator?ref=tiny-helpers

Customize metadata: https://docusaurus.io/docs/markdown-features/head-metadata#customizing-head-metadata

Example: Link currently contains "en-us" fixing locale to US-English. Remove the localization tag to default so it gets customized on client side to reflect locale preference