-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding special call to action row is still pending #99
Comments
I told this to you 2 weeks ago - #56 (comment) |
@sojonatgithub https://github.com/intelops/website/tree/chandu/assets/images/call-to-actions |
@tfsojon , After you done adding that special call to action thing for Compage page, let me know to test it in my local. If everything looks good, you can provide me steps on how to add it for other pages and I will do it myself this weekend. @sojonatgithub @tfsojon , hope you got the updated assets from this link |
added in this commit b2271a9 |
@sojonatgithub @tfsojon This is the video I shared in that comment; just sharing the same in this message as well, |
@tfsojon This video is related to this commit , |
@devopstoday11
Footer has this options in every page
Image alignment in platform and open-source pages are bottom-right aligned.because the CTA was designed like that way. those are different. On other pages the image-alignment is ok. |
Maybe the form provider issue |
We need to add security-header in netlify. don't worry I'm working on it. |
Let me know if I need to add anything to my Netlify for that. |
@tfsojon
![image](https://user-images.githubusercontent.com/59978378/233243171-0f400123-9a51-4506-8f39-06d0a7499140.png)
In one of the videos I asked for this section.
I want it in a way that it is available for every page, and I want to disable or enable to show only when we are ready to show this call to action row in a page.
Please let me know what assets you need from me to get this done. For all the project pages, we made dedicated images and gave different colors on every page. We want to be able to do the same for this call-to-action row wherever we put it.
The text was updated successfully, but these errors were encountered: