Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs

Dashboard
Notifications
Mark all as read
Q&A

How to test CoDesign? Question

+2
−0

If I make any changes to CoDesign. Then, I have to test what changes I made. Is there possible way to build local server (http://localhost/)? To test while making changes.. I have run npm install, npm run build and npm run js_build. I don't know what I should do next.

Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

3 answers

+3
−0

I have a test page on my local dev environment so that I can test things. If you look at .gitignore, you'll find there's an ignore in there for scratch/* already.

Create a directory called scratch, add an index.html in there something like this:

<!-- index.html -->
<!doctype html>
<html lang="en">
<head>
    <meta charset="utf-8" />
    <title>Test Page</title>
    <link href="../dist/codidact.css" rel="stylesheet" type="text/css" />
    <script src="../js/co-design.js" type="application/javascript" defer></script>
    <script src="https://code.jquery.com/jquery-3.6.0.min.js" type="application/javascript"></script>
    <script src="scratch.js" type="application/javascript"></script>
</head>
<body>
    <header class="header is-dark h-bg-green-700">
        <div class="container header--container">
            <div class="header--brand">
                <a class="header--instance-name" href="#">Codidact</a>
                <a class="header--site-name" href="#">Gibberish</a>
            </div>
            <div class="header--menu">
                <a class="header--item is-visible-on-mobile is-complex" href="#">
                    <img src="https://placekitten.com/100/100" class="header--item-image" alt="..." />
                    <span class="header--alert">1</span>
                    <span class="header--trust-level">5</span>
                </a>
            </div>
        </div>
    </header>
    <main class="container">
        <!-- add whatever you want to test in here -->
    </main>
</body>
</html>

I also have a scratch.js file in the same directory so that I can test any JS functionality, but if you're just making CSS changes that HTML is all you'll need.

Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

scratch.js ? :thinking: (5 comments)
+0
−0

Use the following command for live server. said Luap

npx @11ty/eleventy --serve

It is better than other answers.

Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

+0
−0

After searching thousand days, finally found a easy way to directly link CoDesign to qpixel.


Clone qpixel and follow the instruction to run qpixel in your system. Then, make changes to /app/views/layouts/_head.html.erb. Clone CoDesign anywhere you want inside qpixel. Then, write the following line instead of /app/views/layouts/_head.html.erb.

If you are working on JS than, link that to https://github.com/codidact/co-design/blob/develop/js/co-design.js

And, If you are working with design than, you can connect to it. There's lot more but, it's the main one.

Why does this post require moderator attention?
You might want to add some details to your flag.

0 comment threads

Sign up to answer this question »

This community is part of the Codidact network. We have other communities too — take a look!

You can also join us in chat!

Want to advertise this community? Use our templates!