Recently Browsing 0 members
No registered users viewing this page.
By CareerTeam GmbH
We are an executive search agency based in Germany looking for a freelancer (2-5 days per week) supporting us with the development and design of our websites. The position will be located in Hamburg, Germany and it would be great if you are on short call. German language knowledge is mandatory.
You can reach me via email email@example.com.
This profile can be used as a simple business card or blog.
The profile does not use any framework css structure, only styles based on CSS GRID and FLEX.
To minimize page loading, I added lazy load for images ( Tupola Lazy Load ).
With include functions like:
CAN DOWNLOAD FROM THIS LINK:
This profile can be used as a business card or very simple blog.
Requires the latest version processwire 3.0.101 !!!
Milligram Site Profile For Processwire 3x with include functions like:
wireIncludeFile | wireRenderFile
Essentially, this structure uses minimalist CSS framework Milligram and the Flexbox Grid System Gridlex
CAN DOWNLOAD FROM THIS LINK ( Basic Version and simple Blog Version )
If you want to use Laravel Mix you must first ensure that Node.js and NPM are installed on your machine.
Basic example to Debian and Ubuntu based Linux distributions:
curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash - sudo apt-get install -y nodejs
See more installation options LINK
npm is installed with Node.js just check in linux terminal like below:
Set BrowserSync inside folder /templates/webpack.mix.js and change your dev url
proxy: 'http://localhost/mix/', to your installation processwire folder like:
Next install npm packages in your templates folder with command npm install
Now, boot up the dev server npm run watch, and you're all set go!
On completion, use the command npm run production to build styles and scripts in the dist folder
Simple Usage ( Basic Command )
Run npm install Watch npm run watch Build npm run production All files to Webpack build steps is inside file ( webpack.mix.js )
Folder With all SCSS files is inside templates/src/scss
All build styles and scripts is inside the ( dist ) folder
Web Font Loader
Verlok Lazy Load
Tailwind CSS Framework, a utility-first CSS framework for rapidly building custom designs
This thread is a place for ProcessWire developers who use (or would like to use) Tailwind CSS to share their experience, tips, frustrations , solutions, code snippets and generally discuss all things tailwind.
From the creators of Tailwind CSS
Moderator note: the first few posts in this topic were split from this thread.
Thanks, @apeisa! Yes, Tailwind is awesome! Responsive classes are a clever idea indeed, much easier to work with. The authors did an excellent job and keep improving it.
Some people may feel a little sceptical, but I fell in love with it the moment I built my first project. Although nowadays I work alone, I believe that Tailwind makes work between a frontend and backend developers much easier because it makes the HTML more declarative and you can grasp what the classes mean in a glimpse.
By Mike Rockett
Docs & Download: rockettpw/markup-sitemap
Modules Directory: MarkupSitemap
MarkupSitemap is essentially an upgrade to MarkupSitemapXML by Pete. It adds multi-language support using the built-in LanguageSupportPageNames. Where multi-language pages are available, they are added to the sitemap by means of an alternate link in that page's <url>. Support for listing images in the sitemap on a page-by-page basis and using a sitemap stylesheet are also added.
Example when using the built-in multi-language profile:
<url> <loc>http://domain.local/about/</loc> <lastmod>2017-08-27T16:16:32+02:00</lastmod> <xhtml:link rel="alternate" hreflang="en" href="http://domain.local/en/about/"/> <xhtml:link rel="alternate" hreflang="de" href="http://domain.local/de/uber/"/> <xhtml:link rel="alternate" hreflang="fi" href="http://domain.local/fi/tietoja/"/> </url> It also uses a locally maintained fork of a sitemap package by Matthew Davies that assists in automating the process.
The doesn't use the same sitemap_ignore field available in MarkupSitemapXML. Rather, it renders sitemap options fields in a Page's Settings tab. One of the fields is for excluding a Page from the sitemap, and another is for excluding its children. You can assign which templates get these config fields in the module's configuration (much like you would with MarkupSEO).
Note that the two exclusion options are mutually exclusive at this point as there may be cases where you don't want to show a parent page, but only its children. Whilst unorthodox, I'm leaving the flexibility there. (The home page cannot be excluded from the sitemap, so the applicable exclusion fields won't be available there.)
As of December 2017, you can also exclude templates from sitemap access altogether, whilst retaining their settings if previously configured.
Sitemap also allows you to include images for each page at the template level, and you can disable image output at the page level.
The module allows you to set the priority on a per-page basis (it's optional and will not be included if not set).
Lastly, a stylesheet option has also been added. You can use the default one (enabled by default), or set your own.
Note that if the module is uninstalled, any saved data on a per-page basis is removed. The same thing happens for a specific page when it is deleted after having been trashed.