The Neomorphism theme brings a new fresh look to Discourse. It uses the neomorphic design system which involved paper-like realism to the UI.
Full-Width view
Customizable color scheme
Custom Welcome Banner
Wide Search bar
Screenshot:
Customizable welcome banner:
Homepage:
Homepage Layout 2:
Topic page:
Full page search:
This is our first theme and I hope you will like it. We look forward to your feedbacks
「いいね！」 36
Zup
2021 年 5 月 2 日午前 1:40
2
Beautiful work.
Customizable color scheme is a convenient feature. How about customizable font as well?
How might I show the search bar only upon scroll?
Can the header be shown only on the index and nowhere else?
「いいね！」 2
Forgot to mention, it supports customizable fonts as well. Adding that too@Zup
「いいね！」 4
Hi, nice theme, but when using banner collapse I get following.
「いいね！」 2
We have never seen this issue @bubblecatcher . Could you dig in a little and find what plugin/ setting might be causing this ?
「いいね！」 1
@amanintech 素晴らしい出来栄えです！
「いいね！」 1
amanintech
2022 年 7 月 11 日午後 12:26
7
「いいね！」 1
@amanintech さん、うまくいきました。本当にありがとうございます！
よろしくお願いいたします。
「いいね！」 1
お役に立てて嬉しいです。
はい、今のところコーディングが直接的な方法です。設定からモジュール化して直接編集できるのであれば、喜んであなたの貢献をマージします。
「いいね！」 1
こんにちは、
「いいね！」 1
これまでに見たことがありません。このテーマだけで発生していますか、それとも他のテーマでも発生していますか？また、使用しているDiscourseのバージョンを教えてください。最後にテストしたのはバージョン2.9.0 beta 3で、問題なく動作しました。
「いいね！」 1
こんにちは、
「いいね！」 1
Rabbit
2023 年 1 月 22 日午前 2:32
13
ナビバーの navpills におけるバージョン 3 の変更点
barto_95
2023 年 7 月 16 日午後 4:34
14
HI、@amanintech さんのテーマ、ありがとうございます。とても美しいです…@amanintech さん、私も同じ問題があります（最新版の Discourse です）。
isaac
2023 年 9 月 8 日午後 6:27
15
こんにちは @amanintech さん、
検索メニューとそのロジックは、(非推奨の) ウィジェットからGlimmerコンポーネントに変換 されました。この変更は現在、グループベースのフィーチャーフラグによって隠されていますが、将来的にはGlimmer検索メニューを新しいデフォルトにする予定です。この変更により、テーマ内のsearchの上書きはすべて壊れるため、切り替えを行う前にこの件を提起したかったのです。
参考までにPRはこちらです。
main ← experimental-search-menu
opened 04:07PM - 28 Feb 23 UTC
# Top level view
This PR is the first version of converting the search menu and… its logic from (deprecated) widgets to glimmer components. The changes are hidden behind a group based feature flag. This will give us the ability to test the new implementation in a production setting before fully committing to the new search menu.
# What has changed
The majority of the logic from the widget implementation has been updated to fit within the context of a glimmer component, but it has not fundamentally changed. Instead of having a single widget - [search-menu.js](https://github.com/discourse/discourse/blob/main/app/assets/javascripts/discourse/app/widgets/search-menu.js) - that built the bulk of the search menu logic, we split the logic into (20+) bite size components. This greatly increases the readability and makes extending a component in the search menu much more straightforward.
That being said, certain pieces needed to be rewritten from scratch as they did not translate from widget -> glimmer, or there was a general code upgraded needed. There are a few of these changes worth noting:
### Search Service
**Search Term** -> In the widget implementation we had a overly complex way of managing the current search term. We tracked the search term across multiple different states (`term`, `opts.term`, `searchData.term`) causing headaches. This PR introduces a single source of truth:
```js
this.search.activeGlobalSearchTerm
```
This tracked value is available anywhere the `search` service is injected. In the case the search term should be needs to be updated you can call
```js
this.search.activeGlobalSearchTerm = "foo"
```
**event listeners** -> In the widget implementation we defined event listeners **only** on the search input to handle things such as
- keyboard navigation / shortcuts
- closing the search menu
- performing a search with "enter"
Having this in one place caused a lot of bloat in our logic as we had to handle multiple different cases in one location. Do _x_ if it is this element, but do _y_ if it is another. This PR updates the event listeners to be attached to individual components, allowing for a more fine tuned set of actions per element. To not duplicate logic across multiple components, we have condensed shared logic to actions on the search service to be reused. For example - `this.search.handleArrowUpOrDown` - to handle keyboard navigation.
### Search Context
We have unique logic based on the current search context (topic / tag / category / user / etc). This context is set within a models route file. We have updated the search service with a tracked value `searchContext` that can be utilized and updated from any component where the search service is injected.
```js
# before
this.searchService.set("searchContext", user.searchContext);
# after
this.searchService.searchContext = user.searchContext;
```
# Views
<img width="434" alt="Screenshot 2023-06-15 at 11 01 01 AM" src="https://github.com/discourse/discourse/assets/50783505/ef57e8e6-4e7b-4ba0-a770-8f2ed6310569">
<img width="418" alt="Screenshot 2023-06-15 at 11 04 11 AM" src="https://github.com/discourse/discourse/assets/50783505/2c1e0b38-d12c-4339-a1d5-04f0c1932b08">
<img width="413" alt="Screenshot 2023-06-15 at 11 04 34 AM" src="https://github.com/discourse/discourse/assets/50783505/b871d164-88cb-405e-9b78-d326a6f63686">
<img width="419" alt="Screenshot 2023-06-15 at 11 07 51 AM" src="https://github.com/discourse/discourse/assets/50783505/c7309a19-f541-47f4-94ef-10fa65658d8c">
<img width="424" alt="Screenshot 2023-06-15 at 11 04 48 AM" src="https://github.com/discourse/discourse/assets/50783505/f3dba06e-b029-431c-b3d0-36727b9e6dce">
<img width="415" alt="Screenshot 2023-06-15 at 11 08 57 AM" src="https://github.com/discourse/discourse/assets/50783505/ad4e7250-040c-4d06-bf06-99652f4c7b7c">
よろしくお願いします
「いいね！」 1
isaac
2024 年 2 月 6 日午後 6:02
16
テーマを broken
「いいね！」 1
.
