I’m in love but need more

[bribaird]

Good evening.

I’ve spent this week playing around with this tool and I’ve fallen in love.

I’m working with my 16 year old son a getting him to the world of web development as a side line project.

While he’s knee deep managing some very old code heavy sites, I want him to adopt a framework to make website management more of a passive income for him.

And then we found your tool, which by the way is truly remarkable for a single developer project over the timespan you’ve worked on it.

We’ve been playing around with the various deployment methods. Local, docker, aws lightsail and find many use cases. I’m struggling to find the best solution at the moment. But we will get there.

One thing I think I’d find really useful, is an online meeting (or a recorded YouTube video) with you and all of your followers, so you can share your vision for the project. Your preferred ‘best practices’ for the tool. Give us a demo of how you use the tool to build the templates.

This is an amazing project but I have so many questions but most are down to my lack of knowledge.

Hope you see this message even if it’s just for the pat on your back that you very much deserve.

Brian.

[givanz]

Hi,

Thank you!

Deployment should be easy on any platform that runs PHP, on shared hosting is enough to unzip, upload, open page in browser for install, there is also CLI install for automatization.

I don't have experience or the right setup for recording videos, I plan to record some screencasts for video tutorials for common scenarios and setups after I improve documentation.

Until videos will be available feel free to ask any question you might have here in the forum.

Themes don't have any requirement except file structure, like content/post.html for post page, index.html for homepage etc the structure is listed here https://dev.vvveb.com/theme-introduction

Themes are plain html, a static version of the site, there is no template engine/language to keep it simple for the page builder.

Dynamic content from database is inserted using html attributes and dynamic "regions" are grouped as components, for example a posts list using posts component can be rendered using:

<div class="container" data-v-component-posts data-v-limit="6" data-v-image_size="small">      

	<article class="card" data-v-post>
		<img src="/media/posts/1.jpg" data-v-post-image>

			<a href="/hello-world" data-v-post-url>
			  <h3 data-v-post-name>Hello world</h3>
			</a>

		  <p data-v-post-content>
			Post content
		  </p>

		  <a href="/hello-world" data-v-post-url>Read more</a>
	  </article>
	  
</div>

While themes are composed of static html files and can be edited by hand or generated by various tools, the default Landing theme uses gulp to make development easier.

It uses includes for common page parts like header/footer and sections and it also has a script to generate screenshots for sections automatically.

The best way to start a new theme is to git clone the Landing theme to the /public/themes folder and start changing the html code/sections.

The source code is located in /src folder for html and in /scss for saas (css).

After making changes you can run the following commands in the terminal in the theme folder

# install gulp, only needed once after git clone
npm i

# generate html files from html in /src folder
npm run gulp

# watch for changes and compile, used for development
npm run gulp watch

# generate sections/sections.js file that is loaded by the page builder to display theme sections
npm run gulp sections

# generate screenshots for theme sections to use in the page builder
npm run gulp screenshots

Let me know if you need help or other info with theme development or other tasks.

Regards,
Givan