How to setup Semantic-Ui so an update will not destroy your sites or theme. I am new to semantic-UI and also in web development
Thank you in advance
Related
I am a backend django-developper with very limited knowledge of frontend technologies. I decided to challenge myself into building a full-stack application using a pre-made Boostrap Admin dashboard. The problem is the dashboard I chose makes use of npm and gulp, which I know nothing about. Of course, I can try to learn it, but I am wondering if it's possible to remove them and create a compiled version that has all dependencies linked directly in the head tag and at the end of the body tag and style the frontend using vanilla bootstrap.
Your help will be greatly appreciated. Thanks
I started to learn how to develop my own theme for Prestashop.
I set a shop on my local server with my theme inside the themes folder. When I change the CSS, I can immediately see the changes in my shop. But it seems that when I change the structure (changing .tpl files), I need to reload the theme in the back office.
This is really not a convenient process, how do you organize your work during development?
Go to Advanced Parameters -> Performance and enable "Recompile templates if the files have been updated". Disable cache on the same page. You can also set _PS_MODE_DEV_ to true in your config/defines.inc.php:
define('_PS_MODE_DEV_', true)
I was wondering what the best way was to deploy shopify themes locally for testing before deploying. We recently started employing deploybot. We really like deploybot but we also would like a way to not wait five minutes to test our files in an alternate store.
How would I accomplish this?
It's tough to preview themes locally. Check out Themekit if you want a quick way to sync local theme files with a development shop: https://shopify.github.io/themekit/
Here's how to setup a local working environment:
https://www.shopify.com.au/partners/blog/95401862-3-simple-steps-for-setting-up-a-local-shopify-theme-development-environment
Install themekit:
curl -s https://shopify.github.io/themekit/scripts/install.py | sudo python
https://shopify.github.io/themekit/
Setup API credentials by creating a private app in your Shopify admin.
Apps > Create private app
Get your theme id.
visit name.myshopify.com/admin/themes.json to get a list of themes and ids
Create a config.yml file and populate it with the credentials. It should look somewhat like this:
development:
password: 16ef663594568325d64408ebcdeef528
theme_id: "123"
store: can-i-buy-a-feeling.myshopify.com
proxy: http://localhost:3000
ignore_files:
- "*.gif"
- "*.jpg"
- config/settings_data.json
Have themekit listen for any local changes and upload them to Shopify.
theme watch
However the store is still online. Because the Shopify framework is hosted on Shopify there is no localhost solution.
For anyone coming to this in 2018, we now have use of Slate.
https://shopify.github.io/slate/
For an idea of workflow, we have multiple devs working on the same theme and they can see their changes locally with Slate.
How we achieve this
We have a dev store that is a direct clone of our production store.
Each dev creates another theme on the dev store and branches off master locally. They then will ONLY use the theme id of the theme they just created to work with (updated in their config.yml)
Slate will watch changes and deploy to their preview theme and refresh their browser locally too.
Once the dev is happy with their changes, we merge back into master and deploy to the live (master) theme on our dev store.
Once it passes all the tests on our dev store, we push to a production store using slate.
EDIT - For creating new section files, template files, product templates etc
You won't be able to create these files and for them to be displayed locally without a small workaround.
For example, if you create a new product template ("product.my-product.liquid"), you'll need to Publish your preview theme first, then perform a "slate start" in terminal, select your new product template for whatever product you're using it on in Shopify, then re-publish your "master" theme.
You may need to do another "slate start" to get the new theme template displaying on the product locally, but it will work.
This is because Shopify only allows you to assign product templates to the current active theme.
You have a test shop. You are working on a theme. If you are doing it right, any changes you make to the theme, are automatically transferred to the test shop. So all you need to do is watch your browser, since you probably also have a watcher on that auto-reloading on changes.
Have been doing this for years, and I never wait 5 minutes for a deploy, as it takes mere seconds to deploy a change and see the results. Throw in some smart Git hooks and you've even got version control.
Hello I'm new to Yii framework.
And I think I've been succeed to install it in my computer. But the problem is when I want to connect it to my phpMysql in Xampp I cannot find folder name 'protected' which is needed to connect myproject to yii.
So anybody can help me about this? Thank you.
If protected folder is not there, how you can say that you are successded in installing it. try installing it again. Try the below Yii2 template. Follow its guide to install it on your system properly. You must know composer for installing this template.
https://github.com/yiisoft/yii2-app-advanced
Each time I want to test the DotNetNuke module I'm working on, I uninstall it from the DNN website host control panel, I zip my module dev folder, and then I reinstall it from the DNN website.
Is there any faster way to test my module?
Are you testing the install process?
If not - all the changes in DesktopModules/YourModule or App_Code/YourModule will take effect immediately and will be ready for testing (assuming you're using a Website project, and your virtual directory is pointing to your dev. directory)
If you're using the Web Application project - make changes, build, move the files to the virtual directory target folder, then test.
Let me know if this helps.