Skip to content
This repository has been archived by the owner on Nov 30, 2020. It is now read-only.

Project todo list #4

Open
2 of 40 tasks
o3LL opened this issue Jun 3, 2018 · 9 comments
Open
2 of 40 tasks

Project todo list #4

o3LL opened this issue Jun 3, 2018 · 9 comments

Comments

@o3LL
Copy link
Contributor

o3LL commented Jun 3, 2018

Hi there, this is a non-exhaustive, inaccurate and messy list that might be useful for a roadmap.
Thanks to @isneezy we already have a project base looking like this :

Components

Readme

  • Installation
  • Usage
  • Contributing
  • History
  • Credits
  • License

Project related

  • code linting, code style & editorconfig
  • github page configuration (part of it is already been done - assets are being loaded from wrong url/path)
  • unit tests (don't know if it is really necessary)

I will keep this list up to date with everything you suggest.
(Btw this issue could be moved in GitHub Projects)

@isneezy
Copy link
Contributor

isneezy commented Jun 3, 2018

@MUCHZER , thanks on helping out with this. Here are some of my input

components

  • Table
  • Icon
  • Loader
  • Pricing Card
  • Tag
  • Stamp
  • Progress
  • Form - Checkbox, ColorCheck, DatePicker, Input, Switch, etc..

Project Related

  • code linting, code style & editorconfig
  • github page configuration (part of it is already been done - assets are being loaded from wrong url/path)
  • unit tests (don't know if it is really necessary)

I'll try to add some more input into this

@o3LL
Copy link
Contributor Author

o3LL commented Jun 3, 2018

Thanks @isneezy
I have updated my list.

@isneezy
Copy link
Contributor

isneezy commented Jun 3, 2018

Update

Components

  • Avatar
  • ChartCircle
  • Chart (don't know if we should do this may be there are some vue implementations that we should recommend)
  • Maps
  • Store
  • Blog
  • Carousel
  • Gallery

@Nilpo
Copy link
Contributor

Nilpo commented Jun 4, 2018

This is looking good.

I also don't feel that unit tests are necessary since we're just building components. If we implement any advanced logic we can add them at a later date if required.

@Nilpo
Copy link
Contributor

Nilpo commented Jun 4, 2018

I think an issue for each major checkbox is a good way to break this down to begin.

@isneezy
Copy link
Contributor

isneezy commented Jun 7, 2018

@Nilpo can we start it? I had to stop because of this! I wanted to do planed things!

@Nilpo
Copy link
Contributor

Nilpo commented Jun 7, 2018

@isneezy Sure, let's do it. My thought was that we could each pick a group and roll. Creating an issue for each group would let others know who is working on what. What were you planning?

@o3LL
Copy link
Contributor Author

o3LL commented Jun 7, 2018

@Nilpo An issue per group ? or an issue per list element ?

edit: nvm, I'm creating issues for each major checkbox !

@isneezy
Copy link
Contributor

isneezy commented Jun 7, 2018

I want to work on the header of the site but I'll really need your input on that, ill create an issue so we can discuss there

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants