-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add an shortcut information for recognize the contents existed or not on the list #68
Comments
I will work on sending data from the backend |
I will add a shortcut information in item of list |
kdh92417
added a commit
to kdh92417/exporterhub.io
that referenced
this issue
Aug 29, 2021
Joylish
added a commit
to Joylish/exporterhub.io
that referenced
this issue
Aug 30, 2021
…ntents existed or not on the list Doubts while working 1. I don't know where to put the new mark in the header. So I commented out this part. 2. It was ambiguous to divide the criteria because each exporters has differnt types of contents. This issue will be resolved after talking with @kdh92417
Each Characters meaning like below,
I think actually Please check this out @Joylish |
Joylish
added a commit
to Joylish/exporterhub.io
that referenced
this issue
Aug 31, 2021
…ents of card in the exporter list What - remove one of types which is 'E' meaning exporter. It doesn't need to present exporter because it already be exporter - revive 'new' in header and re-arrange status of contents under the name - css works for card
kdh92417
added a commit
to kdh92417/exporterhub.io
that referenced
this issue
Aug 31, 2021
2 tasks
Joylish
added a commit
to Joylish/exporterhub.io
that referenced
this issue
Sep 9, 2021
Problem - Section of contents is cracked in mobile view
Joylish
added a commit
to Joylish/exporterhub.io
that referenced
this issue
Sep 9, 2021
ralfyang
added a commit
that referenced
this issue
Sep 14, 2021
[Issue #68] - Add function get_exporter_contents
ralfyang
added a commit
that referenced
this issue
Sep 14, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: