I like the idea of FAQ content for SEO on my homepage, but the accordion is needed because it helps to hide the content from the user and lessen the amount of page they have to scroll on mobile devices.
Is there a way to make a snippet produce an FAQ accordion?
I’ve wanted to do something like this for years but estimates for this type of work are so expensive it’s not even worth it IMO. I can’t imagine it would cost less than $2500. It would have been great if REW still allowed shared/collaborative projects where multiple site owners could share in the cost of these types of customizations but they did away with that unfortunately.
Hey Brian, that’s actually not accurate. We are completely fine with (and in fact encourage) collaborative projects. I think that gets confused with the fact that we don’t “support” collaborative projects (in terms of free customer support post-launch)
Collabs are still “custom projects” (they are not part of the “product” so collaborators need to know and be aware that not only is there a development cost to the project, but any ongoing maintenance will bear a cost of they build something custom.
Which hopefully makes sense.
By all means do a collab project.
Also, there is another path - and that is right here in the community (what this consumer just did).
Customers (community members) are where we get some (most) of our great ideas.
And so to advocate for a feature (and help spec it) on the community is a great way to get it on the roadmap.
Of course, it can’t be a 1 of (or something 3 or 5 people want) there needs to be a clear demand for large adoption (otherwise the framework becomes a mess of too many features that only a few people use).
But you certainly can spec it out here if you like and we’re happy to participate in the discussion.
FYI - I do take a contrarian positon on this feature however - I do not think anything should be “hidden” for design.
Technically I pasted the code here too so you could just take it here as well.
@Morgan can clarify this though, I am not sure on the REW rules in terms of copying someone’s code. You may have to modify it to some extent as they have something in their TOS about this. Which I believe is more content related but could extend to the code as well.
Also you can’t just copy and paste everything from someone’s site. Often you need style changes in there as well.
Rules are pretty simple - if it’s using standard HTML code that is out there and are just viewing source to “learn how to do it” (ie it’s not custom code) then you’re fine.
Content on the other hand (written words) you cannot copy and them modify. If you do that, you’re engaging in the creation of what is referred as a “derivative work” which still falls under the category of intellectual property theft and is thus illegal.
So never copy someone’s content when looking to create your own.
The same goes for “design code” (like CSS etc) - which is different than a standard feature. CSS (cascading style sheets) are custom-modified and hand written by the creator - in REW you can’t create style sheets anyways, so it’s not really a thing (you should use the CSS built into Renaissance) but it is a TOS violation to take someone else’s CSS,
But viewing source to see how a “standard” HTML element works, and then implementing that feature? No problem whatsoever
I knew I shouldn’t have said it lol… what’s the difference between copying html and css? What’s “standard HTML code” I just don’t want to be giving bad advice to users. I know everything comes back to 1/0’s in the end but that does feel like there’s a lot of room for interpretation and grey space which as a user is tough to swallow.
My guess is you are reserving that for explicit scenarios where it’s a near copy. I truly can’t be upset if someone takes the headers from a community page I created -
WHAT IS THE POPULATION IN DISCOVERY RIDGE?
HOW MANY PEOPLE LIVE IN DISCOVERY RIDGE?
Where they include their own (similar) write up. That’s not a derivative, that’s a foundational piece of content that could be on all pages. Everything would be considered a derivative and nobody could write anything.
You can add custom CSS code on the website through GTM.
BTW - I should clarify (without prejudice), as long as you are not attempting to copy our code elsewhere, and you’re just trying to enhance your own site (on a REW-hosted domain) we certainly encourage creativity in the use of HTML / CSS - we love seeing it in fact.
Obviously nothing nefarious (like removing trademarks or making the “property listed by” 1 pixel high < which would be an MLS compliance violation)
But in general - if you want to flex your creative or nerd muscles (I mean that in the most flattering of contexts as I am also a nerd) - then fill your boots!
In fact come here and share your ideas, ask questions etc
PS. Since we talked earlier on this thread, I was also looking into it.
Just have to write your own CSS to make it (or have us do it) - but it’s a cool implementation. I especially like how they have an on state colour (changes to blue) when you’re on a specific question so you know where you are.
@AmyPye some great design elements on this site in general
Please do add an accordion to Renaissance! Weglot is nice and clean. I also like this example that has a card like design. See it in action at the link. (The resizing animation and color shadow is a little over the top, IMHO) F.A.Q. Accordion Style - Webflow
Agree on extra padding which would bring it closer to Renaissance style. An optional icon just to the left of the question, but still inside the card, could be neat. I can see that being an optional visual indicator to help categorize the FAQ items.
That is fantastic!! Ideally we could drop our own icons/images in there. We’ve long wanted something like this and I can think of several uses we would do. Checklists for seller to prepare homes for listing, quarterly home maintenance, etc. Feature and benefit type lists in addition to the usual FAQ. Morgan had a great point about exposing information. I largely agree! At the same time, I think these can be very useful in certain scenarios.