Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deep dive managed & unmanaged solutions #1714

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Deep dive managed & unmanaged solutions #1714

wants to merge 5 commits into from

Conversation

powerappsviking
Copy link

Category

  • Content fix
  • [x ] New article

Contents of the Pull Request

This is a community article belonging to my blog about Power Apps and enabling citizen developers with tips and tricks to ensure they follow best-practice guidelines as much as possible and avoid pit-falls new developers face.

This post contains information about working with solutions. I would also love to contribute with my other posts about the basics of making model-driven apps in general (a 5-step guide). All of it is of course un-monetized. My main concern is providing as much content to help as possible to make sure everyone creates good apps and solutions.

@LuiseFreese
Copy link
Collaborator

hey there, thank you for contributing. You'll need to reformat the article in proper markdown, so that our site is able to render it correctly. Let me know if you need any help with this.

@powerappsviking
Copy link
Author

powerappsviking commented Jan 25, 2024 via email

@LuiseFreese
Copy link
Collaborator

here is a good article to get you started. Please let me know if you have specific questions, happy to help :-)

https://pnp.github.io/blog/post/what-s-up-with-markdown/

@powerappsviking
Update index.md
5f3164f 
changed format to markdown instead of horrible wordpress-ish html
@powerappsviking
Copy link
Author

powerappsviking commented Feb 4, 2024 via email

@LuiseFreese
Copy link
Collaborator

hey there again and sorry for delay, I've been at conference and traveling. We will need to address 3 things:

  1. links and links to images need to be accessible, which means that in the square brackets [] there should be a description of what we see in the image. like [image of Parker in a blue shirt](/images/parker.png)
  2. the images of your article should be in a subfolder called images and the links should then refer to them
  3. The headings need to make sense. As the title is already handled in the metadata (thats the part in between of the ---) , we start with a heading 2: ## What are solutions. From there on, you can decide, if the following headings are subheadings to the previous heading (then you prefix with ### or shall exist on the same level (then you prefix with ## ). Please avoid unformatted headings or having headings just in bold text - it decreases legibility and accessibility.

@LuiseFreese
Copy link
Collaborator

Do you need help with this @powerappsviking ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@powerappsviking @LuiseFreese