11 Excellent WordPress Themes for 2023 — SitePoint. The result is a WordPress theme that gives you the power to easily create and make changes to the appearance and functionality of your website as you build it

SitePoint

If you purchase through a link on our site, we may earn a commission. Learn more.Are you looking for a way to use automation to boost membership renewals?Getting customers to join your online course or membership site is essential, but getting them to renew their membership happily is another big hurdle. Luckily, with the right WordPress automation tools and strategies, you can reduce churn and make customers more likely to renew.In this article, you’ll learn the types of automations you can use to boost membership renewals, increase customer satisfaction, and reduce customer churn rate. Let’s dive in!Memberships aren’t one-and-done. You need to continue to deliver value to your members throughout their membership to make renewal a no-brainer for them.A customer becoming a new member is the very start of their journey with your business. This is something you should think about well before membership renewal time.Here’s what a solid membership retention campaign can include:This plan will look different depending on the type of membership site you’re running. For example, Starter Story offers an online database of business case studies. However, once you become a member, you’ll get regular updates about new case studies added and the latest reports. This constant reminder encourages you to take action, log into your account, and consume the content you’ve paid for.You’ll create and send these campaigns within your email marketing automation tool. These tools allow you to send individual email campaigns and automated campaigns that you create once and send out automatically.Here’s an example of the visual automation builder within FluentCRM that you can use to create year-long campaigns.Inactive members are users who signed up but haven’t logged into the membership portal in a while. There’s a low chance these members will renew since they aren’t putting the membership program to use.However, you can use automated emails to bring back inactive users and get them to engage with your membership content.These emails can be part of your automated customer retention campaign, or you can run them separately based on your members’ actions.The goal is to get people to actively use their memberships. The more often they use it and gain value, the more likely they are to renew.For example, let’s say you run a paid membership community for eCommerce store owners looking to improve revenue. You’ve found that members who are the most active in the community, ask for feedback, and show up for the monthly calls get the most success.So, your goal for your automated campaign is to get members to post wins, ask for feedback, or simply attend the monthly call.Here, you’d create an automated email campaign encouraging members to log in to their accounts and post a quick win or show up for the monthly call. The key here is to make it something simple to get them back into the routine of using the membership they’re paying for.You’ll need to set up a trigger within your email automation tool to do this. The email is simple; the goal is to get members to open and spend some time in their membership dashboard.If you’ve done everything above correctly, your membership renewal reminder email can be short and sweet. The important thing here is to make it as personalized as possible.Renewal reminder emails can include things like:The great thing about using a tool like FluentCRM is it pulls all kinds of helpful contact data like emails opened, purchase history, and notes. You can use this to create highly personalized emails that make them more likely to convert.Besides making your email feel like it was written just for them, you’ll want to reinforce the benefits of your membership. Even though you have a good idea of the benefits of your program, you need to reinforce this with your current members.One great way to do this is to highlight case studies of other users in your program. These work great on the front end to convert users into members, but they can also help reinvigorate that excitement and possibility with existing members.How you set this up depends on your email marketing platform of choice, but essentially, you’ll create a membership renewal automation email that is sent out based on the date they purchased the membership.Another way to increase renewals is to allow your members to turn on auto-renewals. That way, you don’t have to send reminders to boost renewals; it’ll happen automatically.Instead of simply making it available as an option during checkout, you can incentivize auto-renewals.Some great ways to do this include:Ultimately, the goal is to make the auto-renewal option a value-added choice. Even if it’s cheaper for your members, you can earn more in the long run since there’s less friction in maintaining an active membership.Surveys are a great way to measure your customers’ satisfaction and identify areas for improvement. They can also help you address these issues before it’s time to renew a membership.Remember, all feedback is helpful. Properly addressed negative feedback can improve loyalty and help your members become customers for life.An automated survey email can be simple, but it should be sent out after your member onboarding, once they’ve had some time to get value from the membership.For example, you can create an automated survey that is sent out three months into a new membership to gather valuable feedback. Then, you can use this feedback to improve their experience.The easiest way to do this is to create a time-based trigger in your email automation platform. Then, your members will get an automated survey email three months into their membership.You can use a WordPress-specific tool or a third-party platform like Google Forms or SurveyMonkey. The most important thing is that you create the automated campaign and set aside time to review your responses.If your membership stays the same and doesn’t evolve to meet your members’ needs, you’ll probably see a high drop-off rate.That’s why we recommend implementing customer surveys and always thinking of ways you can add value to your existing membership.Here are some simple value-adds you can consider adding:As you improve your membership, add these announcements and new features to an automated email campaign. For example, if you’re adding new features, content, interviews, or VIP access to the membership this year, spell out the details in your membership renewal emails.Your automated renewal campaigns should be more than a single email.Here’s a simple structure you can use:Finally, if you’ve found that your member doesn’t renew their membership, then you can offer a lower-priced membership to keep them as a customer.For example, if your main offer includes monthly coaching calls, you can create a lower-tier membership that lets them watch the recordings but not participate.Ultimately, this will depend on your original membership offer, but think about how you can package your membership to create different tiers. Many WordPress membership plugins let you create multiple tiers and packages you can offer your users.Then, you can email and create membership renewal automations for members in that tier. For example, FluentCRM has built-in options that let you create automations for specific user tiers.As you can see, boosting your membership renewals is a process that begins the moment a new member joins your program. Creating automations that get sent out throughout the year can help members get the most out of your program and get valuable feedback to improve your membership.However, you can also create a few membership renewal automations that’ll improve renewals across the board. The most important are personalized renewal reminders, benefit-oriented emails, and even down sells to capture members who might not want to pay for your flagship membership.Overall, the best way to create a healthy membership program is always to deliver value while adjusting your membership to their feedback.Recommended SolutionTry it out! ⬆Kevin WoodElevate your catalogs, eBooks, manuals, and educational material with DearFlip 3D flipbook presentations on WordPress. Turn static PDFs into immersive 3D flipbooks, adding interactivity and visual appeal to your onlineWooCommerce email automations help you earn more from your online store. Learn what 6 must-have automations you can implement today.Email is one of the most effective channels for generating leads and creating lifetime customers. Learn effective strategies for list growth, lead nurturing, and improving course sales.Your email address will not be published. Required fields are marked *Comment * Name * Email *                Subscribe to the WP Mayor newsletter.           Δdocument.getElementById( "ak_js_1" ).setAttribute( "value", ( new Date() ).getTime() );Quick NavigationBest PicksResourcesBusiness OpportunitiesTopicsLeave your name, email and website URL below to receive one actionable improvement tip tailored for your website within the next 24 hours."They identified areas for improvement that we had not previously considered." - ElliotBy providing your information, you'll also be subscribing to our weekly newsletter packed with exclusive content and insights. You can unsubscribe at any time with just one click.

7 Automations to Boost Membership Renewals Using FluentCRM. As you can see, boosting your membership renewals is a process that begins the moment a new member joins your program.. getTime() );Quick NavigationBest PicksResourcesBusiness OpportunitiesTopicsLeave your name, email and website URL below to receive one actionable improvement tip tailored for your website within the next 24 hours."They identified areas for improvement that we had not previously considered."

WP Mayor

7 Automations to Boost Membership Renewals Using FluentCRM

Brian CoordsOver the years, WordPress’s developer documentation, originally the Codex but now the WordPress Code Reference, has served the project well. However, there’s been a sense in the community that much of the more recent documentation- for example, the JavaScript APIs and packages coming out of Gutenberg- has been inconsistent and harder to read and understand. Developers often find themselves navigating disconnected designs and organization throughout the various docs, guides, and handbooks for topics that might cover anything from the Shortcodes API to WP-CLI.This past December, WordPress.org’s entire Developer Resources subdomain relaunched with much more intuitive homepage, cohesive navigation, and a modern design. In developer circles and on social media, the relaunch was met with rave reviews, along with more than a few sighs of relief.Although the redesign appeared almost three months ago, it belongs in the WP Tavern as a modern milestone for the WordPress project. I caught up with Nick Diego, a Developer Advocate sponsored by Automattic, to learn more about the story behind the redesign and what else we can expect from WordPress.org’s multi-year migration to a new look and feel.If you’ve seen Nick’s name recently, it may be from his popular WordPress plugins, such as Block Visibility and the Icon Block, or else his work on the WordPress Developer Blog. The team of contributors running the Developer Blog have been busy educating readers on how to work with many of the new and experimental tools coming out of the Block Editor. But some of them are also deep in the trenches trying to rewrite twenty years of legacy developer resources, like Justin Tadlock’s ongoing work with the Theme Handbook.“One of the big focuses for my team,” Nick explained, “was to try and improve the Block Editor Handbook and the Themes Handbook. And so we’re working on the content of it, and there’s still tons of work to do there, but one of the things we identified early on was that the structure and the design of the site, it just made things worse.” (I’ll spare readers the links to my numerous Twitter and podcast rants on that exact topic.)Once they realized this, the team was confronted with a choice. They could simply ignore the issues with the outdated design and continue updating content. They could completely rethink the way that the developer documentation for the project was built and start a massive restructuring. Or they could keep working within the existing architecture but focus on cleaning up the glaring gaps in design.They chose that third approach – focusing on redesigning what they had, rather than trying to advocate for an entirely new documentation platform. That also freed up more time to continue updating the most important part: the content.“I would rather spend my time fixing [the content],” Nick explained. “Because then if we ever get to a point where we want to re-architect the whole thing, then it’s an architectural problem and not an “oh, and all our content’s all wrong problem’.”The team began work on updating the content and design in tandem, and Nick was able to draw on his experience helping out with the recent redesign of the Showcase on WordPress.org.One important caveat for WordPress documentation is that it is also open to contribution, just like WordPress core. That means that the structure in which documentation is written, discussed, and hosted needs to be available to any contributor who might be able to help.Some of the documentation, like the Theme Handbook, is actually post content inside of a WordPress installation. Nick explained that “it’s really hard to contribute to, because you can’t go write a pull request somewhere. You have to open an issue that says, ‘Hey, there’s a spelling error here’ or ‘Hey, this paragraph should be changed’ and then some docs contributor that has permission used to go in and make it. It is wildly challenging.”If the team wants content to be collaborative, it ultimately needs to have some connection to GitHub, where collaboration tends to happen. The benefit to this approach is that developer documentation can be an onramp to becoming a WordPress contributor. Once you’ve made a small pull request fixing a spelling error, it becomes a little easier to consider making a PR with an actual code change.“So we have some pieces of the site [in WordPress],” said Nick. “We have some pieces that are on GitHub. There’s other parts that are generated from source code, other pieces that are part of packages. So it’s a very complicated setup where there’s content in so many different places, and even with the stuff that’s in GitHub, it’s coming from multiple repositories.”For now, any of the documentation that does live on GitHub has a link to “Improve it on GitHub” in the footer, taking you to its source.Updating the Developer Documentation site to match the new design language rolling out across WordPress.org meant migrating it from a classic theme to the same underlying block-based parent theme that all of the newly redesigned WordPress.org sites are using. What some might see as an insurmountable challenge, this team saw as a learning and “dogfooding” opportunity.“The documentation section is huge,” said Nick, “How do you update that to a block theme? So we also looked at it as a project where Meta will learn a lot as the process goes.”The team could take all of their experiences of migrating a massive website- hundreds of pages of content, some authored inside of WordPress but much of it populated by automated integrations with numerous GitHub repositories- and share the lessons they’d learn with the core team that was building the Site Editor itself.One example that I’m sure any developer will resonate with was the issue of version control for a block theme.“Everything in dot org needs version control,” Nick explained. “So the Site Editor works, but then you have to sync all the changes back to the template files in the theme. So there are definitely some challenges that the Meta team have had to circumvent because of the unique requirements of dot org. But it’s been a really interesting case study.”Nick and his colleagues then used their experience to facilitate discussions on GitHub with the broader developer community who are also grappling with these exact issues with block themes.The WordPress.org redesign is a multi-year endeavor with a lot of concurrent projects happening. A few that Nick and his colleagues are focused on next include redesigning the rest of the WordPress Documentation, a segment of end-user-facing content known as the “HelpHub”, along with the Forums and the Patterns Directory.Along the way, their focus is on making sure the community is aware that these redesign projects are all public to review and engage with.Nick added that “Figma is public, the GitHub’s public, but is it as public as it could be from a visual perspective within the community? No. And I think that that’s something that we’re trying to do better. So we’re trying to improve the process so it is more visible moving forward.”The team has been more proactively posting updates on the Make WordPress blog as well as in a dedicated Slack channel, #website-redesign. The end goal for these redesigns is to increase the quality and access to information, but also to make contribution to the project easier.“One of the things that we’ve actually seen,” said Nick “is that once the redesign happened and there was a bit more spotlight on it and people started using it, then the problems with the UI kind of go away and then you start to see problems with the content, which leads to more people fixing the content.” If you’re interested in contributing to the design or the content of some of these upcoming projects, consider joining the WordPress Slack or following along in the Make WordPress blog.Your email address will not be published. Required fields are marked *Comment * Name * Email * Website  Notify me of follow-up comments by email. Notify me of new posts by email. Δdocument.getElementById( "ak_js_1" ).setAttribute( "value", ( new Date() ).getTime() );This site uses Akismet to reduce spam. Learn how your comment data is processed.Enter your email address to subscribe to this blog and receive notifications of new posts by email.Email AddressSubmitWordPress Tavern is a website about all things WordPress. We cover news and events, write plugin and theme reviews, and talk about key issues within the WordPress ecosystem…© All Rights Reserved. Powered by WordPress, hosted by Pressable

WordPress Developer Docs Shows Off a New Block-Based Redesign. (I’ll spare readers the links to my numerous Twitter and podcast rants on that exact topic.)Once they realized this, the team was confronted with a choice.. Learn how your comment data is processed

WP Tavern

WordPress Developer Docs Shows Off a New Block-Based Redesign

The cybercrime group called GhostSec has been linked to a Golang variant of a ransomware family called GhostLocker."TheGhostSec and Stormous ransomware groups are jointly conducting double extortion ransomware attacks on various business verticals in multiple countries," Cisco Talos researcher Chetan Raghuprasad said in a report shared with The Hacker News."GhostLocker and Stormous ransomware have started a new ransomware-as-a-service (RaaS) program STMX_GhostLocker, providing various options for their affiliates."Attacks mounted by the group have targeted victims in Cuba, Argentina, Poland, China, Lebanon, Israel, Uzbekistan, India, South Africa, Brazil, Morocco, Qatar, Turkiye, Egypt, Vietnam, Thailand, and Indonesia.Some of the most impacted business verticals include technology, education, manufacturing, government, transportation, energy, medicolegal, real estate, and telecom.GhostSec – not to be confused with Ghost Security Group (which is also called GhostSec) – is part of a coalition called The Five Families, which also includes ThreatSec, Stormous, Blackforums, and SiegedSec.It was formed in August 2023 to "establish better unity and connections for everyone in the underground world of the internet, to expand and grow our work and operations."Late last year, the cybercrime group ventured into ransomware-as-a-service (RaaS) with GhostLocker, offering it to other actors for $269.99 per month. Soon after, the Stormous ransomware group announced that it will use Python-based ransomware in its attacks.The latest findings from Talos show that the two groups have banded together to not only strike a wide range of sectors, but also unleash an updated version of GhostLocker in November 2023 as well as start a new RaaS program in 2024 called STMX_GhostLocker."The new program is made up of three categories of services for the affiliates: paid, free, and another for the individuals without a program who only want to sell or publish data on their blog (PYV service)," Raghuprasad explained.STMX_GhostLocker, which comes with its own leak site on the dark web, lists no less than six victims from India, Uzbekistan, Indonesia, Poland, Thailand, and Argentina.GhostLocker 2.0 (aka GhostLocker V2) is written in Go and has been advertised as fully effective and offering speedy encryption/decryption capabilities. It also comes with a revamped ransom note that urges victims to get in touch with them within seven days or risk getting their stolen data leaked.The RaaS scheme also allows affiliates to track their operations, monitor encryption status, and payments through a web panel. They are also provided with a builder that makes it possible to configure the locker payload according to their preferences, including the directories to encrypt and the processes and services to be terminated before commencing the encryption process.Once deployed, the ransomware establishes connection with a command-and-control (C2) panel and proceeds with encryption routine, but not before killing the defined processes or services and exfiltrating files matching a specific list of extensions.Talos said it discovered two new tools likely used by GhostSec to compromise legitimate sites. "One of them is the 'GhostSec Deep Scan toolset' to scan legitimate websites recursively, and another is a hack tool to perform cross-site scripting (XSS) attacks called "GhostPresser,'" Raghuprasad said.GhostPresser is mainly designed to break into WordPress sites, allowing the threat actors to alter site settings, add new plugins and users, and even install new themes, demonstrating GhostSec's commitment to evolving its arsenal."The group themselves has claimed they've used it in attacks on victims, but we don't have any way to validate any of those claims. This tooling would likely be used by the ransomware operators for a variety of reasons," Talos told The Hacker News."The deep scan tool could be leveraged to look for ways into victim networks and the GhostPresser tool, in addition to compromising victim websites, could be used to stage payloads for distribution, if they didn't want to use actor infrastructure."State of AI in the Cloud 2024Find out what 150,000+ cloud accounts revealed about the AI surge.Goodbye, Atlassian Server. Goodbye… Backups?Protect your data on Atlassian Cloud from disaster with daily backups and on-demand restores.Find out what 150,000+ cloud accounts revealed about the AI surge.Struggling with GDPR and privacy-focused browsers? Harness first-party data to transform customer engagement.From Humans to Bots: Every Identity in Your SaaS App Could Be a Backdoor for Cybercriminals.Sign up for free and start receiving your daily dose of cybersecurity news, insights and tips.

Alert: GhostSec and Stormous Launch Joint Ransomware Attacks in Over 15 Countries. The cybercrime group called GhostSec has been linked to a Golang variant of a ransomware family called GhostLocker."TheGhostSec and Stormous ransomware groups are jointly conducting double extortion ransomware attacks on various business verticals in multiple countries," Cisco Talos researcher Chetan Raghuprasad said in a report shared with The Hacker News."GhostLocker and Stormous ransomware have started a new ransomware-as-a-service (RaaS) program STMX_GhostLocker, providing various options for their affiliates."Attacks mounted by the group have targeted victims in Cuba, Argentina, Poland, China, Lebanon, Israel, Uzbekistan, India, South Africa, Brazil, Morocco, Qatar, Turkiye, Egypt, Vietnam, Thailand, and Indonesia

The Hacker News

Alert: GhostSec and Stormous Launch Joint Ransomware Attacks in Over 15 Countries

Toby CrynsAccording to the WAVE web accessibility tool, Gravity Forms scores a perfect score out-of-the-box for their front-end forms. Same with Ninja Forms, Contact Form 7, and WP Forms.  I tested 2 other popular WP form plugins that did not fare as well.The Tavern reported in 2021 that Gravity Forms invested heavily in web accessibility with their 2.5 release and also reported that Gravity Forms provides lots of information about their approach to accessibility.  I was curious to dive deeper on Gravity Forms’ specific web accessibility processes.  “We do our testing with keyboard and screen readers,” Morgan Kay, a software engineer at Gravity Forms who works closely with accessibility initiatives at the company says.  “We also consider some other implications, such as how usable a feature is on mobile, how it looks in an RTL language, and whether we have sufficient color contrast.”Gravity Forms also tries to help novice users understand when they are making a change that might break accessibility.“One thing Gravity Forms does that’s particularly valuable is that it warns you if you’re using a feature that has known accessibility issues,  and that’s a huge time saver for professionals,” says web accessibility consultant, Joe Dolson. Gravity Forms promises WCAG AA compliance, which is a great place to start for anyone who is looking to make a website more accessible to users.“WCAG2.1 AA is the standard required by most accessibility laws,” says Gravity Forms’ Kay. By comparison, “WCAG2.1 AAA is very strict, and includes some standards that are not necessarily realistic or necessary for all types of websites,” Kay adds.“Our goal is to make sure that [our forms] comply to WCAG 2.1AA,” says Kay. “This is not only because we want our forms to be accessible, but also because it is required by some countries.”“We provide tools that let users build forms that are WCAG-compliant, but it is still ultimately up to the user to make sure they are following all of the guidelines to meet those requirements,” adds Kay.I tested that statement in the wild, and it’s true: Gravity Forms gives you all the tools to make your front-end form WCAG AA-compliant out-of-the-box and without any configuration.  For example, if you simply add name, email, and phone fields to a Gravity Form, it’ll be WCAG AA compliant.  However, website owners can optionally or unknowingly break compliance – and often do.  For example, deleting the default form labels will break compliance.  You don’t have to go far on the web to run into a text input field without a proper label.  Oftentimes this is done for aesthetic reasons – e.g. hiding labels to make the form more compact.While other form plugins might be able to create accessible forms, they aren’t as simple to configure for WCAG and ADA compliance, according to some accessibility consultants.  “For free plugins, Contact Form 7 allows you to create very accessible forms,  but you have to know what you’re doing. It’s a fine tool if you put in the work, but I wouldn’t recommend it to the average user,” Dolson says.Another web accessibility consultant, Gerson Lacdao noted his appreciation for Gravity Forms’ efforts while adding some constructive criticism of other WP form plugins.“Some [form plugins] have issues in the most basic [web accessibility] things like properly coded field labels,” says Lacdao. His favorite form plugin today is WS Form.  “In terms of accessibility, I would probably put [the WS Form plugin] on top,” Lacdao says. “I like how a lot of accessibility options are available [in WS Form], and I don’t need to add extra CSS or JS hacks just to make it work better.”Lacdao mentioned one example of a popular WP form plugin that is behind on the web accessibility front (I was unable to reach the plugin’s developer for comment and therefore decided to not name the plugin here).  “[That plugin’s accessibility] efforts are mostly reactive and for now only based on tickets or feedback from some users,” says Lacdao. “It’s something I’m a bit frustrated about because I feel like it’s part of their obligation to users to proactively make their product accessible.” In addition to making a clear proactive effort on the web accessibility front, the Gravity Forms team is always on the lookout for new issues. Gravity Forms’ Kay explains, “We usually investigate [accessibility tickets] as soon as they are reported, and we can usually get [them] fixed within one or two minor releases.”It’s tough to talk about web accessibility in the admin side of any plugin without talking about accessibility in the admin of WordPress more generally. Based on my tests using the WAVE tool, neither WordPress core nor any plugin or theme I tested fared well on web accessibility within the admin. That said, admin-side accessibility improvements are definitely on Gravity Forms’ agenda. “[A senior accessibility consultant] has done a complete audit of our plugin in the dashboard, so we know what we need to do to make Gravity Forms accessible in the admin,” Kay said. “We are working on making the admin accessible, and in Gravity Forms 2.9 there will be some improvements.”  Your email address will not be published. Required fields are marked *Comment * Name * Email * Website  Notify me of follow-up comments by email. Notify me of new posts by email. Δdocument.getElementById( "ak_js_1" ).setAttribute( "value", ( new Date() ).getTime() );This site uses Akismet to reduce spam. Learn how your comment data is processed.Enter your email address to subscribe to this blog and receive notifications of new posts by email.Email AddressSubmitWordPress Tavern is a website about all things WordPress. We cover news and events, write plugin and theme reviews, and talk about key issues within the WordPress ecosystem…© All Rights Reserved. Powered by WordPress, hosted by Pressable

Certain WP Form Plugins Make Accessibility Easy. Toby CrynsAccording to the WAVE web accessibility tool, Gravity Forms scores a perfect score out-of-the-box for their front-end forms.. Learn how your comment data is processed

Certain WP Form Plugins Make Accessibility Easy

Posted on Mar 5                      • Originally published at serverauth.com                   For this guide we're assuming you already have PHP, Composer and GIT installed on your computer and that you're familiar with terminal commands.First we are going to create a brand new Laravel application. I have a "sites" folder in my user directory where I keep all my projects. If you already have a folder like this, navigate to it in your terminal, if not you can use the following command to create your own sites folder and navigate into it.Next, we're going to use the "create-project" command from composer to create a new Laravel application in a folder called "filament-app". Use the command below to create the application and navigate into the folder.This command simply, downloads the "laravel/laravel" repository from packagist and runs a composer install on it to install all the framework dependencies. It does this in a folder called "filament-app" and then it changes our terminal directory to the new application.Once finished, that is the base Laravel application installed and we can start to install Filament. If you have a local server running that allows you to run applications you can visit that project locally and you should see the default Laravel application homepage that looks something like this.Next we'll start to install filament. We'll do this via composer again. Use the following command to add filament to your composer file and install it and it's dependencies.Once finished we can create your first panel. Panels are the top most containers within Filament. Panels then include pages, forms, tables, actions, widgets and more that let you build feature rich admin areas.Run the following command to start an interative flow that will ask you for the ID of the panel.It should be prefilled with "admin". Leave this as is, and press enter. The command will now create and attempt to configure your first panel and will provide some information on the status. It should look something like this in your terminal.You will also be asked to give their repository a star on Github. Don't be shy, show them some love ❤️.Next we're going to save the code to Github. If you haven't already, sign up for a github account or login if you already have one.Before proceeding, if you haven't already we recommend you add your SSH key to your Github account.In the top right corner, click the plus icon to open up the drop down menu and click new repository.Give your repository a name and then be sure to select whether the repository should be public or private. For this guide I've called it "filament-app" but you should give it a more descriptive name.Upon creation you'll be given some instructions on how to add code to the repository. Within the Quick Setup section, ensure the SSH option is selected and copy your repository URL. It should look something like ours below but with your username and repository name.Head back to your terminal window and make sure you are within your project root folder and run the following commands.Once completed, your code should all be in your repository on Github. If you head back to your browser and refresh the repository screen that had the quick setup section you should now see all the files and folders that make up the Laravel application we have created so far.For the purpose of this guide we'll assume you already have a server configured with ServerAuth. If you want a guide on creating a server, you can check out our guides on how to set up a server with DigitalOcean or how to set up a server with Hetzner.With your server set up within your ServerAuth account we need to install a few different services if you haven't already got them enabled.First we need to enable "Sites". This will install and configure Nginx and PHP on your server. Once your server is setup, click to manage the server within the ServerAuth platform and head to Sites in the left menu.You will be presented with an info box and a button to "Install Nginx". This button will also install PHP at the same time. Click the button to start the installation and you will be shown an "in progress" screen. You can navigate away from this page while this is installing and you can move onto the next service.Next, head to the Databases section from the left menu. You will be presented with the options to install MySQL and also Redis. We're going to need MySQL to store data for our Filament application so go ahead and click to Install MySQL.Redis is an optional service, you can use Redis to help manage things like caches and user sessions so it can be useful depending on your needs with the application. If you think you are going to need it, go ahead and click the "Install Redis" button too.As with the Sites section, you will see "in progress" screens for MySQL and Redis.Next we need to create a database and database user, once MySQL has finished installing and the page has refreshed, you should see an empty table and a "Create Database" button. Click that to bring up the create database modal, fill out the form but ensure you leave the "Allow remote access" checkbox unchecked. Remember to make a note of the data you enter as this will be needed later.Like Redis, Daemons are an optional service. A Daemon is essentially a task that can run in the background without interaction from a user and depending on the configuration it can be set up to always keep it running.Laravel comes with the ability to run queues and other background jobs that can benefit from being run as Daemons. If you are going to be making use of these then head to the Daemons section. Once there you can "Install Supervisor", which is almost a de-facto standard for running Daemons on Linux.Head back to the "Sites" section once it has finished installing and you should see the option to "Add Site", click this button and you will be taken to the form to create a new site. Fill out the form with your details, ensuring you select the latest version of PHP when doing so. We also recommend you make use of website isolation and create a brand new user for your website to run under. This just adds an extra layer of security to your setup. For this guide, we've created a new user called "filament-app".ServerAuth also provides the ability to create a temporary domain if your website is not yet ready to go live. Check the "Enable Temporary Domain" option and our system will create a subdomain within one of our development domains for you to use while your application is in development.Click add site and our system will begin creating and configuring the Nginx records on your server. While this is happening, you will be taken to the Site Overview page where you will see the details you entered along with your temporary domain if enabled. Avoid visting your temporary domain until the site has finished installing. See below for a screenshot of the Site Overview page.Once your site has finished install, click the Install Application button towards the bottom of the Website Details section, alternatively click "Application" in the left menu. If you haven't already, connect your Github account to ServerAuth and then return to this page. You should then see an option to select your connected Github profile.Select your Github profile and populate the text box with your repository, we'll then try to find your repository and retrieve the list of branches in your repository. As per this guide, we only have one which is our "main" branch.Some extra options will appear once you've selected your branch, check the option for composer install and then click install.While your application is being installed, we'll need to setup your SSH access to the server so we can configure Laravels .env file.Head back to Manage Server via the left menu and then click Server Access. On this page will be a "Grant Access" section. Select yourself from the Team Member drop down and then check the server user you defined when installing the site, ours was "filament-app". We don't need to set any date restrictions so leave that as is.Save that form then head to "SSH Keys" in the top menu and add your SSH key to your account. Once saved, please allow a few minutes for our systems to sync your SSH Key with any servers you have been given access to.Once your site has finished installing and your SSH access has been synced, it's time to log on to your server and update the application .env file! Open up your terminal window and run the following command, swapping out the user and server IP address for your details. You can find your servers IP address on the Server Overview page.If it's the first time, you may be asked to check the fingerprint and the server you are connecting to. Reply "yes" when asked. Because we have logged in to the server as the user running your application, we will be taken automatically to that users home directory where the site should be. You can run ls in your terminal to check list the files and folders available. I entered "filament-app.test" as the domain for the site when creating it so we can see that folder shown below on the server.Change into that directory with the cd command, as shown below. Remember to swap out the domain name for the one you entered.We now need to create the .env file. Laravel ships with an example .env file so we can copy that one with the cp command.Next we want to open that new .env file for editing. For this guide, I'm using nano but use which ever editor you are more comfortable with.Within the .env file, find the block of attributes for the database details and enter the database name, database username and database password you entered when creating the database in an earlier part of this guide. The connection, port and host can be left as the default values.Save the details and close the file editor, now we are ready to run the laravel migrations and create our first user. Run the follow command to run the database migrations and create the needed database tables.Now run the following command to create the first admin filament user.You will be asked to enter a name, email address and password for the user. Once done press enter to save and create your user.Will that, we should now be able to visit your site. Head to your domain (or temprary domain) and add /admin to the end. Our temporary domain was "scenic-spire-3aca605f.serverauth.net" so we have gone to https://scenic-spire-3aca605f.serverauth.net/adminYou should be presented with a login screen, entered the email and password that you just entered to create the filament user. If everything has been successful, you will be logged in and should see a dashboard similar to this.You can now begin developing your application using Filament!When developing, it will be handy to have code automatically pushed to your server. If you head back to the ServerAuth platform and click Sites in the top menu, click manage on your filament app to be taken to the Site Overview page.From here, you can trigger a manual deployment but this isn't great as it would mean having to visit ServerAuth everytime you pushed a commit, instead, we can enable "Auto Deployment". ServerAuth will create a Webhook on your repository that will receive a request everytime you push a commit to your repository. If it's the correct branch that has been pushed, our system will automatically trigger a deployment!To enable it, click Application in the left menu while on the Site overview page. In the main content area you should see a toggle option to turn it on.Now every time you push code to your repository, our systems will automatically deploy it for you! Happy building!Templates let you quickly answer FAQs or store snippets for re-use.        Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.      Hide child comments as well                  Confirm              For further actions, you may consider blocking this person and/or reporting abuse              Clifton Beale - Feb 5                          hub - Feb 1                          Dayvster 🌊 - Feb 24                          Austin Vance - Feb 14            Website Management, Server Management, SSH Access Control and so much more! ServerAuth helps software agencies and development teams manage server access and security and deploy their sites to servers automatically. Now with 1-Click WordPress Setup!      DEV Community — A constructive and inclusive social network for software developers. With you every step of your journey.    Built on Forem — the open source software that powers DEV and other inclusive communities.Made with love and Ruby on Rails. DEV Community © 2016 - 2024.          We're a place where coders share, stay up-to-date and grow their careers.

How to deploy a Filament app. Check the "Enable Temporary Domain" option and our system will create a subdomain within one of our development domains for you to use while your application is in development