---
# System prepended metadata

title: TradeOr (TO) - Project

---

# TradeOr (TO) - Project

By answering all of the questions below we'll have a better understanding of what's involved as well as clearer picture regarding projects timeline and expectations.

[TOC]

## Front-End
> ReactJS Application using latest Hooks API. 

### Blockers

- [ ] **Finalize folder structure:**
    * **`/components`**
        * `/ComponentName`
        
            > index.tsx or ComponentName.tsx ?
            > `Readme.md` - styleguidist file
            > `ComponentName.test` - `TSX` or `JS` file?

    * **`/features`**
        * `/featureName`
            * `/FeatureSpecificComponent`
            > API calls are made from here only?
            > Any other specific logic lives here?
            
    * **`/pages`**
        > List all `App` pages or separate into `/admin` and `/user` specific folders?

    * **`/utils`**
        > What type of logic to keep here?
    * **List all other required folders!**
    

- [ ] **Discuss URL links structure:**
    > Any specific requirements here?


- [ ] **Document each pages feature:**
    - [ ] *Home Page*
        * Timeline
            > How it works?
            > e.g: Infinite auto loading scrolling or Pagination? What those 3 dots at the top of the post do? Describe functionality! Like comment and share functionality same as Facebook? Is it required for **MVP**?
            > 
            > Contains Components:
            > * `<PostComponent/>`
        * News
            > How it works? Describe logic...
        * Watchlist Markets
        * Watchlist People
        * Portfolio

- [ ] **Cross-browser testing and support?**
    > What will we support?
    
- [ ] **Responsive layout**
    > Agree Breakpoints...

- [ ] **Missing Screens**
    > Designers todo list:
    - [ ] Login / Logout

- [ ] **Flesh out API endpoints:**

    > I think we should have ApolloServer... Benefits:
    - [ ] Mock data
    - [ ] Incremental adoption (easily add advanced features later)

    > Or suggest another alternative for mocking data while FE is being built. Need to start thinking about it now!


- [ ] **Testing:**
    > IMO currently it doesn't make sence to write any unit tests until there is solid number of basic components and features are built and we all have good momentum. Because components are changing shape a lot and doing it now will increase dev time. If we had this document as the Technical Spec of sorts at the start then TDD approach would be more than appropriate. However I suppose a good time to start writing unit test would be ~ 2 weeks from now: [time=Mon, Jul 29, 2019]
    >Propose / Agree on structure:
    - [ ] Each component has it's `.test` file or else?

- [ ] **Pull Requests:**
    > Suggest to have 2 reviewers before PR is approved
  


### Concerns

* Too much time collaboratively is currently spent on dicussing things like features / atoms / molecules etc... Decision making should involve not more than 2-3 key people otherwise we have **too many cooks** and 1 call lasting an hour involving 5 people costs 5 hours of work.

* Everyday **TO team standups** are distracting and counter productive - suggest to have them only on Monday (*discuss this weeks target*) and Thursday (*how did we progress are we on target?*) Friday (*finishing the week and winding down*). **Riccardo** can obviously check-in with anyone at any time but that will allow others to keep focus on their tasks. Progress is more than visible by GitScrum and BitBucket commits.

* 8 working hours is **NOT** 8 hours of code output! Let's keep it real.

### Plan Of Action

- [ ] Complete this document - that will also help out to flesh out API endpoints and have better understanding of it all. As far as I know current design is a mold of eTorro and other similar platforms. Has any thoughts been given into every piece of functionality in this project by Product Owners? Maybe something we don't need at all?!

### Realistic Timeline
- [ ] TODO
