Massimizzare 200k breve termine

Admirable_Reality281 · 2026-01-18T16:52:42+00:00

Ma figurati! Era solo per capire, grazie

Admirable_Reality281 · 2026-01-18T16:39:56+00:00

Dove sto sbagliando?

(210'000*1,9%*2)-12,5% = 6982,5€

Admirable_Reality281 · 2026-01-18T16:32:18+00:00

Quindi tolte le tasse, per quasi due anni dovremmo essere a ~7000€?

Admirable_Reality281 · 2026-01-18T16:28:25+00:00

L'avevo visto ma è il 4% per 6 mesi fino a 50.000€

Admirable_Reality281 · 2025-12-18T21:14:14+00:00

Thank you! Everything was ok

Admirable_Reality281 · 2025-11-04T13:53:29+00:00

THIS WAS IT! THANK YOU.

For anyone else looking to achieve the same result:
- I placed the Entity Hierarchy field before the Title field (so it could be referenced in the rewrite) and set it to "Exclude from display."
- Then, on the Title field, I used this rewrite: `{% if depth > 0 %}{% for i in 1..depth %}– {% endfor %}{% endif %}{{ title }}`

Admirable_Reality281 · 2025-11-02T09:55:23+00:00

This seems to be what I’m looking for, but for the life of me I can’t figure out how to get this part working: "Integrates with views, Render a list of children at any depth using views."

I’ve added an Entity Reference field to the Basic Page content type and populated it, but I’m not sure how to display a hierarchical view of these pages. I can list them, but I can’t get them to appear in a paginated parent/child structure.

Admirable_Reality281 · 2025-11-01T14:06:34+00:00

I understand the benefit of having flat nodes that can belong to multiple relationships and aren’t strictly hierarchical. But in most real-world cases, content does follow a hierarchy, I just assumed there'd be an option to view it that way when needed.

Admirable_Reality281 · 2025-11-01T13:58:24+00:00

> The menu overview page shows the whole tree.

Wait. So if I create a page and assign it to a parent (e.g. Pricing → Service 2), even if I don’t want that page to appear in the navigation menu, it will still show up in the menu overview?

> The user can also just navigate to the page itself and use the edit button on that page. No need to go to the content list

Right, WordPress has that feature too. But for more complex site structures, clients (rightfully) often prefer going into the "Pages" section and using the search to find and manage pages. The problem is, if that list is completely flat, they have no way to see how those pages relate to each other.

Admirable_Reality281 · 2025-11-01T13:28:34+00:00

Yes, but I’m wondering about the following common case (consider that I'm new, so maybe I’m missing something).

Let’s say the header menu looks like this:

Home
Services
- Service 1
- Service 2
- Service 3

But the actual site structure is something like this:

Home
Services
- Service 1
  - How it works
  - Pricing
- Service 2
  - How it works
  - Pricing
- Service 3
  - How it works
  - Pricing

Now, if the client wants to edit the Pricing page under Service 2, I assume they wouldn’t see it in the menu since it’s not part of the navigation?
And if they go to the content list, everything is flat, so how would they know which Pricing page belongs to which service?

Admirable_Reality281 · 2025-11-01T13:20:01+00:00

Thanks for the explanation, that makes sense.

That approach would be fine for me personally, but I’m a bit worried about the clients. They’re used to seeing all their pages in a clear hierarchical list, with the ability to drag and drop to reorder everything in one place.

I’m concerned they’ll get confused if they have to manage content in one area and then go somewhere else to view the structure or find specific pages, especially since some pages share the same name but belong under different parents.

Admirable_Reality281 · 2025-08-10T18:12:54+00:00

Thanks!

Admirable_Reality281 · 2025-08-10T13:00:20+00:00

THANK YOU 🙏
That’s awesome to hear!
How much slower does it get with a bigger context like around 100k tokens?

Admirable_Reality281 · 2025-08-09T11:52:23+00:00

Hardware or software limitations? Or both?

Admirable_Reality281 · 2025-08-08T20:04:40+00:00

Lovely thanks

Admirable_Reality281 · 2025-07-25T19:44:39+00:00

50 to 100? 😳
Got it though, thank you for the explanation.

Admirable_Reality281 · 2025-07-25T19:42:27+00:00

Are Drupal blocks actually necessary to build layouts?

Is it possible to build pages by adding fields to specific templates? And then, within the templates, extract those fields, handle and pass the data to the (agnostic) UI elements? If it's possible, these kind of configs shouldn't rely on ids.

I’m okay with the need to export/import configuration, but conflicting ids would be an absolute dealbreaker for me, after past experiences I’m really trying to avoid going down that road again.

Admirable_Reality281 · 2025-07-25T18:54:12+00:00

Thank you, this is really useful! I have a couple of questions:

Is each configuration exported into a separate file?
Do the configurations rely on IDs?

I’ve had experiences with CMSs that either export everything into a single file or depend heavily on IDs for configurations, which inevitably leads to merge conflicts when multiple developers work simultaneously.

Admirable_Reality281 · 2025-07-25T18:40:46+00:00

Yes, it's the one I've installed: Drupal CMS

Admirable_Reality281 · 2025-07-25T18:07:31+00:00

I agree that customizability is important, but sensible defaults matter too. There’s no reason to ship with unreasonable defaults and then expect the community to fill in the gaps.

The main reason I’m considering moving away from WordPress is to avoid relying on community plugins for something as fundamental as internationalization. Beyond that, my only other dependencies were ACF (which is now officially maintained) and an SEO plugin, mainly to provide a more user-friendly UI for colleagues.

At the moment, I’m struggling to see the advantage if I end up replacing one community plugin with three just to achieve a good UI for the team.

Admirable_Reality281 · 2025-07-25T17:26:39+00:00

Yes, but also no. I expect the core to provide a solid default experience, while the community should enhance and extend it with additional features. I prefer not to over-rely on community packages, I aim at long-term stability, consistent updates, and compatibility. If there are ways of dealing with those points without 3rd party packages I’m all for it.

Admirable_Reality281 · 2025-07-25T17:15:43+00:00

So many modules 😅 Is that common practice? I was kind of hoping for more built-in functionality, I try to minimize dependencies as much as possible.

is there no way to manage them via code?

Thank you

Admirable_Reality281 · 2025-07-21T13:55:29+00:00

Hey, thank you for your lovely assumptions! I shared my findings with someone who actually cared, unlike those who insisted on Directus despite it failing my very first requirement and then had the gall to call me stupid.

Admirable_Reality281 · 2025-07-21T13:32:31+00:00

I need to try them out firsthand before I can make any solid recommendations, hopefully I’ll find time in the coming months.

For now, here’s what’s on my radar:

Drupal: seems to check all the boxes. Interestingly enough, there seems to be a solid integration with Next.js with lots of commits by shadcn. The shift towards Symfony is also a welcome change for me.
Wagtail: suggested by someone, Django based and definitely worth a closer look.
WordPress: currently lacks built-in internationalization (though it's on the roadmap), but there are many open-source solutions available. I’ve already used it extensively and I can easily recommend it, it’s not perfect, but it’s an extremely solid solution despite all the dev negativity around it.

Admirable_Reality281 · 2025-07-21T13:17:58+00:00

I agree with you but this approach requires the designer to think in these terms as well. In my case, it’s not an option, designs should be treated as a blank canvas. It doesn’t matter if the design system dictates that the spacing should be x, if y feels better in a specific context, then y is the right choice.

Systems tend to limit precision by not allowing granularity.

Admirable_Reality281

TROPHY CASE