Skip to content

Material View Support for Stock NodeBB

Unsolved Let's Build It
51 3 26.9k 1
  • wrote on last edited by
    #29

    Thanks for explain. Make sense, indeed but it’s not easy to know without Baris help 🙂


    Still with the idea of improving the code, I’m going to focus now on making the selection button appear on Smartphone.

    Indeed, currently, it does not appear because it seems that on Smartphone another component is used

    b46c3d29-7f77-4f85-b207-790f2f10378b-image.png

    10d1925e-fad1-42e0-b209-12fcc9dc6ca5-image.png

  • wrote on last edited by DownPW
    #30

    I test this :

    // ------------------------------------------
    // material View Mode
    // ------------------------------------------
    
    function material() {
        $(document).ready(function () {
            var $buttonContainer = null;
    
            // Check if the screen width is 460px or more
            if ($(window).width() >= 991) {
                // Check if the custom thread view button already exists in the right sidebar
                $buttonContainer = $('[component="sidebar/right"]');
            } if ($(window).width() <= 991) {
                // Check if the custom thread view button already exists in the bottom bar
                $buttonContainer = $('[component="bottombar"]');
    
            }
    
    
  • I test this :

    // ------------------------------------------
    // material View Mode
    // ------------------------------------------
    
    function material() {
        $(document).ready(function () {
            var $buttonContainer = null;
    
            // Check if the screen width is 460px or more
            if ($(window).width() >= 991) {
                // Check if the custom thread view button already exists in the right sidebar
                $buttonContainer = $('[component="sidebar/right"]');
            } if ($(window).width() <= 991) {
                // Check if the custom thread view button already exists in the bottom bar
                $buttonContainer = $('[component="bottombar"]');
    
            }
    
    
    wrote on last edited by phenomlab
    #31

    @DownPW yes, the same methodology is used for the theme switcher in NodeBB v2.x 😀

  • wrote on last edited by
    #32

    ohh yes, don’t see that to be honest.

    Button appear but hard to position it correctly for all resolution.
    The button moves according to the resolution. it is not fixed

  • ohh yes, don’t see that to be honest.

    Button appear but hard to position it correctly for all resolution.
    The button moves according to the resolution. it is not fixed

    wrote on last edited by
    #33

    @DownPW if you use apend then it should reflect the div it is inserted into.

    The version of the theme switcher from the NodeBB v2 series used the same mechanism, and that code is still listed in this forum. It would be a good idea to review that code for inspiration as the placement for the switcher drop down was set depending on screen estate.

  • wrote on last edited by
    #34

    @DownPW this should provide the functionality you are looking for

    // ------------------------------------------
    // material View Mode
    // ------------------------------------------
    function material() {
        $(document).ready(function () {
                // Create the button for custom thread view mode with custom IDs
                if ($('#materialThreadViewButton').length === 0) {
                    var threadViewButton = $('<div class="material-threads-wrapper"><form class="form"><div class="form-check form-switch form-switch-sm material-threads-wrapper"> \
                        <input class="form-check-input" id="materialThreadViewButton" type="checkbox" data-field="materialThreadView"> \
                        <label class=" d-none d-md-inline fw-semibold" for="materialThreadViewButton"></label> \
                    </div></form></div>');
                    
                            // Check if the screen width is 460px or more
            if ($(window).width() >= 991) {
                // Check if the custom thread view button already exists in the right sidebar
                var buttonContainer = $('[component="sidebar/right"]');
                // Append the button to the selected container
                buttonContainer.append(threadViewButton);
            } 
            if ($(window).width() <= 991) {
                // Check if the custom thread view button already exists in the bottom bar
                //$buttonContainer = $('.bottombar-nav.p-2.text-dark.bg-light.d-flex.justify-content-between.align-items-center.w-100');
                if ($("#logged-in-menu").length > 0) {
                var buttonContainer = $('.bottombar-nav ul#logged-in-menu');
                }
                else {
                    var buttonContainer = $('.bottombar-nav ul#logged-out-menu'); 
                }
                            // Prepend the button to the selected container
                buttonContainer.prepend(threadViewButton);
            }
                }
                // Check if there's a stored state for the checkbox and update it
                var storedState = localStorage.getItem('materialThreadViewState');
                console.log("Stored State is " + storedState);
                if (storedState === 'true') {
                    $('#materialThreadViewButton').prop('checked', true);
                }
                
                // Toggle the class 'material' on or off when the checkbox changes state
                $('#materialThreadViewButton').on('change', function () {
                    var isChecked = $(this).is(':checked');
                    var theTooltip = isChecked ? "Material View Off" : "Material View On"; // Update tooltip message
                    
                    // Toggle CSS rules when the button is turned on or off
                    if (isChecked) {
                        console.log('Material Thread view is active.');
                        // Apply your CSS rules here
                        $('[component="category/topic"]').addClass('material'); 
                        $('li[component="category/topic"]').addClass('material'); 
                        $('[component="categories/category"]').addClass('material');
                        
                        $('.posts-container').addClass('material')
                        $('ul[component="topic"]').addClass('material')
                        $('.post-container').addClass('material')
                        $('.timeline-event').addClass('material')
                        $('[component="post/footer"]').addClass('material')
                        $('li.pt-4.deleted').addClass('material') 
                        
                        $('.page-topic .topic .posts.timeline .timeline-event > div:first-of-type, .page-topic .topic .posts.timeline > [component="post/placeholder"] > div:first-of-type, .page-topic .topic .posts.timeline > [component=post] > div:first-of-type').addClass('material');
    
                        $('[component="post"]').each(function () {
                            // Add the 'material' class to matching elements
                            if ($(this).hasClass('pt-4') || $(this).hasClass('self-post')) {
                                $(this).addClass('material');
                                $('[component="sidebar/right"]').addClass('material');
                            }
                        });
                        $('[component="topic/necro-post"]').each(function () {
                            // Add the 'material' class to matching elements
                            if ($(this).hasClass('timeline-event')) {
                                $(this).addClass('material');
                            }
                        });
    
                    } else {
                        console.log('Material Thread view is inactive.');
                        // Remove the CSS rules here
                        $('[component="category/topic"]').removeClass('material');
                        $('li[component="category/topic"]').removeClass('material');
                        $('[component="categories/category"]').removeClass('material');
                        
                        $('[component="post"]').removeClass('material');
                        $('ul[component="topic"]').removeClass('material');
                        $('.posts-container').removeClass('material')
                        $('ul[component="topic"]').removeClass('material')
                        $('.post-container').removeClass('material')
                        $('.timeline-event').removeClass('material')
                        $('[component="post/footer"]').removeClass('material');
                        $('li.pt-4.deleted').removeClass('material'); 
                       
                        $('.page-topic .topic .posts.timeline .timeline-event > div:first-of-type, .page-topic .topic .posts.timeline > [component="post/placeholder"] > div:first-of-type, .page-topic .topic .posts.timeline > [component=post] > div:first-of-type').removeClass('material'); 
    
                        $('[component="sidebar/right"]').removeClass('material');
                        
                    }
                    
                    // Store the checkbox state in localStorage
                    localStorage.setItem('materialThreadViewState', isChecked);
                    
                    // Update the tooltip title
                    $(this).attr('data-original-title', theTooltip).tooltip('dispose').tooltip({
                        placement: 'bottom',
                        title: theTooltip,
                        trigger: 'hover'
                    });
                });
    
                // Check for changes in the checkbox state when the page loads
                $('#materialThreadViewButton').trigger('change');
            
        });
    }
    

    Result

    6246743e-a9dd-40e3-b07f-5a69f6e54002-image.png

    I ddjusted some of your CSS - added this block

    #logged-out-menu .material-threads-wrapper {
        top: 5px;
        position: relative;
    }
    

    Also removed this block

    #materialThreadViewButton {
    }
    

    Not needed 🙂

    There are are two checks - one tests the screen estate and positions the menu item depending on size, and the other will see if the user is logged in or not, and if they are, it uses ul#menu-logged-in else it uses ul#menu-logged-out

    But only for the mobile view because .bottom-bar is based on both logged in and logged out sessions

    Enjoy

  • wrote on last edited by DownPW
    #35

    Thank you Mark for the button in Smartphone.

    In nodeBB 3.5.0, we can use .bottombar-nav-left or .bottombar-nav-right because @baris have created this components follow-up to my topic.

    Maybe update the code at this moment because cleaner.

    See here:

    https://community.nodebb.org/post/96323

    @phenomlab said in Material View Support foir Stock NodeBB:

    There are are two checks - one tests the screen estate and positions the menu item depending on size, and the other will see if the user is logged in or not, and if they are, it uses ul#menu-logged-in else it uses ul#menu-logged-out

    Seems to be good.


    I have again one or 2 other modification like the scroll to top button .material class to add because the button is hard to see on small phone resolutions It blends in with the color of the block of the categories. Nothing insurmountable I think. I’m getting good results

    I’m happy, this code is starting to look like something 🙂

  • Thank you Mark for the button in Smartphone.

    In nodeBB 3.5.0, we can use .bottombar-nav-left or .bottombar-nav-right because @baris have created this components follow-up to my topic.

    Maybe update the code at this moment because cleaner.

    See here:

    https://community.nodebb.org/post/96323

    @phenomlab said in Material View Support foir Stock NodeBB:

    There are are two checks - one tests the screen estate and positions the menu item depending on size, and the other will see if the user is logged in or not, and if they are, it uses ul#menu-logged-in else it uses ul#menu-logged-out

    Seems to be good.


    I have again one or 2 other modification like the scroll to top button .material class to add because the button is hard to see on small phone resolutions It blends in with the color of the block of the categories. Nothing insurmountable I think. I’m getting good results

    I’m happy, this code is starting to look like something 🙂

    wrote on last edited by
    #36

    @DownPW great. I did see the 3.5.0 changes and they look like a good idea, but can’t comment until I’ve tried them.

  • wrote on last edited by
    #37

    you’re right as usual my friend 🙂

  • wrote on last edited by
    #38

    Test material view display on my smartphone. Seems I have a little work again 🙂

  • Test material view display on my smartphone. Seems I have a little work again 🙂

    wrote on last edited by
    #39

    @DownPW Good luck - let me know if you need any help.

  • wrote on last edited by DownPW
    #40

    Seems to be good :

    image.png

    just the line from the timeline on the left that I can’t seem to display. But I note that it’s the same here on Smartphones

    I need to check and recheck now 😉

  • wrote on last edited by DownPW
    #41

    –> For now test function in production…
    I provide all JS and CSS code for all after… and after @phenomlab check and validate of course

    – EDIT :

    Can you correct the title of the topic please ?

  • –> For now test function in production…
    I provide all JS and CSS code for all after… and after @phenomlab check and validate of course

    – EDIT :

    Can you correct the title of the topic please ?

    wrote on last edited by
    #42

    @DownPW done. Fixed a typo

  • wrote on last edited by
    #43

    Hello @phenomlab

    I didn’t even notice because I never use this mode. But when I say never it’s so much that I forget that it’s possible to do it.

    When right sidebar is expand, the button is at the bottom of the sidebar like this :
    image.png

    –> For now, I resolve the problem by change var buttonContainer = $('[component="sidebar/right"]'); for var buttonContainer = $('[component="sidebar/drafts"]');

    // ------------------------------------------
    function material() {
        $(document).ready(function () {
                // Create the button for custom thread view mode with custom IDs
                if ($('#materialThreadViewButton').length === 0) {
                    var threadViewButton = $('<div class="material-threads-wrapper"><form class="form"><div class="form-check form-switch form-switch-sm material-threads-wrapper"> \
                        <input class="form-check-input" id="materialThreadViewButton" type="checkbox" data-field="materialThreadView"> \
                        <label class=" d-none d-md-inline fw-semibold" for="materialThreadViewButton"></label> \
                    </div></form></div>');
                    
                // Check if the screen width is 991px or more
                if ($(window).width() >= 991) {
                    // Check if the custom thread view button already exists in the right sidebar
                    var buttonContainer = $('[component="sidebar/drafts"]');
                    // Append the button to the selected container
                    buttonContainer.append(threadViewButton);
                } 
                if ($(window).width() <= 991) {
                    // Check if the custom thread view button already exists in the bottom bar
                    //$buttonContainer = $('.bottombar-nav.p-2.text-dark.bg-light.d-flex.justify-content-between.align-items-center.w-100');
                if ($("#logged-in-menu").length > 0) {
                    var buttonContainer = $('.bottombar-nav ul#logged-in-menu');
                    }
                else {
                    var buttonContainer = $('.bottombar-nav ul#logged-out-menu'); 
                }
                // Prepend the button to the selected container
                buttonContainer.prepend(threadViewButton);
            }
                }
    
    ..............
    

    it’s clearly better :

    c5c4df57-b33e-46ce-814b-18e514bf6933-image.png

    but if you have better solution (like add text if sidebar is expand for example) I take it 🙂

  • wrote on last edited by phenomlab
    #44

    Seems this solution give me a new bug for tooltip

    image.png

    I have test this with no working :

    if (isChecked) {
           $('[component="sidebar/drafts"]').find('[data-toggle="tooltip"]').tooltip('dispose');
       } else {
           $('[component="sidebar/drafts"]').find('[data-toggle="tooltip"]').tooltip();
       }
    
  • Seems this solution give me a new bug for tooltip

    image.png

    I have test this with no working :

    if (isChecked) {
           $('[component="sidebar/drafts"]').find('[data-toggle="tooltip"]').tooltip('dispose');
       } else {
           $('[component="sidebar/drafts"]').find('[data-toggle="tooltip"]').tooltip();
       }
    
    wrote on last edited by
    #45

    @DownPW Seems to work fine for me?

  • Hello @phenomlab

    I didn’t even notice because I never use this mode. But when I say never it’s so much that I forget that it’s possible to do it.

    When right sidebar is expand, the button is at the bottom of the sidebar like this :
    image.png

    –> For now, I resolve the problem by change var buttonContainer = $('[component="sidebar/right"]'); for var buttonContainer = $('[component="sidebar/drafts"]');

    // ------------------------------------------
    function material() {
        $(document).ready(function () {
                // Create the button for custom thread view mode with custom IDs
                if ($('#materialThreadViewButton').length === 0) {
                    var threadViewButton = $('<div class="material-threads-wrapper"><form class="form"><div class="form-check form-switch form-switch-sm material-threads-wrapper"> \
                        <input class="form-check-input" id="materialThreadViewButton" type="checkbox" data-field="materialThreadView"> \
                        <label class=" d-none d-md-inline fw-semibold" for="materialThreadViewButton"></label> \
                    </div></form></div>');
                    
                // Check if the screen width is 991px or more
                if ($(window).width() >= 991) {
                    // Check if the custom thread view button already exists in the right sidebar
                    var buttonContainer = $('[component="sidebar/drafts"]');
                    // Append the button to the selected container
                    buttonContainer.append(threadViewButton);
                } 
                if ($(window).width() <= 991) {
                    // Check if the custom thread view button already exists in the bottom bar
                    //$buttonContainer = $('.bottombar-nav.p-2.text-dark.bg-light.d-flex.justify-content-between.align-items-center.w-100');
                if ($("#logged-in-menu").length > 0) {
                    var buttonContainer = $('.bottombar-nav ul#logged-in-menu');
                    }
                else {
                    var buttonContainer = $('.bottombar-nav ul#logged-out-menu'); 
                }
                // Prepend the button to the selected container
                buttonContainer.prepend(threadViewButton);
            }
                }
    
    ..............
    

    it’s clearly better :

    c5c4df57-b33e-46ce-814b-18e514bf6933-image.png

    but if you have better solution (like add text if sidebar is expand for example) I take it 🙂

    wrote on last edited by
    #46

    @DownPW It doesn’t look right - the toggle switch is now located at the top of the menu

    a9e329a2-fff6-407c-bc08-9668b9b002c1-image.png

  • wrote on last edited by DownPW
    #47

    yep I test things at the moment

    I’m go back for you to see

    EDIT: You can test now @phenomlab

  • yep I test things at the moment

    I’m go back for you to see

    EDIT: You can test now @phenomlab

    wrote on last edited by phenomlab
    #48

    @DownPW Try this. Change the function to

    function material() {
        $(document).ready(function () {
                // Create the button for custom thread view mode with custom IDs
                if ($('#materialThreadViewButton').length === 0) {
                    var threadViewButton = $('<div class="material-threads-wrapper"><form class="form"><div class="form-check form-switch form-switch-sm material-threads-wrapper"> \
                        <input class="form-check-input" id="materialThreadViewButton" type="checkbox" data-field="materialThreadView"> \
                        <label class=" d-none d-md-inline fw-semibold" for="materialThreadViewButton"></label> \
                    </div></form></div>');
                    
                // Check if the screen width is 991px or more
                if ($(window).width() >= 991) {
                    // Check if the custom thread view button already exists in the right sidebar
                    //var buttonContainer = $('[component="sidebar/right"]ul#logged-in-menu');
                if ($("#logged-in-menu").length > 0) {
                    var buttonContainer = $('ul#logged-in-menu');
                    }
                else {
                    var buttonContainer = $('ul#logged-out-menu');
                }
                    // Append the button to the selected container
                    buttonContainer.append(threadViewButton);
            } 
                if ($(window).width() <= 991) {
                    // Check if the custom thread view button already exists in the bottom bar
                    //$buttonContainer = $('.bottombar-nav.p-2.text-dark.bg-light.d-flex.justify-content-between.align-items-center.w-100');
                if ($("#logged-in-menu").length > 0) {
                    var buttonContainer = $('.bottombar-nav ul#logged-in-menu');
                    }
                else {
                    var buttonContainer = $('.bottombar-nav ul#logged-out-menu'); 
                }
                // Prepend the button to the selected container
                buttonContainer.prepend(threadViewButton);
            }
                }
                // Check if there's a stored state for the checkbox and update it
                    var storedState = localStorage.getItem('materialThreadViewState');
                    console.log("Stored State is " + storedState);
                    if (storedState === 'true') {
                        $('#materialThreadViewButton').prop('checked', true);
                    }
                
                // Toggle the class 'material' on or off when the checkbox changes state
                $('#materialThreadViewButton').on('change', function () {
                    var isChecked = $(this).is(':checked');
                    var theTooltip = isChecked ? "Material View Off" : "Material View On"; // Update tooltip message
                    
                // Remove any existing tooltips
        $(this).tooltip('dispose');
                    
                // Toggle CSS rules when the button is turned on or off
                    if (isChecked) {
                        console.log('Material Thread view is active.');
                        // Apply your CSS rules here
                        $('[component="category/topic"]').addClass('material'); 
                        $('li[component="category/topic"]').addClass('material'); 
                        $('[component="categories/category"]').addClass('material');
                        
                        $('.posts-container').addClass('material')
                        $('ul[component="topic"]').addClass('material')
                        $('.post-container').addClass('material')
                        $('.timeline-event').addClass('material')
                        $('[component="post/footer"]').addClass('material')
                        $('li.pt-4.deleted').addClass('material') 
                        
                        $('.page-topic .topic .posts.timeline .timeline-event > div:first-of-type, .page-topic .topic .posts.timeline > [component="post/placeholder"] > div:first-of-type, .page-topic .topic .posts.timeline > [component=post] > div:first-of-type').addClass('material');
                        $('#pageUp.show').addClass('material');
    
                        $('[component="post"]').each(function () {
                            // Add the 'material' class to matching elements
                            if ($(this).hasClass('pt-4') || $(this).hasClass('self-post')) {
                                $(this).addClass('material');
                                $('[component="sidebar/right"]').addClass('material');
                            }
                        });
                        $('[component="topic/necro-post"]').each(function () {
                            // Add the 'material' class to matching elements
                            if ($(this).hasClass('timeline-event')) {
                                $(this).addClass('material');
                            }
                        });
    
                    } else {
                        console.log('Material Thread view is inactive.');
                        // Remove the CSS rules here
                        $('[component="category/topic"]').removeClass('material');
                        $('li[component="category/topic"]').removeClass('material');
                        $('[component="categories/category"]').removeClass('material');
                        
                        $('[component="post"]').removeClass('material');
                        $('ul[component="topic"]').removeClass('material');
                        $('.posts-container').removeClass('material')
                        $('ul[component="topic"]').removeClass('material')
                        $('.post-container').removeClass('material')
                        $('.timeline-event').removeClass('material')
                        $('[component="post/footer"]').removeClass('material');
                        $('li.pt-4.deleted').removeClass('material'); 
                       
                        $('.page-topic .topic .posts.timeline .timeline-event > div:first-of-type, .page-topic .topic .posts.timeline > [component="post/placeholder"] > div:first-of-type, .page-topic .topic .posts.timeline > [component=post] > div:first-of-type').removeClass('material'); 
                        $('#pageUp.show').removeClass('material'); 
    
                        $('[component="sidebar/right"]').removeClass('material');
                        
                    }
                    
                    // Store the checkbox state in localStorage
                    localStorage.setItem('materialThreadViewState', isChecked);
                    
                    // Update the tooltip title
                    $(this).attr('data-original-title', theTooltip).tooltip('dispose').tooltip({
                        placement: 'bottom',
                        title: theTooltip,
                        trigger: 'hover'
                    });
                });
    
                // Check for changes in the checkbox state when the page loads
                $('#materialThreadViewButton').trigger('change');
            
        });
    }
    

    And modify this CSS to the below

    @media (min-width: 991px) {
    #materialThreadViewButton {
        border-radius: 7px;
        cursor: pointer;
        position: relative !important;
        z-index: 999;
        display: flex;
        left: 15px !important;
        top: 5px !important;
        transform: rotate(90deg) !important;
        }
    }
    

    Essentially, we have to change the positioning of the block to use the logged-in and logged-out ID’s

                // Check if the screen width is 991px or more
                if ($(window).width() >= 991) {
                    // Check if the custom thread view button already exists in the right sidebar
                    //var buttonContainer = $('[component="sidebar/right"]ul#logged-in-menu');
                if ($("#logged-in-menu").length > 0) {
                    var buttonContainer = $('ul#logged-in-menu');
                    }
                else {
                    var buttonContainer = $('ul#logged-out-menu');
                }
                    // Append the button to the selected container
                    buttonContainer.append(threadViewButton);
            } 
    

Related Topics
  • Extended functions for Q&A NodeBB plugin

    Let's Build It q&a panels cards
    3
    4
    5 Votes
    3 Posts
    3k Views
    DownPW
    Very good like always
  • navigation menu panel on mobile

    Solved Customisation nodebb css
    8
    1
    7 Votes
    8 Posts
    3k Views
    phenomlab
    @crazycells hmm. That’s odd. I haven’t made any changes from recollection but I could be wrong. I’ll need to check. EDIT - very strange. I honestly don’t recall adding the below CSS block to alter the bottom bar, but you’re right… .bottombar-nav { padding: 0px !important; } I’ve removed this so it reflects stock Harmony.
  • Switch between list and card view function

    Moved Let's Build It cards layout css
    107
    1
    50 Votes
    107 Posts
    57k Views
    phenomlab
    @crazycells [image: image.png] [image: image.png]
  • Threaded chat support for NodeBB

    Let's Build It threaded chat code
    35
    1
    19 Votes
    35 Posts
    16k Views
    phenomlab
    @DownPW said in Threaded chat support for NodeBB: Better like this : add shadow and border-left on self answer Of course - you style to your own requirements and taste I’ll commit that CSS we discussed yesterday also
  • Threaded post support for NodeBB

    Let's Build It threading nodebb
    146
    3
    50 Votes
    146 Posts
    116k Views
    phenomlab
    Updated git for above change https://github.com/phenomlab/nodebb-harmony-threading/commit/14a4e277521d83d219065ffb14154fd5f5cfac69
  • hover link effect

    Solved Customisation css link hover
    18
    1
    6 Votes
    18 Posts
    7k Views
    phenomlab
    @DownPW Looking at the underlying code, class start is being added on hover by jQuery in this function document.querySelectorAll(".button-gradient, .button-transparent").forEach((button) => { const style = getComputedStyle(button); const lines = document.createElement("div"); lines.classList.add("lines"); const groupTop = document.createElement("div"); const groupBottom = document.createElement("div"); const svg = createSVG( button.offsetWidth, button.offsetHeight, parseInt(style.borderRadius, 10) ); groupTop.appendChild(svg); groupTop.appendChild(svg.cloneNode(true)); groupTop.appendChild(svg.cloneNode(true)); groupTop.appendChild(svg.cloneNode(true)); groupBottom.appendChild(svg.cloneNode(true)); groupBottom.appendChild(svg.cloneNode(true)); groupBottom.appendChild(svg.cloneNode(true)); groupBottom.appendChild(svg.cloneNode(true)); lines.appendChild(groupTop); lines.appendChild(groupBottom); button.appendChild(lines); button.addEventListener("pointerenter", () => { button.classList.add("start"); }); svg.addEventListener("animationend", () => { button.classList.remove("start"); }); }); }) The CSS for start is below .button-gradient.start .lines svg, .button-transparent.start .lines svg { animation: stroke 0.3s linear; } And this is the corresponding keyframe @keyframes stroke { 30%, 55% { opacity: 1; } 100% { stroke-dashoffset: 5; opacity: 0; } } It’s using both CSS and SVG, so might not be a simple affair to replicate without the SVG files.
  • [NODEBB] Help for my custom CSS

    Solved Customisation nodebb css bugfix
    258
    49 Votes
    258 Posts
    168k Views
    cagatay
    mark hi, Refused to apply style from ‘https://efelsefe.com/assets/customfonts/FontAwesome-6-Pro/pro/css/v4-font-face.css’ because its MIME type (‘text/plain’) is not a supported stylesheet MIME type, and strict MIME checking is enabled. I keep getting this error.
  • [NodeBB] Import custom Font

    Solved Customisation custom fonts nodebb css
    12
    3 Votes
    12 Posts
    5k Views
    phenomlab
    @cagatay you’ll need to define this in the body tag (or another element if you want greater or more granular targets) - for example body { font-family: "Poppins"; font-size: 16px; } Essentially, you use the font-size CSS directive.