Saudi OpenAI Employee's Arrest Revives Fears US Tech Companies Are Hiring Spies
Read more of this story at Slashdot.
Read more of this story at Slashdot.
My person running my local social dance community's website has expressed his desire to hand-off the domain, and the website itself is old and convoluted and cannot be transferred, so I'm building a new one on WordPress, and doing my best to replicate the important functions of the old website. My skilllevel with WordPress is mixed as I've built multiple websites using existing themes and plug-ins before but I'm not fluent in which tools are best for what purpose and it's been a minute since I last did it.
This is a little hard to articulate because I'm not sure what all of the functions are that I need or what the different ways to accomplish the same set of goals are. But on the old website, there was a frontend login and only specific people were given accounts. Once logged in, you could choose the category of event you wanted to post, you'd input time, date, venue etc, you'd get a text-editing window to put event details with basic formatting and a photo, and once published, the info about the event would post under the correct category of event. Most events were recurring so they'd stay visible until the creator or the website admin removed them, but special events would expire when the date had passed. The recurring events could be edited at any time by the users who posted them and some users edit them frequently. The "posting" ability was never used for news or updates, the way a blog post would typically be.
I found UsersWP for the front-end log-in and posting capability but there were a few things I was uncertain about:
Would this allow me to limit *who* could register as a user? It's very important that only known local event organizers specific to this community can use the site to post their events.
Is a "post" the closest equivalent out there for what i've described above for listing and editing the events? Or is there some kind of form submission that would allow the contents to be published without a human having to go add it to the page that could give me more control over what info had to be included (venue, time, date, etc)? Would a form submission still be editable by the users later on?
Can these posts or form submissions be automatically sorted into different categories (ex: dances, classes, special events) with existing filters or is that another plug-in? Similarly, is it possible to set some of the posts to "expire" or no longer be visible past a specified date?
If someone would be up for helping me pick apart the functions I need and which tools accomplish that, I'd really appreciate it!
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.
So long story short I migrated my website form Shopify to Wordpress and then initially it was almost 75 for mobile and 90 for PC.
So naturally i optimized it and no it is 40-60 for mobile and 80 for PC.
Here is what I did:
(My product pages are most bad in this.)
1. I did changed the format of images to webp (using Webp optomizer ) and when I used elementor then it really went down.
2. When I use searched online I almost did all of the things.
3. Using JS and CSS minify only decrease the speed drastically.
4. Using lazy load my speed is also very bad.
5. I used custom php to exclude the hero and other first load images form the lazy load.
6.I did all the cahce setting in litespeed chache and still nothing.
7. My most bad thing is LCP and FCP.
8. I also disabled the fonts which were additional.
I also have a bit more then average CSS and a bit JS in my site.
Can you please hepl me in this regard.
here are some screenshots.
And using VPI and lazy load really cause it to slow.
can someone at least tell me some tool to diganost the problem
EDIT: When we run ads the it's almost a 10sec delay to website Soo also bad
Read more of this story at Slashdot.
I implement CRMs for local businesses. Recently, I built a setup for a US-based clinic, and thought the workflow decisions might be useful to others working with appointment-based businesses.
Before this, the front desk and owner handled most things manually: confirming appointments, checking intake forms, giving aftercare instructions and remembering who was due back. They used Excel for reminders, separate booking, invoicing and newsletter tools, and a personal phone for patient texts.
We spent about five hours across a week mapping their process before building it. Their priorities were fairly straightforward:
One opportunity per appointment, linked to the patient
This was the main structural decision.
A patient can have two upcoming appointments with different confirmation statuses, preparation instructions and follow-up needs. A single patient-level opportunity wouldn’t represent those independently.
Each appointment therefore gets its own opportunity. The main appointment stages are:
The critical stage is the front desk’s action list. Automated messages handle the initial chasing, then staff get notified when a call is needed.
The clinic also treats bookings made within four days of the visit as confirmed. That’s their operating rule rather than explicit confirmation from the patient (an important distinction when interpreting the pipeline).
Booking and intake
Patients book through the website and receive an acknowledgement by email and SMS.
The workflow checks whether they have previously completed the initial intake form. If not, the acknowledgement directs them to it. Known personal details are prefilled so they don’t have to enter them again.
Clinic calls and texts run through a dedicated number rather than the personal phone.
Reminders and escalation
The schedule includes:
These use a mix of email and SMS. For unconfirmed bookings, the four-day message includes a confirmation link that updates the appointment record.
If the appointment reaches the critical stage without confirmation, automated chasing is followed by a front-desk notification if there’s still no response.
Cancellation and rescheduling links are included in the relevant messages, along with the clinic’s cancellation policy.
Six treatment categories determine the communication
The clinic offers multiple treatments. We grouped them into six categories, which control preparation instructions, aftercare and longer-term follow-up wording.
That gave us a manageable number of workflows while keeping messages relevant to what someone actually booked.
The day before the visit:
Attendance without another login
Fifteen minutes after the appointment starts, the provider receives an SMS with a link to record attendance.
This lets them complete a routine action without opening the CRM.
Aftercare and return visits
The setup includes treatment-specific aftercare and a review request, with an internal check for whether a previous review has been recorded.
Longer-term follow-ups are scheduled at two, three and six months. Both the timing and treatment category affect the wording, rather than sending the same “time to book again” message repeatedly.
Treatment and follow-up tags also let the clinic identify relevant groups for future outreach.
The most useful part of the discovery work was deciding which actions needed a person, who owned them, and what information they needed at that moment. Building the automations came after that.
For others using a sales-oriented CRM for repeat appointments: do you use an opportunity per visit, a separate appointment object, or another structure? And what reminder cadence did you find most useful/relevant?
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Hello experts,
we have had an opencart store since 2012, 32k products and database is keep building.
We are thinking of migrating to WP but number of reasons
1 - setup a corporate website for lead generation
2 - setup shop on subdomain
What are your honest thoughts of this move?
Read more of this story at Slashdot.
Read more of this story at Slashdot.
Read more of this story at Slashdot.




One issue with CRM systems that often gets overlooked is how data quality degrades when multiple teams follow different workflows. Sales may update contact details, support may maintain separate case notes, and management may rely on reports built from records that are already outdated.
Over time, these small inconsistencies create bigger problems: duplicate customer profiles, unreliable pipeline forecasts, incomplete interaction histories, and conflicting information across departments.
User adoption is another part of the problem. When the CRM requires more effort than the process it replaces, people tend to maintain parallel spreadsheets or enter only the minimum information required. That creates gaps that become difficult to identify later.
I think CRM reliability depends heavily on clear data ownership, consistent field definitions, and workflows that fit how teams actually operate. Without those foundations, even a well-configured system can produce misleading reports and poor decisions.

Read more of this story at Slashdot.