Please add your prompts here.
For the moment I just used:
this is a ejs page with Bootstrap 5 (Cosmo) made with Wappler. Please make the page more appealing and professional.
for now I'm happy with little 
Then it becomes very important to give the name to the various rows, columns etc, so if you need to change something you can refer directly with the name like:
Add an input field in the column "col_newform"
Try:
Create a contact page that includes
- a banner
- important contact information
- a contact form with the following fields
name
email address
phone number
subject
company name
message textbox- a map of Enschede NL with an overlay stating local information
And get:
(I wish I had more thumbs 
)
8 Likes
I wish I would have saved the exact wording I used. But I basically said read the content of the page and then create all the meta tags that I need to rank well in the search engines. It create the standard meta tags, but also created the facebook and twitter(x) tags also. BIG BIG time saver, and very useful.
1 Like
I'm not in need of basic page creation in my project. @ben and @baub have provided great examples and insight. I was having trouble working up to a point and then have to return a few hours (days) later and have github/copilot/chatgpt remember the conversation. So I asked what was the best was to start the ai conversation were I left. The following is the text response I got and at the end is images of the Word doc I created.
Remember: While "As a Wappler expert" is helpful, providing specific context about your versioning system implementation, including key decisions and structures already discussed, is more valuable for maintaining conversation continuity.
This approach ensures efficient communication while maintaining the integrity and consistency of your versioning system implementation.
-
Starting New Sessions
a. Each new chat session starts fresh
b. Previous context is not maintained between sessions
c. Always provide key context points -
Essential Context to Provide
a. Project Identifiers
i. "Continuing our discussion on Wappler versioning system"
ii. "Following up on MariaDB versioning implementation"
iii. Brief mention of previous key decisions
b. Critical Parameters
i. Current timestamp (2025-03-17 22:08:37)
ii. User context (LBDeve)
iii. Environment (Wappler v7, Node.js, MariaDB) -
Efficient Context Restoration
a. Quick Reference Points
i. "Yesterday we discussed [specific topic]"
ii. "We left off at [specific point]"
iii. "We established [key decision]"
b. Topic Anchoring
i. Reference specific components discussed
ii. Mention established structures
iii. Note any decisions made -
Maintaining Consistency
a. Project Parameters
i. Keep referring to same database structure
ii. Maintain consistent naming conventions
iii. Reference established patterns
b. Technical Framework
i. "As a Wappler expert" is helpful but not required if you:
- Reference specific Wappler components
- Mention version (v7)
- Include technology stack
- Effective Follow-up Strategies
a. Summarize Previous Points
i. Brief recap of last discussion
ii. Key decisions made
iii. Outstanding questions
b. Clear Connection
i. Link to previous concepts
ii. Reference established structures
iii. Build on previous decisions - Documentation Reference
a. Keep Notes On
i. Action flow structures
ii. Naming conventions
iii. Implementation decisions
iv. Error handling approaches
b. Reference Points
i. Save important code structures
ii. Keep flow diagrams
iii. Document key decisions
Best Practice Example
*1. Starting New Session
a. "Following up on our Wappler versioning system discussion:
i. Last covered: Transaction rollback structure
ii. Environment: Wappler v7, Node.js, MariaDB
iii. Current timestamp: 2025-03-17 22:08:37
iv. User: LBDeve
v. Key point: [specific detail from last discussion]"
2. Continuing Discussion
a. "Building on our established versioning structure:
i. Using REPEATABLE READ isolation
i. Maintaining transaction integrity
ii. Following our error handling pattern
iii. [New topic or question]"
Key Takeaways
- Context Maintenance
a. New sessions need context restoration
b. Provide key parameters
c. Reference previous decisions - Efficiency Tips
a. Keep notes of key structures
b. Reference specific components
c. Maintain consistent terminology 3. Project Continuity
a. Build on established patterns
b. Reference previous decisions
c. Maintain consistent approach - Communication Strategy
a. Clear references to previous work
b. Specific about implementation details
c. Consistent terminology use
2 Likes
Very good points indeed. As we move on to implement a project wide AI chat agent, we will be definitely supplying many of those context points automatically so that the Wappler AI agent knows exactly about your project and its structure so it can give you great context relative suggestions all in line of your project and enriched with Wappler pro knowledge.
3 Likes
@George This is the single most powerful addition you and the Wappler team have made to the Wappler interface, you're turning what was already an awesome product into a mind blowing best in class tool.
2 Likes
Would there then also be a sitewide 'undo', if you made some sort of sitewide changes could you then revert them. Or would have to go back page by page to revert them?
Yes, this is where git comes in very handy. The AI can commit its changes to git even with AI generated description, and you can undo them if you don’t like them.
But also, when changes are suggested in first place you will have to approve them first before they are made.