Home

My Juno Intranet Development Process

From business analysis to deployment, this is how I build custom SPFx web parts on the Juno Intranet product.

Timeline

The steps below reflect a typical delivery flow.

  1. Business Analysis Meeting

    Illustration of a business analysis meeting with project planning on a whiteboard

    We start with a business analysis meeting with the project manager to align on the business need, user expectations and what the web part should deliver.

  2. Requirement Review

    Illustration of technical requirement review for SharePoint and SPFx

    If more detail is needed, I do a technical review and outline the requirements. For simpler requests, the business analysis meeting is enough.

  3. Effort Estimation

    Illustration of effort estimation and project planning

    Based on the technical review, I provide an effort estimation for the web part. The estimation includes development, integration, testing, possible edge cases, review time and deployment preparation.

  4. Development Planning

    Illustration of development planning with tasks, priorities and timeline on a whiteboard

    Once the effort is approved, I plan the web part development. If needed, I split the work into smaller tasks, define priorities, prepare the development branch and identify reusable components.

  5. SPFx Web Part Development

    Illustration of SPFx development with React, TypeScript and SharePoint Framework

    At this stage, the SPFx web part is built using technologies such as React, TypeScript, Fluent UI, SharePoint REST API or Microsoft Graph, depending on what the feature needs.

  6. Testing & Review

    Illustration of testing and review of an SPFx solution

    After development, I test the web part locally and on pages in the test environment. This includes UI checks, validations, permissions, different user roles, responsive behavior and edge cases.

  7. Deployment

    Illustration of packaging and deploying an SPFx solution

    After testing, the web part package is deployed to the tenant app catalog and rolled out to the relevant environments. Usually, it goes to test first and then to production after approval.

  8. Feedback

    Illustration of gathering user feedback on completed work

    We take feedback from users of the completed work into account in our future development.

Tech Stack

  • SPFx
  • React
  • TypeScript
  • Fluent UI
  • SharePoint REST API
  • Microsoft Graph
  • PnPjs
  • SCSS / CSS Modules
  • Cursor