I don't have that particular template 'Frame' so I'm unsure how it was built. But in my component repository I have something similar, although not exactly the same, you could take a look at https://mock-up.coffeecup.com/ma-comps/ … -text.html .

Thank you for your response, dear Inger! Is it possible to create a breadcrumb in Frameworkless? To be more precise, I understand that it's possible, I just don’t know the exact sequence of steps. I apologize for asking so many questions, I just want to figure things out and decide which path to choose. So far, I prefer Frameworkless because it gives more creative freedom, at least in terms of approach. But to make a definite choice, I need to understand all sides of this decision.

https://youtu.be/4KveYNvtXlo



Sorry to but in
Yes frameworkless allows designing desktop down, but one thing you should be aware of and that is the version of Vanilla CSS that framework uses is to say the least a little bit out of date and limits what you can do WITHIN Site Designer canvas. To achieve some of the things you mention would require more than a modicum of CSS/JS properties etc knowledge AND the effect/style etc WOULD NOT be visible until you purview on a browser.

Which sort of defeats the whole object of using a WYSIWYG app like Site Designer, in my own humble opinion, to start using a lot of custom code to achieve something in Frameworkless defeats the object of many users thinking its easier to use than the other frameworks.

At least the framework |"foundation" for instance (also very behind on CSS, but then there's not a lot CC can do about that, until Zurb foundation update it. and the others have more flexibility, to use built-in components, elements etc.

The effect you are looking at is possible in ALL frameworks but requires custom code in Frameworkless, even it's only 1 line of CSS one line here one line there `1 line everywhere can soon add up.

Oh, that is one I haven't made a component of! I'll make one as soon as I have time. But you can find the steps at W3schools: https://www.w3schools.com/howto/howto_c … crumbs.asp

If there is some CSS setting that you cannot select in SD, then use the first box (for head code) on the Element panel and add it there, like e.g.
<style>
ul.breadcrumb li+li:before {
padding: 8px;
color: black;
content: "/\00a0";
}
</style>

You could try popping it into the head code box of the ul, or if you have a wrapper class for the whole menu, then add it into the wrapper's head code box. Sometimes you need to 'play it by ear' which element's box to add it to.

You could also look into the components which are included with Foundation or Bootstrap. Both have a breadcrumb component that seems to be simpler than the one at W3schools.

Wayan, butt in as much as you like!

The fact that Materialize is somewhat outdated is something I mentioned earlier in this conversation. And many users indeed choose either Bootstrap or Foundation for easiness. Personally, I have also reverted to Foundation if I wanted to achieve something I was very uncertain about, especially if I needed Wayan's help (remember kandoraservice.de , Wayan? )

Exactly, Wayan! That's precisely why I’m asking how to achieve the necessary functionality using Site Designer (SD). I can create the same breadcrumb in a standard HTML editor, but I'm specifically interested in doing it in SD. Everything that the mentioned frameworks offer can be achieved in any HTML editor, and in case of any issues, you can simply refer to the corresponding documentation, which is not the case with SD. Hence my endless questions, because I want to solve tasks that are easy in an HTML editor within SD. And I believe SD has this potential, it’s just that there is no documentation regarding working with Materialize, Bootstrap, Foundation, or Frameworkless inside SD.

I went through the same process when I started using SD, at first reluctantly, in 2016. I have been creating websites since 1996, at first with Notepad, then with various HTML programs (until I came across the one from CC which I'm still using). In 2016 the documentation for SD was far from organised, but it has become so since then. But it is not the kind of documentation that I needed. I would have wanted something that explained things to those who actually have the necessary coding skills, and who are trying to follow what actually happens when you start working with SD. But SD was at first intended to replace the old VSD app that was completely drag and drop, never mind the code.
Well, one finds out about the workwise after a while, but it would have been much quicker if there had been an explanation. One reason for starting that component collection of mine, was to find out how things work, or rather how one can make them work in SD. After some 500-odd components I'm still struggling in some cases.

Yeah, that's tough! If you’re having difficulties, then what can I say about myself?
If there were championships for stubbornness, I would undoubtedly take first place with a huge lead
So, I’m not planning to give up and will still get to the bottom of everything. I’ll need some time to tinker with the existing topics, and little by little, everything will become clear, though I’ll lose a lot of time in the process.

By the way, Wayan! This is exactly what I was asking about! How did you do that?

I will do a step by step video later,