[Team: dev] Requirement clarification

[FP22FD]

I think it could be a good start to define the app’s requirements, scope, etc, instead of jumping directly to write tasks and the code. In this way the team could discuss options and come to agreements. Maybe using pools to obtain internal agreement, like we did in Teams with Bootstrap vs Tailwind.
To get info about the design details needed by us, I think the scrum master can then facilitate the communication cross teams.

For example, I think we need to get more info from the Product Owner, or get internal agreement about:

• how many max columns (Excel itself has limitations),
• how many max rows,
• what should be visible on startup (how many cols/rows),
• which formula should be supported,
• responsive breakpoints,
• should we have a login,
• which data type should be supported (string, number, floating number, image, url, date, date time, etc) and in which format (internationalization support)
• Should be able to download the data,
• Should a column be resizable
• Should a cell be formattable
• Do we need a menu for the most common actions (formatting, etc)
• How can a cell be edited, single-click, double click, editing button, etc
• Should we mark as focused a cell with different style,
• should we include hotjar

Define technical tooling

• Should we use a bundler, like Vite?
• Bootstrap, Tailwind, vanilla
• Should we deploy? In which environment, github or netlify
• Should we consider to use .env for secrets?
• Should we use jsdoc
• Should we use eslint, pre-hooks, prettier

Define common APIs

• Spinner
• Error messages
• Load & save data cell

Define UI interaction

• how many pages, home page, login, etc
• editing with modal or inline,

[WeronikaMartinsen]

Hi Fernanda!

• As we discussed on live session, this is a one page site, without Login/Register.
• Columns and rows will be defined by designers. We can make a mockup demo, before we applied the design. For now we don't need to focus on styles.
• We can focus on cell integration functionality before design is finished.
• We should implement eslint, pre-hooks, prettier.
• Spinner for loading data - Must have.
• Error messages - Must have.
• My suggestion is modal integration for editing cell.

[FP22FD]

Thank for your idea, I would like to listen to others idea, too.

[Anne-Serine]

Hi, this is the brief and requirement for this project ( as for now, mentioned in the onboarding session)
I understand it as it is up to the Design Team to figuere out the look and feel of the Spreadsheet application, and how it is supposed to work. We as the Dev Team has to wait for the design Prototype before we can start building. ( Am I wrong here? )

Maybe we can come up with some user stories, and share them with the Design Team, if there is any special features we would like to integrate? And then it´s up to them to consider them and make the design?
E.g "As a user I want to expand the IDE edeting window" etc.

As developers we can still set up the environment and make the repo ready for building as we wait for the Design Team to finish their prototype. (Like Weronica mentioned above)

Project Brief:

• Plan, design, build and test a spreadsheet web application
• The application uses JavaScript syntax instead of Excell script
• The application has a dark mode look and feel by default
• Can export in multiple formats including CSV, JSON

Short Term Goals:

• A full project plan that will lead to an MVP ( Minimum Viable Product)
• Design prototypes, name & brand identity
• A limited functional demo application
• A test plan and example tests for future

Long Term Goals:

• Full set of completed documentation
• Working MVP including completed theming
• 100% E2E and Unit test coverage
• Advanced export features

Key Tech Concepts:

• Offline features, service workers, IndexedDB
• eval() and the safety concerns associated
• Framework not required, but recommended

Team Allocation:

• 2x sprints starts on Monday

Example User stories:

• I want to click on a cell and access a side panel IDE window to edit the function
• I want to use vanilla JS to write my function and see the return value in the cell
• I want to be able to import an existing CVS or JSON file formats
• I want to do all of the above while offline

[DWNWND]

If you have user stories you can add them to this discussion for the design team: https://github.com/orgs/NoroffFEU/discussions/5

[Anne-Serine]

As for your other topics:

Define technical tooling:

Voting for Vite as a bundler
Vanilla JS and Tailwind
Deployment: Should we deploy? In which environment, github or netlify - I think Netlify is nice and easy
Should we consider to use .env for secrets? - We should defenetly make a .env file first thing, even if we´re not gonna use it. This way we will not push any "secrets" accedentally.**
Should we use jsdoc - Maybe not focus on this for now, but maybe for later..?**
Should we use eslint, pre-hooks, prettier - Yes

Spinner - Yes
Error messages -Definetely
Load & save data cell - sure

How many pages, home page, login, etc - Think it was supposed to be single page..?
Editing with modal or inline. - Editing with modal (using in HTML )

[FP22FD]

I'm also wondering about the branch strategy. As now, we have the branch workflow as "main", and everyone is branching-out from this.
Should we merge workflow to main, or a dev branch, development ?

[Roselynepj1]

Yes we can merge it