You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@iotdb.apache.org by GitBox <gi...@apache.org> on 2022/05/24 10:50:27 UTC
[GitHub] [iotdb] tsunghanjacktsai opened a new pull request, #6003: [IOTDB-3265] Button Text of Main Features Section Overflow on Mobile Version Homepage
tsunghanjacktsai opened a new pull request, #6003:
URL: https://github.com/apache/iotdb/pull/6003
## Description
[[IOTDB-3265] Button Text of Main Features Section Overflow on Mobile Version Homepage](https://issues.apache.org/jira/browse/IOTDB-3265)
In addition to resolving the issue above, I've also made the following changes to the homepage enabling a more responsive layout on mobile:
1. Adjust the title (Apache IoTDB) font size to make it more suitable for viewing on mobile.
2. Resize the "Download" and "Quickstart" buttons to make them aligned on mobile.
3. Resize the carousel to make the whole text visible on mobile and adjust the content position for the desktop view to prevent large empty space.
The following screenshots are the comparison between the mobile (on my 6.1 inches phone) and desktop versions after the changes:
Original (mobile version):
<img src="https://user-images.githubusercontent.com/34185019/170014714-3af22891-83fa-4cad-8ddf-2c26375087bb.jpg" width="20%" height="10%">
New (mobile version):
<img src="https://user-images.githubusercontent.com/34185019/170007396-5bc75c35-ddf7-4f4b-9256-c71450f4f8cc.jpg" width="20%" height="10%">
Old (desktop version):
<img src="https://user-images.githubusercontent.com/34185019/170017484-7cdbdc50-02a0-4076-9a80-45de94a9361e.png" width="20%" height="10%">
New (desktop version):
<img src="https://user-images.githubusercontent.com/34185019/170017341-a0de739e-36b8-414b-b653-54da084a4baa.png" width="20%" height="10%">
<!--
In each section, please describe design decisions made, including:
- Choice of algorithms
- Behavioral aspects. What configuration values are acceptable? How are corner cases and error
conditions handled, such as when there are insufficient resources?
- Class organization and design (how the logic is split between classes, inheritance, composition,
design patterns)
- Method organization and design (how the logic is split between methods, parameters and return types)
- Naming (class, method, API, configuration, HTTP endpoint, names of emitted metrics)
-->
<!-- It's good to describe an alternative design (or mention an alternative name) for every design
(or naming) decision point and compare the alternatives with the designs that you've implemented
(or the names you've chosen) to highlight the advantages of the chosen designs and names. -->
<!-- If there was a discussion of the design of the feature implemented in this PR elsewhere
(e. g. a "Proposal" issue, any other issue, or a thread in the development mailing list),
link to that discussion from this PR description and explain what have changed in your final design
compared to your original proposal or the consensus version in the end of the discussion.
If something hasn't changed since the original discussion, you can omit a detailed discussion of
those aspects of the design here, perhaps apart from brief mentioning for the sake of readability
of this PR description. -->
<!-- Some of the aspects mentioned above may be omitted for simple and small changes. -->
<hr>
This PR has:
- [x] been self-reviewed.
- [ ] concurrent read
- [ ] concurrent write
- [ ] concurrent read and write
- [ ] added documentation for new or modified features or behaviors.
- [ ] added Javadocs for most classes and all non-trivial methods.
- [ ] added or updated version, __license__, or notice information
- [ ] added comments explaining the "why" and the intent of the code wherever would not be obvious
for an unfamiliar reader.
- [ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold
for code coverage.
- [ ] added integration tests.
- [ ] been tested in a test IoTDB cluster.
<!-- Check the items by putting "x" in the brackets for the done things. Not all of these items
apply to every PR. Remove the items which are not done or not relevant to the PR. None of the items
from the checklist above are strictly necessary, but it would be very helpful if you at least
self-review the PR. -->
<hr>
##### Key changed/added classes (or packages if there are too many classes) in this PR
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: reviews-unsubscribe@iotdb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [iotdb] HTHou commented on pull request #6003: [IOTDB-3265] Button Text of Main Features Section Overflow on Mobile Version Homepage
Posted by GitBox <gi...@apache.org>.
HTHou commented on PR #6003:
URL: https://github.com/apache/iotdb/pull/6003#issuecomment-1136624835
Hi, I feel the desktop version of homepage looks not as good as before. 😆
<img width="1509" alt="Screen Shot 2022-05-25 at 9 50 27 AM" src="https://user-images.githubusercontent.com/25913899/170162489-dfd1e1c4-bb42-4545-912e-f7d6554c8abc.png">
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: reviews-unsubscribe@iotdb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [iotdb] HTHou merged pull request #6003: [IOTDB-3265] Button Text of Main Features Section Overflow on Mobile Version Homepage
Posted by GitBox <gi...@apache.org>.
HTHou merged PR #6003:
URL: https://github.com/apache/iotdb/pull/6003
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: reviews-unsubscribe@iotdb.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org