Download the PHP package abetter/wordpress without Composer
On this page you can find all versions of the php package abetter/wordpress. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download abetter/wordpress
More information about abetter/wordpress
Files in abetter/wordpress
Package wordpress
Short Description A Better Laravel + Wordpress integration, for exceptionally fast web applications.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package wordpress
A Better Wordpress
ABetter Wordpress is a turnkey solution for using Wordpress on top of Laravel to build exceptionally fast web applications – while still using the worlds most popular CMS to manage content and translations.
Our methodology to fast web applications is all about Separation of Concerns (SoC) and Scalable Static Caching. We let Wordpress handle the content back-end and Laravel the standalone front-end. Additional API and web services for dynamic content are also routed through Laravel.
With the ABetter Toolkit we give Laravel/Blade some new powerful directives helping us separate as much as possible in standalone and resusable components – much inspired by ReactJS/VueJS.
Requirements
- PHP 7.2+
- Imagick 3+
- MySQL 5.7+
- Composer 1.6+
- Laravel 5.8+
- Deployer 6+
- Node 10.0+
- NPM 6.4+
Installation
Via Composer:
Laravel modifications
Add post install/update script to composer.json:
Note: The script will modify any core files using the global __() method for string translations and add a cross-framework workaround. Sadly wordpress core do not check for function_exists before defining global __(), which breaks Laravel + Wordpress compatibility without modification.
Add middleware to app/Http/Kernel.php:
Note: The middleware helps Blade clear the view cache when developing many nested components.
Preparations
- Setup a local host domain using .loc, (e.g. www.abetter.loc)
- Point the host to /public
- Create a local mysql database
Setup Laravel
Edit .env settings
Note: Use APP_ENV=sandbox when developing with browsersync.
Add routes to /routes/web.php
Note: Remove any other routes for root or wp paths (i.e default Welcome).
Copy the Deployer file to root and run setup once:
Run audit fix if needed:
Note: Only run the setuponce on fresh projects, since it will replace files in /resources and /public.
Test to build the app:
Setup Wordpress
Go to host in browser (e.g. http://www.abetter.loc) and follow install instructions.
Go to /Appearance/Themes, and activate ABetter theme.
Go to /Plugins, and activate:
- Advanced Custom Fields.
- Disable Gutenberg (full support is coming soon...).
- ... Any other of the supported plugins you need.
Add default pages:
Go to /Settings/Reading:
- Select Start as homepage
- Select News as post page
Finaly, go to host in browser:
Congratulations to your new site!
Usage
Development
Use npm to start webpack and browsersync:
... or if using php artisan serve:
NOTE: With "php artisan serve" you need to modify APP_PROXY in .env to http://127.0.0.1:8000.
Component file structure
.
├── public # Handled by build script (will be overwritten)
├── routes # Add any development routes to /web.php
├── resources #
│ ├── scripts # Global scripts in "app.js"
│ ├── styles # Global styles in "app.scss"
│ ├── fonts # Fonts here (will copy to /public on build)
│ ├── images # Images here (will copy to /public on build)
│ ├── videos # Videos here (will copy to /public on build)
│ ├── views #
│ │ ├── <theme> # Subfolder defined in .env / WP_THEME
│ │ │ ├── template.blade.php # Template file requested in route
│ │ │ │ ├── components #
│ │ │ │ │ ├── menu # Component subfolder:
│ │ │ │ │ │ ├── menu.blade.php # Template file : @component('components.menu',TRUE)
│ │ │ │ │ │ ├── menu.scss # Sass file : @style('menu.scss')
│ │ │ │ │ │ ├── menu.js # Javascript file : @script('menu.js')
...
/vendor/abetter/wordpress/ # Default components will be used if not overridden!
├── views # (e.g. html head start/end is rendered from here)
│ ├── default #
│ │ ├── robots.blade.php # Default Robots.txt template
│ │ ├── sitemap.blade.php # Default Sitemap.xml template
│ │ ├── components #
│ │ │ │ ├── html # Default HTML head components
│ │ │ │ ├── missing # Default debugging for missing components
│ │ │ │ ├── robots # Default Robots.txt component
│ │ │ │ ├── sitemap # Default Sitemap.xml component
...Note: Component names will be auto-resolved if the blade file has same basename as folder.
Note: Linked JS/Sass files in components will be external files in development to support browsersync live, but will be embedded in html source on Stage/Production environments for better caching.
Note: You can auto-terminate a @component with TRUE as the second paramater, to avoid writing out @endcomponent, e.g when not using any slots or nested content.
Deployment
(coming soon)
Contributors
Johan Sjöland [email protected]
Senior Product Developer: ABetter Story Sweden AB.
License
MIT license. Please see the license file for more information.
All versions of wordpress with dependencies
intervention/image Version ^2.5
vlucas/phpdotenv Version ^3.6