From f761d687f6698271520a8dffc2f80dc310e046b4 Mon Sep 17 00:00:00 2001 From: Thomas Iwainski Date: Thu, 24 Oct 2024 11:14:56 +1100 Subject: [PATCH 1/7] =?UTF-8?q?Update=20Rule=20=E2=80=9Csprint-forecast/ru?= =?UTF-8?q?le=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- rules/sprint-forecast/rule.md | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/rules/sprint-forecast/rule.md b/rules/sprint-forecast/rule.md index 06a538008a..cb719c33ba 100644 --- a/rules/sprint-forecast/rule.md +++ b/rules/sprint-forecast/rule.md @@ -1,7 +1,10 @@ --- -seoDescription: Do you create a Sprint Forecast? (aka The functionality that will be developed during the Sprint) - Confirming the relationship between the Product Owner and Development Team in Agile Project Management. type: rule -title: Do you create a Sprint Forecast? (aka The functionality that will be developed during the Sprint) +title: Do you create a Sprint Forecast? (aka The functionality that will be + developed during the Sprint) +seoDescription: Do you create a Sprint Forecast? (aka The functionality that + will be developed during the Sprint) - Confirming the relationship between the + Product Owner and Development Team in Agile Project Management. uri: sprint-forecast authors: - title: Adam Cogan @@ -30,13 +33,13 @@ Each Sprint in a Scrum project can be considered a mini-project that has **time* ::: email-template -| | | -| -------- | --- | -| To: | {{Product Owner}} | -| Subject: | {{Client Name}}: Sprint XXX Forecast | +| | | +| -------- | -------------------------------------- | +| To: | {{ PRODUCT OWNER }} | +| Subject: | {{ CLIENT NAME }}: Sprint XXX Forecast | ::: email-content -### Hi {{Product Owner}} +### Hi {{ PRODUCT OWNER }} Sprint Goals (in priority order): From a5f5e415271e99bae96522548c4e3a87bd660ba7 Mon Sep 17 00:00:00 2001 From: Tom Iwainski Date: Thu, 24 Oct 2024 17:35:17 +1100 Subject: [PATCH 2/7] create new rule --- .../rule.md | 71 +++++++++++++++++++ 1 file changed, 71 insertions(+) create mode 100644 rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md diff --git a/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md b/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md new file mode 100644 index 0000000000..7155fd0b4f --- /dev/null +++ b/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md @@ -0,0 +1,71 @@ +--- +seoDescription: Do you know the best Framework to build an Admin Interface for your Web App? +type: rule +title: Do you know the best Framework to build an Admin Interface for your Web App? +uri: do-you-know-the-best-framework-to-build-an-admin-interface +authors: + - title: Tom Iwainski + url: https://www.ssw.com.au/people/thomas-iwainski +related: + - use-nextjs + - why-react-is-great + - why-blazor-is-great + - why-angular-is-great +created: 2024-10-224T00:00:00.001Z +guid: abcdefgh-1234-a1b2-xyza-ffffffffffff +--- + +When it comes to developing an admin interface for your web application, choosing the right framework is crucial. The best option often depends on your existing tech stack, the complexity of your application, and the specific needs of your admin users. We'll explore the factors to consider when selecting a framework and provide some top recommendations. + + + +## Stick to your existing Tech Stack + +If your application already has an established tech stack, it's generally advisable to stick with it. Maintaining consistency across your application can simplify development, reduce onboarding time for new developers, and make it easier to manage dependencies. + +Here are some reasons to stay within your current stack: + +1. Familiarity: Your team is already comfortable with the tools and languages in use. +2. Integration: Existing components and services can be more easily integrated. +3. Reduced Overhead: Fewer technologies mean less complexity in your build and deployment processes. + +However, if your current stack isn't suited for an admin interface, or if there are significant improvements to be made, it might be worth exploring new options. + +## Evaluating Frameworks + +When considering frameworks for building an admin interface, keep the following criteria in mind: + +- **Ease of Use**: The framework should allow for rapid development and easy maintenance. +- **Customizability**: Look for options that provide flexibility for unique UI requirements. +- **Community Support**: A strong community can be invaluable for troubleshooting and finding resources. +- **Performance**: Ensure that the framework can handle your app’s data load efficiently. + +## Top Frameworks to Consider + +### React / Next.js + +- **Why Use It**: React provides a component-based architecture that makes building complex UIs intuitive. With Next.js, you gain additional features like server-side rendering and static site generation, which can improve performance and SEO. +- **Best For**: Applications that require dynamic content and a rich user interface. Ideal for teams already using React for their frontend. + +For some more information visit our rule: + +- [Do you know why Next.js is awesome?](https://www.ssw.com.au/rules/use-nextjs/) +- [Do you know why React is awesome?](https://www.ssw.com.au/rules/why-react-is-great/) + +### Blazor + +- **Why Use It**: Blazor allows you to build interactive web UIs using C# instead of JavaScript. It can be a great choice for .NET developers looking to leverage their existing skills. +- **Best For**: .NET applications where you want a seamless experience across client and server-side development, particularly for teams familiar with C#. + +For some more information visit our rule: + +- [Do you know why Blazor is awesome?](https://www.ssw.com.au/rules/why-blazor-is-great/) + +### Angular + +- **Why Use It**: Angular offers a robust framework for building single-page applications (SPAs) with a strong focus on scalability and maintainability. It includes powerful features like two-way data binding, dependency injection, and a rich set of built-in components. +- **Best For**: Large applications requiring a structured framework that can handle complex features and extensive data management. + +For some more information visit our rule: + +- [Do you know why Angular is great?](https://www.ssw.com.au/rules/why-angular-is-great/) From c8e8329c73abcceb6813db0a583d07e5c0c18623 Mon Sep 17 00:00:00 2001 From: Thomas Iwainski Date: Thu, 24 Oct 2024 17:48:56 +1100 Subject: [PATCH 3/7] Update rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md Co-authored-by: Matt Wicks [SSW] --- .../rule.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md b/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md index 7155fd0b4f..fec5292537 100644 --- a/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md +++ b/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md @@ -12,7 +12,7 @@ related: - why-blazor-is-great - why-angular-is-great created: 2024-10-224T00:00:00.001Z -guid: abcdefgh-1234-a1b2-xyza-ffffffffffff +guid: be0d9e5f-8580-4997-9abd-d7130ec9b240 --- When it comes to developing an admin interface for your web application, choosing the right framework is crucial. The best option often depends on your existing tech stack, the complexity of your application, and the specific needs of your admin users. We'll explore the factors to consider when selecting a framework and provide some top recommendations. From 167940ac5059a8e7f4577f7cab2a84eebb5d93e0 Mon Sep 17 00:00:00 2001 From: Thomas Iwainski Date: Thu, 24 Oct 2024 17:49:15 +1100 Subject: [PATCH 4/7] Update rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md Co-authored-by: Matt Wicks [SSW] --- .../rule.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md b/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md index fec5292537..4516a96e5b 100644 --- a/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md +++ b/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md @@ -1,5 +1,5 @@ --- -seoDescription: Do you know the best Framework to build an Admin Interface for your Web App? +seoDescription: Find the best framework for your admin interface. Explore top choices like React, Blazor, and Angular, based on your tech stack and project needs type: rule title: Do you know the best Framework to build an Admin Interface for your Web App? uri: do-you-know-the-best-framework-to-build-an-admin-interface From dfbca00205edf73e240703733a41a90a66fc761a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tiago=20Ara=C3=BAjo=20=5BSSW=5D?= Date: Thu, 24 Oct 2024 12:07:08 -0700 Subject: [PATCH 5/7] Update rule.md --- .../rule.md | 51 ++++++++++--------- 1 file changed, 27 insertions(+), 24 deletions(-) diff --git a/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md b/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md index 4516a96e5b..0cdfacf2cb 100644 --- a/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md +++ b/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md @@ -1,7 +1,7 @@ --- seoDescription: Find the best framework for your admin interface. Explore top choices like React, Blazor, and Angular, based on your tech stack and project needs type: rule -title: Do you know the best Framework to build an Admin Interface for your Web App? +title: Do you know the best framework to build an admin interface for Web Apps? uri: do-you-know-the-best-framework-to-build-an-admin-interface authors: - title: Tom Iwainski @@ -19,53 +19,56 @@ When it comes to developing an admin interface for your web application, choosin -## Stick to your existing Tech Stack +## Stick to your existing tech stack If your application already has an established tech stack, it's generally advisable to stick with it. Maintaining consistency across your application can simplify development, reduce onboarding time for new developers, and make it easier to manage dependencies. Here are some reasons to stay within your current stack: -1. Familiarity: Your team is already comfortable with the tools and languages in use. -2. Integration: Existing components and services can be more easily integrated. -3. Reduced Overhead: Fewer technologies mean less complexity in your build and deployment processes. +1. **Familiarity** - Your team is already comfortable with the tools and languages in use +2. **Integration** - Existing components and services can be more easily integrated +3. **Reduced overhead** - Fewer technologies mean less complexity in your build and deployment processes However, if your current stack isn't suited for an admin interface, or if there are significant improvements to be made, it might be worth exploring new options. -## Evaluating Frameworks +## Evaluating frameworks When considering frameworks for building an admin interface, keep the following criteria in mind: -- **Ease of Use**: The framework should allow for rapid development and easy maintenance. -- **Customizability**: Look for options that provide flexibility for unique UI requirements. -- **Community Support**: A strong community can be invaluable for troubleshooting and finding resources. -- **Performance**: Ensure that the framework can handle your app’s data load efficiently. +- **Ease of Use** - The framework should allow for rapid development and easy maintenance +- **Customizability** - Look for options that provide flexibility for unique UI requirements +- **Community Support** - A strong community can be invaluable for troubleshooting and finding resources +- **Performance** - Ensure that the framework can handle your app’s data load efficiently -## Top Frameworks to Consider +## Top trameworks to consider ### React / Next.js -- **Why Use It**: React provides a component-based architecture that makes building complex UIs intuitive. With Next.js, you gain additional features like server-side rendering and static site generation, which can improve performance and SEO. -- **Best For**: Applications that require dynamic content and a rich user interface. Ideal for teams already using React for their frontend. +React provides a component-based architecture that makes building complex UIs intuitive. With Next.js, you gain additional features like server-side rendering and static site generation, which can improve performance and SEO. -For some more information visit our rule: +**Best for:** Applications that require dynamic content and a rich user interface. Ideal for teams already using React for their frontend. -- [Do you know why Next.js is awesome?](https://www.ssw.com.au/rules/use-nextjs/) -- [Do you know why React is awesome?](https://www.ssw.com.au/rules/why-react-is-great/) +For more information, see our rules: + +- [Do you know why Next.js is awesome?](/use-nextjs) +- [Do you know why React is awesome?](/why-react-is-great) ### Blazor -- **Why Use It**: Blazor allows you to build interactive web UIs using C# instead of JavaScript. It can be a great choice for .NET developers looking to leverage their existing skills. -- **Best For**: .NET applications where you want a seamless experience across client and server-side development, particularly for teams familiar with C#. +Blazor allows you to build interactive web UIs using C# instead of JavaScript. It can be a great choice for .NET developers looking to leverage their existing skills. + +**Best for:** .NET applications where you want a seamless experience across client and server-side development, particularly for teams familiar with C#. -For some more information visit our rule: +For more information, see our rule: -- [Do you know why Blazor is awesome?](https://www.ssw.com.au/rules/why-blazor-is-great/) +- [Do you know why Blazor is awesome?](/why-blazor-is-great/) ### Angular -- **Why Use It**: Angular offers a robust framework for building single-page applications (SPAs) with a strong focus on scalability and maintainability. It includes powerful features like two-way data binding, dependency injection, and a rich set of built-in components. -- **Best For**: Large applications requiring a structured framework that can handle complex features and extensive data management. +Angular offers a robust framework for building single-page applications (SPAs) with a strong focus on scalability and maintainability. It includes powerful features like two-way data binding, dependency injection, and a rich set of built-in components. + +**Best for:** Large applications requiring a structured framework that can handle complex features and extensive data management. -For some more information visit our rule: +For more information, see our rule: -- [Do you know why Angular is great?](https://www.ssw.com.au/rules/why-angular-is-great/) +- [Do you know why Angular is great?](/why-angular-is-great) From e566d1bb96a55fbbef6bd9b0e851afa23dba9699 Mon Sep 17 00:00:00 2001 From: Tom Iwainski Date: Fri, 25 Oct 2024 10:22:38 +1100 Subject: [PATCH 6/7] Update rules-to-better-websites-development.md --- .../rules-to-better-websites-development.md | 116 +++++++++--------- 1 file changed, 58 insertions(+), 58 deletions(-) diff --git a/categories/software-engineering/rules-to-better-websites-development.md b/categories/software-engineering/rules-to-better-websites-development.md index 9117694b5f..96cdbd0d16 100644 --- a/categories/software-engineering/rules-to-better-websites-development.md +++ b/categories/software-engineering/rules-to-better-websites-development.md @@ -4,64 +4,64 @@ title: Rules to Better Websites - Development guid: 9c19bee6-5906-4978-a864-249ebb7307f6 uri: rules-to-better-websites-development index: -- the-right-technology -- the-steps-to-do-after-adding-a-page -- structured-website -- always-have-a-default-index-page -- have-a-stylesheet-file -- scoped-css -- close-quotations-of-html-attributes -- best-way-to-display-code-on-your-website -- use-heading-tags-h1-h2-h3 -- design-to-improve-your-google-ranking -- do-you-include-google-analytics-in-your-website -- make-your-site-easy-to-maintain -- streamline-development-with-npm-and-task-runners -- 404-useful-error-page -- 404-error-avoid-changing-the-url -- always-put-javascript-in-a-separate-file -- always-use-query-strings -- optimise-favicon -- avoid-deploying-source-code-on-the-production-server -- avoid-using-uncs-in-hrefs -- check-your-website-is-running -- progressive-web-app -- use-dynamic-viewport-units -- improve-performance-with-lazy-loading-of-media-assets -- use-right-site-search-for-your-website -- do-not-use-linkbutton -- why-choose-dot-net-core -- name-webpages-consistently-with-database-tables -- precompile-your-asp-net-1-1-and-2-0-and-later-sites -- provide-modern-contact-options -- remove-the-debug-attribute-in-webconfig-compilation-element -- run-load-tests-on-your-website -- use-css-validation-service-to-check-your-css-file -- do-you-choose-the-best-way-to-send-emails-for-application -- use-jquery-instead-of-javascript -- use-link-auditor -- using-markdown-to-store-your-content -- best-practices-for-frontmatter-in-markdown -- page-owner -- set-language-on-code-blocks -- use-markup-validation-service-to-check-your-html-code -- html-unicode-hex-codes -- generate-pdfs -- centralize-downloadable-files -- use-open-graph -- use-server-side-comments -- best-static-site-tech-stack -- use-nextjs -- cms-solutions -- git-based-cms-solutions -- best-online-documentation-site -- use-web-compiler -- packages-up-to-date -- monitor-packages-for-vulnerability -- do-you-perform-migration-procedures-with-an-approved-plan -- manage-bundle-size -- best-commenting-engine - + - the-right-technology + - the-steps-to-do-after-adding-a-page + - structured-website + - always-have-a-default-index-page + - have-a-stylesheet-file + - scoped-css + - close-quotations-of-html-attributes + - best-way-to-display-code-on-your-website + - use-heading-tags-h1-h2-h3 + - design-to-improve-your-google-ranking + - do-you-include-google-analytics-in-your-website + - make-your-site-easy-to-maintain + - streamline-development-with-npm-and-task-runners + - 404-useful-error-page + - 404-error-avoid-changing-the-url + - always-put-javascript-in-a-separate-file + - always-use-query-strings + - optimise-favicon + - avoid-deploying-source-code-on-the-production-server + - avoid-using-uncs-in-hrefs + - check-your-website-is-running + - progressive-web-app + - use-dynamic-viewport-units + - improve-performance-with-lazy-loading-of-media-assets + - use-right-site-search-for-your-website + - do-not-use-linkbutton + - why-choose-dot-net-core + - name-webpages-consistently-with-database-tables + - precompile-your-asp-net-1-1-and-2-0-and-later-sites + - provide-modern-contact-options + - remove-the-debug-attribute-in-webconfig-compilation-element + - run-load-tests-on-your-website + - use-css-validation-service-to-check-your-css-file + - do-you-choose-the-best-way-to-send-emails-for-application + - use-jquery-instead-of-javascript + - use-link-auditor + - using-markdown-to-store-your-content + - best-practices-for-frontmatter-in-markdown + - page-owner + - set-language-on-code-blocks + - use-markup-validation-service-to-check-your-html-code + - html-unicode-hex-codes + - generate-pdfs + - centralize-downloadable-files + - use-open-graph + - use-server-side-comments + - best-static-site-tech-stack + - use-nextjs + - cms-solutions + - git-based-cms-solutions + - best-online-documentation-site + - use-web-compiler + - packages-up-to-date + - monitor-packages-for-vulnerability + - do-you-perform-migration-procedures-with-an-approved-plan + - manage-bundle-size + - best-commenting-engine + - do-you-know-the-best-framework-to-build-an-admin-interface --- Enhance your web development practices by adhering to essential guidelines that ensure performance, maintainability, and user experience. This collection covers key aspects such as technology selection, site structure, error handling, and optimization techniques, empowering you to create effective and user-friendly websites. From 5711887d4196db5a0a505b2efdfbff6b0514a4c6 Mon Sep 17 00:00:00 2001 From: Tom Iwainski Date: Fri, 25 Oct 2024 10:23:58 +1100 Subject: [PATCH 7/7] Fix date typo in rule.md --- .../rule.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md b/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md index 0cdfacf2cb..7eeeeaaec3 100644 --- a/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md +++ b/rules/do-you-know-the-best-framework-to-build-an-admin-interface/rule.md @@ -11,7 +11,7 @@ related: - why-react-is-great - why-blazor-is-great - why-angular-is-great -created: 2024-10-224T00:00:00.001Z +created: 2024-10-24T00:00:00.001Z guid: be0d9e5f-8580-4997-9abd-d7130ec9b240 ---