{"id":18790522,"url":"https://github.com/lin3s/wordpressstandard","last_synced_at":"2025-06-25T00:32:31.671Z","repository":{"id":35193816,"uuid":"39452151","full_name":"LIN3S/WordpressStandard","owner":"LIN3S","description":"The \"WordPress Standard Edition\" distribution in the LIN3S way","archived":false,"fork":false,"pushed_at":"2018-10-22T18:03:15.000Z","size":626,"stargazers_count":5,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"master","last_synced_at":"2025-04-13T14:13:05.873Z","etag":null,"topics":["cms","headless-cms","lin3s","php","wordpress"],"latest_commit_sha":null,"homepage":"","language":"PHP","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/LIN3S.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2015-07-21T15:00:30.000Z","updated_at":"2021-03-08T11:35:55.000Z","dependencies_parsed_at":"2022-09-07T14:52:38.055Z","dependency_job_id":null,"html_url":"https://github.com/LIN3S/WordpressStandard","commit_stats":null,"previous_names":[],"tags_count":33,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/LIN3S%2FWordpressStandard","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/LIN3S%2FWordpressStandard/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/LIN3S%2FWordpressStandard/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/LIN3S%2FWordpressStandard/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/LIN3S","download_url":"https://codeload.github.com/LIN3S/WordpressStandard/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":248724628,"owners_count":21151561,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["cms","headless-cms","lin3s","php","wordpress"],"created_at":"2024-11-07T21:12:36.380Z","updated_at":"2025-04-13T14:13:11.381Z","avatar_url":"https://github.com/LIN3S.png","language":"PHP","funding_links":[],"categories":[],"sub_categories":[],"readme":"# WordPress Standard Edition\n\u003e The \"WordPress Standard Edition\" distribution in the LIN3S way.\n\n[![SensioLabsInsight](https://insight.sensiolabs.com/projects/b43b0be1-d2b5-44a1-8d4b-a556848129a5/mini.png)](https://insight.sensiolabs.com/projects/b43b0be1-d2b5-44a1-8d4b-a556848129a5)\n[![Scrutinizer Code Quality](https://scrutinizer-ci.com/g/LIN3S/WordpressStandard/badges/quality-score.png?b=master)](https://scrutinizer-ci.com/g/LIN3S/WordpressStandard/?branch=master)\n[![Total Downloads](https://poser.pugx.org/lin3s/wordpress-standard/downloads)](https://packagist.org/packages/lin3s/wordpress-standard)\n\u0026nbsp;\u0026nbsp;\u0026nbsp;\u0026nbsp;\n[![Latest Stable Version](https://poser.pugx.org/lin3s/wordpress-standard/v/stable.svg)](https://packagist.org/packages/lin3s/wordpress-standard)\n[![Latest Unstable Version](https://poser.pugx.org/lin3s/wordpress-standard/v/unstable.svg)](https://packagist.org/packages/lin3s/wordpress-standard)\n\n## Why?\n[**WordPress**][1] is the most important CMS around the world, but its PHP code is dark and unmaintainable. In\n[*LIN3S*][2] we implement this solution providing some useful features that the standard edition of WordPress doesn't\ncome with:\n\n1. [Composer][3]\n2. [PHP namespaces][4]\n3. [Capistrano][5] deploy\n4. [WPFoundation][6] made by LIN3S\n5. [Coding standards library][7] made by LIN3S\n\n## Prerequisites\nThe above sounds great so, now, to start developing WordPress project based on this repo, you need the the following\nrequirements:\n\n1. [PHP][15] 7.1 or higher\n2. [MySQL][16]\n3. Composer: `curl -sS https://getcomposer.org/installer | php`\n4. [Ruby][17]: `gem install bundler \u0026\u0026 bundle`\n\n## Getting Started\nAfter installing all the prerequisites, to create a WordPress project based on this *Wordpress Standard* you should\ncheck the following steps.\n\nFirstly, you need to **create the project**:\n```\n$ composer create-project lin3s/wordpress-standard \u003cproject-name\u003e \u0026\u0026 cd \u003cproject-name\u003e\n```\n\u003e You should remove the header licenses and `LICENSE` itself, because we are not going to be the authors of your\nawesome project :).\n\nCreate the `wp-config-custom.php` copying the `wp-config-custom-sample.php` and customizing with your values.\n\n**Configure the web server** to serve this project. With PHP 5.4 or higher you don't need to configure the web server\nfor this project, because you can use the \"**built-in-server**\":\n```\n$ php -S 127.0.0.1:8000 router.php\n```\n\nUse an [Apache][20], Nginx or other web server of your choice for production environments. If you choose Apache,\nremember that you should create the `.htaccess` copying the base `.htaccess.dist` file.\n\n## Considerations\nIf all goes well you should have your project on top of WordPress Standard running like a charm. However, there are\nfew tips that you should read.\n\n* **Activate all yours plugins before all**: it's a common mistake.\n* Usually, the features WordPress has by default are not enough so new PostTypes, Widgets, ShortCodes, ImageSizes...\nhave to be created. In case you need those changes to the codebase you should go to the `core` folder. There, you will\nfind some examples on how to extend many different WordPress features. In case there is no class for what you need, just\ncreate a new class or a new folder (if there are multiple classes related to that feature as in post types) with your\ncode.\n\n## Deployment\nTo automate deployment process this project is using **Capistrano**. All related configuration is inside located inside the\n`deploy` directory. You can customize deployment tasks simply, modifying the `deploy/deploy.rb` file.\n\nYou should update the *wordpress-standard* application name for your awesome project name and the repo url with your\nproject git url.\n\nInside `deploy/stages` directory there two files that can be considered as pre-production stage and production stage.\nThere is no logic, these files only contain few parameters that you should customize for your proper deployment.\n\nAfter all, and following the Capistrano [documentation][11] to configure the server, you can deploy executing:\n```\n$ cap \u003cstage\u003e deploy    # \u003cstage\u003e can be dev1, prod or whatever file inside stages directory\n```\n\n\u003e In the Capistrano shared directory you should create the `uploads` folder, the `.htaccess` file (if you are using\nApache), the `robots.txt` and the `wp-config-custom.php` files.\n\n### Downloading database dump\n\nTo download the file just run `cap dev1 database:download`. A sql file will be downloaded to your local environment\n\n### Replacing uploads with remote ones\n \nTo steps are required to get all the uploads located in the remote environment, download and extract.\n\n`cap dev1 uploads:download` will download a .tar.gz file to the root of your local environment and \n`cap dev1 uploads:extract` will extract the downloaded file into `src/uploads` folder, replacing all the existing \nuploads.\n\n### Ensuring remote files and folders\n\nThe first time you deploy the project, all linked files must be created in order to be symlinked. In order to\nautocreate folders and uploads your local files to the remote server (very handy when using W3 Total Cache), just run:\n\n`cap dev1 server:ensure`\n\nAfter this, just deploy without any problem.\n\n### Clearing remote caches\n\nWhen working with PHP7 \u0026 Opcache, for example, you won't see all changes after deploying. Caches need to be flushed\nwith the correct website domain. If you need this feature, just open the `deploy.rb` file and remove the commented line:\n\n```\nafter :finishing, 'cache:clear'\n```\n\nYou also need to configure the website domain in each stage file. If the website is password protected, the `curl`\ncommand must use the `-u user:password` given in the `dev1.rb` example file.\n\n## Licensing Options\n[![License](https://poser.pugx.org/lin3s/wordpress-standard/license.svg)](https://github.com/LIN3S/WordpressStandard/blob/master/LICENSE)\n\n[1]: https://wordpress.org/\n[2]: http://lin3s.com\n[3]: https://getcomposer.org/\n[4]: http://php.net/manual/en/language.namespaces.php\n[5]: http://capistranorb.com/\n[6]: https://github.com/LIN3S/WPFoundation\n[7]: https://github.com/LIN3S/CS\n[15]: http://php.net\n[16]: http://dev.mysql.com/downloads/\n[17]: https://www.ruby-lang.org/en/downloads/\n[20]: http://httpd.apache.org/\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Flin3s%2Fwordpressstandard","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Flin3s%2Fwordpressstandard","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Flin3s%2Fwordpressstandard/lists"}