Template-a-thon Review and Frequently Asked Questions

As we reflect on the past two months, we are incredibly excited and grateful for the overwhelming response we received for the 4EVERLAND Template-a-thon Challenge. Developers from all over the world actively participated and submitted impressive works. These creations showcased the creativity and technical skills of the developers while adding a diverse range of content to the Template Center.

The purpose of this challenge was to provide a platform for template enthusiasts and creators to share their innovative ideas and templates with the world. We are thrilled to see the variety of ideas and solutions submitted during this period. Templates related to social interactions, practicality, and development tools came pouring in, and each submission demonstrated the originality and dedication of our developer community.

Currently, our event is still ongoing, and we have carefully reviewed the templates that have been submitted so far. The judging criteria include originality, sustainability, potential impact, technical capability, practicality, user experience, and engagement. Our core team and judges meticulously evaluate each template based on these criteria, which is a challenging task. By now, many developers have indeed received the corresponding T-4EVER rewards, and we want to extend our congratulations to them! We firmly believe in the importance of supporting developers and motivating their hard work. and we ensure that these outstanding templates will receive official marketing support from 4EVERLAND.

If you haven't participated in the challenge yet but are interested, please visit the link to obtain detailed information. We look forward to your participation.

Frequently Asked Questions

We have noticed that developers often encounter the following common issues since the launch of the Template-a-thon. Please take note of the following:

1. Lack of SSR (Server-Side Rendering) support: Currently, 4EVERLAND does not support the deployment of SSR projects. Therefore, templates of this type cannot pass the review process. If you are using the Next.js framework but support static output, please specify this in your package.json file.
2. Location of the config.json file: The Template Center compiles your code before uploading it. It is required that the config.json file be located in the root directory after the code has been compiled; otherwise, it will not be able to be read.
3. Referencing the config.json file in the code: After your code is compiled, the relative path of the config.json file may change. Therefore, it is important not to use relative paths when referencing the config.json file in your code.

Error cases

import data from "../../public/config.json"

Correct Example (It is recommended to use the GET request method to read the config.json file in the root directory)

this.$axios.get('./config.json').then(res=>{
      console.log(res.data);}

In addition, please adhere to the specifications of the config.json file. For detailed information, please refer to: https://docs.4everland.org/hositng/guides/site-deployment/templates-configuration-file

Lastly, we extend our heartfelt gratitude to all participants of the 4EVERLAND Template-a-thon challenge. Your creativity, passion, and hard work have made an indelible mark on 4EVERLAND. Your spirit of dedication continues to inspire us, and we look forward to witnessing your continuous growth and achievements.

Thank you for accepting the challenge and showcasing your exceptional template-making skills!

About 4EVERLAND

4EVERLAND is a Web3 infrastructure powered by blockchain technology that provides developers with convenient, efficient, and low-cost storage, network, and computing capabilities. It is committed to helping developers smoothly transition from Web2.0 to Web3.0 and building a Web3.0 cloud computing platform friendly to Web2.0.

Website | Twitter | Telegram | Discord | Reddit | Medium | Email