Next.js folder structure:
I want to create a dashboard folder under my pages folder. Inside that every page will have a fixed dashboard structure. So I want to make a file like _app inside dashboard folder where I will provide my layout so that I can have every page under dashboard to have same layout.
How can I make this?
Related
I am currenty working in a project that runs on Node.js on Docker. For that, I have built a landing page using Bootstrap. In the middle of project, our team would implement Wordpress as CMS.
Can I use that landing page inside Wordpress CMS?
Yes you can. Just create your page in the WordPress. Grab the id of the page and then use it to create your file. For instance, page-12.php and then copy this file in the root of your theme directory. You can copy your bootstrap/html code to this file. And then simply go to www.yourdomain.com/landingpage. Hope this makes sense.
I am working on my first shopware project. I need to create a new contact us page on shopware using my own template. My contact us page contains two forms and some other contents.
If someone can tell me how to create a custom template page on shopware I know how to add two forms and the other page contents into it.
In theme folder, there is a folder called “custom” for the content pages such as “about us” . I need to create a same type of page for my new contact us page.
Please let me know if the question is not clear.
You have to create a custom Theme via the Theme Manager in the Backend, the CLI or on your own with a Folder below themes/Frontend/ThemeNameHere and a file "Theme.php"(documentation).
After that you have to create a file at the same place where the one you want to override. In your case below themes/Frontend/ThemeNameHere/frontend/forms.
Then simply name the file like the original file and put in the first line {extends file="parent:frontend/forms/fileNameHere"} and copy the smallest available {block name="specificBlockName"}{/block}. After that you only have to change the selected theme in the backend to your new theme.
I think this is very well explained in the documentation.
Additional you can take a look at Udemy but it is in german.
Instead of just using Express for single-page-sites and web applications, I've recently been trying to use express to replace a php Intranet site, where the site has many different pages and some of those pages are just intended to be totally different from others on the same site.
As I develop web pages on Express, there's one aspect (and only one) of php I kind of miss and that is:
With php you could easily group all static-files related to a particular web page into one folder with the server-side-scripting.
For example, sometimes a page I create has static files and views that are not going to be needed by other pages in the entire site, and for pages like this, I like to just put all the images, client-side-javascripts, css, and server-side-scripting into a single folder. Later, if I need to edit this page, I can go right-click on that folder and open all related files (client-side and server-side) in my text-editor at once.
With Express, I have to create a route in one place, put static files in a folder some other place and create views in yet another place. Later when I want to open up all the files related to the page, I have to go to multiple places to get all those files tabbed into my text-editor.
With php, there was no need to create a route. By simply placing an index.php file into a folder the route was created. Then, placing all page-related resources into that same folder was no problem for php.
I am no fan of PHP; I've never liked it as a scripting language. Yet, every once in a while I miss certain aspects of it. This is one of those aspects.
Has anyone published an app.js file where, during first launch, it recursively scans the application's folders auto creating routes based on the fact that a folder contains an index.js file in it? Also, such a script would also have to make all other files in these folders static, except for server-side-resource files like views and server-side scripts.
I'm not even sure this is a good idea, but I'm curious if anyone has attempted to build something on top of express that acts similar to what I'm describing.
I have started a new orchard project and I uncheck Use IIS Express in my Orchard.web property's Web section and change the Project Url to http://localhost/TestOrchard, then I press Create Virtual Directory.
I uploaded some pictures in my Media folder and use it in my homepage.
Everything seems ok when I view it locally.
But when I deploy it to my website, the link pointing to the media file becomes
/TestOrchard/Media/Default/image/mypic.PNG
Since the TestOrchard folder does not exist in the remote server, media files cannot be read and also the media tab on my Admin control panel shows nothing.
The correct url should be /Media/Default/image/mypic.PNG
How do I remove the unwanted TestOrchard/ folder shell?
In the Admin/Settings, you can change your Base Url.
I've downloaded Drupal 6 and installed it on my local server, and ported a basic web site as a custom theme. I've set this as the default theme and everything works okay; the page appears nice with all the images and layout.
The problem is that now, no matter what I type as the URL I always get to my page. So how can I go to the admin page? /q=user does not work. I can change the theme from the database but that is not what I want. I just want to keep this theme and be able to access all the Drupal functionality.
For the custom page i've created the page.tpl.php and .info file. Along with the CSS file I've put them all in a new folder in the themes directory.
#abhaga's answer is spot on - you've turned the entire site's theme into a single page's HTML, so they're all going to be the same.
If you'd like to avoid glitching the admin side of things with a bad template file, you can set one of the core themes as your "administration theme" (in Site Configuration) - that way, the admin backend will always use that theme regardless of the other templates.
Ah! Basically page.tpl.php specifies the over all structure of site. Look at the original page.tpl.php file - it will be printing a variable called $content somewhere. That is the variable holding all the content of your specific page. You will need to print it at appropriate place in your pge.tpl.php
You should check out the right way of creating a theme here: http://drupal.org/theme-guide/6