amanintech
30. April 2021 um 07:20
1
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 âGefĂ€llt mirâ
Zup
2. Mai 2021 um 01: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 âGefĂ€llt mirâ
Forgot to mention, it supports customizable fonts as well. Adding that too@Zup
4 âGefĂ€llt mirâ
Hi, nice theme, but when using banner collapse I get following.
2 âGefĂ€llt mirâ
We have never seen this issue @bubblecatcher . Could you dig in a little and find what plugin/ setting might be causing this ?
1 âGefĂ€llt mirâ
@amanintech Tolle Arbeit!
1 âGefĂ€llt mirâ
Hallo @hollosch , danke fĂŒr die WertschĂ€tzung.
Vorerst haben wir keine dynamischen Steuerelemente zur Seitenleiste hinzugefĂŒgt.
Forken Sie das Repository GitHub - twimbit/neomorphism-discourse: Discourse theme with neomorphism design
Ersetzen Sie diese Datei durch Ihre gewĂŒnschten Elemente - neomorphism-discourse/desktop/after_header.html at main · twimbit/neomorphism-discourse · GitHub
Installieren Sie das Theme fĂŒr Discourse
Lassen Sie mich wissen, ob es geholfen hat.
1 âGefĂ€llt mirâ
Hey @amanintech , es funktioniert. Vielen Dank!
Viele GrĂŒĂe,
1 âGefĂ€llt mirâ
amanintech
3. August 2022 um 11:22
9
Freut mich, dass es geholfen hat.
Ja, vorerst wĂ€re das direkte Programmieren der direkteste Weg. Wenn Sie es modular gestalten und direkt ĂŒber die Einstellungen bearbeiten können, werde ich Ihre BeitrĂ€ge gerne ĂŒbernehmen.
1 âGefĂ€llt mirâ
Hallo,
1 âGefĂ€llt mirâ
amanintech
7. August 2022 um 17:50
11
Habe ich noch nie zuvor gesehen. Tritt dies nur bei diesem Thema auf oder auch bei anderen? Teilen Sie mir auch mit, welche Discourse-Version Sie verwenden. Wir haben zuletzt auf Version 2.9.0 beta 3 getestet und es funktionierte einwandfrei.
1 âGefĂ€llt mirâ
Hallo,
1 âGefĂ€llt mirâ
Rabbit
22. Januar 2023 um 02:32
13
BrĂŒche in Version 3 in den Navigationsleisten-Navigationspills
barto_95
16. Juli 2023 um 16:34
14
Hallo,
danke fĂŒr dein Theme @amanintech , es ist wunderschönâŠ
Ich habe das gleiche Problem @amanintech (letzte Version von Discourse)
isaac
8. September 2023 um 18:27
15
Hallo @amanintech ,
Das SuchmenĂŒ und seine Logik wurden von (veralteten) Widgets in Glimmer-Komponenten umgewandelt . Die Ănderungen sind derzeit hinter einer gruppenbasierten Feature-Flag verborgen, aber wir beabsichtigen, das Glimmer-SuchmenĂŒ in naher Zukunft zum neuen Standard zu machen. Die Ănderungen werden alle search-Ăberschreibungen in Ihrem Theme brechen, daher wollte ich Sie darauf aufmerksam machen, bevor wir den Wechsel vornehmen.
Hier ist der PR als Referenz.
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">
Danke,
1 âGefĂ€llt mirâ
isaac
6. Februar 2024 um 18:02
16
Ich habe das Thema als broken oben erklĂ€rt habe, basiert das Thema auf dem Widget-SuchmenĂŒ, das veraltet ist und nun vollstĂ€ndig aus dem Kern entfernt wurde hier . Es muss umgestaltet werden, um das komponentenbasierte SuchmenĂŒ zu berĂŒcksichtigen.
1 âGefĂ€llt mirâ
.
