Hi @JacobDK, I’m sure one of the team will respond to this, in the meantime, I am wondering if you could provide a bit more information about what is not working for you in terms of backend vs. frontend styling.
I know you said those previous posts didn’t help, so as they contain several messages that show the basic strategy that Cwicly allows you to share the styles in both places, I want to make sure that you get what you need.
In summary, any styling you want on the backend and frontend for post content, you can apply to the Post Content block within your template. This even works with global classes applied to the Post Content block.
This post provides some screenshots showing the process and general tips for achieving commonly used styling (such as a max-width and centring).
If there is something still unclear or any steps that you are missing, if you post your specific needs, I am sure they will be addressed and that will help the Cwicly team also improve the documentation.
This is not working - and if I try with a Page-template it is not working either.
But I need a step-by-step as with many other awesome features. For filters there is only a video showcasing a couple of categories … For the awesome Fot Managr I have to find out about adding Helvetica or the basic fonts … somewhere … The list goes on …
Yes, I found out about woo and also the Helvetica. Not the problem, but thank you anyways.
The steps you provide in the post with the relative styling is a good example. The steps are not detailed enough and simply does not meet the simple instructions that I need.
There are steps you presuppose in order to do that. Also - it does not say if Relative Styling is necessary. Also the solution is bloated with complexity if I simply want a 700 px centered post content.
It is not clear to me how I then go about having the image being 850 px wide where as the text in the blog post should only be 700px. That is probably where the relative styling becomes awesome.
Edit that global class by clicking its chip in the block inspector (so it is highlighted with a light border)
Add whatever background colours and styles you require for the entire block (with the class still selected)
For individual elements (e.g. paragraphs and headings) add relative styles to the global class as per this post:
You have complete control over the styling of any and all blocks within the post content and these styles will be applied to the editor and the front-end display.
Please note: Some screenshots in that post show relative styles directly on the post content block, I am recommending applying them to the global class instead, let me know if you need further clarification on this.
@Louis I think we have a language-related bug here again - as with the post content appearing twice - switching back and forth between danish and english seems to make it work as intended - this is indeed frustrating to say the least - a waste of time … EDIT _ not angry … just frustrated
I send you a PM to confirm and test out with login and pass.
@JacobDK, you have a point here, it isn’t standardised. My apologies for the wasted time.
And playing with this does make me think a specific width setting for the post editor itself would be more than useful.
No, it is not standardized and streamlined and mainstreamed for me. But this is not making sense to me. Such an awesome builder - although an HTML-builder (that accidently uses wordpress :)) more than a pagebuilder for wordpress - and then you do not really offer support in ters of helpful instructions and guidance for it. Maybe it is meant to be a secret how to use Cwicly.
A mystery to me more than anything these decisions.
Anyways … Much respect for your talents and vision.
Cwicly is my first WP builder. I tried many but never adopted one. I’m used in designing custom WP sites with Figma and coding in VSC. A simple Pro bono project landed about a charity organisation and I thought it was the time to use that Cwicly license I got last November. I was advised that it has a steep learning curve but was lured by its capabilities. Two weeks on and still learning basic functionality. It’s not a rant, it’s how things are.
Also it shold be tested by others and confirmed/rejected and perhaps included in the how-to/tutorial, that if you have set a maintenance and coming soon page with a template override of 99 as in the tutorial - see youtube-link - the template for the post type you want to layout and design should be a higher number than 99, thus taken presedence over the other template apparently - that was at least one way I got it to work.